BusinessIssue #184

Cloudflare Just Gave Bots Names and Wallets

The payment feature isn't live yet — but agent identities just went live.

Oswarld (Kwangseob Ahn)· Writer & editor of OZ Talking

Cloudflare Just Gave Bots Names and Wallets

Opening

Reader, on August 4th, Cloudflare rolled out two things at once: Cloudflare Wallets, a stablecoin1 wallet built for AI agents, and cloudflare.pay, which gives each agent its own unique address.

The line CEO Matthew Prince attached to the announcement captures exactly what this is about.

“When an agent shows up at your front door, you should be able to know who sent it.”

Most of the coverage zeroed in on the “AI can finally pay for itself” angle. But I think the order of this announcement matters more. Actually loading and spending money from the wallet was only promised as coming “soon” — the one thing you can do right now is claim your cloudflare.pay name tag.

Let me give you the conclusion up front. What Cloudflare sold here wasn’t a payment service — it’s an identity system for agents. And that’s simply the next natural step in what this company has been building for 15 years.

The Wallet Is Split Into Two Layers

Let’s start with the product itself. Cloudflare Wallets splits the wallet into two layers.

The Account Wallet is managed by a human. It’s the layer where you fund via bank transfer, withdraw, and delegate permissions. Below that sits the Virtual Wallet, one attached to each individual agent. It’s accessed via API key and can only spend within the limits set by the layer above it.

The way limits get imposed is quite specific:

  • A total spending cap per wallet and a maximum amount per transaction
  • A whitelist of approved merchants
  • A weekly budget (the blog’s example: “$100 per employee per week”)
  • Anomaly detection that flags unusual spending velocity for human review

It’s the exact same structure as handing out corporate cards to your team with caps and merchant restrictions attached. The only difference is that the recipient of the card is a program, not a person.

There’s one point worth flagging here. This structure is not a defense against attacks like prompt injection2. It doesn’t stop an agent from being fooled — what it does is cap in advance the maximum amount that can leave if the agent is fooled. It’s closer to loss-limit design than security. Confusing the two in practice will bite you later.

And the payment itself runs on a protocol called x4023. On the merchant side, it’s handled by Monetization Gateway, which Cloudflare launched earlier; on the buyer side, this new Wallets product takes over. Settlement happens in USDC on Base and Solana, and transaction costs run under 1 cent.

Fragment looks accurate. No corrections needed.

The Real Product Is the Name Tag

So far, this has been a story about payments. But there’s an analogy in Cloudflare’s blog post that gets at something bigger.

“Just as DNS gave IP addresses human-readable names.”

That sentence is the real point of this announcement. Once an agent gets an address like research.example.cloudflare.pay, its organization and its purpose are baked right into the name itself. It could also travel anonymously — but in that case, it gets treated the way VPN traffic does: “not necessarily suspicious, but needs a bit more verification.”

This is exactly what Cloudflare has been doing for 15 years: deciding who gets to walk through the door. Chief Strategy Officer Stephanie Cohen says 57% of web traffic today is bots. In a world where more than half of internet traffic is already machines, this company has been standing guard at that door.

What it just did is start running the badge office and the tollbooth at the same time. It hands incoming agents a name (cloudflare.pay), charges them at the gate (Monetization Gateway), and even hands them the wallet they pay from (Wallets). It’s now standing on both sides of the door.

A namespace4 is an asset that, once it takes hold, is extraordinarily hard to dislodge. Domain names were like that. App store bundle IDs were like that. Even if better technology comes along later, once everyone’s already calling each other by a given name, the cost of switching becomes unbearable.

So the fact that names were the first thing settled here is no accident. The money features can be built out slowly, but the naming layer had to be seeded and locked in first.

cloudflare gave agents names---

But Nobody’s Actually Using It Yet

I need to do some fact-checking here — starting with whether this market actually exists.

