Galaxy Digital Maps the Full x402 Agentic Payment Stack as AI Commerce Nears $5 Trillion
Galaxy Digital published its most comprehensive institutional analysis of agentic payment infrastructure on March 23, tracing in granular detail how value moves from an AI agent's initial service request through coordination, facilitation, currency, and on chain settlement a layered stack the report's authors argue will quietly make blockchains the invisible backbone of the emerging AI economy. The report, titled "Agentic Payments: x402 and AI Agents in the AI Economy" and authored by Lucas Tcheyan and Vikram Singh , arrives as Cloudflare simultaneously updated its Agents SDK to include first class support for both x402 and the new Machine Payments Protocol (MPP) , cementing the two standards as the leading candidates for machine native commerce. The x402 Standard and Its Architecture The x402 protocol , launched by Coinbase in May 2025, repurposes the long dormant HTTP 402 Payment Required status code a response type included in the original HTTP specification but left unimplemented for decades due to the absence of supporting infrastructure. Under x402, when an AI agent requests a paid resource from a server, the server responds with a 402 status that specifies the payment amount, accepted token types, destination wallet address, and target blockchain. The agent then returns a cryptographic signature authorizing the payment, and a facilitator service executes the on chain transfer before the server delivers the resource. Coinbase's own teams described the ambition plainly: "Let's kill the API key." Version 2 of the standard, released on December 11, 2025 , expanded the protocol along three dimensions: a unified payment interface supporting multiple blockchains and assets through a single format, wallet based identity with reusable access sessions to reduce repeated on chain interactions, and automatic service discovery allowing facilitators to index endpoints and pricing without manual configuration. These additions enabled x402 to support subscriptions, prepaid access, usage based billing, and multi step agent workflows beyond the simple per request model of the initial release [1]. The Full Value Flow The Galaxy report maps x402's payment stack in five discrete layers. At the top, the Agent Layer initiates task requests and determines constraints including price tolerance, latency, and preferred chain. The Coordination Layer handles service discovery, intent signaling, constraint enforcement, and multi agent orchestration before any payment is triggered. The Facilitation Layer then routes, verifies, and executes the transaction, abstracting away blockchain specific complexity such as wallet management, gas selection, and network routing. The Currency Layer defines what is transferred primarily USDC stablecoins, enabling predictable machine native pricing. Finally, the Blockchain Layer executes and finalizes the transfer, providing cryptographic settlement and an auditable record that propagates confirmation back up the stack to the service provider [1]. The report's central argument is that this architecture renders blockchain infrastructure effectively invisible to end users and developers. Agents transact autonomously, businesses receive payment in stablecoins settled on public networks, and neither party needs to interact with crypto infrastructure explicitly. As the Galaxy team put it, the standard aims to: "enable value to move across the internet as seamlessly as information, whether the actor is a human, an app, or an agent." Adoption Signals and Shifting Usage Patterns Early x402 adoption followed a pattern familiar to crypto infrastructure launches. An initial surge in late October and early November 2025 was driven largely by speculative activity, including memecoin minting and apparent wash trading. Since early December, however, that pattern has shifted measurably. Gaming and wash trading activity defined by Artemis Analytics as apparent self dealing dropped below 50% of total transaction volume, replaced by growing market share from agent to agent services, data as a service, and infrastructure and utility payments [1]. Among the concrete deployments cited in the Galaxy report: Nous Research , a decentralized AI lab, enabled x402 payments for access to its Hermes 4 language model, allowing agents to pay per inference call rather than managing subscription accounts. Trading agents have similarly begun purchasing individual API calls to blockchain data provider Nansen on demand, paying only for the data required to complete a specific analytical task rather than maintaining standing subscriptions. Cloudflare SDK and the MPP Comparison On March 24, Cloudflare updated its Agents SDK documentation to confirm official support for both x402 and MPP , the Machine Payments Protocol co authored by Tempo Labs and Stripe and currently on the IETF standards track [2]. The two protocols serve overlapping but distinct functions, as the table below illustrates: | Aspect | x402 (Coinbase) | MPP (Stripe/Tempo) | | | | | | Payment Methods | On chain stablecoins (USDC on Base, ETH, Solana) | Cards, Bitcoin Lightning, stablecoins | | Model | Per request | Sessions (streaming, pay as you go) | | Standards Body | x402 Foundation (Coinbase + Cloudflare) | IETF standards track | | Latency/Cost | Standard blockchain confirmation | Sub millisecond, sub cent | | Backwards Compatible | N/A | MPP clients work with x402 services | A critical interoperability note from the Cloudflare documentation: MPP is backwards compatible with x402 , meaning MPP clients can consume existing x402 services without any modification to the server side [2]. Both protocols share the same core HTTP flow a client requests a resource, receives a 402 payment challenge, fulfills the payment, and retries with a payment credential but MPP extends the pattern with formal WWW Authenticate: Payment and Authorization: Payment header schemes that enable session based streaming payments at sub millisecond latency and sub cent per tra…