x402 hit 119M transactions — here’s the layer that still isn’t built

x402 交易量突破 1.19 亿 —— 缺失的架构层仍待构建

Base’s cumulative x402 transaction count passed 119 million. Total volume: $35M+. Cloudflare built it into pay-per-crawl tooling. Nous Research uses it for per-inference billing of Hermes 4. Gas costs are nominal (<$0.0001 per transaction). x402 is production-viable. This is no longer an “interesting protocol” — it’s live infrastructure with real volume. That makes the missing layer more urgent, not less.

Base 链上的 x402 累计交易量已突破 1.19 亿次，总交易额超过 3500 万美元。Cloudflare 已将其集成到“按抓取付费”（pay-per-crawl）工具中，而 Nous Research 则将其用于 Hermes 4 模型的“按推理付费”结算。其 Gas 费用极低（每笔交易低于 0.0001 美元）。x402 已具备生产环境应用能力，它不再仅仅是一个“有趣的协议”，而是拥有真实交易量的实时基础设施。这使得缺失的架构层变得更加紧迫。

What x402 does cleanly

x402 的核心优势

The HTTP 402 status code says “payment required.” An agent receives it, pays via stablecoin on Base, and gets access. The flow is clean because it’s stateless — no account setup, no API key negotiation, no subscription. The economics work because gas on Base is effectively zero. Cloudflare’s pay-per-crawl use case is the canonical example: an AI agent accessing web content pays per page. Nous Research’s per-inference billing is the model API version of the same pattern. Both of these are agent-as-consumer scenarios — the agent is buying access to a resource.

HTTP 402 状态码代表“需要付款”。当 AI Agent 收到该状态码时，通过 Base 链上的稳定币支付即可获得访问权限。这种流程非常简洁，因为它无需状态维护——无需注册账户、无需协商 API 密钥，也无需订阅。由于 Base 链上的 Gas 费用几乎为零，这种经济模型得以成立。Cloudflare 的“按抓取付费”是典型的应用案例：AI Agent 在访问网页内容时按页面付费；Nous Research 的“按推理付费”则是模型 API 领域的同类模式。这些都属于“Agent 作为消费者”的场景，即 Agent 正在购买资源访问权。

The agent-as-principal scenario

“Agent 作为委托人”的场景

What x402 doesn’t address: when the agent is a financial principal making spending decisions on behalf of a human. Not “pay to access this API” but “buy this ticket, make this reservation, spend up to $200 on this task.” In the consumer-access scenario, x402’s transaction is the proof. In the agent-as-principal scenario, you need more: was this spend within the mandate the human gave? Was the context at execution time what the authorization was based on? Can a counterparty trust this agent’s payment history? Those questions require a layer above the protocol.

x402 未能解决的问题是：当 Agent 作为财务委托人，代表人类做出消费决策时该怎么办？这不再是“支付以访问 API”，而是“购买这张票、进行这项预订、为这项任务支出最高 200 美元”。在消费者访问场景中，x402 的交易记录即是证明；但在“Agent 作为委托人”的场景中，你需要更多信息：这笔支出是否在人类授权的范围内？执行时的上下文是否与授权基础一致？交易对手能否信任该 Agent 的支付历史？这些问题需要协议之上的架构层来解决。

MnemoPay’s position in the x402 ecosystem

MnemoPay 在 x402 生态中的定位

MnemoPay is not a competitor to x402. It’s the accountability layer that sits above it. Agent FICO (300-850 machine creditworthiness score) uses payment history across x402 and other rails to build a trust signal for machine principals. The signed receipt model links each transaction to its upstream authorization. 672+ tests, v1.0.0-beta.1, 1.4K weekly npm downloads. The SDK works alongside x402 — you add the intent-linkage and receipt layer without changing your payment rail. As x402 moves from developer tooling (119M Cloudflare/Nous transactions) toward consumer-scale agent commerce (Visa’s holiday 2026 forecast), the accountability layer becomes non-optional.

MnemoPay 并非 x402 的竞争对手，而是位于其之上的问责层。Agent FICO（300-850 分的机器信用评分）利用 x402 及其他支付渠道的交易历史，为机器委托人构建信任信号。其签名收据模型将每笔交易与其上游授权关联起来。目前该项目已完成 672 次以上测试，版本为 v1.0.0-beta.1，每周 npm 下载量达 1.4K 次。该 SDK 可与 x402 并行工作——你无需更改支付渠道，即可添加意图关联和收据层。随着 x402 从开发者工具（1.19 亿次 Cloudflare/Nous 交易）向消费者规模的 Agent 商业化（Visa 预测 2026 年假期实现）迈进，问责层将成为不可或缺的组件。

Dev portal: https://mnemopay.com