Cloudflare Wallets

Cloudflare Wallets is a programmable wallet system announced in August 2026 for the agentic Internet. Account Wallets belong to people or organizations, while API-key-operated Virtual Wallets let AI agents transact within explicit constraints. The system is designed to pair identity, delegation, and web-native payments.

Key Features

• Two Wallet Types: Account Wallets hold funds and issue Virtual Wallets for individual agents.
• Programmable Guardrails: Set spending caps, merchant allowlists, and maximum transaction sizes.
• x402 Payments: Stablecoin micropayments support pay-per-request access to APIs and content.
• Delegated Identity: A cloudflare.pay handle can identify an agent as acting for an account.
• Monetization Gateway Pairing: Providers can charge agents at the point of access.

Use Cases

Who Should Use This Tool?

• API Providers monetizing machine-accessible resources.
• Agent Platforms issuing controlled wallets per workload.
• Organizations that need visible delegation between an account and its agents.

Problems It Solves

1. Shared-wallet risk: Virtual Wallets isolate agent credentials and policies.
2. Payment onboarding: x402 supports request-level payment flows.
3. Agent attribution: Optional handles communicate who an agent represents.

Pricing

Advantages & Unique Selling Points

Compared to Competitors:

1. Web-edge context: Wallets connect naturally to Cloudflare-hosted APIs and content.
2. Delegation model: Account and Virtual Wallet separation clarifies ownership.
3. Native monetization path: x402 and Monetization Gateway cover both buyer and seller workflows.

What Makes It Stand Out:

• Human-readable agent identity through cloudflare.pay.
• Guardrails applied per virtual wallet.

User Reviews

"Account-level funding with separate agent wallets is a practical model for production teams." — Illustrative platform engineer feedback

"Pairing identity with x402 makes machine requests easier to reason about and audit." — Illustrative API developer feedback

Getting Started

Quick Start Guide

1. Reserve a handle at cloudflare.pay.
2. Follow availability updates for full wallet issuance.
3. Define guardrails for each planned Virtual Wallet.
4. Prepare x402 endpoints for agent-paid resources.

Integration

Integrates with:

• x402 payment flows
• Cloudflare Monetization Gateway
• Emerging x402 Foundation identity standards

Frequently Asked Questions

Are full wallet features available now?

Handle reservation is live; on/off ramps and Virtual Wallet issuance were announced for following months.

How do agents authenticate?

Virtual Wallets operate through API keys.

Can a wallet restrict merchants?

Yes. Merchant allowlists are among the announced guardrails.

Alternatives

• caipay: Open x402 wallets with gas-free Base transactions.
• Coinbase Agentic Wallets: TEE-backed autonomous wallets.
• Crossmint: Agent wallets, cards, and Merchant of Record services.

Tips & Best Practices

1. Issue one wallet per role: Avoid sharing credentials across unrelated agents.
2. Set narrow merchant lists: Match access to each agent's task.
3. Use delegated identities: Make organizational attribution explicit where appropriate.

Conclusion

Cloudflare Wallets brings policy-controlled spending and identity to the same web edge where many agents consume services. Its account-to-agent delegation model is especially promising for organizations building paid, attributable machine traffic.