Micropayments for AI Agents
Micropayments are tiny payments — fractions of a cent to a few cents — for a single API call, query or unit of work. They matter for agents because an agent transacts constantly and per-use pricing fits machine behaviour better than subscriptions. What makes them newly viable is a machine-native payment flow: a protocol like x402 lets an agent pay for a request inline, without a checkout, a card form or a human in the loop.
Why now
Micropayments failed on the human web because a person will not approve a checkout for a cent. An agent will — if the payment is inline and automatic within its owner’s policy. Machine-native payment flows make the per-request economy practical, turning "pay per call" from a slogan into a thing an agent actually does thousands of times a day.
Related standards
Questions
Won’t fees eat a micropayment?
Conventional card fees would. Machine-native and chain-neutral flows are designed for small amounts, which is what makes per-request pricing workable.
How does an agent stay within budget?
Its owner’s policy caps spend by amount, rate and category; anything outside the policy escalates to a human.
Where this lives in the estate
Flashy Gold — machine-native payment and value
Keep reading
By Michael Gord · published 2026-10-04 · part of the Agentic Encyclopedia. Dates are the day of publication; events are cited at their own dates.