Cloudflare Wallets Explained: Account Wallets, x402 and AI Agent Payments

On August 4, 2026, Cloudflare announced Cloudflare Wallets — a system that lets AI agents, APIs and digital services hold and move money on their own, using payment rails Cloudflare already runs in front of a large share of the web. Right now, AI agents can browse for you, but they can't buy anything for you. That's the gap Cloudflare is trying to close.

Cloudflare Wallets is not another crypto wallet, even though that's what most people assume from the name. It's a new era for machine payments, built primarily for AI agents, API keys and digital services.

What's available now

Right now, the only thing you can actually do is claim a Cloudflare Wallet handle — a reservation, not a working account. Cloudflare has said plainly that funding a wallet, storing stablecoins, receiving payments and spending are not yet generally available, and it hasn't given a launch date for any of it. The announcement reads, in places, like these features already work. They don't.

Account Wallets and Virtual Wallets

There will be two levels of wallets. The base wallet belongs to a person or an organization — funds can be added to it and withdrawn from it, and funds inside that account can also be delegated. An agent won't be able to spend all of it, only what you allow: you can set it a weekly budget, or write the budget manually.

Cloudflare calls that base layer an Account Wallet. Virtual Wallets sit on top of it, built specifically for AI agents — created and controlled through APIs, since an agent has no interface to click through.

How x402 works

This is a new payment standard built on top of HTTP 402, not a new cryptocurrency or blockchain. The server replies with a price, the accepted asset, the network and the seller's address; the client builds a signed payment and repeats the request; the server or an intermediary verifies it and settles the payment. After that, the resource comes back together with proof of payment.

In short, x402 revives an HTTP status code that has sat unused for decades and gives it an actual job inside a normal web request.

The $10 example, and how spending stays in bounds

The strong point here is that limits don't just reduce risk — they also give the agent more autonomy. If you give an agent $10, for example, it can test dozens of cheap APIs on its own and pick the best one for you, without asking for approval on every single purchase. That's what makes it useful as a product in everyday terms.

Cloudflare also says an owner can restrict which services an agent is allowed to pay and cap how large any single payment can be, on top of the budget itself. For the basics of keys and custody behind any wallet, see our guide on what a crypto wallet is.

What sellers get from Monetization Gateway

Monetization Gateway is the seller-facing half of this. It routes incoming x402 payments so a site or API operator can actually collect and reconcile them — treating AI agent traffic as a paying customer instead of something to block. This only works once both sides show up: sellers pricing content through the gateway, and agent builders wiring in x402 payments. Neither exists at scale yet.

What's still unclear, and the real distinction

Cloudflare hasn't confirmed which assets and networks Wallets will support, what fees apply, which jurisdictions are covered, how KYC works, or how refunds and disputes get handled.

What sets Cloudflare Wallets apart from an ordinary crypto wallet isn't how many coins it supports — it's who's allowed to spend the money. Not just a person, but a software agent, within limits a person or organization sets for it.

And Cloudflare Wallets isn't a competitor to Ledger, Trezor, Exodus or MetaMask. Those hold crypto for a person. This is infrastructure for machines paying other machines, with a person or organization setting the limits. If you're comparing this to how you actually store and control your own crypto, see our crypto wallet comparison or crypto exchange vs wallet instead — this announcement doesn't change that decision.

The idea itself is simple: machines have never been able to buy things on their own, and this is Cloudflare's attempt to fix that at the protocol level. Whether it catches on depends on things Cloudflare doesn't control — sellers pricing through it, other companies building compatible agents. For now, what exists is one wallet handle and a set of stated plans.

FAQ