Solo execution

We are building a logistics rail for the x402 protocol ourselves

Working system, not slideware. Real money stays gated behind counsel, bank, and audit clearances.

Buttons open your mail app — or write directly to alex.carney@nettrux.net with subject “Nettrux x402 rail”.

The moment

Agents are becoming buyers.

Jul 2026

x402 goes institutional

x402 — the open protocol for machine payments over HTTP — became a Linux Foundation standard.

40 members

The x402 Foundation

Founding roster includes Visa, Mastercard, American Express, Stripe, Google, and AWS.

100M+

Payments processed

Through the protocol's reference facilitator — almost entirely micro-transactions (~$0.30 average). Invoice-scale money remains the white space.

One hundred million machine payments show the rail runs at machine speed — at an average of about thirty cents each. Invoice-scale money is the white space, and freight invoices are where we live.

Working system, not slideware

The Agent Factoring Rail ran end-to-end on a test chain.

  1. 01

    An agent negotiates Net-30 terms

    priced, signed, bound to an exact terms hash.

  2. 02

    A factor approves them

    through a seam built for factor networks.

  3. 03

    A named human mints the escrow

    agents cannot — the platform refuses them.

  4. 04

    Delivery evidence verifies

    against stored documents, checksums recomputed.

  5. 05

    Funds release

    citing the verification decision, on an append-only ledger.

In the recorded live run, two freight rails reached RELEASED end-to-end on our production billing engine — once straight through on verified delivery documents, and once through a dispute that a second, separately-empowered person resolved on the record. Then we attacked our own gates:

REFUSED · 401

An agent credential attempted the mint. The surface does not recognize software as an approver.

REFUSED · 400

An evidence bundle with fabricated document checksums — refused before any state changed.

EXACTLY ONCE

The mint was replayed. The engine returned the original recorded result — one approval mints one agreement, ever.

18/18

The escrow contract's full test suite on a live local test chain — including a hard refusal to sign on any real-money chain.

Sandbox disclosure: the recorded run uses a test chain, a valueless test token, a deterministic stand-in factor, and fictional parties. Every state transition, policy decision, and refusal is the real platform engine. No real money exists anywhere in the system today — by design, until the production gates pass.

Honesty as the position

What runs today. What is flagged off.

Runs today

  • The rail lifecycle above, end-to-end, on a test chain with a valueless test token.
  • The refusal gates: agent mint, fabricated evidence, replay — each held in the recorded run.
  • The freight operation underneath: production billing, EDI, a customer portal, live loads.

Flagged off

  • Real-money settlement. No production chain signing. No live facilitator against freight invoices.
  • Anything that would move customer or factor funds. Counsel, bank, and audit clearances come first.

Who is building this

A working freight operation, built in-house.

Nettrux is a California 3PL with production systems live today: a billing engine on production accounting, enterprise shipper billing including EDI, an operating factoring workflow, and a customer portal. The agent rail is built on those systems — we are not starting from a deck. Solo execution as of 2026-08-19: we build the rail ourselves.

Why this one holds

Compliance is the design, not the appendix.

Write if you want the detail.

How the rail is built, what is gated, and why. Subject-only mail — no form.

Talk to us about the rail

No mail app? Write to alex.carney@nettrux.net.

This page describes a working system and a stated build plan. It is not a forecast. Figures describing third-party networks and protocols are as publicly reported or as stated by their principals and have not been independently audited by Nettrux.