When the web was young, its designers left a door open and never built the room behind it. HTTP 402 Payment Required has been reserved in the specification since the 1990s — a status code with a name, a number, and no agreed meaning. For most of three decades it sat unused: there was no standard way for a server to say "pay me" and no standard way for a client to answer. Browsers had cookies and logins and, eventually, checkout pages, but the protocol itself never learned to charge for a request. 402 was a placeholder waiting for a use case that hadn't arrived yet.
x402 is what finally gave that status code a job. It is a machine-payment protocol built directly on HTTP 402. The flow is deliberately small: a caller requests a paid endpoint, the server responds with 402 and a set of payment terms (an amount, a token, a destination, a chain), the caller pays on-chain, and then retries the same request with proof of that payment attached. On the second try the server sees the proof and returns the actual content. No account to create, no invoice to reconcile, no human clicking approve. The request and the payment travel in the same protocol that already moves everything else on the web.
That is a strange thing to want until you picture who is doing the calling. The caller x402 was built for is usually not a person — it is an AI agent hitting an API on its own, dozens or thousands of times, faster than any manual approval flow could keep up with. Card rails assume a human on one side: a billing relationship set up in advance, a statement reviewed later, a chargeback available if something goes wrong. Agent-to-agent commerce has none of that patience. An agent needs to discover a price and settle it inside a single round trip, the same way it would follow a redirect. x402 makes payment a property of the request rather than a relationship negotiated around it.
This is no longer a thought experiment. As of 2026-08-12, agenteconomy.to reports roughly $41.28M in cumulative x402 settlement, with organic daily volume around $28K. The traffic is also volatile in a way worth noticing: transaction counts have swung from a peak near 3.8 million in a day down to 7,320 on 2026-08-12. So the protocol is real and in use, but the shape of that use is still forming — which is exactly the moment to be precise about what x402 does and does not carry.
Here is the part that gets glossed over. x402 gives a server proof of payment. It says nothing about proof of delivery, and it says nothing about who the wallet on the other side actually is. A brand-new address with zero history looks identical, at the protocol level, to an address that has cleanly settled thousands of legitimate calls. For a human-run service that ambiguity is usually survivable, because reputation and chargebacks act as a backstop. On-chain settlement removes that backstop by design: a paid x402 request is irreversible. There is no chargeback to file. And because the payment happens before the content is returned, the party who eats the loss when a deal goes wrong is the buyer — the agent that already paid. Speed and finality are the whole selling point, but they also mean the usual safety net is simply gone.
Two data points show why "the wallet paid" is a weaker signal than it sounds. A 2026-07 analysis by Visa and Artemis, "Agentic Payments from the Ground Up" (base date 2026-04-21), attributes 38.5% of x402 traffic to wash and test activity combined — payments that move value without representing a genuine buyer-seller exchange. (The report gives the combined figure; it does not break down how much is wash versus test.) Separately, on the identity side, a 2026 study (arXiv:2606.26028) of the ERC-8004 agent-identity standard found roughly 173,000 registered agents but only about 3-15% showing real activity, and transaction-backed feedback on under 1.3% of them. Registration is cheap; a track record is not. Being registered, and even having paid before, is not the same as being worth paying.
So, does x402 matter to you? If you run an API and want machines to be able to buy from it without a signup funnel, x402 is the mechanism that makes that possible today. If you are building an agent that needs to pay its own way through the tools it uses, x402 is how it will settle those bills. And if you are doing either of those things at machine speed, the gap above becomes your problem: you are auto-accepting or auto-sending irreversible payments to counterparties you have never met, with no way to claw one back.
That gap is the reason vet402 exists. Given a wallet address or an ERC-8004 agent ID, vet402 returns a trust score, a recommendation, and the underlying signal breakdown — identity, reputation, wallet history, x402 payment history, and sybil-risk indicators — meant to be checked in the request path, before a payment settles rather than after. It does not make x402 slower or add a human back into the loop; it turns "unknown wallet, decide now" into "wallet with a stated history and risk tier, decide now." A score is a signal, not a guarantee — but at machine speed, having one before you pay is the difference between a default you can defend and a coin flip.