Agent-to-agent shipping: how a shipper's AI books freight on x402

Agent-to-agent shipping sounds like a demo until you put a pallet on a dock. Then it becomes a liability problem. Nettrux is building that product as the first 3PL on x402: a California freight broker and forwarder where a shipper's AI agent quotes a lane on the freight API and commits it through the x402 handshake, while a named human still approves every mint.

This article is the plain-language version of that story — what agent-to-agent shipping means in freight, what Nettrux has live today, and what is still honestly in build.

What "agent-to-agent" means here

Two software agents talk to each other over HTTP. On the shipper side, an ops or procurement agent decides a lane needs to move. On the Nettrux side, the freight API answers with ranked options, a price-locked quote, and — when the agent is ready to commit — an x402 challenge whose payment terms ride in the HTTP 402 response.

That is the product direction on nettrux.ai: agents quote a lane on the freight API and commit it through the x402 handshake. Payment terms are the HTTP 402 challenge.

It is not "an unsupervised wallet books a truck." Freight fails the usual agentic-commerce assumptions on purpose. Stakes are high. Identity is hard. Settlement is messy. So Nettrux's public rule stays the same: agents negotiate; humans approve everything that moves money or leaves the building; software is not an approver on this rail.

Why freight is a useful hard case for x402

x402 is an open HTTP payment protocol. A server can answer 402 Payment Required with machine-readable terms, and a client that already speaks HTTP can pay and retry. Early x402 services mostly sell digital goods — API calls, data, compute. Those purchases are cheap, reversible, and low-identity.

A freight booking is none of those things:

1. A bad book is an expensive mistake.
2. No HTTP standard proves which company a stranger agent works for, or whether that company will pay a multi-thousand-dollar freight bill.
3. Freight is often paid on terms, audited against EDI invoices, and sometimes financed — not a single micropayment for a JSON blob.

So a 3PL on x402 is not "paste a stablecoin address onto a tender." It is a brokerage that designs shop → propose → human-approve → settle so the agent can do the tedious work without getting the keys to the building.

The flow we are building

Documented on the agent guide and in the freight API OpenAPI:

1. Discover. Fetch https://www.nettrux.ai/.well-known/x402. Today that URL is a pointer to the freight API host. The on-origin resources array is empty while the discovery publish switch is off.
2. Rate-shop. Authenticated POST /v1/rates/shop returns ranked options.
3. Price-lock. Authenticated POST /v1/quotes creates the quote id the commit route needs.
4. Commit via x402. Authenticated POST /v1/immediate-bookings/commit with { "quote_id": "..." } and no X-PAYMENT header is documented as the x402 v1 402 challenge. A retry with the payment header is documented as verify, then settle, then book.

Bearer tokens are required. This site does not issue them and does not describe self-serve signup. Guest checkout routes exist in the OpenAPI and stay flagged off.

What is live today (honest)

For shippers, no agent required:

• Multi-carrier LTL rates, full truckload, and air quoting and booking on the Nettrux portal
• A shareable per-load tracking link customers can open with no login
• BOL, POD, invoice, and rate confirmation kept on the load
• EDI-native operations (X12 204, 210, 214) and QuickBooks-oriented invoicing for enterprise books

Ocean is labeled In build.

For agents, discoverable today:

• Discovery pointer at nettrux.ai/.well-known/x402
• Agent guide at nettrux.ai/agents
• OpenAPI at nettrux-edge.fly.dev/openapi.json

Still flagged off (baked into the public deploy gates):

• EDGE_X402_DISCOVERY_PUBLISHED — false
• X402_REAL_MONEY_SETTLEMENT_LIVE — false
• GUEST_X402_CHECKOUT_ENABLED — false

Nettrux has settled a real x402 USDC payment on Base in testing. That is not the same as a public pay-and-book endpoint or open production settlement. We say that plainly because agent builders deserve the truth more than a hype line.

Why we still keep a human on every mint

The homepage line is deliberate: operators built it; AI runs the routine; humans approve everything that moves money or leaves the building.

That guardrail is the product. An agent that can shop fifty lanes in a minute is valuable. An agent that can mint a spend alone is a compliance and credit problem the HTTP stack cannot solve. Putting the human on the mint — not on the shopping — is how agent-to-agent shipping becomes something a desk will actually turn on.

Who this is for

• Agent builders who want freight as a real purchase type, not a toy SKU
• Ops and procurement teams at AI-native companies who will eventually let software shop lanes
• Shippers who just need LTL or FTL moved in California and beyond, with tracking and documents that do not live in email

If you are in the first two groups, email [e-mail] and say what you are building. If you are in the third, start a quote at nettrux.ai.

FAQ

Can my agent book a truck today with no human?

Not via a public self-serve agent API. Humans still book through the Nettrux portal and desk. The public agent pay-and-book surface is in build. The authenticated commit handshake is documented; the discovery, real-money settlement, and guest checkout switches are off.

Does "first 3PL on x402" mean Nettrux is the only logistics company touching x402?

No. There are x402 APIs that sell logistics data. The claim is about a 3PL with a native x402 transaction surface for the move itself.

What modes are live?

LTL, FTL, and air are labeled Live on the portal. Ocean is In build.

Questions: [e-mail]. Quotes and booking: nettrux.ai.

Alex Carney, Nettrux