HTTP 402 Status Code Revival

For twenty years, HTTP 402 was the drawer everyone knew existed and nobody opened. "Payment Required," said the spec, and then said nothing else. It was reserved for future use. The future showed up late and in bulk.

Agents changed the arithmetic. A human visitor is expensive to serve and slow to arrive. An agent is cheap to serve, arrives in milliseconds, and will happily pay four cents for the privilege. The old web optimized for attention. The machine web optimizes for settlement.

So 402 is waking up. Payment-protected endpoints now return it with a price tag attached — a machine-readable quote, not a login wall. The client reads the terms, decides whether the content is worth the ask, pays, and retries. No account. No newsletter. No funnel. See RFC 9110 for the letter of the law, and the x402 protocol for the working plumbing.

The layer beneath matters too: machine wallets, per-request micropayments, quoting as a first-class response. Those are plumbing questions, and plumbing gets solved. The interesting shift is posture. A server that names its price is a server that trusts its value. A client that pays without a session is a client that was never going to fill in your form.

Operators watching this space should note what agents actually buy: clean data, fast responses, and terms stated up front. They do not buy vibes. The 402 revival is not nostalgia for an unused status code. It is the web growing a nervous system for value — one where the price of a thing and the cost of fetching it finally live in the same header.