What Are API Micropayments?
API micropayments are sub-dollar payments settled per individual API call, typically ranging from fractions of a cent to under a dollar, on a low-cost blockchain. Each payment is atomic: the call either pays and succeeds, or it does not execute.
What counts as an API micropayment
The rough threshold is a charge below about $0.50 per call. What sets it apart is individual settlement on a low-cost chain rather than a monthly invoice. The payment is atomic, so there is no partial state: the request pays and returns data, or it does not run at all.
Why credit card rails break below a dollar
Card processors charge roughly $0.30 plus 2.9% per transaction. On a $0.03 call that fixed fee alone is ten times the price of the call. Bundling into a subscription hides the problem but adds its own friction: credit checks, billing disputes, and a separate account per vendor. Layer 2 stablecoin transfers, at under $0.001 in gas, remove the fixed-fee floor.
How stablecoins and x402 make it practical
The technical foundation is x402 over the HTTP 402 status code. The server responds with a price, currency, and address, the agent's wallet signs a transfer, it retries with an X-Payment header, and the server verifies and returns the data. On Base and Solana, settlement finality is sub-second, and AgentCash supports Base, Solana, and Tempo.
Use cases driving adoption
Inference endpoints like language models, image generation, and embeddings have variable per-call costs that suit micropayments. Data-enrichment APIs such as company lookup, geolocation, and contact verification cost cents per query. Web scraping can move to pay-per-page instead of a monthly plan, so you stop paying for capacity you do not use.
Historical attempts and what changed
HTTP 402 was reserved in 1997, but no standard emerged. Efforts in the 1990s and 2000s, like Millicent, PayWord, and W3C proposals, failed on proprietary wallets and unstable units of account. The crypto era added price volatility that made pricing impractical. The breakthrough was stablecoins, plus Layer 2 rollups, plus AI agents that actually need programmatic, permissionless payments.
How AgentCash aggregates micropayment APIs
A single USDC balance covers all providers, with no per-vendor signup. Create a wallet with npx agentcash, fund it, and call any x402-protected endpoint. AgentCash indexes one origin with 30 priced endpoints today, at a median of $0.028 per call and a range of $0.002 to $0.440 as of April 2026, plus an MCP server for coding agents.
Related
References: the HTTP 402 status code on MDN and the x402 protocol site.
Frequently asked questions
What is the smallest viable micropayment?
There is no protocol minimum, so the practical floor is set by gas costs. On Base a transfer costs under $0.001, which makes a $0.002 call viable. The lowest price AgentCash has observed across its indexed endpoints is $0.002, and the median sits at $0.028 per call today.
How is this different from PayWord or Millicent?
x402 uses the standard HTTP 402 status code, needs no proprietary wallet software, and settles in stablecoins on Layer 2 chains. The older protocols relied on custom software, unstable units of account, and had no deployment network. Stablecoins and cheap Layer 2 settlement are what make x402 practical now.
Do I need a minimum USDC balance?
No minimum is enforced. You just need enough to cover the calls you make plus a small amount of gas, and a few dollars is sufficient for most cases. Because each call settles individually, you can start small and top up the balance whenever it runs low again.
Put it into practice
AgentCash gives your AI agent a wallet to pay for any payment-protected API — no keys, USDC on Base.