x402 Explained: How the HTTP 402 Protocol Lets AI Agents Pay With Stablecoins

For almost three decades the web has had a status code for payments that nobody used. HTTP 402, “Payment Required”, sat in the specification waiting for a purpose while the internet built ads, subscriptions and card forms instead. In 2025 Coinbase gave it a job. x402 is an open protocol that turns a stablecoin payment into part of an ordinary web request, so a program can pay for an API call, a dataset or an article in the same round trip it uses to fetch it. It is one of the building blocks of agentic commerce, where AI agents find, buy and pay for things on our behalf.

This guide explains what x402 is, where the 402 status code came from, how a payment works step by step, who is behind the protocol, what the 2026 usage data really shows, and what it all means for businesses that accept crypto.

What x402 Is

x402 is an open payment standard that lets a server ask for payment, and a client pay, using nothing more than HTTP, the protocol every website and API already speaks. The name comes from the status code it uses: 402 Payment Required.

The core ideas are simple:

• Payments happen inside the web request. There is no separate checkout page, redirect or invoice.
• No accounts for the buyer. A wallet with a stablecoin balance is enough. There are no sign-ups, API keys or card details.
• Built for small amounts. Prices can be a fraction of a cent, which card payments cannot handle economically.
• Built for software. An AI agent or script can read the price, decide whether to pay, pay and continue, all without a human clicking anything.
• Open. Anyone can implement it, and no single company has to approve a seller.

Most x402 payments today are made in USDC, a dollar-backed stablecoin, mainly on the Base and Solana networks. If stablecoins are new to you, our guide to what stablecoins are explains why a token that holds a steady dollar value is a natural fit for automated payments.

The 30-Year-Old Status Code Behind It

HTTP status codes are the short numbers a server returns with every response. Most people know 404 Not Found and 500 Internal Server Error. Code 402 Payment Required appeared in early drafts of HTTP in the early 1990s, and when HTTP/1.1 was standardized in 1997 it was formally “reserved for future use”. The current HTTP standard, published in 2022, still describes it the same way.

The idea was always there: a server should be able to say “this costs money” in the same language it uses to say “this page moved” or “you are not logged in”. What was missing was money that could travel over the internet as easily as data.

In the 1990s, micropayment experiments such as DigiCash and Millicent tried to fill that gap and never took off. Card payments became the default instead, and cards are poorly suited to tiny amounts. A typical online card fee includes a fixed charge of around 30 cents per transaction, so charging one cent for an API call makes no sense.

Three things changed:

1. Stablecoins gave the internet a digital dollar that can be sent by software without a bank in the middle.
2. Fast, cheap networks such as Base and Solana made it possible to send a few cents for a fraction of a cent in fees, and to confirm the payment in seconds.
3. AI agents created millions of potential buyers that cannot fill in card forms, pass identity checks or sign up for subscriptions.

x402 connects these pieces by finally giving status code 402 a standard meaning.

How an x402 Payment Works, Step by Step

From the outside, an x402 payment looks like an ordinary web request that takes a moment longer. Inside, six things happen.

1. The client asks for something. An agent requests a resource, for example a weather report from an API.
2. The server replies 402 Payment Required. Instead of the data, it returns a machine-readable price: how much, in which token, on which network, and to which address.
3. The client’s wallet signs a payment for exactly that amount.
4. The client repeats the request with the signed payment attached in an HTTP header.
5. The server verifies and settles the payment, either itself or through a service called a facilitator, which checks the signature and submits the transfer to the blockchain.
6. The server returns the data with a normal 200 OK response and a payment receipt.

On fast networks the whole exchange usually completes within a few seconds. The facilitator does not hold the money. It executes a transfer the buyer has already signed, from the buyer’s wallet to the seller’s address. Coinbase runs a hosted facilitator, and other companies offer their own, so sellers do not need to run blockchain infrastructure to accept x402 payments.

What a 402 Response Tells the Buyer

The heart of x402 is the payment request a server sends back with the 402 code. It is written for machines, but it is easy to read.

Because the request is standardized, any compatible client can understand any compatible server. An agent does not need a custom integration for every API it pays. It reads the request, checks the price against its budget and pays or walks away.

Who Is Behind x402

x402 started as a Coinbase project, but it has grown into a shared industry effort.

• Coinbase introduced x402 in May 2025, published the specification and reference code, and runs a hosted facilitator.
• Cloudflare joined Coinbase in announcing the x402 Foundation in September 2025 and has added x402 support to its tools for building agents. Cloudflare also uses 402 responses in its pay-per-crawl program, which lets publishers charge AI crawlers for access.
• Google included an x402 extension in AP2, its Agent Payments Protocol, so agents that use AP2 can settle in stablecoins.
• The x402 Foundation now operates under the Linux Foundation. Visa, Mastercard, Stripe and 14 other premier members joined its governance in 2026.