x402 is a protocol that Coinbase created and handed over to the x402 Foundation under the Linux Foundation in April 2026. More than 20 companies have joined, including AWS, Cloudflare, Anthropic, Circle, Visa, and Mastercard. By Coinbase’s own count, the first year saw 169 million payments, 590,000 buyers, and 100,000 sellers. Looking at the numbers alone, it seems like the market has already taken hold.

But on-chain data analytics firm Artemis sees it differently. More than 95% of all transactions aren’t real trades — they’re test signals confirming that the protocol works, the firm says. A significant portion, it points out, involves wallets sending money to themselves or sellers funding buyers to run repeated transactions. According to CoinDesk’s report this past March, x402’s actual daily transaction volume was around $28,000. That’s less than ₩40 million a day. For the entire global agent payment market.

Sentiment on the demand side isn’t there yet either. In a survey conducted this past June, only 14% of consumers said they trust “AI buying things without human verification.” In a PYMNTS survey, half of respondents worried about fraud and identity theft, and only 5% said they weren’t worried at all.

So here’s where things stand: the companies laying down the infrastructure are moving well ahead of actual demand. And that’s not strange at all. If you wait to claim a namespace until after demand shows up, you’re already too late. It’s the same reason people who bought domain names in 1995 weren’t doing so because web traffic was already high back then.

We’re Still Fighting Over “Who Issues,” Not “Who Pays”

In the last issue, I talked about how Korea’s network usage fee structure is making it harder just to access agent payment infrastructure in the first place. This announcement stacks one more layer on top of that problem.

While Cloudflare hands out name tags today, Korea still hasn’t legally defined what a won-denominated stablecoin even is. The Digital Asset Basic Act was originally targeted for passage in Q1 of this year, but it got pushed back by local elections, National Assembly committee organization, and disagreements among relevant agencies. Right now, the plan is to introduce a joint party-government unified bill in the September regular session of the National Assembly.

Looking at the points of contention makes the nature of this time lag clearer. The debate centers on the equity structure of the issuing entity. There’s a compromise floating around where banks would hold a majority stake in the consortium (50% + 1 share), while a single fintech company could hold up to 34% — and the industry is pushing back against a proposal to cap exchange major-shareholder stakes at 15–20%.

Here’s the summary: outside Korea, they’re deciding “who pays.” Inside Korea, we’re deciding “who issues.” Both discussions matter, but they’re happening in reverse order. By the time the issuing entity is settled, there’s a good chance the agent identity system will have already hardened around someone else’s name.

To be fair, this isn’t purely a case of regulatory laziness. Stablecoin issuance directly touches on monetary sovereignty and financial stability, so there’s plenty of reason to proceed carefully. My point is simply that it’s worth calculating what that caution costs. And a reminder: this piece is commentary on institutional and industry trends, not investment or legal advice.

Oswald’s Lens

I think this announcement has to be read alongside the earnings that came out the same day.

Cloudflare posted Q2 revenue of $696.1 million, up 36% year-over-year. Large customers spending over $100,000 annually grew 27% to 4,698, and dollar-based net retention5 climbed from 114% to 120%. The company also raised its annual guidance, and the stock jumped 18% in after-hours trading.

But in that same quarter, the company let go of 1,100 people — 20% of its workforce. Headcount at the end of June was 4,700, down from 5,483 three months earlier. Restructuring costs alone came to $150.7 million — about ₩210 billion in our currency — baked into this quarter’s results. Prince described this shift as “a fundamental restructuring of the internet for machine-to-machine traffic.”

A company growing revenue 36% just cut its headcount by 20% — and in the same week, handed machines a wallet and a name. The layoffs and the wallet aren’t two separate news items; they’re one bet. The bet is that the internet’s primary customer going forward is machines, not people, and that a business serving machines needs fewer humans.

There’s a pattern I keep running into when I design go-to-market strategy. When a new layer emerges, what determines who wins isn’t product performance — it’s whether you were there the moment the standard hardened. Payment methods can change later; settlement might end up running on something other than stablecoins. But once the naming system that answers “who is this agent?” sets, it sticks. Cloudflare isn’t competing on performance. It’s competing on naming rights.

