DEV Community: Nettrux

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

Nettrux — Mon, 09 Nov 2026 21:10:31 +0000

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:

A bad book is an expensive mistake.
No HTTP standard proves which company a stranger agent works for, or whether that company will pay a multi-thousand-dollar freight bill.
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:

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.
Rate-shop. Authenticated POST /v1/rates/shop returns ranked options.
Price-lock. Authenticated POST /v1/quotes creates the quote id the commit route needs.
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 dispatch@nettrux.net 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: dispatch@nettrux.net. Quotes and booking: nettrux.ai.

Alex Carney, Nettrux

Why Nettrux is the first 3PL on x402

Nettrux — Mon, 09 Nov 2026 20:20:46 +0000

Nettrux is the first 3PL on x402: a California freight broker and forwarder building a native x402 transaction surface so software agents can shop a freight lane the way a shipping manager would, while a named human still approves every mint.

That sentence is the positioning. This article is the explanation — what "first 3PL on x402" does and does not mean, which parts of Nettrux are live for shippers today, and which parts of the agent rail are still in build.

What x402 is, in freight terms

x402 is an open HTTP payment protocol: a server can answer 402 Payment Required with machine-readable payment terms, and a client that already speaks HTTP can pay and retry. Most early x402 services sell digital goods — API calls, data, compute. Freight is different. A pallet that leaves a dock cannot be refunded with a click. Carriers need to get paid. Someone has to be accountable for the load.

So a 3PL on x402 is not "put a stablecoin wallet on a tender and hope." It is a freight brokerage that designs the shop → propose → human-approve → settle path so an agent can do the tedious work without getting the keys to the building.

What "first 3PL on x402" means

It means Nettrux is building a native x402 transaction surface for the move itself — not only for shipping data such as container charges or authority checks.

It does not mean:

That a public pay-and-book agent endpoint is live today. It is not. Nettrux now publishes a discovery pointer at nettrux.ai/.well-known/x402 and an agent guide, but the published resource list is still empty and the discovery, real-money settlement and guest checkout switches are all off.
That real-money settlement is open to the public. We're building the public rail; production money movement stays flagged off until compliance clearances pass. Nettrux has settled a real x402 USDC payment on Base in testing — that is not the same as a public endpoint.
That ocean is live. Ocean is labeled In build. LTL, FTL, and air quoting and booking are labeled Live on the Nettrux portal.

What shippers can use today without any agent

Independent of the agent rail, Nettrux already runs as a California 3PL:

Multi-carrier LTL rates across a 131-carrier rating directory, cheapest to fastest with transit days
Full truckload and air on the same desk
A shareable per-load tracking link customers can open with no login
BOL, POD, invoice, and rate confirmation kept on the load
EDI 204 / 210 / 214 and QuickBooks-oriented invoicing for enterprise books

Those are the boring, necessary surfaces. The x402 work sits on top of them, not instead of them.

Why a 3PL is a hard but useful x402 test

Agentic commerce demos often pick products that are cheap, digital, and reversible. Freight fails all three tests on purpose:

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

That is why Nettrux's public copy keeps repeating the same guardrail: agents negotiate; humans approve every mint; software is not an approver on this rail.

The honest roadmap line

The homepage describes the position Nettrux is building: agents quote a lane on the freight API and commit it through the x402 handshake, with the payment terms carried in the HTTP 402 challenge. The site's llms.txt lists the deploy switches in plain text, and today all three are off.

Until the discovery document lists payable resources and those switches are on, treat every agent-payment demo you see elsewhere as someone else's surface, not Nettrux's public rail. Edge's booking commit is designed around an x402 402 challenge for authenticated agents; that is not public or open. Nettrux's public product today is the portal, the tracking link, the documents on the load, and the brokerage desk. The x402 surface is the direction of the platform — we're building it, and we have settled a real x402 USDC payment on Base in testing.

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 dispatch@nettrux.net and say what you are building. If you are in the third, start a quote at nettrux.ai.

FAQ

Is Nettrux's public x402 endpoint live?

Not yet. As of Nov 9, nettrux.ai/.well-known/x402 is a discovery pointer to the freight API, but its resource list is empty and discovery, real-money settlement and guest checkout are all switched off. The freight API documents an x402 402 challenge on authenticated booking commit; that is not a public surface yet. Agent builders can read the agent guide now.

Can my agent book a truck today without talking to anyone?

Not via a public self-serve agent API. Humans still book through the Nettrux portal and desk. The agent lane is in build.

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. Ocean is In build.

Questions: dispatch@nettrux.net. Quotes and booking: nettrux.ai.

Alex Carney, Nettrux