CLAWD COMPUTESign inGet API key
The official Clawd guide · x402

Every chain. One payment protocol.

x402 is the open standard that lets any client — a person, an app, an AI agent — pay for any API, on any blockchain, inside a single HTTP request. No accounts, no subscriptions, no API keys: the payment is the authentication. This is the omni-chain guide: what x402 is, how it started, how it works, and how to get on board.

Get on board → See the chain matrix → How it started →
The idea

A status code waited 26 years for its moment

HTTP has had a payment status code since the beginning: 402 Payment Required. The 1999 HTTP/1.1 specification defined it in one sentence — "This code is reserved for future use" — and every revision since (RFC 7231 in 2014, RFC 9110 in 2022) carried the same placeholder forward. The web's designers always knew machines would need to charge machines. What they didn't have was money that could move at HTTP speed: programmable, borderless, and final in seconds.

Stablecoins on modern blockchains are that money. x402 is the mechanism the 402 code was waiting for: a server names its price in an ordinary HTTP response, the client signs a payment with its own wallet, and a facilitator verifies and settles it on-chain. The whole exchange rides inside the request the client was already making.

How it started

From reserved code to open standard

June 1999

402 is reserved

RFC 2616 (HTTP/1.1) defines 402 Payment Required as "reserved for future use" — §10.4.3, one sentence, no mechanism. The placeholder survives unchanged into RFC 9110 (2022).

6 May 2025

Coinbase launches x402

Coinbase's Developer Platform launches x402 — "instant stablecoin payments directly over HTTP" for APIs, apps and AI agents, with AWS, Anthropic, Circle and NEAR named at launch. Version 1 settles USDC, primarily on Base, using EIP-3009 signed authorizations: the payer signs, the facilitator submits and pays the gas.

16 September 2025

Google's AP2 adopts x402 for crypto settlement

Google announces the Agent Payments Protocol (AP2) with 60+ organizations, standardizing authorization for agent purchases — and releases the A2A x402 extension, built with Coinbase, the Ethereum Foundation and MetaMask, as the production path for settling those mandates in stablecoins via x402.

23 September 2025

Coinbase + Cloudflare announce the x402 Foundation

Coinbase and Cloudflare announce their intent to create the x402 Foundation to steward x402 as an open internet standard. The same day, Cloudflare ships x402 support in its Agents SDK and MCP tooling, proposes a deferred scheme (identity handshake now, settlement later), and is building pay-per-crawl on the same rails.

11 December 2025

x402 V2 — and 100 million payments

V2 moves all payment data into headers — PAYMENT-REQUIRED, PAYMENT-SIGNATURE, PAYMENT-RESPONSE — standardizes network ids on CAIP-2, and adds facilitator discovery and wallet-based sessions. Coinbase reports over 100 million payments processed in the protocol's first seven months.

April – July 2026

The Foundation becomes the neutral home

The Linux Foundation launches the x402 Foundation (2 April 2026), welcoming Coinbase's contribution of the protocol; by its operational launch on 14 July 2026, 40 member organizations have joined, and the specification and code live at github.com/x402-foundation/x402 under Apache-2.0.

November 2026

The omni-chain era — our chapter

Facilitators stop being single-chain. Our hub, x402.wtf, goes live fronting Solana, Base, Robinhood Chain, HyperEVM, Bitcoin, Lightning and Cardano behind one discovery document — the same protocol, every chain a leg. This guide, and the facilitator skill below, are how we hand that foundation to everyone else.

How it works

One request, four moves

STEP 1 — ASK

The client requests a resource

An agent calls a paid API exactly as it would call a free one.

STEP 2 — 402

The server names its price

The answer is 402 with a PAYMENT-REQUIRED header: the exact amount, asset, network and payTo address — machine-readable, no checkout page.

STEP 3 — SIGN

The client signs a payment

The client's own wallet signs a payment payload — an EIP-3009 authorization on EVM chains, a signed transfer on Solana, a broadcast proof on Bitcoin — and retries with PAYMENT-SIGNATURE.

