What is x402?
Short answer
x402 is an open standard for paying for things over the web with a normal HTTP request. A server answers with status 402 Payment Required and a price, the caller attaches a signed payment and asks again, and the server returns the result. No account, API key or checkout page is involved.
The short version
HTTP has always had a status code for "you need to pay": 402 Payment Required. For decades nothing used it. x402 gives it a job.
A server that charges for something replies to an unpaid request with status 402 and a machine-readable price. The caller signs a payment for that price and sends the same request again with the payment attached. The server checks the payment, settles it, and returns what was asked for.
Because the whole exchange happens inside ordinary HTTP, software can do it without a person. That is why x402 is mostly talked about for AI agents and APIs: an agent can pay a fraction of a cent for one search, one page render or one model call, with no sign-up.
Key facts
| What it is | An open payment standard built on HTTP status 402 |
| Created by | Coinbase, launched in May 2025 |
| Run by | The x402 Foundation, hosted by the Linux Foundation since 2026 |
| Licence | Apache-2.0 |
| Current version | Version 2 (version 1 is still supported by the reference SDKs) |
| Protocol fees | None. The standard itself charges nothing |
| Paid in | Tokens on a blockchain, most often the USDC stablecoin |
| Typical price | Fractions of a cent to a few dollars per request |
What makes it different from an API key
- No account. The payment is the permission. A caller that has never seen the service before can use it on the first request.
- Pay per call. There is no subscription or prepaid plan built into the protocol. Each request carries its own payment.
- The price is in the reply. The 402 response says exactly what is owed, in which token, on which network, and to whom.
- Any HTTP client can learn it. Paying is a matter of reading one header and adding another.
What you need to use it
To pay, you need an x402 client library and a wallet that holds the token the seller asks for. See how to pay an x402 API. If you do not want a wallet, see using x402 services without a crypto wallet.
To charge, you add a piece of middleware to your server and choose a facilitator to settle payments for you. See how to accept x402 payments.
To see one, paste any paid endpoint into the 402 checker. It shows the price and payment options without paying anything.
Where x402 sits among similar standards
x402 is not the only way for software to pay. MPP also uses status 402 and adds card payments. L402 uses Bitcoin's Lightning Network. AP2 and ACP deal with shopping and checkout rather than per-request payment. The comparison table puts them side by side.
Sources
- x402 repository README
- x402 documentation
- x402 version 2 launch post
- Linux Foundation announcement of the x402 Foundation
Facts checked against these sources on . Protocols change, so the official specification wins if it disagrees with this page. Read this page as Markdown.
Related questions
Who writes this. Ask402 is published by Havok Holdings LLC, which also runs Agent402, one of the x402 services covered here. Agent402 is labelled wherever it appears. Everything else is described from each project’s own documentation, and nobody pays to be listed.