What Is x402? How AI Agents Are Starting to Pay for Things on Their Own
An AI agent booking your flights or pulling data from a paid API used to hit the same wall every time: it couldn't actually pay for anything. Someone had to sign up, enter a card, and top up credits by hand. x402 removes that step. It's a payment protocol built on a piece of the web that's been sitting unused since the 1990s, and in the last year it's picked up backing from Google, Visa, AWS, and Anthropic. Here's what it actually does.
x402 turns a payment into something that happens inside a normal web request, instead of a separate checkout flow a human has to complete.
x402 Lets Software Pay Without a Human Clicking "Buy"
x402 is an open payment protocol that lets an AI agent, or any piece of software, pay for a digital resource automatically, as part of the same request that asks for it. No account creation, no saved card, no human approving a checkout screen. The agent asks for something, gets told what it costs, pays, and gets the resource — all in a couple of round trips that take a fraction of a second.
The Coinbase Developer Platform published the first version of the spec in May 2025. It didn't get much attention outside crypto circles at first. That changed once AI agents capable of actually executing multi-step tasks became common: an agent planning a trip, pulling data from a paid research API, or calling a specialized model mid-task all hit the same wall previously — they couldn't pay for anything themselves. x402 is one of the more widely adopted answers to that specific problem.
It Resurrects an HTTP Status Code Nobody Ever Used
The 402 code was reserved for "future use" when HTTP was first specced out — x402 is the first standard to actually build on it.
When the HTTP protocol was first laid out, its authors set aside status code 402 for "payment required" and left it unimplemented — a placeholder for a payment layer the web never got. Every other status code you recognize, like 404 for "not found" or 200 for "OK," got put to work. 402 sat there for three decades.
x402 finally uses it. Here's the flow in practice: an agent (the client) requests a resource from a server that requires payment. The server responds with a 402 status and a header describing exactly what it costs and how to pay. The agent's wallet signs that payment and resubmits the request with a payment header attached. A third party called a facilitator verifies the payment on-chain and settles it, and the server returns the resource along with a receipt. The whole exchange happens inside two HTTP requests.
1. Request
The agent asks an API or service for something — data, a tool call, an image, a document.
2. 402 response
The server replies with a 402 status and the exact price, instead of the content.
3. Sign & resend
The agent's wallet signs a payment and resubmits the original request with it attached.
4. Verify & deliver
A facilitator checks the payment, the server settles it, and returns the resource plus a receipt.
Who's Actually Behind This
Whitepaper published
Coinbase Developer Platform releases the original x402 specification as an open standard, not a Coinbase product.
x402 Foundation launches
Coinbase and Cloudflare set up a foundation to govern the standard so it isn't controlled by one company.
Major platforms join
Google, Visa, AWS, Circle, Anthropic, and Vercel join as members, alongside Solana and other settlement-layer partners.
Production use spreads
Cloudflare reports more than 20 companies participating in agent-initiated payment flows built on x402; MCP servers start shipping with x402 payment support built in.
That membership list matters more than it might look. Visa and AWS aren't crypto companies — their involvement signals that x402 is being treated as basic internet plumbing for the "agentic economy," not a blockchain side project. Anthropic's presence fits the same pattern: agents built on Claude are exactly the kind of software this protocol is meant to unlock.
It's Not the Only Agent-Payments Standard
x402 solves one specific piece of the problem — signaling that payment is required and settling it inline. It isn't the only proposal trying to solve pieces of agent commerce, and the three that come up most aren't really competing so much as covering different layers.
| What It Handles | Backed By | |
|---|---|---|
| x402 | HTTP-layer payment signaling and settlement, inline in a request | Coinbase, Cloudflare, x402 Foundation |
| AP2 | Agent-to-agent payment intent and authorization — did the user actually approve this? | |
| MPP | Discovery of paid endpoints via an OpenAPI extension, so agents know what's payable | Stripe |
In practice these are described as complementary rather than rival standards — an agent might use MCP to reach a tool, AP2 to confirm it has authorization to spend, and x402 to actually move the payment. Settlement on x402 doesn't have to be a cryptocurrency either; the protocol standardizes the request-and-verify handshake, and a given service can settle in stablecoins, or route to a card network behind the scenes.
What This Changes for a Small Business or Freelancer
- An agent can top up its own usage of a paid API without you manually re-entering a card each time it runs out
- Micropayments become practical — paying fractions of a cent per API call instead of a monthly subscription
- Lets you monetize a tool or dataset per-request instead of building your own billing system from scratch
- Backed by major infrastructure players, so it's unlikely to disappear the way niche crypto protocols often do
- Giving an agent a funded wallet means setting real spending limits — a misbehaving agent can now actually spend money
- Reference implementations mostly settle in stablecoins, which some businesses still aren't set up to hold or convert
- Tooling and dashboards for tracking "what did my agent buy and why" are still early and provider-specific
- The standard is barely a year old — expect breaking changes before it fully settles
Frequently Asked Questions
What is x402 in simple terms?
An open protocol that lets software pay for something automatically inside a normal web request, using the HTTP 402 "Payment Required" status code that's existed since the 1990s but was never actually used until now.
Who created x402 and who supports it?
Coinbase's developer platform published the spec in May 2025. Coinbase and Cloudflare then set up the x402 Foundation, which now counts Google, Visa, AWS, Circle, Anthropic, and Vercel among its members.
Do I need cryptocurrency to use it?
The reference setup settles in stablecoins like USDC, but x402 only standardizes the payment-required signal and verification — individual services can settle through other rails if they choose.
More AI Explainers, Written Clearly
Browse our full library of AI guides, updated as tools and standards change.
More from the creator
Explore two other projects from the same creator.