The x402 payment rail, explained for people who build agents (not exchanges)
HTTP 402 has existed since 1997 as a placeholder — "Payment Required", defined but never used. In 2026 it carries settled USDC between machines. The flow, concretely: your agent calls a paid endpoint, the server answers 402 with exact terms (amount, payee address, chain, asset — on Base, fees are negligible); the agent signs an EIP-3009 transfer authorization and retries the request with the receipt in a header; the server verifies through a facilitator, settles, and returns the actual response.
The facilitator is the only trusted third party, and it is swappable — the x402.org facilitator is free for development, commercial facilitators exist for production. Because the rail is plain HTTP with a standard status code, nothing about it is crypto-specific to the client: it is one fetch call with one retry.
Why builders should care even if they never touch a wallet: per-request pricing removes the signup wall that kills agent adoption of human-oriented APIs, and the same endpoint can still serve humans — two acceptance paths, one codebase. The measured market is still early: 782 services listed, $91,606 USDC settled in 30 days, 4,669 unique on-chain buyers. The rail works; the demand side is arriving. Build pay-per-use now, price for today's volume, and your API becomes callable by every agent that ships a wallet — no account creation step between your service and someone else's agent.
Agent Payments this week — from Issue #001
5. Agentic payments are growing — but most x402 payments aren't from AI agents — PYMNTS (via GNews)
Link: https://news.google.com/search?q=PYMNTS+x402+payments+AI+agents
Independent measurement lands on the same picture we publish daily from x402-list.com: 782 services, $91,606 USDC settled in 30 days, 4,669 unique on-chain buyers — real volume, driven mostly by human-operated wallets so far. Builders: the rail works; the demand side is still arriving. Build pay-per-use now, price for today's volume.
6. Kakao Pay completes agentic payment PoC for AI agent buying/selling, linked to stablecoins — bloomingbit (via GNews)
Link: https://news.google.com/search?q=Kakao+Pay+agentic+payment+PoC
Korean bank-grade rails testing agent commerce end-to-end. Another signal that stablecoin settlement is becoming the boring backbone of agent commerce.
7. SK Telecom proposes RCS standard as final approval channel for AI agent transactions — thelec.net; Ant names 10 Asian wallets for AMP — Tech Wire Asia (via GNews)
Link: https://news.google.com/search?q=SK+Telecom+RCS+AI+payments+standard
The quiet battle isn't which rail moves money — it's who owns the final approval UX. Telcos (RCS) and super-apps (AMP wallets) are both claiming the human-confirm step. If your agent makes purchases, design for an approval layer you don't control.
Sources & further reading:
x402 protocol · x402-list state of x402 · A0Flow x402 services