On August 4, 2026, Cloudflare announced two products, “Cloudflare Wallets” and “cloudflare.pay,” aimed at agents running on its own platform: the company’s stated goal is to attach a durable identity to those agents and let them make purchases1. On the receiving side, a business would learn whose authority an incoming request carries; on the agent side, spending would stay inside limits its owner has set, according to Cloudflare1.
Cloudflare frames the problem as an Internet designed for people, not agents. Its press release argues that a merchant receiving a request from an agent — one making a purchase, or opening a free trial — currently has no dependable way to separate a genuine customer’s assistant from someone abusing the system1. Older bot-detection tooling, the company argues, was designed around search crawlers and not around software that buys things as someone’s delegate; the result, in its telling, is that site operators are left with a choice between locking the door and hoping for the best1.
Identity: a unique web address on the account
The design has two layers, identity and payment. On the first, each Cloudflare account is to receive its own web address serving as a durable identifier1. That identity is then to be delegated down to individual agents, which is what would let the recipient of a request trace it back to the party that authorized it, according to the company1.
Co-founder and CEO Matthew Prince put the argument this way: “When an agent shows up at your door, you need to know who sent it. 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”1.
This assumes AI agents are treated not as standalone software but as someone’s delegate. Where conventional bot defenses asked whether a visitor was human, the question here becomes whose authority the visitor is acting on.
Payment: a central balance and per-agent wallets
The payment side is to be built from two kinds of wallet. Cloudflare describes an “Account Wallet” as a central balance that will hold stablecoins and handle receiving and managing them, from which owners will be able to assign a “Virtual Wallet” to an individual agent1.
Each Virtual Wallet is described as shipping with limits its owner defines: a cap on spending, a list of merchants the agent is allowed to buy from, and a maximum size for any one transaction1. Cloudflare’s own framing is that its wallets and IDs, combined with the Monetization Gateway, would round out both sides of a payment market for agents1.
That level of granularity matters to anyone running agents in production. The trouble with delegating work to an agent is rarely what it can do; it is what it does unprompted. The same concern surfaced when Gemini API’s managed agents gained hooks that can block tool calls, plus token budgets. Mechanisms to halt execution and mechanisms to halt spending are now arriving from different providers in quick succession.
An agent with payment authority also raises the payoff for attacking it. Prompt injection — slipping instructions into the external data an agent reads — has mostly been discussed in terms of data leakage and unauthorized actions, but once a wallet is attached, it becomes a path to direct financial loss. Spending caps and merchant lists can be read as a way to put a mechanical ceiling on that damage.
Right now, you can only reserve a handle
The timeline deserves attention. Cloudflare says handle reservation opens on the day of the announcement, while the rest — moving funds in and out, and issuing Virtual Wallets to agents — is slated for the coming months1. Handles can be claimed, and access notifications requested, at cloudflare.pay1.
Which stablecoins will be supported, and how onramping and offramping will work in practice, are not stated. Neither is the fee structure. The press release itself carries a forward-looking statements notice, and both the features and the timing are written as plans. For now this is best read as a stated direction plus a waitlist.
When “whose delegate” carries a price tag
There is something notable in this infrastructure for autonomous transactions coming from a general-purpose Internet provider rather than a payments company. Cloudflare sits in front of a large number of sites, which puts it in a position to hand the receiving business the fact of who authorized a given request.
Still, once agent behavior carries money, cleaning up after failures gets more complicated. Who bears responsibility when an AI acts without human instruction remains unsettled in US law, and having a spending cap is a separate question from who absorbs a loss incurred within it.
If you already run agents, the practical move for now is to reserve a handle and, in parallel, take stock of the permissions your agents already hold. There will be room to check whether the controls behave as described once real money starts moving.
Sources
- Cloudflare Gives AI Agents an Identity and a Wallet - Cloudflare press release (August 4, 2026)