That last point matters. When the two largest card networks and the largest online card processor sit on the board of a stablecoin payment protocol, it signals that agent payments are likely to use several rails side by side rather than one replacing the other. Our guide to agentic commerce covers the card-based alternatives in detail.

Real Usage in 2026: Hype vs Volume

x402 has some impressive headline numbers and some sobering details underneath them.

The headline transaction counts are inflated by testing, incentive campaigns and activity that some analysts describe as wash trading. A surge in late 2025 was driven partly by token-minting campaigns that used x402 payments, not by people buying services.

The commercial picture is much smaller. About $28,000 per day works out to roughly $10 million a year. That is tiny next to card networks, but it is real money for a protocol that is little more than a year old, and it is flowing into exactly the use cases x402 was designed for: paid APIs, data and services bought by software.

The honest summary: developer interest is very high, the infrastructure is being built by serious companies, and genuine demand is early. Treat the big numbers with caution and watch the commercial volume instead.

What x402 Is Good For

x402 works best where payments are small, frequent and made by software.

• Pay-per-call APIs. Instead of selling monthly plans and managing API keys, a provider charges per request.
• Data and research. Market data, search results or analytics can be sold one query at a time.
• Content for AI crawlers. Publishers can charge AI companies for each page they read, rather than blocking crawlers or signing one-off licensing deals.
• Compute and storage. Processing time, file storage or bandwidth can be billed by the second or by the megabyte.
• Premium articles and media. Readers or their agents can pay for a single article without a subscription.
• Agent-to-agent services. One agent can pay another to translate a document, check a fact or run a specialized task.

What these use cases share is that the buyer is often not a person at a checkout page, and the amount is too small for a card.

x402 vs Card Payments vs Crypto Checkout

x402 is not a replacement for every kind of payment. It fills a gap that existing methods leave open.

For a business selling physical goods or services to people, a crypto checkout or a card form is still the right tool. x402 matters when your customer is a program.

Limits and Open Questions

x402 is promising, but several important problems are not solved yet.

• Thin real demand. As the usage data shows, genuine commercial volume is still small.
• Refunds and disputes. There are no chargebacks. If an API returns bad data after payment, buyer protection has to come from reputation, escrow or future standards.
• Identity. A seller often cannot tell which person or company an agent is acting for. Card networks are building agent identity systems, and x402 will need something similar for larger payments.
• Spending controls. An agent with a funded wallet can overspend if it is badly configured or tricked. Budgets and limits have to be built into the wallet or the agent.
• Regulation. Rules for payment providers and stablecoins were written with people in mind. Regulators are still working out how they apply to software that pays on its own.
• Stablecoin dependence. Most x402 payments use USDC. Its issuer can freeze tokens at specific addresses when required by law, which adds a central point of control.
• Competing standards. ACP, AP2 and the card networks’ agent programs overlap with x402. Several standards may coexist for years.

None of these are reasons to ignore x402. They are reasons to experiment carefully rather than rebuild your business around it today.

What It Means for Businesses That Accept Crypto

The most important point first: you do not need x402 to accept crypto payments from customers. A crypto payment gateway already lets people pay for orders, invoices and subscriptions in BTC, ETH, USDT, USDC and other coins. x402 adds a new kind of buyer, software, and a new kind of product, small pay-per-use access.

What x402 does tell you is where payments are heading:

• Stablecoins are becoming the default money for machines. If you do not accept USDC and USDT yet, start with our guide on how to accept USDC payments.
• Payments are becoming programmable. Orders that are created, confirmed and fulfilled automatically will matter more than checkout pages.
• APIs matter more than buttons. An agent cannot click your checkout button, but it can call your API.

Bcon Global is built for this direction. Payments go straight to your wallet with a flat 1% fee, and the Bcon Global API lets your systems create payment requests, track their status and receive confirmations automatically, the same building blocks that agent payments rely on.

How to Prepare: A Short Checklist

You can get ready for machine payments without betting on any single protocol.

1. Accept stablecoins now, so the money machines prefer is already part of your checkout.
2. Make prices and products machine-readable with clear pricing pages, structured data and public documentation.
3. Automate order confirmation through an API and webhooks instead of manual checks.
4. List what you could sell per use, such as reports, data, access or support time.
5. Set limits and monitoring for any automated selling, including rate limits and alerts for unusual volume.
6. Follow the standards, including the x402 Foundation, AP2 and the card networks’ agent programs, and test a small pilot when one fits your product.

x402 is a clever answer to an old problem: how to pay for something on the internet as easily as you request it. By reviving a forgotten status code and pairing it with stablecoins, it gives software a way to buy what it needs without accounts, cards or humans in the loop.

The protocol is real and backed by serious companies, but the market is young and the headline numbers overstate actual commerce. For most businesses the practical move today is not to build on x402, but to get the foundations right: accept stablecoins, automate payment confirmation through an API and keep your funds in a wallet you control. When agent buyers arrive in numbers, you will be ready for them.