Glossary · Infrastructure

What is HTTP 402?

HTTP 402 is 'Payment Required': a status code the web specified in the 1990s and never used, because there was nothing to pay with. It sat reserved until machine-to-machine payments gave it a job: a server answers 402 with a price, a client answers with payment, the request proceeds.

The code matters because it standardizes the handshake: any client, any server, one meaning. AI agents buying API calls, meters buying electricity, cars buying charging: 402 is the door they knock on.

HTTP 402 on U.CASH

U.CASH implements 402-native payments for machine and agent flows: agents hold keys, answer 402 challenges, and pay per call, with the same non-custodial settlement as every other rail.

See also

AI agentsDeveloper docs

HTTP 402: FAQ

Why is it called 402?
It is the HTTP status code for Payment Required, defined early and unused for decades. Payments on the web finally gave it work.
What pays in a 402 handshake?
Whatever the server prices in, typically a token the client's wallet holds. The handshake is the standard; the asset is a parameter.
Keep reading

The glossary, A to Z

Every term behind the rails, the assets, and the settlement.