• Pricings

  • Stablecoin

    x402 Protocol Explained: Stablecoin Payments Over HTTP

    November 19, 2026

    8 mins read

    The x402 protocol puts stablecoin payments inside HTTP requests so software and AI agents can pay per call. How it works and what to check before using it.

    Orochi Network banner: x402 Protocol Explained, Stablecoin payments inside ordinary HTTP requests, with a code panel icon
    The x402 protocol is an open payment standard that puts stablecoin payments inside ordinary HTTP requests, using the "402 Payment Required" status code that the web's standards have long left "reserved for future use". It lets software, including AI agents, pay for a single API call or page without an account, a card or a checkout page. The server names a price, the client signs a stablecoin payment, and the content comes back once the payment settles.
    Payments and treasury teams keep hearing about it for a reason. On 8 November 2026 CoinDesk reported that Allium counted 68.3 million agent payments across the rails it tracks in the third quarter of 2026, double the quarter before, worth $3.7 million in total. That is about 5 cents a payment, and CoinDesk calls x402, which settles in stablecoins with no card involved, a purer version of this model. The count is rising fast while the money is still tiny, which is exactly when an institution should learn how the rail works and where its gaps are.

    How one x402 request works

    x402 adds three HTTP headers and a payment step to a normal web request. In version 2 of the specification (December 2025), now kept by the x402 Foundation on GitHub, one paid request runs like this:
    1. The client asks. An app or an agent sends an ordinary HTTP request for a resource, for example a data feed or an API result.
    2. The server names its price. Instead of the content, the server answers with status 402 and a PAYMENT-REQUIRED header. It lists what it accepts: the payment scheme, the network, the amount, the asset (usually USDC) and the address to pay.
    3. The client signs a payment. The client picks one of those options, signs a payment authorization with its wallet (a signed message that allows that one transfer; no money moves yet) and sends the request again with a PAYMENT-SIGNATURE header.
    4. The payment is checked and settled. The server checks the payment itself or asks a facilitator to check it. A facilitator is a service that verifies x402 payments and sends them on-chain, so neither side has to manage gas fees or blockchain nodes. Once the payment is valid, the facilitator settles it on-chain.
    5. The content comes back. The server returns the resource with status 200 and a PAYMENT-RESPONSE header that carries the settlement result.
    Sequence diagram of one x402 protocol request between client, server and facilitator The price, the payment and the receipt all travel in HTTP headers, so paying needs no account or checkout page.
    The protocol supports more than one way to pay. The exact scheme charges the advertised price. The upto scheme lets the client approve a maximum while the server settles only what was used, which suits metered services. Networks include Base, Solana and other chains, and the asset is a token that supports these signed transfer authorizations, with USDC as the common case. The x402 website says the protocol needs "no accounts or personal information" and charges no protocol fee; users pay the normal network fees.

    Who runs x402 now

    Coinbase started x402 and contributed it to the Linux Foundation. The Linux Foundation announced the x402 Foundation in April 2026 and its operational launch on 14 July 2026, with 40 member organizations at that point, among them Visa, Mastercard, American Express, Google, Stripe and Circle, the issuer of USDC. The main code repository now sits under the x402 Foundation, and Coinbase's copy is a development fork.
    For an institution this matters more than any single feature. A payment standard governed by a neutral foundation with card networks, cloud providers and a stablecoin issuer at the table is a different risk from a protocol owned by one company. It also means the specification can change through an open process, as it did when version 2 replaced the older headers.

    How much real activity x402 carries

    The best independent measure so far comes from TRM Labs, a blockchain analytics firm. In "Who's Actually Paying?" (9 September 2026), TRM looked at x402 payments through known facilitators on Base, Solana and Polygon since May 2025.
    Measure (TRM Labs, Sep 2026)Value
    Settlement transactions198.9 million
    Total value settledabout $52.7 million
    Share of value in USDC99.6%
    Value left after removing self-payments, bulk flows and sellers with few buyersabout $25.6 million
    Share of that value that looks like AI agents0.6% to 7.5%
    Self-payments are addresses paying themselves, and bulk flows are large streams from one or two payers; neither, nor a seller with only a handful of buyers, looks like real buying. The headline transaction count is large, but the value per payment is small and most of the volume is not AI agents buying things. TRM's own summary is blunt: "x402 is the most widely used agent-payment rail, but most of its volume is not agentic". The range of 0.6% to 7.5% depends on how strict the test for "agent" is, and TRM says its strict test may undercount. Allium's count in the CoinDesk report and TRM's measure use different data and methods, so their totals do not match; both show the same picture of many payments worth very little. Either way, x402 today is an early rail with real traffic, not yet a large payment flow.

    Where x402 sits in the agent payment stack

    x402 is one layer of a wider stack. BlackRock's paper "The Machine-Native Economy" (September 2026) maps it out. At the base sit protocols that let agents reach tools and talk to each other, such as Anthropic's Model Context Protocol (MCP). On top sit payment and trust protocols: Stripe and OpenAI's Agentic Commerce Protocol for checkout with existing merchants, Google's Agent Payments Protocol (AP2) for signed mandates, Visa's Trusted Agent Protocol for telling approved agents from bots, and x402. x402 is the one built around paying per HTTP request in stablecoins. Our guide to what agentic finance is covers the wider shift these protocols serve.
    Card networks are building next to it rather than against it. Mastercard's Agent Pay for Machines, shown in October 2026, runs on x402 and settles on Base, with spending limits the business sets for each task. It is a pilot with developer early access, not a general release. For a wider view of how these rails fit together, see our post on stablecoin stack layers and our crypto payment infrastructure report.

    What institutions should check before using x402

    x402 makes paying simple. The questions a bank, a payment service provider (PSP) or a stablecoin issuer has to answer sit around the protocol, not inside it.
    1. Who you rely on to settle. Most deployments use a facilitator to verify and broadcast payments. The specification says no scheme may let the facilitator or the server move funds other than as the client intended, but the facilitator still decides when a payment reaches the chain. Choose a production facilitator, run your own, or settle directly, and know which one you use for each route.
    2. Where identity and screening happen. The protocol asks for no account or personal information by design. Know your customer (KYC) checks, sanctions screening and limits are the job of whoever runs the service or the wallet. Our guide to stablecoin rules in 2026 covers the regimes that set those duties.
    3. Whether the volume you see is real. TRM removed about half of x402 value as self-payments, bulk flows and sellers with very few buyers before it looked for agents. Any business case built on headline x402 numbers should apply a similar screen.
    4. What record you keep of what was paid for. The on-chain settlement shows the amount, the asset and the two addresses. It does not show what the paying agent was asked to do, what data it priced the purchase from, or what content came back. TRM puts the gap in one line: "The agent signs and a facilitator broadcasts, with no review in between." Our post on agentic payments and what the settlement record must prove covers this record in detail.
    5. Which version and scheme you support. Version 2 changed the header names, and newer schemes such as upto have been added since. Pin the version your systems accept and follow the x402 Foundation's changes.
    The fourth point is the one most explainers skip, and it is where Orochi works. zkDatabase, the verifiable database built by Orochi Network, is designed to keep the data behind an agent's payment decision with a Zero-Knowledge Proof for every insert, update and query, so a counterparty or an auditor can check what the agent used without seeing the raw data. In plain terms, the proof shows that the data was stored and processed as claimed, without showing the data itself. That matters most for a treasury or payments agent that moves real money, where the record of why it paid counts as much as the payment.

    See how zkDatabase keeps proof of agent data

    Explore zkDatabase to see how a proof for every query lets a counterparty check which data an agent used for a payment, and that it was stored and processed as claimed, without seeing it.