Micropayments for APIs: Why Now Is Different

Per-call API pricing has been technically possible for a long time, since HTTP 402 Payment Required was written into the web's earliest specs, but it never became a working standard. This brief covers why earlier micropayment systems failed, what changed with agent-driven payment, and how the x402 flow works in practice. Forrester argues that every earlier attempt assumed the paying entity was a person, while agents have no mental transaction cost. AgentCash adds the cost side: card fees dwarf small charges, while Layer 2 stablecoin transfers cost under $0.001 in gas. The brief closes with pricing figures, suitable workloads, pitfalls and answers to common developer questions.

Key concepts

API micropayment

A sub-dollar payment settled per individual API call, typically fractions of a cent to under a dollar, on a low-cost blockchain. The rough threshold is a charge below about $0.50 per call. S3 · agentcash.devS4 · scoredetect.com

HTTP 402 Payment Required

A status code placeholder in the original web specs, meant to return the specification of charging schemes available. HTTP/1.1 in 1997 marked it reserved for future use. S1 · buttondown.comS3 · agentcash.dev

x402

A protocol built on the HTTP 402 status code. The server returns a price, currency and address; the agent's wallet signs a transfer and retries with an X-Payment header. S3 · agentcash.dev

Machine Payments Protocol (MPP)

Protocol launched by Stripe and Tempo on March 18, 2026, built for agents to pay rather than humans, with no human decision point between request and payment. S2 · forrester.com

Atomic payment

A payment with no partial state: the request pays and returns data, or it does not run at all. S3 · agentcash.dev

Aggregate and pay later

The prevailing earlier workaround, used by Apple and Facebook, that bundles small purchases into one card transaction and lets users prepay by loading credit onto accounts. S5 · cs.stanford.edu

The x402 request-pay-retry flow

1. Agent requests a paid resourceThe agent calls an x402-protected API endpoint like any other HTTP request, with no prior account signup at that vendor.
2. Server answers with HTTP 402The server responds with a price, a currency and an address, which together describe what the agent must pay.
3. Wallet signs a transferThe agent's wallet signs a stablecoin transfer. Payment is a programmatic step in the request-response cycle, not a conscious decision.
4. Agent retries with X-Payment headerThe agent repeats the original request and attaches an X-Payment header carrying the signed payment.
5. Server verifies and returns dataThe server verifies the payment and returns the data. Settlement on Base and Solana is sub-second, and the call either pays and succeeds or does not execute.

Why human-paid micropayments failed

Micropayments were attempted for decades with a human payer. Ted Nelson proposed tiny payments in the 1960s, and in 1999 IBM and Compaq developed their own platforms while the W3C worked on micropayment markup. Companies such as BitPass, FirstVirtual, Cybercoin, Millicent and Digicash floundered: advertising was paying the bills, and consumers expected web content to be free. Blendle priced articles at $0.19 and $0.49 while a full subscription cost $12 for a month of the Times, and the startup is now defunct. Rita McGarth wrote in 2010 that no standard perceived value had emerged for web content. One account concludes that micropayments failed for asking too often, rather than for asking too much. Forrester states the common thread more bluntly: every earlier attempt assumed the paying entity was a person, and humans hesitate, abandon carts and resent friction. Aggregation was the workaround that endured, with Apple bundling song purchases into one card transaction and allowing prepayment.

What changed: agents, stablecoins and Layer 2

Forrester dates the shift to March 18, 2026, when Stripe and Tempo launched the Machine Payments Protocol alongside the Tempo Mainnet, a payments-focused blockchain codeveloped with Paradigm. The protocol embeds payment in the request-response cycle, so there is no checkout moment and no human decision point between request and payment. Forrester adds that payment is a prerequisite for an agent, which cannot substitute a free alternative when a required API is unavailable. On cost, AgentCash notes that card processors charge roughly $0.30 plus 2.9% per transaction, so on a $0.03 call the fixed fee alone is ten times the price of the call. Layer 2 stablecoin transfers, at under $0.001 in gas, remove that fixed-fee floor. x402 uses the standard HTTP 402 status code, needs no proprietary wallet software, and settles in stablecoins; on Base and Solana settlement finality is sub-second. Older schemes relied on custom software and unstable units of account.

Pricing, workload fit and practical starting points

AgentCash defines API micropayments as sub-dollar payments settled per call, with a rough threshold below about $0.50 per call. Each payment is atomic, so the call either pays and succeeds, or it does not execute. Workloads it names as suited include inference endpoints such as language models, image generation and embeddings, which have variable per-call costs; data-enrichment APIs such as company lookup, geolocation and contact verification, at cents per query; and web scraping priced per page instead of a monthly plan. As of April 2026, AgentCash indexes one origin with 30 priced endpoints, at a median of $0.028 per call and a range of $0.002 to $0.440. There is no protocol minimum, so the practical floor is set by gas; on Base a transfer costs under $0.001. A single USDC balance covers all providers with no per-vendor signup, and a wallet can be created with npx agentcash. These figures come from a single indexed origin.

Human-era vs agent-era micropayments

Timeline

1. 1992
   HTTP 1 spec includes PaymentRequired 402 as a placeholder for charging schemesbuttondown.com
2. 1997
   HTTP/1.1 drops the details and marks code 402 reserved for future usebuttondown.com
3. 1999
   W3C Micropayments Working Group and IBM and Compaq platforms emergebuttondown.com
4. 2010
   Rita McGarth publishes Why I hate micropayments in Harvard Business Reviewbuttondown.com
5. 2025
   An official web monetization spec is launchedbuttondown.com
6. 2026-03
   Stripe and Tempo launch the Machine Payments Protocol with Tempo Mainnetforrester.com

Common pitfalls

• Fixed card fees break small prices: at roughly $0.30 plus 2.9% per transaction, the fixed fee alone is ten times the price of a $0.03 call.
• Price volatility made crypto-era pricing impractical. Settling in stablecoins, rather than volatile assets, is what AgentCash credits for making x402 practical.
• Agents need to transact independently only within predefined controls, so spending limits and authorization rules are part of any agent payment design.
• A published standard does not guarantee adoption: an official web monetization spec launched in 2025, yet few people have seen a request or paid a few cents to read a site.

Key takeaways

• Earlier micropayments failed because the payer was human; agents execute payment as a function call without hesitation.
• x402 uses HTTP 402 and stablecoin settlement on Layer 2, avoiding the card fee floor of $0.30 plus 2.9%.
• Per-call pricing suits inference, data-enrichment and scraping APIs, with a median of $0.028 per call in one index.

FAQ

How this page is made. Built from the full text of 5 sources found with the AISA Tavily API (advanced search), refreshed weekly. A language model organizes what those sources state into the blocks above; each block links the sources it draws on, and figures that do not appear in the sources are removed.