x402 hit 165 million transactions — here's what it still can't do

By late April 2026, x402 had processed 165 million transactions across Coinbase Agent.market, Stripe Machine Payments, CoinGecko paid endpoints, Circle Wallets, and the Cloudflare Agents SDK, representing roughly $50 million in cumulative volume. That's not a proof-of-concept. That's production infrastructure for agent-to-service payments running at scale.

It's also a partial solution to a much bigger problem — and the gap between what x402 handles and what a fully monetized agent ecosystem requires is where most builders are getting stuck.

what x402 actually solves

x402 is payment transport. The protocol is elegant: a paid endpoint returns a 402 status with payment details, the calling agent pays in USDC, and retries with a payment receipt header — all without human intervention. For synchronous, single-agent, single-request payment flows, it works.

The five named production deployments all use x402 in exactly this mode: an agent calls an endpoint, pays per call, gets the response. Coinbase Agent.market is the clearest example — agents purchase API access at per-call rates, x402 handles the USDC settlement, the transaction confirms on Base.

The 69,000 active agents on x402 by late April are mostly doing exactly this: discrete, synchronous, agent-to-service payments where the agent has a pre-funded wallet and the service charges a flat rate per call.

what x402 doesn't handle

The harder patterns are the ones that don't fit that mold.

Multi-agent settlement. When one orchestrator agent dispatches three sub-agents that each call paid services, the payment flow is no longer point-to-point. You need to split fees, attribute revenue to the right endpoint, and handle cases where the orchestrator is paying on behalf of a delegated agent that itself may have billing authority. x402 has no primitive for this — each call is independent, and the relationship between calls is invisible to the payment layer.

Agent identity and reputation. x402 verifies payment, not the payer. A new agent with a funded wallet looks identical to a well-behaved agent that has made 50,000 successful requests. For services that want to offer lower rates or higher throughput to trusted agents, x402 provides no basis for that differentiation. Rate-limiting is blind — you cap everyone or you cap no one.

Rate negotiation. x402 endpoints publish a fixed price. There is no mechanism for an agent to present its usage history and negotiate a volume rate, or for a service to dynamically price based on an agent's creditworthiness. The $50 million in x402 volume all settled at fixed per-call rates.

Outcome-based billing. The emerging monetization model for agentic services is outcome-based: charge when the agent succeeds, not when it calls the endpoint. x402's payment-before-response architecture is a poor fit for this — the agent pays to make the call, not to get the result.

what fills the gap

The payment-identity layer is the primitive that makes these patterns possible. An agent that carries a signed reputation score — derived from its payment history, error rates, and task completion record — can present that score at billing time. Services can price dynamically based on that score. Orchestrators can use it to route to sub-agents with proven reliability rather than the cheapest available endpoint.

This is what Agent FICO is: a 300-850 scoring system baked into the payment JWT, so the monetization layer and the trust layer are the same primitive. When an agent makes a payment through MnemoPay, its FICO score updates in real time. Services see the score on every request. Orchestrators can set minimum FICO thresholds for sub-agent delegation.

It ships today on npm. The agent payment infrastructure that x402 opened up, MnemoPay closes out — identity, reputation, multi-agent settlement, and outcome-based billing in one SDK. https://mnemopay.com