Quick answer
Cloudflare proposes wallet handles as optional, human-readable identity for agents acting as delegates of a Cloudflare account. The announcement connects this concept to Web Bot Auth, which uses a keypair for agent identity.
A readable handle can improve attribution; it does not prove trustworthiness, authority to spend, identity of the ultimate human, compliance status, or permission to access a merchant resource. Start with the Wallets preview lifecycle.
Identity layers
| Layer | What it can establish | What it cannot establish alone |
|---|---|---|
| Wallet handle | Human-readable account-linked label | Wallet availability, funds, or transaction authority |
| Web Bot Auth keypair | Cryptographic continuity for the presenting agent | Merchant trust, purpose, or payment approval |
| Account delegation | Claimed relationship between agent and account | Permission for every target, action, or amount |
| Merchant policy | Whether a known or unknown agent may transact | Correct settlement or legal compliance by itself |
Cloudflare says agent declaration is optional and merchants may decide whether to prioritize known agents. Unidentified does not automatically mean malicious; identified does not automatically mean safe.
Verify without over-collecting
Ask only for identity evidence needed by the transaction and risk model. Verify cryptographic proof, current key status, delegated scope, wallet or payment authority, merchant allowlist, amount, purpose, and expiration independently.
Avoid turning a handle into a universal profile. Define retention, disclosure, revocation, account recovery, key rotation, impersonation response, and privacy review before linking transaction history to a persistent label.
Merchant decision policy
Merchants should decide how known and unknown agents differ in rate limits, trial eligibility, payment requirements, resource access, and review. Keep the rule explainable and resistant to agents creating many handles under one account.
For delegated financial controls, read Virtual Wallet spending guardrails and Account Wallet vs. Virtual Wallet.
Frequently asked questions
What does a Cloudflare Wallet handle identify?
Cloudflare proposes a human-readable account-linked handle that an agent may optionally declare as a delegate when interacting with merchants.
How does Web Bot Auth relate to wallet identity?
Cloudflare says Web Bot Auth already lets agents register identity through a keypair and proposes wallet-linked IDs as a human-readable label for that cryptographic identity.
Does a verified agent identity authorize a payment or action?
No. Identity supports attribution. Merchant policy, account authority, payment verification, target permission, risk controls, and legal obligations remain separate.
Official sources
Source check: August 12, 2026. Recheck handle availability, identity proof, delegation, privacy, merchant policy, recovery, and terms.