
Cloudflare Launches Wallet, Enabling AI to Transfer Stablecoins
Written by: Xiao Bing
Cloudflare, one of the world's largest internet infrastructure companies, announced the launch of Cloudflare Wallets yesterday.
First off, this wallet might not be what you expect—it has nothing to do with MetaMask, exchanges, or DeFi. The wallet Cloudflare built is for AI agents (Agents).

What Problem Does It Solve?
Current AI agents face a fundamental barrier: they cannot spend money on their own.
When an AI agent needs to call an API, it must first register an account, bind a payment method, and generate keys. This entire process is designed for humans, and agents simply cannot navigate it. In most cases, agents can only kick these steps back to humans and wait idly.
The logic behind Cloudflare Wallets is: give agents a wallet so they can pay and purchase services on their own.
How does it work?
A two-layer structure.
The first layer is called the Account Wallet, managed by humans. Deposits, withdrawals, and rule settings all happen at this layer.
The second layer is called the Virtual Wallet, used by agents. Humans assign a virtual wallet to an agent, setting spending limits, a whitelist of allowed merchants, and per-transaction limits. Within this framework, the agent can spend autonomously without needing approval for every transaction.
An analogy: the Account Wallet is the company's finance department, and the Virtual Wallet is an employee's travel budget card. The card has a limit; spending stops automatically if exceeded, but within the limit, the employee decides how to spend.
Payments use stablecoins via a protocol called x402, which embeds payment information directly into HTTP requests. In plain language: when an agent accesses an API, payment and invocation are completed in the same action, without needing a separate payment process.
Another Layer: Identity
Cloudflare also launched the cloudflare.pay domain service. Each wallet can bind a readable identity identifier, such as research.example.cloudflare.pay. Merchants no longer see an anonymous machine request but can identify it as "a research agent from Company X."
This solves the trust problem. Currently, websites treat agents similarly to VPN users; if they don't know who you are, they default to distrust. With identity identifiers, merchants can choose to offer trial credits or contract discounts to verified agents, just like treating a real corporate client.
Why Is It Worth Paying Attention To?
Cloudflare handles over 20% of global website traffic.
Its blog mentions that most traffic on the internet now comes from bots. When this company decides to embed stablecoin payments and an agent identity system into its infrastructure layer, the signal it releases is far more significant than "just another Web3 project."
Several keywords: stablecoins as a payment medium, the x402 protocol (embedding payments into HTTP), and agent-native identity and spending capabilities.
This system, together with the Monetization Gateway released by Cloudflare last week (helping website owners charge agents), forms a bilateral market: sellers use Monetization Gateway to price and collect payments, buyers use Wallets to pay and consume, the currency in between is stablecoins, and the channel is HTTP.
For the crypto industry, one point worth noting is: Cloudflare did not mention any public chain names at all, did not mention Ethereum, Solana, or Base, nor does it intend to issue a token; it only said "stablecoins." This is a choice by an infrastructure company: it wants the functionality of stablecoins as a payment tool, and its attitude toward the underlying chain is instrumental and replaceable.
The scenario where stablecoins truly achieve large-scale adoption may be machine-to-machine micropayments, far exceeding person-to-person transfers. Cloudflare has just paved this path into the pipeline layer of the internet.













