Install Jentic One Beta

Connect the TM-Shippers: Spot Market API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TM-Shippers: Spot Market API, 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%2Fe2open.com%2Fe2open-tms" | 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%2Fe2open.com%2Fe2open-tms" | 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 TM-Shippers: Spot Market API.

Search the Spot Market for available truckload loads by query

Retrieve a load's details, supported charge codes, and allowed rate bases

Create a basic, detailed, or contract offer on a load

Update or withdraw an existing offer on a load

Review the full offer history for a load

GET STARTED

Start building with TM-Shippers: Spot Market API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use TM-Shippers: Spot Market API for, with concrete tasks.

★ AI Agent Freight Bidding

Let an AI agent find and bid on truckload freight on behalf of a carrier: it searches the Spot Market for loads on a lane, retrieves a load's supported charge codes and allowed rate bases, and submits a detailed offer. Through Jentic the agent discovers the right E2open operation by intent and calls it with the load id, so bidding runs without a developer wiring the search-and-offer flow by hand.

Search the Spot Market for truckload loads on a lane, retrieve a load's charge codes, then create a detailed offer on it

Offer Management

Carriers adjust their bids as market rates move and pull offers that no longer make sense. The API reviews the full offer history for a load, updates the current offer's charges, and withdraws it entirely. This keeps a carrier's active bids current without re-posting from scratch.

Retrieve the offer history for a load, update your current offer's rate, then withdraw it if the load is no longer viable

Counteroffer Handling

When a shipper counters a carrier's bid, the carrier responds to keep the negotiation moving. The API fetches the current offer details for a load and updates the status of the counteroffer to accept or reject it. This lets an agent close a freight negotiation that would otherwise sit in a portal.

Fetch the current offer details for a load, then update the status of the shipper's counteroffer to accept it

Key Endpoints

10 endpoints — the e2open tm-shippers spot market api lets carriers find truckload freight postings and bid on them.

METHOD

PATH

DESCRIPTION

GET

Search Spot Market loads by query

GET

/load/{loadID}/

Get a specific load

POST

/load/{loadID}/offer/

Create an offer on a load

GET

/load/{loadID}/offer/

Get the offer history for a load

PUT

/load/{loadID}/offer/{offerID}

Update an offer on a load

DELETE

/load/{loadID}/offer/{offerID}

Withdraw an offer from a load

PUT

/load/{loadID}/counteroffer/{offerID}

Update the status of a counteroffer

GET

/load/{loadID}/chargecodes

Get supported charge codes for a load

GET

Search Spot Market loads by query

GET

/load/{loadID}/

Get a specific load

POST

/load/{loadID}/offer/

Create an offer on a load

GET

/load/{loadID}/offer/

Get the offer history for a load

PUT

/load/{loadID}/offer/{offerID}

Update an offer on a load

DELETE

/load/{loadID}/offer/{offerID}

Withdraw an offer from a load

PUT

/load/{loadID}/counteroffer/{offerID}

Update the status of a counteroffer

GET

/load/{loadID}/chargecodes

Get supported charge codes for a load

Why Jentic?

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

Setup

Wiring the E2open Spot Market API by hand means handling its basic authentication, picking the right North American or European regional host, and learning its charge-code and rate-basis model per load. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.

Permission scoping

E2open puts the load id and offer id in the URL path (/load/{loadID}/offer/{offerID}), so a rule can pin your agent to specific loads and the operations you pick. You choose the operations it may call, so searching loads and creating offers can be allowed while withdrawing an offer or answering counteroffers are not included unless you add them.

Credential isolation

Your E2open 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 'find truckload loads' or 'make a freight offer', and Jentic returns the matching E2open operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using TM-Shippers: Spot Market API through Jentic.

What authentication does the E2open Spot Market API use?

The E2open TM-Shippers Spot Market API authenticates with HTTP basic authentication per its OpenAPI spec, so each request carries your username and password. Through Jentic those credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never enter the agent's context.

Can I submit offers on truckload loads with the E2open Spot Market API?

Yes. The create-offer operation submits a basic, detailed, or contract offer on a specific load, where a basic offer carries a single total charge and a detailed offer breaks charges out by code. You can then update, withdraw, or review the history of your offers on that load.

Does the E2open Spot Market API have regional endpoints?

Yes. The API serves separate North American hosts (na-api.tms.e2open.com) and European hosts (tms.eu.e2open.com), along with colour-coded sandbox hosts for testing. Send requests to the host that matches your account's region so loads and offers resolve correctly.

Is there an E2open Spot Market MCP server?

You don't need an MCP server to give your agent the E2open Spot Market API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent calls operations like searching loads or creating an offer. 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 E2open Spot Market API?

Yes. Write a rule that allows only load search and offer creation, so the agent can find loads and bid but cannot withdraw offers or answer counteroffers. Because E2open addresses loads and offers by id in the URL path, a rule can also pin the agent to specific loads, and every call is logged.

How do I bid on a load with the E2open Spot Market API through Jentic?

Search Jentic for 'search spot market truckload loads' to find the search operation, retrieve a load's charge codes and rate bases, then create an offer on it. To run it on your own infrastructure, install Jentic One from its GitHub repo.

E2open TM-Shippers: Spot Market API

AI ReadinessNon-Ready (F)29/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceShipping Logisticsbasic10 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Search Spot Market truckload postings, create basic, detailed, or contract offers on a load, and update, withdraw, or counter offers. Covers 10 operations for carriers bidding on freight.

Use for: Search the Spot Market for available truckload loads, Get the details of a specific load, Create an offer on a load, Update my existing offer on a load

Not supported: Does not handle shipment tracking, label generation, or less-than-truckload freight. Use for Truckload Spot Market load search and offers only.

The E2open TM-Shippers Spot Market API lets carriers find truckload freight postings and bid on them. Agents can search the Spot Market for available loads, retrieve a load's details along with its supported charge codes and allowed rate bases, and submit basic, detailed, or contract offers. Existing offers can be updated or withdrawn, the full offer history reviewed, and counteroffers answered by updating their status. The API covers Truckload loads only and serves separate North American and European regional hosts.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

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

12%

Example Density

How richly the API is illustrated with examples.

95%

Example Validity

Percentage of examples that conform to their schemas.

78%

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

38%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

32%

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

10%

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

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the TM-Shippers: Spot Market API to your agent

Capabilities

Start building with TM-Shippers: Spot Market API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

E2open TM-Shippers: Spot Market API

Jentic AI Readiness Score

TM-Shippers: Spot Market API

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