x402 is an internet-native payment protocol built on HTTP — launched by Coinbase in May 2025, now governed by the x402 Foundation (Coinbase + Cloudflare) — that revives the long-dormant HTTP 402 "Payment Required" status code to embed stablecoin micropayments directly into standard HTTP requests. Over 100 million payments processed in its first six months. It solves the problem that card payments are economically unviable for the per-query, per-token, per-call billing model that AI agents actually need.
The Problem It Solves
Every existing payment method has a floor below which it's uneconomic:
- Credit cards: ~$0.30 + 2.9% per transaction — unviable for a $0.001 API call
- Prepaid API keys: human friction, periodic top-ups, hard to delegate to agents
- Subscriptions: flat rate hides actual usage, no agent-level spending control
AI agents need to pay for individual API calls, data queries, and compute units — in real time, autonomously, across thousands of micro-transactions — without a human authorising each one. x402 makes this native to HTTP itself.
How It Works
The protocol repurposes HTTP's unused 402 status code as a payment handshake:
1. Agent sends request to API endpoint
2. Server returns: HTTP 402 Payment Required
PAYMENT-REQUIRED: { amount, currency, network, facilitator }
3. Agent constructs payment: signs transaction with USDC/USDT
4. Agent retries: original request + PAYMENT-SIGNATURE header
5. Server verifies payment via facilitator, returns 200 OK + resource
This is stateless, HTTP-native, and works with any standard HTTP client. No new session protocols, no login screens, no OAuth flows. Any library that can set request headers can implement x402.
Infrastructure
Coinbase Developer Platform provides a hosted facilitator service with a generous free tier (1,000 transactions/month), supporting:
- ERC-20 stablecoins: USDC, USDT on Base, Polygon, and Solana
Cloudflare ships a Workers-native middleware — any API deployed on Cloudflare can accept x402 payments with minimal configuration and no custom server code.
Vercel ships x402-next middleware for Next.js API routes and an x402-fetch client wrapper for agents.
SDK support:
- TypeScript/JavaScript:
x402-fetch(client),x402-express,x402-next,x402-fastify(servers) - Python, Go: community implementations
What It Unlocks for AI Agents
| Pattern | How x402 enables it |
|---|---|
| Per-query AI API billing | Agent pays $0.001 per inference call rather than monthly subscription |
| Pay-per-article / paywalled content | Agent fetches content with inline micropayment |
| Agent-to-agent service markets | One agent pays another for computation or data |
| Autonomous procurement | Agent spends within a budget across thousands of calls without human approval per transaction |
Circle Labs demonstrated an agent autonomously paying $0.01 USDC to retrieve a blockchain risk report, end-to-end in a single x402 HTTP exchange. This pattern is not possible with card payments.
Ecosystem and Traction
- 100M+ payments processed in the first six months (May–November 2025)
- x402 Foundation (September 2025): neutral governance body, co-founded by Coinbase and Cloudflare
- Partners at launch: Coinbase, Circle, Alchemy, Visa TAP, Stripe ACP, Cloudflare, Google Cloud, AWS, Anthropic
- v2 spec released ~November 2025: adds session-based pre-authorisation for high-frequency APIs
Relationship to ACP and AP2
x402 operates at a different layer from ACP and AP2:
| Protocol | What it does | Best for |
|---|---|---|
| x402 | HTTP payment execution, micropayments | Agent-to-API, data APIs, compute billing |
| ACP | Merchant discovery + checkout UX | B2C shopping, cart + checkout flows |
| AP2 | Cryptographic authorisation mandates | Trust model, delegated spending, dispute liability |
These are complementary — a production agentic system might use x402 for API-layer micropayments, ACP for consumer checkout, and AP2 for the authorisation trust model.
Why Trial, Not Adopt
For Trial:
- 100M+ transactions processed — this isn't vaporware
- HTTP-native design means zero new client infrastructure;
x402-fetchwraps standardfetch - Cloudflare GA support means any Workers-deployed API can accept payments today
- x402 Foundation governance provides vendor-neutral stewardship
- Anthropic listed as a partner — potential future Claude agent native support
Why not Adopt:
- Stablecoin-only today — fiat, card, and bank transfer support is roadmap, not GA
- Crypto custody requirement — agents need a wallet with USDC; not suitable for all enterprise environments
- Spec not yet v1.0 — breaking changes expected before Q3 2026 backward-compatibility target
- Regulatory grey area — stablecoin payments by autonomous agents sit in undefined territory in most jurisdictions
- Not yet integrated in major AI runtimes — Claude, GPT, Gemini native x402 support is planned, not shipped
Key Characteristics
| Property | Value |
|---|---|
| Launched | May 2025 |
| Current spec | v2 |
| v1.0 target | Q3 2026 |
| Governance | x402 Foundation (Coinbase + Cloudflare) |
| Networks | Base, Polygon, Solana (ERC-20 / SPL stablecoins) |
| GitHub | coinbase/x402 |
| Website | x402.org |
| Docs | docs.cdp.coinbase.com/x402 |
| Related | ACP, AP2, Worldpay MCP |