Cloudflare has started handing out wallet handles to its customers, and the pitch sounds like a convenience feature: let your AI agent buy the API it needs without pinging you for a credit card. Read the fine print, though, and the more interesting product is the ceiling.
For the first time, "how much money can my agent lose before someone notices" becomes a setting you configure rather than a question you answer after the fact.
The company announced Cloudflare Wallets today. Right now, you can only claim a handle — a unique username that identifies you to merchants. Funding, spending, and the rest arrive later.
The problem: agents keep giving up
Cloudflare's framing of the gap is blunt. An agent that wants to try a new API has to work through a login page built for humans, get a person to attach a payment method, generate an API key, and then figure out how to call the thing. Agents lack a stable identifier and any native way to pay, so they routinely abandon the attempt and hand registration back to a human. Comparing a dozen services becomes a chore nobody does.
Two wallets, one of them on a leash
Account Wallets belong to people. They hold funds, delegate spending, and pull money back out. Virtual Wallets belong to agents and operate through API keys, and this is where the guardrails live: an allowance, an allow list of approved merchants, and a maximum transaction size. An agent spends only inside those limits, capped by whatever the Account Wallet owner sets.
Cloudflare argues the constraint is liberating. An agent responsible for $10 needs far less supervision than one responsible for $1,000 — and if an API costs a few cents to sample, $10 buys a lot of exploration. Anyone who blows through their cap can request a manual override, and unusual spending patterns trigger a human review rather than a silent drain.
For security teams, that reads differently: a spending policy is a blast radius control. A prompt-injected or simply confused agent can only burn what its Virtual Wallet holds.
Payments ride on HTTP 402
The plumbing is x402, the open protocol that attaches payment to an HTTP request by finally putting the long-dormant 402 "Payment Required" status code to work. It pairs with Monetization Gateway, Cloudflare's seller-side product announced July 1, which lets customers charge per request for pages, datasets, APIs, and MCP tool calls. Wallets supply the buyer side of that market. Settlement happens in stablecoins — dollar-pegged tokens cheap enough to make sub-cent transactions viable.
Cloudflare Chief Strategy Officer Stephanie Cohen told Fortune that roughly 57% of web traffic is now bots, and that the shift demands a rebuild: "every interaction on the internet is a chance for commerce," she said.
Agents get a name, optionally
The second half of the announcement is identity. Wallets link to a Cloudflare account through cloudflare.pay, so a research agent might live at research.example.cloudflare.pay — enough for a merchant to know which organization it answers to. Cloudflare compares the idea to DNS: a readable name bolted onto an unreadable keypair, building on Web Bot Auth, which already lets agents register identity cryptographically.
Declaring identity stays optional. Cloudflare's own analogy is VPN traffic — unidentified does not mean untrustworthy, but it does mean proving yourself harder. Expect merchants to start pricing that difference.
What to do now
Claim the handle. Namespaces are first-come, and an agent identity tied to your brand is worth locking down before someone else does. Beyond that, the open questions are operational: which geographies get fiat on-ramps, who qualifies for stablecoin self-funding, and which merchants actually accept the wallet at launch.
If you run APIs or content agents that might buy, now is the moment to decide whether you will serve anonymous agents, identified ones, or charge them differently.