Cloudflare has opened registration for Cloudflare Wallet handles and outlined a programmable wallet system intended to let AI agents pay for APIs and digital content with stablecoins. The identity handle is available now, but the wallet, funding and payment functions remain planned features rather than a live payments service.
The August 4 announcement expands Cloudflare’s agentic-commerce strategy from the seller side to the buyer side. Its previously announced Monetization Gateway is designed to let websites and API providers request stablecoin micropayments through the x402 protocol. Cloudflare Wallets would give buyers and their software agents a way to hold funds, authorize purchases and identify themselves to participating merchants.
That distinction matters for payments teams. Cloudflare has described an architecture and made handles claimable, but it has not announced a production date for stablecoin payments, named supported stablecoins or blockchain networks, disclosed pricing, or identified the regulated entities that would provide custody, conversion and geographic access.
Account wallets would delegate limited spending
Cloudflare plans two wallet types. Account Wallets would be controlled by human Cloudflare account owners, who could add or remove funds and delegate spending authority. Virtual Wallets would operate through API keys and let individual agents transact within permissions set by the account owner.
The proposed controls include allowances, merchant allow lists and maximum transaction sizes. Cloudflare also described spending caps, recurring budget rules and a manual-override process for agents that reach their limits. In one example, a company could assign a weekly budget for AI inference to each employee’s virtual wallet.
For enterprise payment operations, this delegation model is more consequential than the wallet label alone. An autonomous buyer needs a defined funding source, transaction authority and exception path. Limits can reduce exposure when an agent behaves unexpectedly, but they do not by themselves resolve approval governance, credential security, reconciliation, fraud monitoring or responsibility for disputed purchases. Those operating requirements will depend on the controls Cloudflare delivers and on the providers involved in moving and safeguarding funds.
Wallet identity would be optional
Cloudflare said wallet handles will connect to its proposed cloudflare.pay identity layer. An agent could use a human-readable subdomain associated with a Cloudflare account when interacting with a merchant. The company said disclosure would be optional, leaving merchants to decide whether to prioritize or require identified agents.
The design addresses a practical problem in machine commerce: conventional registration and checkout flows assume a human can create an account, enter a payment method and manage an API key. A persistent identifier could help a merchant recognize repeat agent activity and apply account-level policies. It is not, however, equivalent to legal identity verification, sanctions screening or authorization by the person or company the agent claims to represent. Merchants and payment providers would still need controls appropriate to their products and jurisdictions.
Stablecoin payments are still on the roadmap
Cloudflare said Wallets will eventually store stablecoins, buy services and receive funds across the web. It plans to connect the product to x402-compatible endpoints, including its Monetization Gateway, so a payment request and proof can travel with an HTTP transaction.
The company also said it intends to offer on- and off-ramp options in supported geographies, with stablecoin self-funding as an alternative for eligible users. It did not identify the providers, launch markets or eligibility criteria. Cointelegraph reported that Cloudflare had not supplied a rollout timetable when asked for additional details.
The announcement therefore represents a product and control model, not evidence of completed stablecoin transactions or commercial adoption. The near-term milestone is the availability of wallet handles. The payments-industry test will come later: whether Cloudflare can pair delegated agent spending with clear custody, compliance, settlement, reconciliation and merchant-risk responsibilities at production scale.