Account owners hold stablecoins and issue capped Virtual Wallets to their agents. Handle reservations open Tuesday; funding, onramps and agent spending arrive “in the coming months.”
Cloudflare launched Cloudflare Wallets on Tuesday, giving AI agents that run on its network a stablecoin balance and a human-readable name to present when they pay for APIs, content and MCP tools.
The product gives Cloudflare the buy side of agent payments a month after it built the sell side. Its Monetization Gateway, announced July 1, lets sites charge agents per request in stablecoins over x402, the protocol that repurposes the HTTP 402 status code for payments. Wallets is the account those agents pay from. Both sides run through a network that spans 337 cities and, by the company’s count, powers one in five websites.
x402 has settled 160.6 million transactions worth $41.2 million across seven chains and 18 tracked facilitators, according to Agent Economy, which counts transfers from known facilitator addresses on EVM chains and Solana. That averages about 26 cents per transaction. The tracker cautions that its totals include tests, infrastructure traffic and repeated service calls, and trackers using narrower facilitator lists report lower figures.
“When an agent shows up at your door, you need to know who sent it,” said Matthew Prince, Cloudflare’s co-founder and CEO, in the announcement. “Cloudflare can give agents a face — a link to the human or organization that owns them — so that trust, accountability, and real commerce can follow.”
Two Wallets, One Owner
Cloudflare split the product in two. Account Wallets belong to the human owners and operators of a Cloudflare account, who fund them, delegate spending and withdraw. Virtual Wallets are operated by API key and assigned to individual agents, spending within limits the Account Wallet owner sets.
The guardrails Cloudflare names are an allowance, an allow list and a maximum transaction size.
“Want to give every employee a $100 per week budget for AI inference?” the post asks. “Simply provision an Account Wallet with the right balance and create Virtual Wallets for each employee with that rule.” Spending that trips a threshold goes to a human: “When something anomalous happens, such as unexpectedly fast spending, a human will be able to review and confirm whether everything is operating as intended.”
The post was written by Will Papper, who works on agent payments at Cloudflare and co-founded onchain developer platform Syndicate.
Papper’s case for caps is that they make it easier to hand an agent money at all.
“If an agent is responsible for $10, you can worry less about its spending than if it is responsible for $1,000,” he writes. At x402 price points, $10 still buys a lot of attempts: “If an API only costs a few cents to try, then $10 is more than sufficient to pursue and evaluate many options.”
Handles Over Keypairs
The identity half of the launch is cloudflare.pay, where account owners can reserve a handle starting Tuesday. Agents can then optionally declare who runs them — the post’s example is research.example.cloudflare.pay, which tells a merchant the organization behind the request.
Cloudflare already lets agents register a cryptographic identity through Web Bot Auth, which uses keypairs. The handle is a label on top of that. “We are proposing a human-readable identifier for a not-very-readable keypair, similar to the URL and IP-address pairings used in DNS,” the post says.
Unidentified agents still get through. The post compares them to VPN users: “If someone is unidentified, they are not inherently untrustworthy, but they need to prove themselves more.” Traffic without a handle stays subject to the bot detection Cloudflare already sells, Turnstile and Bot Management.
Both Sides Of The Trade
Cloudflare has been assembling the pieces since last year. It announced the x402 Foundation with Coinbase in September 2025 and added x402 support to its Agents SDK and MCP servers. The Linux Foundation said in April it would host the standard, with 22 organizations signaling support, and launched it operationally on July 14 with 40 members. Cloudflare and Stripe are two of its 17 premier members, alongside Visa, Mastercard, Google, Amazon Web Services and Circle.
Cloudflare’s x402 documentation lists support for Base, Ethereum, Polygon, Optimism, Arbitrum, Avalanche, Solana, Aptos, Stellar and Sui, with USDC as the settlement asset and Coinbase’s public facilitator used in all of its examples. Stablecoin supply stands at $307.7 billion, with Tether’s USDT at $183.2 billion and Circle’s USDC at $72.2 billion, according to DefiLlama.
Other agent-payment plumbing arrived on the same schedule. Amazon Web Services and Coinbase wired x402 into CloudFront and WAF in June for publishers charging agents in USDC, and MoonPay open-sourced the Open Wallet Standard in March with PayPal and the Ethereum Foundation.
What Cloudflare Left Out
The post does not say which chains or stablecoins the wallets themselves will use, whether Cloudflare or a third party will custody the funds, what it will charge, or which onramp and offramp partners it is working with. It commits only to “simple ways to onramp and offramp funds within supported geographies, with self-funding via stablecoins available as an alternative for eligible users.” Neither the post nor the press release names a launch customer.
Handle reservations are the only piece live today. Funding, Virtual Wallet issuance and onramping are due “in the coming months,” per the press release.
Stephanie Cohen, Cloudflare’s chief strategy officer, framed the reasoning in an interview with Fortune: “The internet needs a different business model. In order to have a different business model, you need payments that actually will support that.”
