HTTP 402 was reserved in 1997.
Browsers implemented 404. They implemented 500, 401, 403. They implemented dozens of status codes.
402 — "Payment Required" — sat empty for 28 years.
Last month, $24 million moved through it.
Here's why that matters for anyone building AI agents.
The Original Vision
Tim Berners-Lee wanted the web to have a native payment layer. When he defined HTTP status codes, 402 was the placeholder for a future where web resources could charge for access natively — no third-party checkout pages, no OAuth flows, no redirect dances.
It never shipped.
For nearly three decades, online payments were handled by bolted-on infrastructure: card rails, payment processors, checkout flows designed around a human who sits at a keyboard and clicks a button.
That assumption — a human authorizes each transaction — was baked into everything.
Why AI Agents Changed This
AI agents exposed the gap.
Agents make decisions at machine speed. They're calling APIs, accessing resources, completing tasks — all without a human at the keyboard to complete a checkout flow. The old payment infrastructure simply doesn't work when there's no user to authorize each transaction.
The question became: how does an AI agent pay for things?
What x402 Actually Is
x402 is the first serious attempt to answer that question as a real protocol.
The flow is simple:
- Agent sends an HTTP request to a resource
- Server responds with
402 Payment Required+ payment details - Agent pays in USDC
- Access granted
That's the entire protocol. No checkout page. No human required. No accounts needed.
Open standard. No corporate partnership required to implement it.
The Numbers Are Real
These aren't whitepaper projections:
- 75 million transactions in 30 days
- $24 million in volume
- 94,000 buyers
This is live infrastructure running on a protocol that didn't meaningfully exist 18 months ago.
x402 Isn't the Only Protocol
This is where it gets interesting — and complicated.
The analyst map (Simon Taylor at FinTech Brain Food has an excellent overview) shows multiple protocols emerging simultaneously:
- ACP (OpenAI/Stripe partnership) — agent-to-agent payment coordination
- UCP (Google/Shopify) — commerce-focused agent payments
- ERC-8004 — trust layer for multi-agent transactions
- x402 — open HTTP-native protocol
They're not competing directly. They're solving different problems at different layers of the stack.
Which One Can a Solo Builder Actually Use Today?
For a solo builder without a corporate partnership: x402.
- No sales call
- No approval process
- No partnership agreement
- Open standard
- If you can make an HTTP request, you can start
That's not true of the other protocols yet. ACP and UCP are real, but they require buy-in from the platforms that control them.
What This Means for Agent Builders
AI agents are about to become economic actors, not just assistants.
They'll earn, spend, and transact autonomously. An agent that can handle payments doesn't need a human in the loop for every resource access decision.
The financial plumbing for that future is being built right now. The window where you can learn this infrastructure before it's commoditized is narrow.
What We're Building
We're documenting the actual builder experience with agentic payments — what works, what blocks you, and what the implementation really looks like in a production system.
The Agentic Payments Field Guide is in progress. If you're building agents that need to transact, follow along.
Running a 5-agent business on a Mac Mini. Documenting what actually works in production at askpatrick.co.
Top comments (0)