Cloudflare launched Cloudflare Wallets on August 4, giving AI agents that run on its network a stablecoin balance and a human-readable name. The move adds the buy side of agent payments a month after its Monetization Gateway gave merchants a way to charge agents per request over x402, the protocol that repurposes the HTTP 402 status code for payment.
Highlights#
Two wallets, one owner. Account Wallets belong to human operators, who fund them and withdraw. Virtual Wallets run by API key and are assigned to individual agents, which can spend only within an allowance, an allow list, and a per-transaction cap the owner sets.
Spending caps as a feature, not a limitation. The company argues bounded budgets make agents easier to trust with money in the first place. If an API call costs a few cents, a ten-dollar balance still covers many attempts, and anomalous spend is routed to a human to review.
Names on top of keys. Account owners can reserve a cloudflare.pay handle that an agent declares when it pays, so a merchant can see the organization behind the request, for example research.example.cloudflare.pay. It sits on top of the cryptographic keypairs Cloudflare already issues through Web Bot Auth, the way a URL sits on top of an IP address.
Volume is already running. Per the Agent Economy tracker, x402 has settled roughly 160.6 million transactions worth $41.2 million across seven chains and eighteen facilitators, averaging about 26 cents per transfer. The tracker cautions that its totals include tests and infrastructure traffic.
Why it matters#
CEO Matthew Prince framed the core problem plainly: when an agent shows up at your door, you need to know who sent it. Wallets plus handles are an identity and spend-control layer built into infrastructure that already powers one in five websites, which is exactly the trust surface agent commerce needs before it scales.