Install Jentic One Beta

Connect the BlueCargo to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BlueCargo, 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%2Fbluecargo.io%2Fbluecargo" | 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%2Fbluecargo.io%2Fbluecargo" | 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 BlueCargo API.

Create container bookings and list the ones you have placed

Look up a shipment by its bill of lading

List the carriers you can book with and read one by name

List your shipments and check their state

GET STARTED

Start building with BlueCargo API

Explore with Jentic One

View OpenAPI Document

Shipment status by bill of lading

Track a container by the one identifier everyone shares: its bill of lading. The agent passes the bill of lading to the shipment lookup and reads the shipment's current state, so a logistics workflow can report arrival status without manual portal checks.

Look up a shipment with GET /shipments/{bill_of_lading}

Carrier lookup

Pick the right carrier before placing a booking. The agent lists the carriers available to it and reads one by name to confirm details, so bookings are placed against a valid carrier.

List carriers with GET /carriers, then read one with GET /carriers/{name}

Key Endpoints

7 endpoints — the bluecargo api manages container logistics around bookings, shipments, and carriers.

METHOD

PATH

DESCRIPTION

POST

/bookings

Create a container booking

GET

/bookings

List bookings

POST

/shipments

Create a shipment

GET

/shipments/{bill_of_lading}

Look up a shipment by bill of lading

GET

/carriers

List carriers

GET

/carriers/{name}

Read a carrier by name

POST

/bookings

Create a container booking

GET

/bookings

List bookings

POST

/shipments

Create a shipment

GET

/shipments/{bill_of_lading}

Look up a shipment by bill of lading

GET

/carriers

List carriers

GET

/carriers/{name}

Read a carrier by name

Why Jentic?

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

Setup

Wiring BlueCargo by hand means learning its `X-Api-Key` header auth and its booking, shipment, and carrier shapes keyed by bill of lading. Through Jentic you install once, import BlueCargo from the API Directory, store the key once, and your agent calls it.

Permission scoping

BlueCargo puts the bill of lading in the URL path (/shipments/{bill_of_lading}), so a rule can bound your agent to reading specific shipments. You choose which operations it may call, so creating bookings or shipments stays out unless you add them, letting a read-only agent track freight without placing orders.

Credential isolation

Your BlueCargo key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'look up a shipment by bill of lading' or 'create a container booking', and Jentic returns the matching BlueCargo operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using BlueCargo API through Jentic.

What authentication does the BlueCargo API use?

The BlueCargo API authenticates with an API key sent in the `X-Api-Key` header per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Can I track a shipment by its bill of lading with the BlueCargo API?

Yes. Pass a bill of lading to the shipment lookup and BlueCargo returns that shipment and its current state. You can also list all your shipments or register a new one for tracking.

Can I limit what my agent is allowed to do with the BlueCargo API?

Yes. Write a rule that allows only the shipment and carrier read operations, so your agent can track freight and look up carriers but cannot create bookings or shipments unless you add those operations. BlueCargo carries the bill of lading in the URL path, so reads can be bound to a specific shipment.

What are the rate limits for the BlueCargo API?

The OpenAPI spec does not specify rate limits. Check the BlueCargo documentation at https://bluecargo.io for current limits before polling shipment status frequently.

Is there a BlueCargo MCP server?

You don't need an MCP server to give your agent BlueCargo. Jentic connects it directly from the API Directory: import it, store your key once, and your agent runs the booking, shipment, and carrier operations on demand. That also keeps extra tool definitions out of the agent's context.

How do I look up a shipment by bill of lading with the BlueCargo API through Jentic?

Search Jentic for 'look up a shipment by bill of lading' and it returns the BlueCargo shipment operation with its input schema. Your agent passes the bill of lading and reads back the shipment and its state. To run it on your own infrastructure, install Jentic One from its GitHub repo.

BlueCargo

AI ReadinessFoundational (C+)57/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceShipping LogisticsapiKey7 EndpointsREST

For Agents

Manage container logistics with BlueCargo: create and list bookings, register shipments, look up a shipment by its bill of lading, and list carriers across 7 endpoints.

Use for: Create a container booking with a carrier, Look up a shipment by its bill of lading, List all my current bookings, Register a new shipment for tracking

Not supported: Does not handle customs clearance, freight payments, or warehouse inventory. Use for container bookings, shipments, and carrier lookups only.

The BlueCargo API manages container logistics around bookings, shipments, and carriers. It creates and lists container bookings, registers shipments and lists them, and looks up a shipment by its bill of lading to read its current state. Carriers can be listed and read by name, so an integration can place a booking with the right carrier and follow the container through to arrival.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

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).

100%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

46%

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: FSignals: 4

49%

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.

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: C-Signals: 1

50%

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: C-Signals: 1

50%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the BlueCargo to your agent

Capabilities

Start building with BlueCargo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

BlueCargo

Jentic AI Readiness Score

BlueCargo

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