Concepts / agent → payments & commerce
x402 changing
x402 payment protocol · Coinbase; now the x402 Foundation under the Linux Foundation
- Spec
- v1 · x402 Foundation, April 2026
- Published
- Reviewed
What it is
x402 revives the unused HTTP 402 Payment Required status to make machine-to-machine payment part of the request. An agent can buy a single API call, a page, or a compute job without signing up for anything. Coinbase launched it in May 2025. Coinbase and Cloudflare announced a foundation for it in September 2025, and in April 2026 the Linux Foundation launched the x402 Foundation with 22 members including AWS, Google, Microsoft, Visa, Mastercard, Stripe and Shopify.
How it works
- Client requests a resource.
- Server responds
402with payment requirements: amount, asset, network, recipient. - Client signs a stablecoin transfer (typically USDC) and retries with the payment attached in a header.
- A facilitator verifies and settles the payment. The server returns the resource.
Nothing about the flow requires the client to be human, which is why it fits agents.
When to use it
- You want to charge agents per call with no onboarding.
- Your agent needs to buy access to services on the fly.
For a purchase a person has to authorize, look at AP2. For selling goods inside ChatGPT or Gemini, look at Agentic Commerce Protocol and UCP.
What changed
- April 2026: Linux Foundation launches the x402 Foundation and takes the protocol contribution from Coinbase.
- September 2025: Coinbase and Cloudflare announce the foundation.
Watch out for
- It is stablecoin rails. Your accounting and compliance teams will have questions.
- You trust the facilitator. Know who runs yours.
Related
- AP2 Agent Payments Protocol
- Agentic Commerce Protocol Agentic Commerce Protocol (ACP)
- UCP Universal Commerce Protocol
- MCP Model Context Protocol