Cloudflare announced Wallets on 4 August as a programmable wallet for agent traffic, and the problem statement is specific: an agent trying a new API has to get through a login page built for humans, ask a person to attach a payment method, generate an API key and then work out how to call the service. Agents lack both a stable identifier to sign up with and a native way to pay, so they hand registration back to humans and stop comparing alternatives.
The design answers both halves. An account wallet holds stablecoins and gives the account a shareable handle that acts as a stable identity with merchants, and each account can mint Virtual Wallets for its agents, bounded by an allowance, an allow list and a maximum transaction size. The guardrails are the product: spending authority is delegated as a budget with a scope rather than as a credential, so an agent can try many APIs with managed risk. Cloudflare pairs this with a Monetization Gateway supporting micropayments attached to HTTP requests through x402.
Budget-scoped delegation is the commerce counterpart of the identity work in Claude commerce agents packaging shopping and merchant workflows, and it lands on the enforcement surface tracked in Cloudflare turning MCP traffic into a network control surface. The agent security hub follows the authority side.
Much of this is future tense: the post says wallets can be created now while paying for APIs, the gateway and virtual-wallet guardrails are described as coming. The condition to watch is whether a Virtual Wallet's spend is itemised per API call, because an allowance without a per-purchase record delegates budget but not accountability.