On August 4, Cloudflare announced Cloudflare Wallets and a companion identity service called cloudflare.pay, giving AI agents deployed on its network a verifiable identity and a stablecoin-funded budget they can spend within limits set by a human owner. Account holders can now reserve a handle at cloudflare.pay. The ability to actually fund a wallet, delegate spending to an agent, and complete a transaction is expected to follow in the coming months, according to the company.
The launch addresses a problem that has been building for a while. AI agents now routinely browse websites, call APIs and even attempt purchases on behalf of the people or businesses that deployed them, but the tools websites use to tell a legitimate agent from a scraper or a bad actor were mostly built for search engine crawlers, not autonomous buyers. Matthew Prince, Cloudflare’s co-founder and CEO, framed the gap directly: “When an agent shows up at your door, you need to know who sent it.”
How the Two-Part System Works
Cloudflare split the product into two layers. The identity layer gives every Cloudflare account a unique, human-readable web address, similar in spirit to how a domain name maps to an IP address. Account owners can extend that identity down to individual agents, so a merchant receiving a request can trace it back to the organisation or person responsible, rather than treating it as anonymous traffic.
The payment layer sits on top of that identity. An Account Wallet holds stablecoins on behalf of the human account owner, who can then create Virtual Wallets for specific agents. Each Virtual Wallet carries its own guardrails, including a spending cap, a list of approved merchants and a maximum size for any single transaction. Cloudflare’s own example describes an internal use case, setting up a 100-dollar weekly Virtual Wallet per employee for AI inference costs, with anything unusual flagged to a human rather than executed automatically.
The payment rail underneath this is x402, a protocol that Cloudflare and Coinbase jointly developed and later handed to an independent x402 Foundation. It repurposes the long dormant HTTP 402 Payment Required status code so a server can ask an agent for a stablecoin payment mid-request, get paid, and hand over the resource, without a human clicking through a checkout page. Cloudflare had already built x402 into its Agents SDK and its Monetisation Gateway, a tool that lets website owners charge agents for scraping or querying their content. Wallets and cloudflare.pay complete that picture by giving agents something to pay with.
What the press release leaves out
The announcement is genuinely a milestone for the young field of agentic commerce, but it is worth separating what shipped today from what Cloudflare is promising. What is live right now is handle reservation. Nobody can fund a wallet, issue a Virtual Wallet or complete a real transaction yet, and Cloudflare has not named a public launch date, a list of onramp geographies, or any merchant or integration partner who has committed to accepting these payments. That is a normal way to stage a product launch, but it is a meaningfully smaller step than AI agents can now pay for things, which is closer to how the release frames it.
There is also a structural point the press release does not raise. x402 settlements are final. Once a stablecoin payment clears on-chain, there is no chargeback and no dispute window, because the protocol was not built with the card network reversal process that consumers are used to. That is a deliberate design choice, since agents and APIs do not generate the kind of disputes credit cards were built to arbitrate, but it is a real difference from competing agentic payment efforts. Mastercard’s Agentic Tokens and OpenAI’s Shared Payment Tokens both keep dispute rights intact because they ride on card rails rather than stablecoin rails. Businesses evaluating Cloudflare Wallets for real purchases will want to build refund logic into their own application, since there is no network-level safety net to fall back on.
Cloudflare is not the only company chasing this market either. Google has folded x402 into its own Agent Payments Protocol for agents running on Google Cloud, and Circle has built sub-cent Nanopayments on the same rail using USDC. Coinbase, which created x402 and still runs its largest facilitator, reported tens of millions of agent transactions on the protocol earlier this year. Cloudflare’s advantage is reach rather than being first. Its network already sits in front of a large share of global web traffic, so wiring identity and payments into that layer could put the capability in front of far more sites and agents than a standalone payments company could reach on its own.
What It Means Going Forward
For businesses running or planning to run AI agents, the practical takeaway is to treat this as a preview rather than a finished product. Reserving a cloudflare.pay handle now costs nothing and locks in a namespace, which is worth doing if the brand name matters. Actually budgeting real money for agents to spend autonomously should wait until Cloudflare publishes onramp details, geographic availability and, ideally, a list of merchants willing to accept the payments. The identity half of the announcement, giving agents a traceable link back to their owner, is likely to matter sooner, since it addresses a bot detection problem that already exists today, independent of whether the wallet side ships on schedule.
