Announcing Cloudflare Wallets (Cloudflare Blog)

Summary

Cloudflare Wallets gives AI agents the missing half of the Agent Web transaction: a way to pay. It answers the podcast’s “agents don’t have wallets” objection directly. Two wallet types: Account Wallets (human-owned; fund, withdraw, set spending policies) and Virtual Wallets (agent-operated via API keys, with owner-set limits). Guardrails include allowances, allow lists, maximum transaction sizes, and anomaly flagging for human review.

Wallets store stablecoins, with onramp/offramp “within supported geographies” and self-funding for eligible users. They integrate with x402 / Pay-per-Crawl micropayments, the Monetization Gateway, and Cloudflare’s Agents SDK. Agents can optionally identify to merchants via human-readable handles (e.g., research.example.cloudflare.pay).

Status: handles claimable now at cloudflare.pay; actual wallet setup and use is “coming soon” as of August 2026.

Key Claims

  • Account Wallets (human) vs. Virtual Wallets (agent, API-key-operated with owner-set spend limits).
  • Guardrails: allowance, allow list, max transaction size, anomalous-spend flagging.
  • Stablecoin-based, geographic restrictions on funding rails.
  • Integrates with x402, Monetization Gateway, and the Agents SDK.
  • Handle claiming live; full functionality not yet shipped (2026-08-04).
  • Agent identity disclosure to merchants is optional.

Connections

Contradictions

  • None. Confirms the podcast’s “agents will have wallets” prediction is Cloudflare’s explicit roadmap — but as of now it’s a handle reservation, not a working payment product.