STEP 4 — SETTLE

The facilitator settles

A facilitator verifies the payload and settles it on-chain. The server serves the resource with a PAYMENT-RESPONSE receipt. One payment, one call.

The three roles

The client (payer)

Holds a wallet; pays per call. Any agent with a wallet and the x402 flow can buy from any x402 seller on any supported chain — see the pay-side skill in the onboarding section.

The resource server (seller)

Any API that prices a route. It answers 402 with its price and a payTo, asks a facilitator to verify and settle, and never touches a blockchain itself.

The facilitator (settler)

Exposes GET /supported, POST /verify and POST /settle. Verifies signatures and amounts, relays settlement, pays the gas. Non-custodial for the standard exact scheme: the payer signs, the facilitator never holds payer keys.

Omni-chain

One facilitator, every chain a leg

x402 names networks in CAIP-2 (eip155:8453, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp), so one facilitator can settle the same protocol everywhere. This is the live chain matrix of our omni-chain hub, x402.wtf — statuses are the truth of its code paths, verified against each network:

ChainNetworkHow it settlesStatus
Solanasolana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpSigned USDC transfer; the facilitator can co-sign as fee payer, so the payer needs no SOLLIVE
Baseeip155:8453EIP-3009 transferWithAuthorization, delegated to Coinbase's CDP FacilitatorLIVE
Robinhood Chaineip155:4663EIP-3009 in USDG, settled by the hub's gas-only relayerLIVE — settle needs relayer ETH
HyperEVMeip155:999EIP-3009 in USDC, settled by the hub's gas-only relayerLIVE — settle needs relayer HYPE
Bitcoinbip122:000000000019d6689c085ae165831e93Payment proof: the payer broadcasts; the hub verifies the txid and amount on a public indexerLIVE
Lightningbitcoin-lightningPreimage proof: sha256(preimage) must equal the payment hashLIVE
Cardanocip34:1-764824073Payment proof verified via Koios: lovelace or native-asset sums to the payTo addressLIVE
ZcashzcashDelegates to the operator's Zaino scan backend for shielded verificationBACKEND PENDING — fails closed (503)
NEAR Intentscross-chainIntent quotes across 232 assets / 39 chains via 1Click, alongside the facilitator legsLIVE

Discovery is one document per facilitator — read ours: musebook.trade/.well-known/x402-facilitator and the registry at musebook.trade/api/x402/catalog. A leg is listed only when its path is complete and verified; gated legs say so, here and in the discovery document itself.

Get on board

Three ways in

1 · Pay — use x402 tools

Give your agent one skill file and it can call all 215 pay-per-call tools on this gateway, register domains with USDC, and use the Musebook facilitator — Solana or Base, no accounts or API keys. It also wires in 402reviews: check a paid API's track record before paying, leave a review after.

Raw file →
https://clawdcompute.us/SKILL.md

2 · Sell — price your API

Put a price on a route and let a facilitator handle the money: answer unpaid calls with a 402 challenge naming your price and payTo, verify and settle through a facilitator, serve on success. List your routes where agents look — the Musebook registry catalog is public and free to read.

3 · Settle — run a facilitator

Spin up your own facilitator on any blockchain, on this foundation: the standard /supported + /verify + /settle contract, per-chain leg recipes (Solana, any EIP-3009 EVM chain, Bitcoin, Lightning, Cardano), discovery, registry listing, and the safety rules — in one skill any agent can follow.

Raw file →
https://clawdcompute.us/FACILITATOR-SKILL.md
The Clawd x402 stack

Built on it, end to end

Honest edges. Historical dates and ecosystem figures on this page are attributed to their sources (Coinbase, Cloudflare, the Linux Foundation, the RFCs) and were verified on 2026-11-21; payment-volume figures are Coinbase-reported. Chain statuses describe our hub's own code paths today — a leg marked gated is gated, and its discovery document says the same. x402 itself is an open standard stewarded by the x402 Foundation; this guide is Clawd's, and the protocol belongs to everyone.