x402 hit 119M transactions — here's the layer that still isn't built
x402 hit 119M transactions — here's the layer that still isn't builtbase's cumulative x402 transaction count passed 119 million. total volume: $35M+. cloudflare built it into pay-per-crawl tooling. nous. . .
x402 hit 119M transactions — here's the layer that still isn't builtbase'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. what x402 does cleanlythe HTTP 402 status code says "payment required. " an agent receives it, pays via stablecoin on Base, 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. the agent-as-principal scenariowhat 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. MnemoPay's position in the x402 ecosystemMnemoPay 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. dev portal:https://mnemopay. com