What is x402, really?
x402 lets software pay other software, in cents, instantly, with no contracts. It’s not a company. It’s a small open standard, a few hundred lines of spec, and a growing ecosystem of services that speak it.
For 25 years, the HTTP standard has carried a status code meant for this. 402 Payment Required. The day machines could pay each other directly. That day was always “coming soon.” Stripe couldn't do it. Minimum fees made it impossible to charge $0.001. Bank transfers took days.
Stablecoins changed the math. A digital dollar that settles in 400 ms makes a $0.001 transaction not just possible but cheap. x402 wraps that capability in standard HTTP so any developer can use it without learning crypto.
The result: AI agents (the LLM-powered programs that have started to do work on your behalf) can now pay APIs the same way you tap a card to buy coffee. No accounts. No usage caps. No contracts.
An agent needs something it doesn’t have.
Maybe a weather forecast. Maybe a webpage rendered to text. Maybe one second of compute. It asks for a URL, exactly like your browser does.
The API replies "402: that costs $0.003."
No account, no signup, no API key. The price is right there in the response. The agent decides if it’s worth it.
It pays. The data arrives. The whole thing took 400 ms.
Settled on-chain in stablecoin. The API operator gets paid instantly. No invoice, no chargeback risk, no Stripe.
Everything you need to know to follow what's happening.
- x402
- A way for software to pay other software automatically, using the long-forgotten HTTP "402 Payment Required" status code. No accounts, no API keys, no invoices.
- agent
- A program (often built on top of an LLM) that decides what to do on your behalf. When it needs data or compute it doesn’t have, it pays for it.
- MCP
- Model Context Protocol, a standard way for agents to plug into tools and data sources. An MCP server can be free or paid; if paid, it usually charges via x402.
- facilitator
- A server that watches the blockchain and tells an API "yes, the agent paid you." Removes the need for the API to run its own crypto stack.
- USDC
- A digital dollar that lives on a blockchain. One USDC = one US dollar. x402 uses USDC for payments because it settles in under a second.
- split
- When a single payment is automatically divided between several wallets, for example, the API operator, the platform that sent the agent, and the protocol itself.
- gate
- A small wrapper that sits in front of your API and turns it into an x402-payable endpoint. With Chest Gate, deploying one is a single command.
- referrer
- The platform, agent host, or developer that brought a paying agent to an API. With trustless splits, the referrer earns a share of every payment they originate.
Putting your API behind x402 takes ten minutes.
The simplest version is a wrapper around your existing endpoint that returns 402 when the X-Payment header is missing, and 200 when it's present and verified. Receiving USDC, watching the chain, and splitting revenue between you, your platform, and a referrer are the hard parts. Chest Gate handles all of them.