connected@0xjmori

x402

x402: How a Crypto Payment Agent Pays for a Request

x40211 min read

HTTP status 402 has meant Payment Required since the 1990s, and almost nobody sent it. x402 is the open protocol that finally does. A client — a person, an app, or an agent — asks for a resource. If the resource costs money, the server answers 402 with payment terms. The client pays and retries. There is no merchant account to open first, no card form, and no session to keep warm.

The request cycle

  1. The buyer requests the resource. At this moment it may not know the price.
  2. The server returns 402 Payment Required. The PAYMENT-REQUIRED header carries the terms: how much, which asset, which network, where the payment must land.
  3. The buyer signs a payment payload and sends it back on PAYMENT-SIGNATURE. The signature is the authorization. A raw key does not travel.
  4. A facilitator checks the payload and submits the settlement. In the Coinbase and Cloudflare descriptions, the facilitator does not hold the funds. It verifies and broadcasts a transaction the client already signed.
  5. The server delivers the resource.

That is a buy engine for things that are not really “orders”: an API call, a document, a query another agent will not answer for free. It fits machine-to-machine trade better than it fits a sofa. The sofa has tax, a truck, and a merchant of record. The API has a price per request and a buyer who may be software.

What the money is

x402 is not a coin. It is a way to attach a payment to HTTP. The smoothest asset in current descriptions is an EIP-3009 token such as USDC, which can move with a signature rather than a prior on-chain approval. Other ERC-20 tokens can be used through Permit2. Clients are expected to speak more than one network, including EVM chains and Solana. Cloudflare’s Monetization Gateway, in a closed beta announced at the end of September 2026 for eligible U.S. buyers and sellers, settles through Coinbase’s facilitator in USDC on Base. Those are deployment choices. They are not the whole protocol.

A crypto payment agent therefore needs a budget that is as dull as a Visa decline threshold. Which asset. Which chain. How much per call. How much per hour. Which hosts. An agent with a hot wallet and a curious find-loop will buy the internet by accident. x402 makes paying easy. Easy is the hazard. The mandate still has to be narrow, and it still has to be the principal’s.

Whose standard it became

Coinbase built x402 and open-sourced it. On 23 September 2025 it said it intended to stand up an x402 Foundation with Cloudflare. On 14 July 2026 the Linux Foundation said that foundation was operational and that Coinbase had contributed the protocol. The point of the move is governance. A payment header that only one company can change is a product. A payment header stewarded in the open, beside projects like the Linux kernel’s institutional home, can be infrastructure.

The member list is the strategic fact. Premier members reported with the foundation include Visa and Mastercard, Stripe and Adyen, American Express, Amazon Web Services, Google, Coinbase, Circle, Shopify, and Fiserv, plus chain organizations including Ripple, the Solana Foundation, the Stellar Development Foundation, and the Monad Foundation. The card networks did not stand outside the stablecoin door. They joined the body that specifies it. That is the context for the next essay: Visa’s token model and x402 are two buy engines, and the same companies intend to understand both.

Cousins, not clones

Mastercard’s Agent Pay for Machines, described on 20 October 2026, uses x402 as its basis: a business sets a task and a limit, a service answers 402, the agent signs a payment voucher inside the limit, the provider checks the voucher and does the work. Vouchers can be exchanged off-chain and redeemed later. A Cloudflare Connect demo showed nine payments to two merchants under one approved budget. Same family as a Visa mandate — a ceiling, a signature, a refusal path — different settlement. Google’s September 2025 AP2 work also described an agent-to-agent x402 extension. The pattern is stable even where the asset is not: the agent pays because a person bounded the spend, not because the model felt confident.

Published by FindBuyAgent.com. Canonical URL findbuyagent.com/blog/what-is-x402.