🔶 Cloudflare Wallets：面向智能体互联网的可编程钱包
英文标题：🔶 Cloudflare Wallets: The programmable wallet for the agentic Internet
Cloudflare 推出 Cloudflare Wallets，旨在解决 AI Agent 缺乏稳定身份和原生支付能力、难以自主试用 API 的问题。用户现可在 cloudflare.pay 领取唯一钱包标识，后续可使用钱包通过 x402 协议为 API、内容和 AI 推理等服务进行稳定币微支付。该产品包含面向人类账户所有者的 Account Wallets，以及可由 Agent 通过 API 密钥使用、并受额度和白名单等规则约束的 Virtual Wallets。Cloudflare 还希望通过人类可读的钱包标识，让商家识别 Agent 所代表的个人或组织，从而构建面向机器交易的双边智能体市场。
1.1 KB
2.6 KB
51.6 KB
51.6 KB
18.2 KB
46.9 KB
1.1 KB
100.5 KB
中文
如今，AI Agent 很难试用新的 API。它们通常必须穿过专为人类而非 Agent 设计的登录页面，联系人工客服添加支付方式，生成 API 密钥，然后再弄清楚如何调用该 API。
这一流程对 Agent 而言非常困难，原因有二：Agent 没有可用于注册 API 的稳定标识符，也没有原生的 API 支付方式。由于缺少这些能力，它们往往难以完成软件服务的接入，这限制了智能体商业的发展。AI Agent 经常会直接放弃这些任务，将注册、添加支付方式和生成 API 密钥重新交给人类处理。这使得 Agent 很难试用和比较大量 API。
为解决这一问题，我们创建了 Cloudflare Wallets。从今天起，你可以为自己的账户领取 Cloudflare Wallet handle，它将提供一个唯一用户名，帮助你更好地与商家建立连接。很快，你将能够设置并使用 Cloudflare Wallet，为 API 和内容付费。
本月早些时候，我们发布了 Monetization Gateway，帮助 Cloudflare 客户通过其网站和应用获得收入。Monetization Gateway 将支持使用 x402 协议进行微支付，该协议允许将支付附加到 HTTP 请求中。这些微支付可用于从 AI 推理、数据到内容等各类用途。如果你想为 Monetization Gateway 以及其他 兼容 x402 的端点背后的服务付款或收款，就需要一个钱包。
Cloudflare Wallets 将允许你存储稳定币、购买服务，并在整个 Web 上接收资金。每个拥有钱包的账户还可以为其 Agent 创建 Virtual Wallets，使 Agent 能够购买 API、MCP Tools、内容等。你可以为 Virtual Wallets 定义安全护栏，例如额度、允许列表和单笔交易最大金额，以帮助 Agent 从你的账户中安全地花钱。这将让 Agent 能够以低摩擦、风险可控的方式试用大量 API。钱包用户还可以选择分享其 Cloudflare Wallet handle，从而在与商家互动时拥有稳定身份。
构建双边智能体市场
Cloudflare 的 Monetization Gateway将允许符合条件的 Cloudflare 客户，以无头方式向智能体买家销售其资源，例如内容或 API。但要让这一市场真正发展起来，Agent 还需要更多工具，以机器原生的方式向商家购买服务。Wallets 将为 Cloudflare 的 Agents SDK 增加另一项工具，使 AI Agent 能够通过微支付轻松购买所需的 API 和内容。
Cloudflare Wallets 将有两种类型：Account Wallets 和 Virtual Wallets。
Account Wallets 面向 Cloudflare 账户的所有者和用户等人类用户。它们可以充值、将消费权限委托给由 Agent 管理的虚拟钱包，并在需要时提取资金。
相比之下，Virtual Wallets 面向 Agent 设计，并通过 API 密钥运行。在 Virtual Wallet 中，Agent 可以按照自身权限支出资金。其最高支出将受到 Account Wallet 所有者设定限额的约束。该框架既让 Agent 可以代表用户自主行动、无需持续的人工批准，也限制了 Agent 过度消费的能力。
探索的自由
Virtual Wallets 令人兴奋之处在于，它们将让 Agent 做自己最擅长的事：探索数十乃至数百项服务，并为特定用例找到最佳选择。通过 x402 实现的稳定币微支付，将使用户无需创建账户即可简单地试用 API，让 Agent 能以极低摩擦测试新选项。Virtual Wallets 的消费上限旨在让人类能够在安全的支出范围内，让 Agent 自主探索。这些限制看似是约束，但反直觉的是，它们反而赋予 Agent 更多自由。如果一个 Agent 只负责 10 美元，你对其消费的担忧会低于它负责 1,000 美元时的情况。如果试用一个 API 只需几美分，那么 10 美元足以用于寻找和评估众多选项。
一旦你或你的 Agent 选定要使用的 API，你在 Account Wallet 中设置的策略将作为 Virtual Wallets 的成本控制机制。想为每名员工提供每周 100 美元的 AI 推理预算？只需为 Account Wallet 充值适当余额，并为每位员工创建适用该规则的 Virtual Wallets。任何超出其 Virtual Wallet 限额的用户，都可以向获授权修改 Account Wallet 的人工人员申请手动覆盖。
我们希望让 Account Wallets 能够轻松设置灵活但严格、无需每天主动监控的支出策略。当发生异常情况时，例如支出速度意外加快，人类可以审查并确认一切是否按预期运行。如果该支出是有意为之，Account Wallet 管理员可以提高限额，或批准一次性注入资金。如果该支出并非有意为之，那么为虚拟钱包添加资金的支出策略就通过设置上限发挥了作用。
我们正在努力让这些钱包的充值和使用尽可能简单。我们将从在受支持地区提供简便的资金入金和出金方式开始，符合条件的用户也可以选择通过稳定币自行注资。互联网不会在一夜之间完全转变，但如今Web 上的大多数流量已由机器人驱动，我们很高兴能为 Agent 和商家提供一流的智能体商业工具。
不止于支付
让人类能够将权限委托给 Agent，从而轻松买卖服务，是一个有益的起点。但当商家与 Agent 互动时，这种委托关系并不总是显而易见。如今，如果一个 Agent 访问你的网站，即便它代表某个人或组织行事，你对其作为用户的了解也可能很少。这种归属信息的缺失给许多传统 Web 商业模式带来了挑战。向人类或组织提供一周免费试用或注册额度很容易；但要向缺乏稳定身份的 Agent 提供同样的权益则很困难，尤其是一个人可以在其控制下创建数十个 Agent。
我们通过 cloudflare.pay 将钱包关联至 Cloudflare 账户来解决这个问题。cloudflare.pay将允许 Agent 选择性地表明自身身份，因为其身份是该账户的委托身份。一个研究 Agent 可以位于 research.example.cloudflare.pay，让商家知道它来自某个特定组织。这种方式将使 Agent 能够维持一致且持久的身份，为所有参与方改善体验。Agent 是否声明身份将完全由其自行选择，企业也可以自行决定是否优先与已知身份的 Agent 进行交易。
Agent 标识符应当人类可读
我们认为，对待 Agent 的方式将类似于对待 VPN：未识别身份的人并不天然不可信，但他们需要提供更多证明。这也是我们推出 Turnstile以及在 Bot Management中开展其他机器人检测计划的原因。我们的身份原语将建立在这些既有工作的基础上。例如，Web Bot Auth已经允许 Agent 通过密钥对注册身份。关联至 Cloudflare Wallets 的 ID 将使该密钥对变得人类可读。
我们知道，智能体身份标准正在快速变化，因此希望保持方法简单。我们提出的方案，是为不太易读的密钥对提供一个人类可读的标识符，类似于 DNS中 URL 与 IP 地址的配对关系。我们并不试图定义某种特定模式或其他验证系统。我们只想让身份易于记忆、易于声明。随着通过 x402 Foundation 的倡议不断发展出用于丰富智能体身份的模式，我们将寻求采用这些模式，并鼓励其他人也这样做。
智能体商业的未来
在 Cloudflare，我们希望提供让智能体商业取得成功所需的全部构件。Monetization Gateway 将为卖家提供一种无需搭建传统支付基础设施即可收款的方式。Wallets 将为买家提供一种通过 Agent 以无头方式付款的途径。身份系统将使商家能够与主动表明身份的买家沟通，或执行身份识别要求。
所有这些构件将为互联网打造一个无头市场。如果你对此感到兴奋并希望参与，现在就可以领取你的 handle。我们期待看到你将构建和变现什么。
English / 原文
Today, it is difficult for AI agents to try out new APIs. They often have to navigate through a login page designed for humans and not agents, contact a human to add a payment method, generate an API key, and then figure out how to call the API.
This flow is very difficult for agents for two reasons: Agents do not have a stable identifier to sign up for an API, and they do not have a native way to pay for APIs. Because they lack these things, they often struggle to onboard onto software, which limits the growth of agentic commerce. AI agents often give up on these tasks entirely, kicking registration, payment methods, and API key generation back to humans. This makes it very difficult for agents to try out and compare many APIs.
To solve this, weâve created Cloudflare Wallets. Starting today, you can claim a Cloudflare Wallet handle for your account, which will provide a unique username to help you better connect with merchants. Soon, you will be able to set up and use your Cloudflare Wallet to pay for APIs and content.
Earlier this month, we announced the Monetization Gateway to help Cloudflare customers get paid for their websites and applications. Monetization Gateway will support micropayments using the x402 protocol, which allows for payments to be attached to HTTP requests. These micropayments will be able to pay for uses ranging from AI inference to data to content. If you want to pay or get paid for services behind Monetization Gateway and other x402-compatible endpoints, youâll need a wallet.Â
Cloudflare Wallets will allow you to store stablecoins, purchase services, and receive funds across the web. Each account with a wallet will also be able to create Virtual Wallets for its agents to enable them to buy APIs, MCP Tools, content, and more. You will be able to define guardrails for your Virtual Wallets (such as an allowance, an allow list, and a maximum transaction size) to help your agent spend money safely from your account. This will allow your agent to try out many APIs with low friction and managed risk. Wallet users will have the option to share their Cloudflare Wallet handles, which will give them a stable identity when interacting with merchants.
Building the two-sided agentic market
Cloudflareâs Monetization Gateway will allow eligible Cloudflare customers to sell their resources (such as content or APIs) headlessly to agentic buyers. But for that market to truly develop, agents need more tools to buy from merchants in a machine-native way. Wallets will add another tool to Cloudflareâs Agents SDK, enabling AI agents to easily purchase necessary APIs and content using micropayments.
There will be two types of Cloudflare Wallets: Account Wallets and Virtual Wallets.
Account Wallets are designed for humans who are owners and users of Cloudflare accounts. They will be able to add funds, delegate spend to virtual wallets managed by agents, and remove funds as needed.Â
Virtual Wallets , by contrast, are designed for agents and operate via API keys. Within a Virtual Wallet, an agent will be able to spend funds according to its permissions. Its maximum spend will be capped by the limit set by the owner of the Account Wallet. This framework gives agents freedom to act on behalf of users without constant manual approval while limiting an agentâs ability to overspend.
The freedom to explore
Virtual Wallets are exciting because they will allow agents to do what theyâre best at: explore dozens or hundreds of services and find the best one for a particular use case. Stablecoin micropayments via x402 will make it simple to try an API without an account, allowing agents to test new options with little friction. The spending caps on Virtual Wallets are designed so that humans can let agents explore autonomously within safe spending limits. These limits may seem like constraints, but counterintuitively they give agents more freedom. If an agent is responsible for $10, you can worry less about its spending than if it is responsible for $1,000. If an API only costs a few cents to try, then $10 is more than sufficient to pursue and evaluate many options.
Once you or your agent has picked an API to use, policies set by you in your Account Wallet will act as cost controls for Virtual Wallets. Want to give every employee a $100 per week budget for AI inference? Simply provision an Account Wallet with the right balance and create Virtual Wallets for each employee with that rule. Anyone who exceeds the limits on their Virtual Wallet will be able to request a manual override from a human who is authorized to make changes to the Account Wallet.
We want to make it easy for Account Wallets to set flexible yet firm spending policies that do not require daily, active monitoring. When something anomalous happens, such as unexpectedly fast spending, a human will be able to review and confirm whether everything is operating as intended. If the spend was intentional, then the administrator of the Account Wallet will be able to raise the limit or approve a one-time injection of funds. If the spend was unintentional, then the spending policies for adding funds to virtual wallets did their job by imposing caps.
We are working to make it as easy as possible to fund and use these wallets. We will start with simple ways to onramp and offramp funds within supported geographies, with self-funding via stablecoins available as an alternative for eligible users. The Internet will not shift completely overnight, but with a majority of traffic on the web now being driven by bots, we are excited to give agents and merchants first-class tools for agentic commerce.
Beyond payments alone
Allowing humans to delegate authority to agents to easily buy and sell services is a helpful starting point. But this delegation is not always obvious to the merchants as they interact with agents. Today, if an agent comes to your website, you may know little about them as a user, despite the fact that the agent is acting on behalf of an individual or an organization. This lack of attribution challenges many traditional web business models. Itâs easy to give a one-week free trial or sign-up credits to a human or an organization. Itâs hard to give these same perks to an agent that lacks a stable identity and when one human can spin up dozens of agents under their control.
We solve this problem by linking wallets to a Cloudflare account via cloudflare.pay. cloudflare.pay will allow agents to optionally identify themselves, since their identity is a delegate of the account. A research agent could live at research.example.cloudflare.pay, allowing merchants to know that it is an agent from a particular organization. This approach will permit agents to maintain consistent and persistent identities, making the experience better for all parties. It will be completely optional for agents to choose to declare their identity or not, and it will be up to businesses to decide whether they want to prioritize transacting with known agents.
Agent identifiers should be human-readable
We believe that the approach to dealing with agents will look like the approach to dealing with VPNs: If someone is unidentified, they are not inherently untrustworthy, but they need to prove themselves more. This is why we have Turnstile and other initiatives to detect bots within Bot Management. Our identity primitive will build on top of this prior work. For example, Web Bot Auth already allows agents to register their identity via a keypair. IDs attached to Cloudflare Wallets allow this keypair to become human-readable.
We know that agentic identity standards are changing quickly, which is why we wanted to keep our approach simple. We are proposing a human-readable identifier for a not-very-readable keypair, similar to the URL and IP-address pairings used in DNS. We are not trying to define a particular schema or other verification system. We only want to make identity simple to remember and easy to declare. As schemas to enrich agentic identity develop through the x402 Foundationâs initiatives, we will seek to adopt them and intend to encourage others to do the same.
The future of agentic commerce
At Cloudflare, we want to offer all the building blocks for agentic commerce to succeed. Monetization Gateway will offer a way for sellers to get paid without setting up traditional payment infrastructure. Wallets will offer a way for buyers to pay headlessly via agents. Identity will allow merchants to communicate with buyers who identify themselves or enforce identification requirements.
All of these building blocks will create a headless marketplace for the Internet. If you are excited about this and want to participate, you can claim your handle now. Weâre excited to see what you build and monetize.