The 402 rails for AI agents. Live in production.
tools402 is an x402 marketplace where AI agents pay HTTP APIs per call in USDC, on-chain. Buyer payment is live on Base, Polygon, and Solana today. Tier 2 EVM chains (Arbitrum, Optimism, Avalanche) are live as settlement infrastructure (reported by /v1/_health). Wallet-only identity, no KYC, no account. The live catalog (158 endpoints per /v1/_meta), the marketplace logic, and the multi-rail failover router are the core moats. Operated as an independent experimental project — no corporate entity yet.
Built with rigor. Shipped weekly.
Solo operator
Built by a single autodidact developer to scratch a personal itch — autonomous agents that pay for the APIs they use, without a human signing up. The roadmap moves at the pace of one pair of hands; the codebase, the deployment cadence, and the operating decisions all sit in one head for now. Operator identity will be disclosed when a commercial entity is incorporated.
Agents call APIs faster than humans can sign up for them.
The project started from a concrete observation: LangChain and MCP agents being wired up couldn't pay for the APIs they needed without a human sitting at the keyboard filling forms. HTTP 402 is a 30-year-old reserved code. USDC on Base, Polygon or Solana settles in roughly a second. Putting these two together gives you a marketplace where agents can transact without a human.
tools402 is the answer one would want as a buyer (call APIs, get JSON back, pay per call) and as a seller (publish your endpoint, sign once, get paid daily). Wallet-only, no KYC, no platform fees. 3 % paywall, 4 % proxy on the sell-side. That's the only revenue the project generates.
No VCs. Bootstrapped.
tools402 takes no venture funding. No accelerator. No external investor. The runway is the take rate and the buy-side endpoint revenue. The structural choice is deliberate — independence on the roadmap, no obligation to scale into a regulated CASP perimeter, no pressure to extract more than 3 % from sellers.
If that changes, this paragraph will too — and the changelog will record the date.
Thin infrastructure. Boring on purpose.
Every component is open source. Anyone could rebuild the routing layer in a weekend. The moat is the operating discipline (uptime, multi-facilitator failover) and the catalogue volume — not the stack.
The router. Free for everyone.
The piece that keeps tools402 alive during a facilitator outage is a proprietary routing engine — 105 tests, 100 % coverage, battle-tested in production. It is the operational moat.
Three rules I never break.
No KYC. No account. No API key.
Public ledger or it didn't happen.
Solo built. Operational moats.
How to reach me.
One person reads every email. Replies usually within 24 hours.