How AI agents pay for APIs: the pay-per-call model

2026-09-20 · tech

AI agents need data from other services, but they cannot fill in a checkout form. A growing answer is pay-per-call: every API request carries its own tiny payment, usually a few fractions of a cent, settled in a stablecoin.

How it works

The best-known open version of this idea is x402, a payment protocol originally built by Coinbase. The flow is simple:

• An agent requests a resource, for example GET /cve/CVE-2024-xxxx.
• The server answers 402 Payment Required with the price and a wallet address.
• The agent signs a stablecoin transfer, typically USDC on Base, and retries with proof of payment.
• The server verifies the payment and returns the data.

No accounts, no API keys, no monthly invoices. Each call pays for itself.

Why it matters

• Micropayments finally work. Credit-card fees make a $0.002 charge impossible. On a low-fee network like Base, settlement costs a fraction of a cent.
• Agents become customers. A coding assistant, a security scanner, or a research bot can buy exactly the data it needs, when it needs it.
• Small publishers can sell data. You do not need a sales team or a billing department to monetize an API. A pricing file and a wallet address are enough to start.

What to watch

Pay-per-call is still early. Standards for pricing discovery, receipts, and refunds are evolving, and most directories that list paid APIs are new. But the direction is clear: as more software is operated by agents rather than humans, machine-to-machine payments stop being a novelty and start being infrastructure.