Cloudflare's agent wallet is not the part that shipped

Cloudflare has built a business out of deciding which automated traffic is allowed to reach somebody else's website. On 4 August it announced two products whose purpose is to let automated traffic pay for things.

The products are Cloudflare Wallets and cloudflare.pay [1]. The wallet is the headline. It is not the thing you can use this morning.

What was announced

The design splits the money in two. An Account Wallet sits with the human or the organisation, holds stablecoin balances, and delegates spending to Virtual Wallets, which are what an agent operates through an API key [2]. Each Virtual Wallet carries an allowance, an allow list of merchants and a ceiling on any single transaction, so an agent's worst afternoon is bounded by a number its owner typed in [1].

Underneath it is x402, which attaches a stablecoin payment to an ordinary HTTP request using the 402 status code that has sat in the specification, unused, for most of the web's life [2]. Fortune describes x402 as an open-source protocol developed by a consortium including Coinbase, Cloudflare and Stripe [3].

What is actually available today

Handle reservation at cloudflare.pay opened on the day of the announcement. Funding a wallet, taking money back out, and issuing Virtual Wallets to your agents are all described as arriving in the coming months [1].

That is a schedule rather than a failing, and a stated schedule is the most useful line in any launch post. But it changes what the story is. Cloudflare has not put money in front of agents this week. It has opened a register of names and invited you to take yours.

Matthew Prince, Cloudflare's co-founder and chief executive, argued the identity case rather than the payments one, saying the internet is shifting from human-driven browsing to agent-driven commerce and the infrastructure needs to keep up [1]. Speaking to PYMNTS he was plainer: when an agent turns up at your door, you need to know who sent it [4].

Cloudflare's chief strategy officer told Fortune that roughly 57 per cent of web traffic is bots [3]. Read that as one firm's measurement taken from its own vantage point rather than a settled industry number. But that vantage point is the whole case for doing this. A company sitting in front of that much traffic is unusually well placed to become the thing that names it.

The second agent wallet in eight days

MoonPay launched PayBox on 29 July, a non-custodial vault that plugs into Claude and ChatGPT and lets an agent prepare a transaction the user then approves with a passkey [5]. It ships an Always Ask mode and an Autonomous mode bounded by limits the user sets, and it uses x402 for payments outside crypto rails [6]. Neeraj Prasad, chief engineer at MoonPay Labs, framed it directly against the platforms, saying the giants are building agentic payments inside their own walls while MoonPay's bet is your own money on open rails [5].

Two agent wallets in eight days, neither of them custodial, both reaching for the same protocol. The custody question is being treated as settled. Nobody is going to hand an agent a card number, and everybody has independently concluded that the answer is delegation with a ceiling.

Read from the rails

I spent years on the operations side of payments, and the incidents that actually hurt were never about a payment being too large. They were about nobody being able to say afterwards who authorised it. Reconstructing that chain is the job. The amount ends up as a line near the bottom of the report.

Both of these launches lead with the spending cap, because a cap demonstrates beautifully. You set a limit, the agent reaches it, the agent stops. It is legible from the back of a room. It is also the least interesting control in the set, because a cap tells you how much was lost and nothing at all about who is answerable for it.

The control worth wanting is the record. When an agent buys something and a human disputes it three weeks later, the useful question is not whether the purchase sat inside its allowance. It is whether the chain from human to agent to merchant can be rebuilt by somebody who was not in the room at the time. Cloudflare's identity layer is the first of these that is visibly trying to answer that, which is why the handle is the news and the wallet is not.

So go and claim the handle. Not because the wallet is coming, but because handles are first come first served, and registries like that fill up well before the product they point at exists.

Everybody is building the thing that stops an agent spending too much. The harder problem is proving, weeks later, who told it to spend at all.