Cloudflare has unveiled Cloudflare Wallets, a planned programmable wallet system intended to give AI agents a persistent identity and a controlled way to pay for online services. Users can already claim a Cloudflare Wallet handle, but the payment functionality is not yet available. The company said wallet setup and purchases for APIs and digital content will arrive later, making the current release an identity and reservation layer rather than a fully operational payment product.
The wallets are designed to connect with Cloudflare’s Monetization Gateway, which lets eligible customers place payment requirements in front of websites, datasets, APIs and Model Context Protocol tools. Stablecoin micropayments will be attached directly to web requests through x402, reducing the need for agents to create accounts, maintain subscriptions or navigate checkout interfaces built for humans.
Separate Wallets Give Humans Control Over Agent Spending
Cloudflare plans to divide the system into Account Wallets and Virtual Wallets. Account Wallets will belong to human-controlled Cloudflare accounts, allowing owners to add or withdraw funds and delegate spending authority. Virtual Wallets will operate on behalf of agents through API keys, with permissions and balances derived from the controlling account rather than giving software unrestricted access to all available funds.
The proposed controls include allowances, approved-service lists and maximum transaction sizes. Owners will also be able to cap an agent’s total spending and review anomalous activity before adding more funds or granting an override. These guardrails are central to Cloudflare’s model of delegated commerce, because autonomous purchasing becomes more practical only when the human or organization funding the agent can contain financial exposure.
x402 uses the HTTP 402 “Payment Required” status code to let a service return machine-readable payment instructions. A client can sign the requested payment, resend the request and receive the resource after verification and on-chain settlement. The protocol turns payment into part of the normal request-response flow, potentially allowing an agent to test a low-cost API without first opening an account or buying a subscription.
Cloudflare Builds Both Sides of Agentic Commerce
Cloudflare’s Monetization Gateway represents the seller side of that framework, while Wallets are intended to provide the buyer side. The gateway is expected to manage payment policies and verify transactions at Cloudflare’s edge, with stablecoins used for settlement at launch. Together, the products are designed as infrastructure for machine-to-machine commerce, not merely as another consumer crypto wallet.
Identity is another component of the design. Cloudflare Wallet handles will map human-readable names to wallet keypairs and may allow merchants to recognize that an agent is acting for a particular account or organization. Declaring that identity will remain optional, and Cloudflare has emphasized that the handle is a simple identifier rather than a complete verification standard.
The announcement adds a major web-infrastructure provider to efforts aimed at embedding stablecoin payments into automated services. However, Cloudflare did not disclose a firm rollout date, usage targets or transaction forecasts for the wallet system. Its commercial significance will depend on execution after the handle launch, including supported regions, funding methods, developer adoption and whether agents generate meaningful payment volume once the financial features go live.