Install Jentic One Beta

Connect the Future Fulfilment Direct Injection - v3.1 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Future Fulfilment Direct Injection - v3.1, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Finjection-api.futurefulfilmentsoftware.com%2Ffuture-fulfilment" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Finjection-api.futurefulfilmentsoftware.com%2Ffuture-fulfilment" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Future Fulfilment Direct Injection - v3.1 API.

Retrieve shipping rates for a parcel before booking

Validate a shipment request against carrier rules before creating it

Create a shipment and generate its carrier label

Void a previously created shipment by its id

Manifest one or more shipments for carrier handover

GET STARTED

Start building with Future Fulfilment Direct Injection - v3.1 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Future Fulfilment Direct Injection - v3.1 API for, with concrete tasks.

★ AI Agent Shipment Booking

An AI agent connected through Jentic books outbound parcels end to end: it fetches a rate, validates the shipment request, creates the shipment, and retrieves the label ready to print. Because the agent calls each operation directly, order-management systems can trigger fulfilment without a human stepping through the carrier portal.

Fetch a rate for a 2 kg parcel, validate and create the shipment, and retrieve its label

Rate Shopping Before Fulfilment

Before committing a booking, a merchant's system queries the rate operation to price a parcel and decide whether to ship. Validation then confirms the shipment request is acceptable, so the create call rarely fails for avoidable reasons.

Request a rate for a parcel to a Sydney postcode and validate the shipment request before creating it

End-of-Day Manifesting

At the close of fulfilment, the manifest operation groups the shipments created during the day into a single carrier handover document. This closes out bookings in one call rather than per parcel.

Manifest all shipments created today so they are ready for carrier pickup

Key Endpoints

6 endpoints — the future fulfilment direct injection api books and manages parcel shipments for fulfilment in australia.

METHOD

PATH

DESCRIPTION

GET

/rates

Get a shipping rate for a parcel

POST

/shipments/validate

Validate a shipment request

POST

/shipments/create

Create a shipment and its label

GET

/labels/{shipmentId}

Get a shipment label

POST

/shipments/{shipmentId}/void

Void a shipment

POST

/manifests/create

Manifest shipments for handover

GET

/rates

Get a shipping rate for a parcel

POST

/shipments/validate

Validate a shipment request

POST

/shipments/create

Create a shipment and its label

GET

/labels/{shipmentId}

Get a shipment label

POST

/shipments/{shipmentId}/void

Void a shipment

POST

/manifests/create

Manifest shipments for handover

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Future Fulfilment Direct Injection API by hand means setting up HTTP Basic authentication, attaching your account number header to every call, and sequencing validation before create yourself. Through Jentic you install once, import it from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The API carries shipment details in the request body, so rules bound which operations your agent may call, not which shipments it can touch. You choose the operations it may use, such as fetching rates and creating shipments, so voiding a booking is not included unless you add it.

Credential isolation

Your Future Fulfilment account number and Basic auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get a shipping rate' or 'create a shipment', and Jentic returns the matching Future Fulfilment operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Future Fulfilment Direct Injection - v3.1 API through Jentic.

What authentication does the Future Fulfilment Direct Injection API use?

It uses HTTP Basic authentication and also requires your account number in the `accountNumber` request header, as declared in its OpenAPI spec. Both are sent on each request. Through Jentic these credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never appear in the agent's prompt or logs.

Can I get a shipping rate before creating a shipment with this API?

Yes. The rate operation returns pricing for a parcel, and you can validate the shipment request first and then create the shipment and its label once you are ready to book.

What are the rate limits for the Future Fulfilment Direct Injection API?

The OpenAPI spec does not specify rate limits for the Future Fulfilment Direct Injection API. Check the limits documented in your Future Fulfilment account before scaling automated bookings.

Can I limit what my agent is allowed to do with the Future Fulfilment Direct Injection API?

Yes. Write a rule that allows only the rate-lookup and shipment-create operations, so the agent can quote and book shipments but cannot void them, and every call it makes is logged. Voiding and manifesting stay out of reach until you add them to the rule.

How do I create a shipment with this API through Jentic?

Search Jentic for 'create a shipment', add the Future Fulfilment Direct Injection API from the directory, and store your Basic credentials and account number once. Your agent then validates the request, creates the shipment, and retrieves the label. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Future Fulfilment Direct Injection API MCP server?

You don't need an MCP server to give your agent the Future Fulfilment Direct Injection API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent calls the rate, shipment, label, and manifest operations. That keeps extra tool definitions out of the agent's context.

Injection Api Futurefulfilmentsoftware Future Fulfilment Direct Injection - v3.1

AI ReadinessAI-Aware (B)63/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceShipping Logisticsbasic, apiKey6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Get shipping rates, validate and create parcel shipments, retrieve labels, void bookings, and manifest parcels for Australian fulfilment.

Use for: Get a shipping rate for a parcel to an Australian address, Create a shipment and generate the label, I want to validate a shipment before booking it, Void a shipment I created by mistake

Not supported: Does not handle order management, inventory, or payment collection. Use for parcel shipment creation and label generation only.

The Future Fulfilment Direct Injection API books and manages parcel shipments for fulfilment in Australia. It returns shipping rates, validates a shipment request against carrier rules, creates shipments with their labels, voids bookings, and manifests parcels for carrier handover. Each request carries the sender's account number so bookings are attributed to the right fulfilment account.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A+Signals: 4

90%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C+Signals: 4

45%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

85%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

30%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

73%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Future Fulfilment Direct Injection - v3.1 to your agent

Capabilities

Start building with Future Fulfilment Direct Injection - v3.1 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Injection Api Futurefulfilmentsoftware Future Fulfilment Direct Injection - v3.1

Jentic AI Readiness Score

Future Fulfilment Direct Injection - v3.1

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness