Coinbase Unveils x402 Protocol for HTTP-Native Stablecoin Micropayments
Collaborating with Circle, Anthropic, AWS, and NEAR, the open standard revives the dormant HTTP 402 code to enable autonomous transactions for software and AI agents.
At a glance Announced
- What happened
- Coinbase launched x402, an open standard utilizing HTTP 402 to let applications and AI agents conduct instant stablecoin micropayments over web protocols.
- Why it matters
- The standard allows software to pay programmatically per API request or compute resource without manual credit card billing or subscription setups.
- Who is affected
- Web developers, API providers, autonomous AI agent builders, and stablecoin issuers including Circle.
- Takes effect
- 2026-11-04
- What's next
- Wider deployment of developer tooling and client SDKs alongside launch partners Circle, AWS, Anthropic, and NEAR.
- Primary source
- coinbase.com: Introducing x402: a new standard for internet-native payments
Key points
- Coinbase introduced x402, an open standard embedding instant stablecoin micropayments directly into HTTP via the 402 status code.
- The launch includes industry partners Circle, Anthropic, Amazon Web Services (AWS), and NEAR.
- The architecture uses standard HTTP headers verified by onchain payment facilitators to let AI agents and software transact autonomously.
Coinbase launched x402 on Nov. 4, introducing an open standard designed to integrate instant stablecoin settlements directly into the web's HTTP architecture 1. The payment protocol revives the long-dormant HTTP "402 Payment Required" status code, allowing automated scripts, developers, and artificial intelligence agents to pay for digital services like application programming interfaces (APIs) and software access using stablecoins such as $USDC 1.
Coinbase is rolling out the protocol alongside several technology and infrastructure partners, including Circle, Anthropic, Amazon Web Services (AWS), and NEAR 1. The system operates through standard client-server exchanges: an HTTP server responds to an unauthorized request with a 402 status code containing pricing and accepted tokens, after which the client submits an encoded payment payload in an HTTP header 1. A payment facilitator—such as the Coinbase x402 Facilitator service—verifies and finalizes the settlement onchain before the requested resource is served 1.
Solving Friction for Agent Commerce
According to Coinbase Developer Platform head of engineering Erik Reppel, traditional rails like credit cards and bank transfers remain too slow, geographically bounded, and manual to power an autonomous machine economy 1. The emergence of low-cost Layer-2 networks like Base, where transaction fees have declined to roughly 1 cent, has made web micropayments economically feasible compared to earlier Bitcoin-based iterations 1. Circle VP of product management Gagan Mac stated that x402 simplifies monetization by stripping away registration steps, conventional authentication barriers, and complex signatures 1. NEAR co-founder Illia Polosukhin noted that pairing x402 with NEAR intents allows cross-chain settlements that mask underlying blockchain complexity from users 1.
The protocol enables pay-per-request monetization models, such as metered software usage and pay-as-you-go API consumption, without requiring subscriptions or advance billing 1. Autonomous applications include automated compute provisioning, market intelligence retrieval, and algorithmic inventory replenishment without human intervention 1. The launch comes as onchain machine interactions scale rapidly, following recent data highlighted in Chainalysis: AI Agent Commerce Surges Past 138M Transactions on Base regarding the expansion of automated web commerce. At the time of writing, $BTC traded at $80,335 while $ETH changed hands at $2,422.
Questions this story raises
- What is the HTTP 402 status code?
- HTTP 402 Payment Required is a reserved status code in standard web protocols created for digital payments, which historically remained largely unused due to the lack of native internet payment infrastructure.
- How does x402 facilitate autonomous transactions?
- An HTTP server responds to requests with 402 and pricing details. Software or AI agents then return an encoded payment payload in an HTTP header, which is settled onchain via facilitators before access is granted.
Sources
- [1] Introducing x402: a new standard for internet-native payments — coinbase.com, November 4, 2026
Written by Basis Desk's newsroom system from the primary sources above and machine-verified against them before publication. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.
The Daily Brief, in your inbox at 07:00 ET
Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.
Get the big crypto stories first
A few alerts a day at most: major breaking news and the morning brief. Switch off anytime.
Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.