Cloudflare
Cloudflare announced "Cloudflare Wallets" on August 4 — a wallet system that lets AI agents pay directly for APIs and content without going through a human. But only one thing actually works today: reserving a wallet handle at cloudflare.pay. For the payment functionality itself, the company wrote only that it will be "available to set up and use soon."
Cloudflare is a CDN and security infrastructure company through which a large share of global web traffic passes. It is neither a payments company nor a bank. Why such a company built a wallet is stated plainly in the first paragraph of the announcement. Today, for an agent to try a new API, it must pass through a human login page, ask a human to register a payment method, and get issued an API key. Agents have neither a persistent identity to sign up with nor a way to pay. As a result, the announcement says, most give up midway and hand the task back to a human.
What Works Today, and What Doesn't Yet
Reading the announcement sentence by sentence reveals a clear split in tense. Handle reservation is "starting today." Paying with a wallet is "soon." Everything beneath that is phrased as "will be able to." Neither account wallets, virtual wallets, nor funding are live yet.
So the only decision available right now is this: should you claim your organization's name before someone else does. A handle is a unique username tied to an account, and per the company's description, it becomes the identifier linked to a seller. It functions much like domain squatting — hard to reverse once someone else takes it.
Account Wallets and Virtual Wallets: Limits That Enable Freedom
Wallets come in two types. The Account Wallet is for humans. It holds funds, delegates spending authority to virtual wallets, and can withdraw funds when needed. The Virtual Wallet is for agents and operates via an API key. Within a virtual wallet, an agent can spend only up to the authority it's been granted, with a ceiling set by the account wallet owner.
Three guardrails are specified: an allowance, an allow list, and a maximum transaction size. The company's example: to give each employee a $100 weekly budget for AI inference, you fund the account wallet and create per-employee virtual wallets under that rule. Anyone who exceeds the limit must request manual approval from the account wallet's authority holder.
Notably, the company frames these limits not as constraints but as a mechanism that enables freedom. An agent responsible for $10 carries less risk than one holding $1,000, and if testing an API costs only a few cents, $10 is enough to compare dozens of options. Humans only need to step in when spending spikes abnormally; if the spending is intentional, they can raise the limit or approve one-time funding.
The Selling Side Was Already in Place
Wallets are the buy side. The sell side arrived a month earlier, on July 1, with the Monetization Gateway — an engine that lets anything sitting behind Cloudflare, whether a webpage, dataset, API, or MCP tool, be priced and sold, with payments settled via x402 in stablecoins.
Here, the pricing examples are far more concrete: a few cents per web search call; a base fee of $0.001 plus $0.01 per MB for an upload endpoint; $0.99 per resolved customer inquiry. Rule examples are also given: charging $0.01 for every GET or POST to a specific path, applying variable pricing up to $2 for compute-heavy tasks like image generation, or intercepting a 401 Unauthorized normally returned by the origin server and rewriting it as 402 Payment Required, sending price and payment method together in the response. Rules can be managed via dashboard, API, or Terraform.
Put the two announcements together and the picture closes: the gateway sets the price, the wallet pays it. In the company's own words, it's a "headless marketplace."
402 Is a 30-Year-Old Status Code
x402 is an open protocol for making payments over HTTP, named after the 402 status code. The flow is simple: a client requests a paid resource, and instead of the resource, the server returns 402 Payment Required along with a small payload specifying the price, the accepted asset, and where to send it. The client pays, attaches proof of payment, and repeats the same request; a facilitator verifies it, and the server then releases the resource. There's no redirect to a checkout page, and no separate payment API to call.
Two properties make it suited to machine payments: near-zero protocol overhead lets amounts be split down to fractions of a cent, and because the payment itself serves as the credential, the buyer never needs to create a seller account. Settlement happens peer-to-peer, landing directly in the seller's wallet. x402 is being built collaboratively by more than 25 organizations under the x402 Foundation, part of the Linux Foundation.
The company's CEO made this exact point on a podcast six weeks earlier. "The internet originally had a response code called 402. Everyone knows 404 is 'not found' and 500 is an error, but 402 was 'payment required,' and we never built anything around it. I think that's about to happen." He said this while discussing collaborations with Coinbase and Stripe.
Why Cloudflare, of All Companies
Earlier in the same interview, he made a more fundamental point: "For the past 28 years, the internet's core business model has basically stayed the same — mostly advertising. The problem is that bots don't click on ads. Within the next five years, the internet's business model is going to change dramatically."
The announcement rests on the same premise: that bots already generate the majority of web traffic. The Monetization Gateway announcement adds another figure — AI crawlers request content anywhere from 100 to tens of thousands of times for every human visitor they redirect. That's why the old exchange, sustained by ads and subscriptions, no longer holds up.
Cloudflare's claim to this space rests not on a payments license but on position. Because the gateway runs at the edge in more than 330 cities, the x402 handshake completes close to the buyer, and verification and settlement happen before the request ever reaches the origin server. In the company's words, it's one of the few places where identity verification, rule enforcement, and payment confirmation can all happen within a single request.
Giving Agents a Readable Name
The second pillar of the wallet is identity. Today, when an agent visits a site, there's no reliable way to know who it's acting on behalf of. It's easy to give a person or organization a free trial week or signup credit, but hard to extend the same benefit to an agent that has no fixed identity and that a single person could spin up dozens of.
Cloudflare's answer is to tie the wallet to the account via cloudflare.pay. A research agent could have an address like research.example.cloudflare.pay, letting a seller know it's an agent belonging to a specific organization. Disclosing identity is optional, and whether to require it is up to the seller.
The company compared this to a VPN: not disclosing identity doesn't automatically make you untrustworthy, but it means you may need to prove more. Technically, this builds on the existing Web Bot Auth, which registers identity via keypairs; the ID attached to a wallet is a layer that attaches a human-readable name to that hard-to-read keypair. The company was explicit that it isn't defining a new schema, comparing the approach to how DNS attaches names to IP addresses.
What Remains Unconfirmed
The biggest open question is timing. Payments, funding, and virtual wallets all lack a launch date. The Monetization Gateway currently only has an open waitlist.
Geography is also unresolved. The company said only that it will first enable deposits and withdrawals in "supported geographies," offering stablecoin self-funding as an alternative for eligible users. Whether Korea is included is not stated in the announcement. Using this in Korea would also require separately checking domestic regulations on stablecoin handling — a matter outside the scope of this announcement.
Fee structure hasn't been disclosed either. On the gateway side, only seller-set pricing examples are given; neither announcement states how much cut Cloudflare takes in the middle. Settlement speed is described as a goal of "sub-second," not a guaranteed figure.
In short, there's exactly one decision to make today: whether to reserve a handle under your organization's name. Everything else is a preview, and judgment can wait until payments are actually live.
