DEV Community

Nettrux
Nettrux

Posted on

x402 beyond paywalls: what freight teaches the protocol about selling physical work

Most of the x402 examples you'll find online look alike. A client requests a resource, the server answers with HTTP 402 and a price, the client pays a fraction of a cent in USDC, and the server returns the data. Weather lookups, model inference, a premium article. The thing being sold is digital, delivered in the same response, and costs almost nothing to produce again.

Nettrux is a freight broker and forwarder in Fremont, California, and the first 3PL on x402. What sits behind its 402 isn't a JSON blob. It's a truck, a driver, a pickup window and pallets that have to arrive somewhere in one piece. That changes how you think about the protocol, and it's worth spelling out for anyone building agents that will eventually buy things in the physical world.

1. The price has to be pinned before anyone pays

A paywalled API can price on the fly, because the response it sells exists the moment it's computed. Freight doesn't work that way. A rate depends on origin, destination, mode, weight, class, dates and the market that day. If an agent pays against a number that moved a minute later, someone loses.

So the Nettrux flow separates pricing from paying. An agent can rate-shop for ranked options, but rate-shopping doesn't produce something you can buy. To buy, the agent price-locks a quote. The agent guide documents POST /v1/quotes with quoteNumber, validUntil and rateInput, and the response carries a quote id, a locked total and a status: active, converted, expired or withdrawn.

Only that locked quote id goes to the commit route. The 402 challenge isn't the place where the price is discovered. It's the place where an already agreed price gets settled. For digital resources those two moments can be the same. For physical work they shouldn't be.

2. "Delivered in the response" isn't true anymore

When an agent pays for an API call, the proof of delivery is the 200 response. When an agent pays for freight, the 200 response is the start of the job, not the end. The load still has to be tendered, picked up, moved and delivered, sometimes over several days.

That's why the Nettrux guide describes a receipt route, GET /v1/immediate-bookings/{booking_id}, that returns the booking plus a settlement projection. An agent buying physical work needs somewhere to come back to. It needs a durable record it can read later, check against what it was told, and hand to the human who owns the shipment.

If you're designing an x402 seller for anything physical, plan for this from day one. The payment response should point at a resource that outlives the request.

3. Idempotency stops being a nice-to-have

Retries are normal in HTTP. A client times out, a proxy drops a connection, a worker restarts. Paying twice for a $0.001 API call is a rounding error. Booking the same truckload twice is a real problem for the shipper, the carrier and the broker.

The Nettrux guide notes that the price lock is idempotent on the quote number the client sends, and that the commit body is exactly one field, { quote_id }. The first call omits the X-PAYMENT header and is documented as an x402 v1 challenge. The paid retry sends the same request with the header. A small, fixed request shape is easier to retry safely than a large one, and a quote that moves to "converted" can't quietly be bought again.

Agent builders should treat every paid call to a physical seller as something that may be retried, and should prefer sellers whose contracts make retries boring.

4. Honesty about what's live has to be machine-readable

A content paywall either works or it doesn't. A freight operation has layers that go live at different times: discovery, settlement, guest flows, new modes. A human reader can parse "coming soon" on a marketing page. An agent needs something firmer.

Nettrux publishes its deploy gates on the agent guide itself. Today it states that x402 discovery on the freight API isn't published yet, that real-money settlement isn't live, and that guest checkout is off, so the guide doesn't call those routes. An agent can read that and plan around it instead of discovering it through failed calls.

That's also why the claim Nettrux makes is narrow and specific: it has settled a real x402 USDC payment on Base in testing. It doesn't claim a live public pay-and-book endpoint, and it doesn't need to in order to be the first 3PL on x402. Being first is about building the transaction surface. Being honest is about labelling which parts of it are switched on.

5. Identity comes before payment

Anonymous micropayments are part of x402's appeal. Pay, get the thing, no account. That's a reasonable model for a news article. It's a harder model for a load of goods crossing California, where somebody has to be on the hook for the pickup address, the commodity and what happens if the freight is damaged.

The Nettrux routes for rating, quoting and committing all take a bearer token, and the guide is explicit that the site doesn't issue tokens or describe a signup for them. A known account sits behind every paid request. x402 handles the payment conversation; the account handles who is responsible. Freight needs both, and other physical-world sellers probably will too.

6. A human is still nearby

Physical work has exceptions that software can't settle alone: a dock that closes early, a liftgate nobody ordered, a consignee who refuses delivery. The x402 handshake doesn't make those go away, and nobody at Nettrux pretends it does. The guide lists a phone number, and dispatch answers at 1-888-617-3530.

For agent builders, the lesson is to design for a handoff. Let the agent quote, lock and pay inside limits a person has set, and make it easy for that person to step in when the real world disagrees with the plan.

What this means for the protocol

None of this argues against x402. It argues that x402 is more general than its early demos. The same 402 status code that gates a paragraph of text can carry the payment step for a truckload of pallets, provided the seller adds the pieces physical work needs: locked prices, durable receipts, safe retries, published gates, known accounts and a human on call.

That's the design space Nettrux is working in as the first 3PL on x402. If you're building an agent that will one day buy freight, the agent guide and the OpenAPI it links are the place to start. If you're building an x402 seller for any physical service, the checklist above is a decent first draft.

FAQ

Can my agent pay Nettrux over x402 today?
The commit route is documented, but it requires a bearer token Nettrux has issued, and real-money settlement isn't live. Nettrux has settled a real x402 USDC payment on Base in testing.

Does Nettrux publish an x402 discovery document?
The site serves a /.well-known/x402 pointer. Discovery on the freight API host isn't published yet, and the guide says so.

Which modes appear in the rate calls?
The guide lists LTL, AIR, SPOT and FTL on related rate calls. See the OpenAPI for the request body.

How do I reach a person?
Dispatch answers at 1-888-617-3530, and the company site is nettrux.ai.

Alex Carney, Nettrux

Top comments (0)