Standard · Transact
x402
HTTP 402 Payment Required, with a stablecoin payment in the retry: pay per call, no account.
What it is
A server answers a request with the old HTTP 402 status and a price. The agent pays, usually in a stablecoin, and retries. No account or subscription is needed.
An analogy
At a glance
- Owner
- Coinbase and Cloudflare (May 2025); reported moved to an x402 Foundation at the Linux Foundation in 2026
- Maturity
- Watching The foundation, its backers (reported as Stripe, AWS and Google) and call volumes in the hundreds of millions are reported, not confirmed from a primary page.
- Where it lives
- x402.org
- Framework domain
- Transact: Be chosen
- What it serves
- Charge agents per request without accounts
Who should care
The roles this standard touches most. See all the roles on the personas page.
- Engineering and product. Build the access, data, endpoints and actions that agents use, on open standards.
- Commerce and sales. Make offers, prices, availability and checkout work for agents buying on someone’s behalf.
How to adopt it
- 1
Consider it only if you sell data or API calls that agents would pay for one at a time.
- 2
Pilot on one low-risk endpoint.
- 3
Involve finance and legal early, since the payments are in digital currency.
The Institute’s view
A clever fit for machine-to-machine payments. It suits a narrow set of businesses, and the figures around it are reported. Watch it and pilot only if per-call pricing is already your model.
Standards change fast. Last reviewed November 2026.