How AI Agents Use Crypto to Pay for Data and APIs
- AI software can now use digital money to pay for web searches or computer data in under a second without needing a human to type in a credit card or set up an account.
- Traditional credit card companies charge around 30 cents per purchase, which is too expensive when a bot only wants to buy a single 10 cent piece of information. Bots use stablecoins like USDC on fast networks because the transfer fees cost less than a penny.
- When a bot asks a server for data, the server replies with a special code saying the cost is 20 cents. The bot automatically sends the payment, and the server hands over the data.
- Major tech and finance companies like Coinbase, Amazon, Cloudflare, Stripe, Visa, and Google are setting up systems so web servers can charge AI bots per request.
- While big numbers get reported, analysts found that up to 89% of the transactions are just programmers testing systems or software trading with itself. Only about 15 million dollars in real purchases had happened through early 2026.
- Unlike regular credit cards, crypto payments cannot be refunded if something goes wrong. Plus, because AI software is not a human, the legal responsibility for any overspending belongs entirely to the person or company that owns the digital wallet.
Do Truly Autonomous AI Agents Exist?
AI agents pay for data and APIs with crypto by sending small stablecoin payments inside ordinary web requests. The most used method is x402, an open standard that revives the HTTP 402 “Payment Required” status code. The agent requests a resource, the server replies with a price, the agent signs a USDC payment, and the server returns the data. No account, card, or API key is needed.
That flow is live today, though the real money moving through it is far smaller than headline figures suggest. Five points cover most of what follows:
- The standard is settled. Coinbase published x402 in May 2025 and finished handing it to the Linux Foundation on 14 July 2026, where 40 members now govern it.
- The money is stablecoins. Almost all settlement happens in USDC on low fee chains such as Base, Solana, and Polygon.
- The buyers are developers. Agents mostly pay for data lookups, web scraping, model calls, and search results, each costing a few cents.
- The volume is mostly noise. Independent analysts at Artemis removed about 89% of reported value as wash trading and testing.
- The rules are missing. Software has no legal personhood, so the person or company that funded the wallet carries the liability.
| Question | Short answer |
|---|---|
| What is it? | Machine payments for web resources, settled in stablecoins over HTTP |
| Main standard | x402, governed by the x402 Foundation under the Linux Foundation |
| Typical payment | Around $0.20 to $0.30 per call |
| Settlement asset | USDC, mostly on Base, Solana, and Polygon |
| Protocol fee | None, though facilitators and blockchains charge small amounts |
| Verified cumulative value | About $15.0 million to 21 April 2026, after filtering |
| Biggest gap | No dispute process, no chargebacks, and no agreed liability rules |
What Does It Mean for an AI Agent to Pay With Crypto?
An AI agent pays with crypto when it holds a wallet and spends from it without asking a person first. The agent still works inside limits its owner sets, such as a monthly cap or a list of approved sellers. Within those limits, it buys what it needs and keeps working.
Those purchases are small and frequent. A research agent might buy one company record, then a web page, then a model call, spending a few cents each time. Over a month those cents add up to a normal software bill.
Why Cards and API Keys Break for Software Buyers
Every payment method most people use assumes a human is present. Someone types a card number, clicks a confirm button, or signs up for a plan. When the buyer is a piece of software, each of those steps becomes a blocker.
Then there is the cost of the payment itself. A card charge carries a fixed cost of roughly 30 cents plus a percentage, so a payment worth a tenth of a cent cannot cover it. Because of that, providers bundle usage into subscriptions and prepaid credits instead.
Bundling then creates its own friction. An agent calling 30 different services would need 30 accounts, 30 billing cycles, and 30 keys to store and rotate. If the credits run out at 3am, the agent stops and waits for a person.
What Agents Actually Buy Today
So far, the paid services with real traffic are developer tools. StableEnrich sells per request access to lookup APIs including Firecrawl, Exa, and Google Maps. BlockRun bundles more than 55 large language models and data APIs behind per call billing. HYRE Agent sells decentralised finance data.
Other sellers follow the same shape. CoinGecko offers market data per request, Freepik sells images, and Nous Research bills per inference for its Hermes model. Each product replaces a subscription with a price per use.
The Words You Need to Know
Before going further, four terms repeat throughout this topic, so it helps to fix them early.
- Agent: An agent is software that pursues a goal, calls tools, and takes actions with little human input.
- Stablecoin: A stablecoin is a token designed to hold a steady value, usually one US dollar. USDC is the one used in nearly all agent payments.
- x402: x402 is the open standard that carries the price and the payment inside a normal web request.
- Facilitator: A facilitator is the service that checks a payment is valid and settles it on a blockchain, so the seller never touches crypto plumbing.
How Does the Payment Actually Work?
Now that the words are clear, the mechanics are easier to follow. The whole exchange happens inside one request and reply cycle, and it usually finishes in about a second.
The Four Steps of an x402 Payment
That cycle breaks into four steps, and every one of them is machine readable.
- The agent sends a normal request to a paid address.
- The server answers with status code 402 and a small payload. That payload names the price, the accepted token, the chain, and the wallet to pay.
- The agent signs a payment for that exact amount and sends the request again, with proof of payment attached.
- A facilitator checks the proof and settles it onchain. The server then returns the data.
Nothing here needs a checkout page or a redirect. The payment travels in an HTTP header, which is why any web server can take part.
Who Are the Four Parties?
Behind those four steps sit four roles, and mixing them up causes most of the confusion.
First, the buyer is the agent with the wallet. The seller is whoever runs the API, dataset, or page. The blockchain is where value actually moves. The facilitator sits in the middle and does the crypto work for the seller.
Sellers can skip the facilitator and settle payments themselves. Most choose not to, because running that layer means running blockchain systems they would rather avoid.
Which Chains and Coins Settle These Payments?
Once those roles are in place, the money still has to move somewhere, and USDC does nearly all the work. Base was the early default because its fees are close to zero, and Solana and Polygon then took large shares of traffic. Token Terminal counted about 14 million x402 transfers in the 30 days to mid August 2026, with 7.3 million on Base and 5.6 million on Polygon.
The choice of chain matters because of cost and speed. A payment worth a fraction of a cent only makes sense when the fee is smaller still, and when the transfer settles in under a second.
What Does It Cost to Send and Receive?
Because the protocol is open, x402 itself charges nothing. Costs come from three other places, and they are small.
| Cost | Who pays | Typical amount |
|---|---|---|
| Blockchain fee | Buyer or facilitator | A fraction of a cent on Base, Solana, or Polygon |
| Facilitator fee | Seller | Coinbase reports a free tier, then about $0.001 per transaction |
| The resource itself | Buyer | Around $0.20 to $0.30 on average, with many calls far below that |
Two extra costs are easy to miss. Money sitting in an agent wallet earns nothing, because the GENIUS Act bans yield on payment stablecoins in the United States. Teams also carry the engineering cost of spending limits, logging, and reconciliation, which is where most of the real work sits.
Which Payment Standards Compete, and How Do They Fit Together?
Those costs explain why crypto rails appeal for tiny payments, but x402 is one layer of a taller stack. Four standards launched within about a year, and they answer different questions.
x402, MPP, AP2 and ACP Compared
First, the table below covers the four standards with the most public traction. Several smaller ones exist, so treat this as the main field instead of a complete list.
| Standard | Backer | Launched | What it handles | Best fit |
|---|---|---|---|---|
| x402 | Coinbase, now the Linux Foundation | May 2025 | Payment per request over HTTP | APIs, data, content, tool calls |
| MPP | Stripe and Tempo | March 2026 | Session based spending, settled at the end | Metered use across a whole task |
| AP2 | Google, with 60 or more partners | September 2025 | Proof that a user approved the spend | Purchases needing an audit trail |
| ACP | OpenAI and Stripe | Rolled out in ChatGPT in early 2026 | Checkout with merchants | Shopping inside a chat |
Two patterns run through that table. First, only x402 and MPP move the money, while AP2 and ACP handle permission and checkout. Second, they combine well, so a production system often uses AP2 to prove approval and x402 to settle.
Where Cards Still Win
While those standards fight over machine payments, card networks have kept the larger baskets. Visa and Mastercard both built agent products, and a joint Visa and Artemis report from 16 July 2026 argued that stablecoins will carry small machine payments while cards keep bigger purchases.
That split makes sense for one practical reason. Cards offer chargebacks and dispute processes that stablecoin payments have no equivalent for. When an agent buys a $400 flight, that protection matters more than a saving of a few cents in fees.
How Cloudflare and AWS Turned Web Servers Into Toll Booths
Meanwhile, the clearest sign that this is becoming standard came from two infrastructure giants. AWS made x402 payments generally available in CloudFront and WAF on 15 June 2026, so any site behind them can charge agents per request. Cloudflare announced its Monetization Gateway on 1 July 2026, covering pages, datasets, APIs, and tool calls.
Cloudflare then added the buyer side. On 4 August 2026 it announced Cloudflare Wallets, which hold funds, apply spending caps, and give an agent a readable identity.
Behind both moves sits one number, which is traffic. Cloudflare reported that AI related crawlers made 52% of crawler requests in June 2026, up from 22% in spring 2025, and from 15 September 2026 its new defaults block training and agent bots on ad supported pages.
How Much of the Reported Volume Is Real?
Those launches make the plumbing sound finished, so the honest question is how much money actually flows through it. The answer depends heavily on who is counting.
The Headline Numbers
Start with the public figures, which are large. Chainalysis found that x402 payments on Base passed 100 million cumulative transactions in about three quarters, rising from almost nothing in mid 2025. Coinbase has reported roughly 165 million transactions and about $50 million in cumulative value by late April 2026.
Chainalysis also found that the mix is shifting upward. Payments above $1 grew from 49% of value in early 2025 to 95% by early 2026, while payments between 10 cents and $1 fell from 46% to 4%.
What Independent Analysts Found
Yet onchain analysts reach much smaller numbers. Artemis Analytics built a filter that flags wallets trading with themselves or cycling funds in a loop. Applied to the Visa and Artemis July 2026 report, raw totals of about $135.7 million across 178.3 million transactions fell to $15.0 million across 109.6 million transactions.
That filter removed roughly 89% of the value and 39% of the transactions. Artemis counts a wallet as a genuine seller only when it has taken at least three filtered payments from at least two separate buyers.
Other reporting points the same way. Some analysts found in March 2026 that real daily volume sat near $28,000, with an average payment of about $0.20 and roughly half of activity looking artificial. An Artemis analyst summed it up in February 2026 by calling the boom “still mostly a mirage.”
Which Numbers to Trust
So the gap between sources is the story. For one 30 day window in early 2026, x402.org showed about $24 million, Allium Labs showed just over $3 million, and Artemis showed under $2 million. That is an order of magnitude between measurements of the same period.
Because of that spread, three habits help when reading any figure here.
- Check the filter. A number is only useful when the source explains what it removed and why.
- Separate counts from value. Transaction counts are inflated by cheap testing loops, while value is a better guide to real trade.
- Watch conversion instead of totals. Chainalysis found tester to payer conversion improved fourfold in six months, which says more about adoption than any headline.
Some inflation is normal at this stage. Coinbase has argued that open standards invite experiments, and Artemis expects the artificial share to fall as teams move from testing into production.
What Are the Risks, Rules and What Happens Next?
Measurement is one gap, and the legal and security gaps are wider still. This is the part that decides whether finance teams and regulated firms can use these rails at all.
Who Is Liable When an Agent Overspends?
Start with liability, because software has no legal personhood. An agent cannot sign a contract or carry legal responsibility. Responsibility falls to whoever deployed the agent and funded its wallet.
That places the burden on controls. Spending caps, approved seller lists, session limits, and full logs are the practical answer, and platforms such as AWS Bedrock AgentCore Payments and Cloudflare Wallets now build them in.
What the Rules Say Right Now
So far, no major jurisdiction has written rules for spending by software. What exists instead is stablecoin regulation that shapes the money underneath.
- United States: The GENIUS Act, signed on 18 July 2025, set the first federal framework for payment stablecoins. It treats issuers as financial institutions under the Bank Secrecy Act, requires know your customer and sanctions programmes, and bans interest on payment stablecoins.
- European Union: MiCA governs stablecoin issuers and crypto service providers, so an EU firm building agent payments needs to check whether its role triggers authorisation.
- Everywhere: Identity of the agent remains unsettled. Work on verified agent identity is early, and firms such as Visa and Mastercard are building their own checks.
Because of those gaps, anyone in a licensed business should treat agent payments as a live compliance question.
Security and Money Laundering Risks
Security carries its own set of problems. Payments that settle instantly and cannot be reversed create obvious openings. A hijacked or prompt injected agent can spend real money before anyone notices, and there is no chargeback to undo it.
Analysts have also flagged laundering risk. High frequency machine payments split value into thousands of tiny transfers, which is exactly the pattern that makes tracing harder.
Beyond the legal questions, the protocol has gaps of its own. There is no agreed dispute process, no trust score to tell an agent whether a seller is worth paying, and no large merchant has yet added x402 as a visible consumer payment option.
So, How Do AI Agents Use Crypto to Pay for Things?
So the plumbing for machine payments now works, and it is backed by an unusually broad group covering Coinbase, Cloudflare, AWS, Stripe, Visa, Mastercard, and Google. An agent can price a resource, pay for it, and use it in about a second, with no account and no card.
What has yet to arrive is the demand. Filtered value across the whole protocol reached about $15 million by April 2026, which is a rounding error next to card networks, and most sellers are still developer tools serving crypto native buyers.
For a business, the sensible move is to prepare without overcommitting. API providers can add a 402 priced endpoint cheaply and learn from the traffic. Teams building agents should set hard spending limits before the first payment, because the liability sits with them and no refund exists.