{"slug": "x402-hit-119m-transactions-here-s-the-layer-that-still-isn-t-built", "title": "x402 hit 119M transactions — here's the layer that still isn't built", "summary": "Base's x402 transaction count has surpassed 119 million, with total volume exceeding $35 million and gas costs below $0.0001 per transaction. Cloudflare has integrated x402 into its pay-per-crawl tooling, and Nous Research uses it for per-inference billing of Hermes 4. MnemoPay, an accountability layer for agent-as-principal scenarios, has released v1.0.0-beta.1 with 1.4K weekly npm downloads, providing a signed receipt model and machine creditworthiness scoring.", "body_md": "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).\n\nx402 is production-viable. this is no longer an \"interesting protocol\" — it's live infrastructure with real volume.\n\nthat makes the missing layer more urgent, not less.\n\n**what x402 does cleanly**\n\nthe 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.\n\ncloudflare'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.\n\nboth of these are agent-as-consumer scenarios — the agent is buying access to a resource.\n\n**the agent-as-principal scenario**\n\nwhat 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.\"\n\nin 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?\n\nthose questions require a layer above the protocol.\n\n**MnemoPay's position in the x402 ecosystem**\n\nMnemoPay 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.\n\n672+ 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.\n\nas 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.\n\ndev portal: [https://mnemopay.com](https://mnemopay.com)", "url": "https://wpnews.pro/news/x402-hit-119m-transactions-here-s-the-layer-that-still-isn-t-built", "canonical_source": "https://dev.to/t49qnsx7qtkpanks/x402-hit-119m-transactions-heres-the-layer-that-still-isnt-built-d0b", "published_at": "2026-06-16 22:21:48+00:00", "updated_at": "2026-06-16 23:21:40.890596+00:00", "lang": "en", "topics": ["ai-agents", "developer-tools"], "entities": ["Base", "Cloudflare", "Nous Research", "MnemoPay", "x402", "Hermes 4", "Visa"], "alternates": {"html": "https://wpnews.pro/news/x402-hit-119m-transactions-here-s-the-layer-that-still-isn-t-built", "markdown": "https://wpnews.pro/news/x402-hit-119m-transactions-here-s-the-layer-that-still-isn-t-built.md", "text": "https://wpnews.pro/news/x402-hit-119m-transactions-here-s-the-layer-that-still-isn-t-built.txt", "jsonld": "https://wpnews.pro/news/x402-hit-119m-transactions-here-s-the-layer-that-still-isn-t-built.jsonld"}}