The x402 Settlement Layer: How Machine-to-Machine Payments Actually Work on Base
For three decades, the internet has had no native way to charge per request. Subscriptions, API keys, and credit-card checkout all assume a human is in the loop. The x402 protocol removes that assumption. Named after HTTP status code 402 ("Payment Required"), it lets one machine send a payment and receive data in the same round trip — no account, no checkout, no approval queue.
The problem x402 solves
Every AI agent that wants to buy data, compute, or a service today hits the same wall: it cannot swipe a card. Stablecoins changed this. An agent that holds USDC in a wallet can sign a payment as naturally as a browser sends a cookie. x402 is the convention that turns "I'll pay you" into a single HTTP header.
How a paid request flows
- The agent calls a resource. The server replies
402 Payment Requiredwith a price and a settlement address. - The agent's wallet signs a USDC transfer on the settlement chain (Base, by default).
- The agent retries the request, attaching the signed payment proof.
- The server verifies on-chain and returns the full response.
The whole exchange settles in about two seconds. The facilitator — Coinbase's x402 reference implementation — charges no fee, so the agent pays exactly the listed price.
Why Base, and why USDC
Base is Coinbase's Layer-2 on Ethereum. Its transaction fees are fractions of a cent, which makes micro-payments of a few cents economically sane. USDC is the settlement token because it is a regulated, dollar-pegged stablecoin: the worker receives dollars, not a volatile token that could drop 20% before payout.
What this unlocks
x402 is not a feature; it is infrastructure for a machine economy. Agents can now:
- Pay per call for market data, scraped pages, or verification services.
- Sell their own capabilities the same way — expose an endpoint, set a price, collect USDC.
- Compose: an agent pays a sub-agent to do part of a job, automatically.
The Linux Foundation launched the x402 Foundation in 2026 to standardize the protocol across AI agents and applications, signaling that this is becoming a shared standard rather than a single vendor's product.
The honest limits
x402 is early. Most paying traffic today is agent-to-agent, not human-to-agent. Discovery is fragmented across marketplaces. And the scarce resource is trust: buyers need proof a machine will finish what it starts. But the rail itself works, and it works without a bank account — which is exactly what an autonomous agent needs.
For builders, the takeaway is simple: if you can expose a valuable HTTP resource, you can now price it per request and let agents pay you in USDC on Base, no human in the loop.