So the practical advice I’d give Korean businesses is a little unglamorous: claim your handle now. Reserving a name like cloudflare.pay is possible today, and it costs practically nothing. x402 might not take off — that’s a real possibility, not a small one. But if it fails, all you lose is a name. If it succeeds and you didn’t claim it in time, what you lose is your brand itself. Bets with this kind of asymmetry don’t come around often.

Closing

Here’s the gist, in three lines.

  • What Cloudflare sold wasn’t a wallet — it was an identity system for agents. The fact that they solved “who’s the agent” before “how does the agent pay” is the tell.
  • Real demand isn’t there yet. Daily x402 transaction volume sits at around ₩40 million (~$29,000), and over 95% of transactions are test signals. The infrastructure is running well ahead of demand.
  • Korea is busy deciding “who gets to issue,” while the rest of the world is deciding “who gets to pay.” The sequence is backwards.

If you do just one thing this week, check whether a cloudflare.pay handle exists under your company’s name. Just seeing whether someone’s already claimed it will give you a feel for the temperature of this market.

💬 Have you ever discussed, internally, the question of actually giving an AI agent the authority to spend real money? Tell me in the comments where the conversation stalled, or what scared people most. I’ll dig into limit design and approval structures separately in a future issue.

📨 If you know a colleague who’s been looking into payments or agent infrastructure, please share this piece with them.

References & Further Reading

Primary sources

Background

Related past issues

📝 Glossary

Kwangseob Ahn profile illustration

The author, Kwangseob Ahn, is a professor of business administration at Sejong University and lead consultant at OBF (Oswarld Boutique Consulting Firm). He teaches statistics and data analysis, including business data management and business analytics, while leading GTM and AI strategy consulting in the field, designing the seam between technology and business. He has published academic research on a memory architecture for AI dialogue systems (HEMA) and runs Daily Arxiv, a daily curation of global AI papers. He holds a master's from Korea University's Graduate School of Technology Management and a KMBA. He is the author of Homo Brainless: The People Who Outsource Their Thinking.

Footnotes

  1. Stablecoin: A cryptocurrency pegged in value to a fiat currency like the dollar. Because its price doesn’t swing, it’s built to be used as a payment and settlement instrument rather than an investment vehicle. ↩

  2. Prompt injection: An attack in which hidden instructions are planted inside a webpage or document, causing an AI that reads that document to follow those instructions instead of its original owner’s. It’s the equivalent of slipping someone a fake note while they’re out running an errand. ↩

  3. x402: A payment protocol that revives HTTP’s long-dormant response code 402, “Payment Required” — present in the spec for 27 years but never actually used. When a server replies “here’s what this costs,” the requester attaches proof of payment and asks again. No login, no payment page needed, which makes it well-suited for machines to use. ↩

  4. Namespace: A space of names managed so they don’t collide with one another. The domain address system is the classic example, and once a namespace hardens into a standard, switching to a different system becomes very difficult. ↩

  5. Dollar-based Net Revenue Retention (DNR): A metric measuring how much more (or less) existing customers spent this year compared to a year ago. A rate of 120% means that even without adding a single new customer, revenue grew 20% from existing customers alone. ↩

Your take shapes the next issue

What resonated most in this issue, or where has your experience been different?

Any registered reader can comment for free.

Related issues

Issue #183Business

The Four-Year Pledge SanDisk Extracted From Its Customers

Customers guaranteed $16.5 billion before a single chip shipped.

Issue #182Business

No Solo Unicorn Yet, but Solo Millionaires Have Doubled

The prophesied one-person unicorn never arrived, but payment data reveals a new way to grade solo-founder success stories.

Issue #181Business

$800 Billion: The World's Most Famous Wrong Number

It undercounts global AI spending by $200 billion while overcounting America's by exactly the same amount.