Install Jentic One Beta

Connect the Just Trade to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Just Trade, 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%2Fjust-trade.co.uk%2Fjust-trade" | 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%2Fjust-trade.co.uk%2Fjust-trade" | 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 Just Trade API.

Create a standard export, CMR, DGN, or IATA DGN transaction with a transaction_ref, document_type, and data block

Allocate a transaction's invoice items into pallets with the packings operation

Generate a transaction's trade documents, such as a commercial_invoice, packing list, cmr, eur1, cargo_label, or certificate_of_shipment

Save dangerous goods templates with un_no, class, subsidiary_risk, and packing_group for reuse across DGN declarations

GET STARTED

Start building with Just Trade API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Just Trade API for, with concrete tasks.

★ Agent-Prepared Export Paperwork via Jentic

An AI agent at a freight forwarder creates a standard export transaction from an order's details, allocates the items into pallets, and generates the commercial invoice, packing list, and certificate of shipment in one call. Through Jentic the agent discovers each operation by intent and calls it with the session token your own instance holds, so a coordinator reviews finished documents instead of typing them.

Create a standard export transaction with transaction_ref 'EXP-2026-118' and document_type 'invoice', allocate its items into two pallets, then generate the commercial_invoice and packing documents

Dangerous Goods Declarations

Shippers of hazardous cargo keep a dangerous goods template per product with its un_no, class, subsidiary_risk, packing_group, and IATA description, then create a DGN or IATA DGN transaction that uses it. Reusing the template keeps the hazard details identical on every declaration.

Create a dangerous goods template with un_no '1263', class '3', and packing_group 'III', then create an IATA DGN transaction for the shipment and generate its documents

Road Freight CMR Notes

Hauliers and exporters moving goods by road create a CMR transaction with the consignment data and generate the CMR document alongside the invoice and delivery note. Custom statuses such as loaded, in transit, and delivered track each consignment.

Create a CMR transaction for a road shipment, generate its cmr and delivery_note documents, and update it to the 'In transit' custom status

Key Endpoints

30 endpoints — the just trade api creates export shipment transactions and generates the trade documents that go with them.

METHOD

PATH

DESCRIPTION

POST

/api/login

POST

/api/transaction/standard

Create a standard export transaction

POST

/api/transaction/cmr

Create a CMR transaction

POST

/api/transaction/dgn

Create a DGN transaction

POST

/api/transaction/{transactionId}/packings

Allocate items into pallets

POST

/api/documents/generate

Generate transaction documents

GET

/api/transaction/{transactionId}

Get a transaction by id

POST

/api/templates/dg

Create a dangerous goods template

POST

/api/login

POST

/api/transaction/standard

Create a standard export transaction

POST

/api/transaction/cmr

Create a CMR transaction

POST

/api/transaction/dgn

Create a DGN transaction

POST

/api/transaction/{transactionId}/packings

Allocate items into pallets

POST

/api/documents/generate

Generate transaction documents

GET

/api/transaction/{transactionId}

Get a transaction by id

POST

/api/templates/dg

Create a dangerous goods template

Why Jentic?

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

Setup

Wiring Just Trade by hand means logging in with email and password to obtain a JWT, sending it as a bearer token, and learning a separate request shape for each transaction type and document flag. Through Jentic you install once, import Just Trade from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Just Trade puts the transaction id and template id in the URL path (/api/transaction/{transactionId}, /api/templates/dg/{templateId}), so a rule can pin your agent to one shipment or template and the operations you pick. You choose the operations it may call, so destructive ones like deleting a transaction or a dangerous goods template are not included unless you add them.

Credential isolation

Your Just Trade credential 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 'generate a commercial invoice' or 'create a CMR consignment', and Jentic returns the matching Just Trade operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Just Trade API through Jentic.

What authentication does the Just Trade API use?

The Just Trade API authenticates with a JWT bearer token in the Authorization header, per its OpenAPI spec. You obtain the token from POST /api/login with your email and password; registration, email verification, and password reset are separate operations under /api. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time.

Is there a Just Trade MCP server?

You don't need an MCP server to give your agent Just Trade. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent creates transactions and generates documents as it needs to. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

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

Yes. For example, write a rule that allows only the transaction read, document list, and document generate operations, so a paperwork agent can produce invoices and packing lists for existing shipments but cannot create, change, or delete transactions. Because the transaction id sits in the path, a rule on /api/transaction/{transactionId} can also hold an agent to one shipment, and every call is logged.

Which documents can the Just Trade API generate?

Per its OpenAPI spec, the document generation operation takes a transaction id and flags for each document wanted, including proforma_invoice, commercial_invoice, packing, cmr, eur1, cargo_label, delivery_note, certificate_of_shipment, quotation, and purchase_order, among others.

What are the rate limits for the Just Trade API?

The Just Trade OpenAPI spec does not specify rate limits. Check with Just Trade at https://just-trade.co.uk for current limits.

How do I generate export documents with the Just Trade API through Jentic?

Search Jentic for an intent like 'generate a commercial invoice for an export', import Just Trade from the API Directory, and store your login once. Your agent then creates the shipment with POST /api/transaction/standard and calls POST /api/documents/generate with the transaction id and the documents it needs. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Just Trade

AI ReadinessAI-Aware (B)63/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceShipping Logisticsbearer30 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create export, CMR, DGN, and IATA dangerous goods transactions, allocate items to pallets, and generate trade documents such as commercial invoices, packing lists, CMR notes, and EUR1 certificates. Includes dangerous goods templates and custom statuses.

Use for: I need to create a CMR consignment for a truck shipment to Poland, Generate the commercial invoice and packing list for transaction 482, Allocate the invoice items for this export into three pallets, Create a dangerous goods template for UN1263 paint

Not supported: Does not handle carrier booking, label purchase, or customs duty calculation. Use for creating export transactions and generating their trade documents only.

The Just Trade API creates export shipment transactions and generates the trade documents that go with them. A transaction can be a standard export, a CMR road consignment, a dangerous goods note (DGN), or an IATA dangerous goods declaration, each carrying a document_type and its data, and invoice items can be allocated into pallets as packings. From a transaction it generates documents such as proforma and commercial invoices, packing lists, CMR notes, EUR1 certificates, cargo labels, delivery notes, and certificates of shipment. Reusable dangerous goods templates hold UN numbers, hazard class, subsidiary risk, and packing group, and custom transaction statuses track each shipment's progress.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

95%

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

30%

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

55%

Example Density

How richly the API is illustrated with examples.

90%

Example Validity

Percentage of examples that conform to their schemas.

26%

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

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.

60%

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

75%

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

60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Just Trade to your agent

Capabilities

Start building with Just Trade API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Just Trade

Jentic AI Readiness Score

Just Trade

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