A micropayment is a very small payment — often a fraction of a cent up to a few cents — charged for a single small thing rather than bundled into a larger bill. Paying $0.01 for one API call, or $0.001 for one page a crawler reads, is a micropayment. The idea is old; what's new in 2026 is that it finally works at that size, which is why per-call API pricing is suddenly practical.
This is the plain-language version: what a micropayment is, why it didn't work for decades, and what changed to make sub-cent API payments viable now.
Why micropayments didn't work before
The problem was never the idea — it was the fee. Card networks charge roughly a fixed fee plus a percentage per transaction (commonly around 30 cents plus ~3%). On a $50 purchase that's noise. On a one-cent charge, the fee is thirty times the payment. You'd lose money collecting it.
So the web routed around micropayments. APIs bundled usage into monthly subscriptions and quotas; content sites sold ads or annual memberships instead of charging per article. "Charge a tiny amount for a tiny thing" stayed theoretically nice and practically impossible for thirty years.
What changed
Two things made sub-cent payments viable:
- Stablecoins on low-fee networks. USDC on a high-throughput, low-cost network like Base drove the per-transaction cost down to a fraction of a cent — small enough that a one-cent charge nets out positive. The fee no longer dwarfs the payment.
- An HTTP-native way to ask for it. x402 revived the long-dormant HTTP
402 Payment Requiredstatus code into a working handshake: a server quotes a price, the caller pays, the call succeeds. That gave programs a standard way to make a micropayment without a checkout page.
The result shows up in real prices. CoinGecko runs an x402-priced API endpoint at $0.01 per request (coindesk), and independent trackers put the median x402 call around $0.028, ranging from $0.002 to $0.44. Those are numbers card rails simply can't serve.
Micropayments and APIs
Pay-per-call API pricing is a micropayment use case: each request is charged individually instead of rolled into a plan. That's the whole point of pay-per-call — the caller pays the quoted price for a call and gets the result, with no "calls left this month" to manage.
It fits autonomous callers especially well. An AI agent with a budget can decide, call by call, whether a result is worth a cent — something it can't do with a subscription it would have to sign up for. Micropayments are what let an API charge a caller it has never met, for exactly one call.
The honest state in mid-2026
Worth saying plainly: the plumbing works, but demand is still early. On-chain data through early 2026 showed x402 doing only tens of thousands of dollars in real daily volume, a lot of it testing rather than commerce — the narrative is running ahead of adoption (coindesk). The technical barrier that blocked micropayments for thirty years is gone; the market that uses them is still being built. For a fuller take, see is x402 worth it yet?.
FAQ
What is a micropayment? A micropayment is a very small payment — usually a fraction of a cent to a few cents — charged for a single small unit of value rather than bundled into a larger bill. Paying one cent for one API call is a micropayment.
Why didn't micropayments work before? Card fees. A fixed fee plus a percentage per transaction (around 30 cents plus ~3%) costs far more than a one-cent payment, so collecting micropayments over cards lost money. Stablecoins on low-fee networks removed that floor.
Are micropayments only for crypto?
The payment settles in a stablecoin (USDC), but you don't need crypto knowledge to accept them — you set a price and add an SDK, and the platform handles the payment side. The status code that signals "payment required" (402) is itself payment-agnostic.
How do micropayments relate to APIs and AI agents? Per-call API pricing is a micropayment use case: each request is charged on its own. It fits AI agents because an agent can weigh a result against its price call by call, and pay for a single call without an account or subscription. See how AI agents pay for APIs.
Next steps
- The concept: what is x402?
- How agents actually pay: how AI agents pay for APIs
- Charge for your own API: the monetization playbook
- Try it free: pricing and create an account