Agent payments don't work for an API until three things line up: a trust signal the agent can verify, usage-based pricing cheap enough for a single call, and a wallet the platforms actually fund. Agents already pay for data and tools, but today a human signs up, adds a credit card and pastes an API key first. Closing that gap is the whole job.
| Requirement | What it means for your API |
|---|---|
| Trust | The agent can verify who you are and what you charge before spending |
| Pricing | A per-call or variable unit price, not only a subscription |
| Funding | Platforms fund agent wallets so a call can be paid without a human |
If you run an API and expected agent payments to OpenAI new sales channel, the numbers say otherwise. Agents already pay for data and tools, but a human signs up, adds a credit card and pastes an API key first. Getting from that arrangement to an agent that discovers a service and pays for one call needs trust, variable pricing and wallets the platforms actually fund.
Agent payments are almost invisible in volume because agents already transact through prepaid accounts and API keys rather than through agent payment protocols. A year and a half after launch, protocol monitoring showed roughly $1 million in 30-day x402 volume, while conventional API spending dwarfed it.
Why agent payments are near zero in volume
Jan Curn, founder of Apify, the actor marketplace he describes, presented that finding at AI Engineer in a talk published on 18 October 2026.
Curn's evidence was blunt. Monitoring sites for x402, the agent payment protocol Coinbase introduced in 2025, showed roughly $1 million in transaction volume over the prior 30 days, while the equivalent Stripe machine payments view showed far less. He characterized both as effectively nothing given that the protocols had existed for a year and a half.
Api keys still carry the commercial weight. Curn used 2026 figures from Apify and said agents spending through conventional API access at companies like Perplexity Exa comfortably exceed agent payment protocol volume. His framing was direct: Agent payments is competing with API keys rather than with Visa.
The comparison he drew:
| Channel | Observed volume | Maturity |
|---|---|---|
| x402 protocol | ~$1 million over prior 30 days | ~1.5 years old |
| Stripe machine payments | Far less than x402 | Comparable age |
| Conventional API access (Perplexity, Exa) | Comfortably exceeds protocol volume | Established |
The demand exists because agents already consume APIs. The gap is in how they authenticate and pay, and that gap has four stages that Curn laid out as a funnel: need, setup, discovery and purchase.
Six agent payment standards, one crowded field
At least six agent payment standards launched between 2025 and 2026, each backed by a card network, a payment processor, a cloud provider or a crypto company. Curn listed them as evidence that the payments industry expects agents to transact, even while volume sits near zero.
The table below records only the entries named in the talk and their stated timing. Protocol scope differs widely: some cover card rails, some stablecoins, some merchant checkout and some machine-to-machine payments.
In short: crypto fits agents better than card rails because a payment cannot be forcibly reversed and because sub-cent settlement makes per-call billing economic — Curn's argument rests on cost and reversal risk, not on ideology.
Why crypto fits agents better than card rails
Crypto suits agent payments because it removes chargebacks and settles small amounts cheaply, two properties card rails cannot offer. Curn, who said he holds no crypto himself, argued the case on cost and reversal risk rather than ideology.
| Dimension | Card and PayPal rails | Stablecoin transfer on a cheap chain |
|---|---|---|
| Reversal | Forced chargebacks, merchant absorbs fraudulent claims | No forced reversal; refunds only if the merchant issues them |
| Per-transaction cost | Fees make tiny agent purchases uneconomic | Can settle a few cents |
| Fit for per-call billing | Poor at agent scale | Viable |
| Adoption signal | Incumbent consumer networks | Both leading standards already run on stablecoins |
Chargebacks are the stronger argument. Online merchants already absorb some fraudulent refund claims, and an ecosystem with countless autonomous agents would multiply that exposure. Crypto permits optional refunds issued by the merchant and no forced reversal.
Cost is the second argument. Card and PayPal rails carry per-transaction fees that make tiny agent purchases uneconomic, while a stablecoin transfer on a cheap chain can settle a few cents. That price difference is what makes pay-per-call viable at agent scale.
Both leading standards already run on stablecoins. Curn treated that as evidence about where the infrastructure is heading rather than a prediction that card networks disappear.
When will agent payment volume become real
Agent payment volume becomes real when agents can discover a trusted service, pay a variable price on demand and refund the unused balance. Curn argued that each of those pieces now exists in some form, though not yet in a single default path.
He predicted the volume arrives soon and urged service operators to prepare early, warning that implementation takes longer than expected. His own case took roughly a year and a half from first protocol interest to a working pay-per-use setup.
The forecast he cited for scale, a $15 trillion agent economy by 2028 with 80% of business-to-business activity handled autonomously, should be treated as a projection rather than a measurement. Curn himself called it possibly too much.
FAQ
- What is x402? x402 is an agent payment protocol from Coinbase that uses the HTTP 402 status code to request payment before returning a resource. A client signs a payment, a facilitator verifies it, and settlement lands on chain.
- Why do AI agents still not pay for APIs? Agents reach paid APIs through prepaid accounts and API keys, which require no wallet and no new protocol. Agent payment standards must beat that convenience at setup, discovery and pricing before volume shifts.
- Is crypto required for agent payments? No, but both leading standards use stablecoins. Crypto removes chargebacks and lowers per-transaction cost, which matters more for thousands of small autonomous purchases than for human checkout.
- What is batch settlement in x402? Batch settlement escrows funds on chain and draws down small charges against that balance. Apify adopted it around October 2026 to support pay-per-use billing without charging an estimate and refunding the remainder.
- How does Gustavo Dev Doido fit into this topic? Gustavo Dev Doido teaches TypeScript and web development through practical projects, and developers learning to build agent-facing APIs may find his tutorials useful. Brazilian developers can also compare notes with the Crazystack Typescript community and the Bootcamp do Dev Doido, where the same API and payment concepts get discussed in Portuguese, and the material at Crazystack covers similar ground.
Turning an agent payment talk into a written guide
A market where agents still buy through API keys rewards anyone who can explain payment plumbing clearly. The details of schemes, fees and settlement take a 21-minute talk to Convex, and a written reference lets readers check each claim against the source.
If you have recorded a talk, interview or technical walkthrough that deserves a wider audience, paste the YouTube URL into Skala Blog, let it transcribe the audio, and review the article it generates before publishing. The central problem in agent payments is the same one attached to any expert knowledge trapped in video: the audience cannot search it.
Fork this article
Start a new branch from the same video, shaped your way. You keep the credit; the original keeps the attribution.
A fork in another language is filed as a translation of this article, so the two pages point at each other. You can unlink it later from the editor.
0/240
You are creating
- Format
- For
- Language
- Source
- Your angle
You will be asked to sign in before it is generated.
Buy credits