x402 is an open standard for paying for things on the web with a single HTTP request. A server answers 402 Payment Required with its price, the client signs a USDC payment, retries the request with that payment attached, and gets the result. No signup, no API key, no card form.
HTTP has reserved status code 402, Payment Required, since the 1990s, but nothing ever used it. x402 gives it a job: the 402 response carries a machine-readable price list, and the next request carries the payment. The standard was published by Coinbase and is open for anyone to implement.
An AI agent cannot fill in a credit card form, pass a CAPTCHA, or wait for an invoice. It can read JSON and sign a message. x402 turns paying into exactly that: read the price, sign a payment authorization, resend. That makes per-call pricing practical for amounts as small as a cent, which card rails cannot carry.
Most x402 payments today are USDC, a dollar stablecoin, on Base (Coinbase's Ethereum layer 2) or Solana. The payer signs an authorization; a facilitator checks it and puts it on chain. The seller never holds the payer's keys and the payer never trusts the seller with a card number.
The full walk-through is in how x402 works.
No. x402 is a payment protocol built on HTTP. It moves an existing stablecoin, usually USDC, over an existing chain such as Base or Solana.
No. The payer needs a wallet holding USDC. There is no signup, API key or billing account with the seller.
Coinbase published the x402 standard as an open specification that anyone can implement, on the buyer side, the seller side, or as a facilitator.