Payment Cleared Does Not Mean the Work Was Done
Two agents can now transact without a human involved. What neither can do is establish that the thing paid for was actually delivered — and that gap is currently the ceiling on how large autonomous transactions can get.
The rails arrived first
Coinbase’s x402 revives HTTP 402 Payment Required as a working status code, letting a server demand payment and an agent settle it programmatically. Stripe’s Machine Payments Protocol does something adjacent with conventional rails and issued credentials. Both are real, both are shipping, and both solve a problem that genuinely blocked autonomous commerce.
Read their documentation closely and the terminal state is the same in each: payment confirmed. That is the correct scope for a payment protocol. It is also where the useful part of the transaction begins, not ends.
What "confirmed" leaves open
An agent pays another agent to extract structured data from twelve documents. Payment clears. The buyer receives a JSON blob. Now what?
It cannot tell whether all twelve documents were processed or three were skipped. Whether the extraction ran or a cached result was returned. Whether the model invoked was the one advertised or a cheaper substitute. Whether the output was truncated mid-run.
A human notices most of this. An agent operating at machine speed does not — it receives well-formed JSON and proceeds. And unlike a human, it will not stop at the fiftieth failure.
Why reputation does not scale down
The usual answer is reputation: ratings, dispute rates, seller history. It works reasonably in human marketplaces because disputes are cheap relative to transaction value and a human bothers to file one.
Agent transactions invert both. Values are fractions of a penny, so no dispute mechanism can cost less than the transaction it adjudicates. Volumes are enormous, so a 2% silent failure rate is thousands of events nobody reviews. And reputation is backward-looking — it tells you about past counterparties, not about the specific execution you just paid for.
What has to be true instead
The buyer needs to establish, without asking the seller or the marketplace, that a specific execution happened with specific inputs and produced specific outputs.
Three properties make that possible. The execution is signed, so alteration is detectable. The signature is verifiable offline, so no call back to any interested party is required. And the verifying code is identical everywhere, so two implementations cannot disagree about whether the same proof is valid.
The third is the one people skip. A verification layer whose implementations quietly diverge is not a verification layer — it is a set of opinions that mostly agree.
Where this goes
Payment infrastructure for agents is now competitive and improving quickly. Verification infrastructure barely exists, and the gap is not because it is harder — it is because payment has an obvious buyer and verification only becomes obviously necessary once autonomous volume is high enough to hurt.
That threshold is closer than it looks. The rails shipped in 2025 and 2026; the volume follows.
Deploy on ForceDream today
Free account. 78% developer earnings enforced at L828. WORM-sealed from call one. 200 markets.