x402 and agent payments: what a machine-payable endpoint means for your site

HTTP 402 has said Payment Required since the early 1990s, reserved for a micropayment future that never arrived. x402 is the attempt to use it, and it arrives for a specific reason: software agents now make requests, and an agent cannot complete a checkout page, accept terms, or wait for an invoice.

Coinbase released x402 in May 2025. The mechanics are simple enough to describe in a paragraph, which is most of its appeal.

The flow

1. The client makes an ordinary request with no payment attached.
2. Instead of the resource, the server returns 402 and advertises what it accepts: the scheme, the network, the asset, the amount and the destination address.
3. The client signs a stablecoin payment, attaches the proof in HTTP headers, and repeats the request. A facilitator verifies and settles it, and the server returns the resource.

No account, no API key, no human. Most traffic settles in USDC on Base or Solana, and on EVM chains the signature is an EIP-3009 transfer-with-authorization, so the client authorises a transfer rather than broadcasting a transaction itself.

It is worth being clear about what x402 is not. It is not a chain and not a token — it is a convention for carrying payment in HTTP, which is why it does not need anyone to adopt a new currency.

Where it sits in a stack that is still forming

x402 is one of several agent-payment efforts and they are not direct competitors:

The split matters when you are deciding what to implement. AP2's signed mandates are the part that answers "did a person actually authorise this purchase", which is the question a disputed transaction turns on. x402 is the part that moves the funds. Infrastructure is wrapping both: Amazon Bedrock AgentCore Payments, built with Coinbase and Stripe, negotiates the 402 handshake, the wallet authentication and the proof delivery on the agent's behalf.

What it means if you run a website

Three consequences, in descending order of how soon they will matter to you.

A priced endpoint is a rate limit you get paid for. This is the genuinely attractive part. Bulk extraction currently costs a scraper the price of residential proxy bandwidth and costs you the bandwidth, the compute and the data. Charging per call moves that cost onto the caller and converts it into revenue. It is the same economic argument as proof of work, with the cost denominated in money rather than CPU time and payable to you rather than burned.

Payment is not authorisation. A funded wallet is not a vetted customer. An attacker who will pay a tenth of a cent per request to take your entire catalogue is a paying customer by every measure x402 can see, and the volume problem is unchanged — you have simply been compensated for it at a price you set before you knew what it was worth. Anything that must not happen at scale still needs a separate decision, which is the argument for keeping human verification on the flows where scale causes the harm.

402 becomes a response your logs need to understand. If you adopt it, your metrics have a new terminal state that is neither success nor failure. If you do not, you will still start seeing clients that handle 402 gracefully, and that is itself a signal about what is on the other end.

A paywall presumes you know who must pay

A paywall presumes you can already tell who has to pay, and that is exactly what a site operator cannot do.

The problem is not charging for API access with request caps, which has never been hard. It is preserving a free experience for customers while an increasing share of traffic is automated. A retailer has to show products to shoppers for nothing, so the unpaid path stays open — and an automated client that is indistinguishable from a shopper will simply use it. x402 lets you charge the clients that volunteer to be charged. Deciding who must be charged is a separate problem, and it is the one that determines whether any of this reduces abuse.

Three further problems are worth holding in view.

It can discourage honest agent identification. If operators allow-list a handful of well-known crawlers and route everything else to micropayments, the rational move for a small, well-behaved agent is to stop declaring itself and present as a browser instead. Pricing and identity pull against each other, and identity schemes decay when declaring yourself is punished.

Charging per fetch collects once, and the content leaks permanently. Per-crawl pricing assumes repeat access. A crawler that stores what it took pays for one request, and the value is gone. That is why the figure a publisher would need to be made whole is nothing like a fraction of a cent per page.

It creates a new abuse vector. Low-quality content, priced just cheaply enough that agents do not balk at it, is a viable business. Register domains, host a wide spread of mediocre pages, set the price low, and collect on volume.

Micropayments also have a history. Pay-per-request API paywalls built on Lightning have existed for years, and Flattr before them; none became mainstream, and the friction was always client-side wallet setup. x402's real advantage is that the wallet now belongs to a machine rather than a person, which is a genuine change rather than a repackaging. The remaining question is transaction cost: a bank-to-bank FedNow transfer costs about 4.5 cents regardless of size, and per-request settlement has to come in meaningfully below that to make sense at the volumes being described.

On governance, the Linux Foundation launched the x402 Foundation on 2 April 2026 with Coinbase contributing the protocol, which makes it a neutral home rather than one company's standard.

What we would actually advise

If you are protecting an API today, the ordering we would suggest has not changed much:

• Work out which calls cost you money, and bound those first. See API security for why most of the OWASP list is authorisation logic only your own code can fix.
• Decide whether you want per-call revenue or a subscription. Per-call pricing suits data that is valuable in small quantities and awkward to meter any other way.
• Keep a view on who is calling. x402 tells you a payment cleared. It tells you nothing about whether this caller should be able to do this a million times, and that remains the question that matters for abuse.

The reason to pay attention now is not that agents are about to pay you. It is that the plumbing for them to do so is being built, and the decision about whether a paying automated client is welcome on your site is one you will be asked to make.