Cloudflare has announced Cloudflare Wallets, a programmable wallet system designed to let AI agents pay for APIs, content, and other online services without relying on human-facing signup and billing flows. Account holders can claim a unique Wallet handle now, while funding and payment features are set to follow. The company plans to support stablecoins and x402, a protocol that attaches micropayments to HTTP requests.
The system will have two layers. Account Wallets will let Cloudflare account owners add and remove funds, then delegate spending to Virtual Wallets managed by agents. Those agent wallets will operate via API keys and follow controls chosen by the owner, including allowances, allowlists, maximum transaction sizes, and overall spending caps. Agents that reach a limit could request a manual override from an authorized human.
Introducing Cloudflare Wallets. They will allow you to store stablecoins, purchase services, and receive funds across the web. https://t.co/ucAaoKMs4Q
— Cloudflare (@Cloudflare) August 4, 2026
Cloudflare is positioning this model as a way for agents to compare dozens or hundreds of low-cost services without requiring them to register for each one, add payment details, or generate API keys. An agent could test several APIs for only a few cents each, while the owner limits its total exposure. The same controls could allocate recurring AI inference budgets to employees and flag unusually fast spending for human review.
Wallets will supply the buyer side of Cloudflare’s broader agentic commerce push. Its Monetization Gateway is intended to enable eligible Cloudflare customers to sell APIs and content via x402-compatible endpoints, while Wallets will add purchasing support to the company’s Agents SDK. Initial funding options will include onramps and offramps in supported geographies, with self-funding in stablecoins planned as an alternative for eligible users.
Cloudflare also plans to link wallets to accounts through cloudflare[.]pay, giving agents optional, persistent, human-readable identities such as research.example.cloudflare.pay. The identifier would serve as a readable label for a cryptographic key pair, building on Cloudflare’s Web Bot Auth work. Merchants could decide whether to favor or require identified agents, while agents could choose whether to declare who they represent. Together, payments, spending controls, and optional identity are meant to give agents a machine-native route to buy services while keeping people in control of budgets and exceptions.
