Protocol guide · updated 2026-07-18What is x402?
x402 is an open protocol that lets AI agents and applications pay for web resources over HTTP. When a client requests a paid resource, the server answers with the HTTP 402 Payment Required status code and machine-readable payment instructions. The client pays — typically in USDC stablecoins, settled in seconds — retries with proof of payment, and receives the resource. No account, no API key, no checkout form.
Originally created by Coinbase in May 2025, x402 is now stewarded by the x402 Foundation under the Linux Foundation with 40 member organizations, including Visa, Mastercard, American Express, Stripe, Google, AWS, Cloudflare, Circle, Shopify, and Coinbase. The protocol specification lives at x402.org.
Why trust this page: ForgeMesh Labs operates 11 x402 services and counting — 500+ paid endpoints priced from $0.001 —, and runs an independent crawler of the x402 discovery ecosystem. Everything here is written from first-hand operation, not summaries of summaries.
How does x402 work?
An x402 payment is a four-step HTTP exchange that completes in a few seconds:
1. The agent requests a resource
A client — usually an AI agent — sends an ordinary HTTP request to a paid endpoint, with no credentials of any kind.
2. The server answers 402 Payment Required
The response body and PAYMENT-REQUIRED header carry structured payment requirements: price, currency, network, receiving address, timeout, and often the input schema and a worked example.
3. The agent pays and retries
The client signs a payment authorization from its wallet (commonly USDC on Base) and retries the same request with an X-PAYMENT header containing the proof.
4. The server verifies, settles, and serves
A facilitator verifies and settles the payment on-chain, and the server returns the resource. If the handler fails, settlement is cancelled — the buyer is not charged for errors.
The protocol defines payment schemes— "exact" for fixed prices, with "upto" and Cloudflare's proposed "deferred" scheme extending it to usage-based pricing and settlement over traditional rails.
A brief history of x402
| Date | Milestone | Why it matters |
|---|---|---|
| May 2025 | Coinbase releases x402 | Coinbase publishes x402 as an open-source protocol and whitepaper at x402.org, activating the HTTP 402 status code for machine-native payments with stablecoins. |
| September 23, 2025 | Cloudflare and Coinbase announce the x402 Foundation | Cloudflare ships x402 support in its Agents SDK and MCP integrations, and proposes the deferred payment scheme that decouples cryptographic verification from settlement. |
| July 1, 2026 | Cloudflare opens the Monetization Gateway waitlist | Any resource behind Cloudflare — pages, APIs, datasets, MCP tools — can charge agents per request, settling over x402. |
| July 14, 2026 | Linux Foundation launches the x402 Foundation operationally | 40 member organizations at launch, including Visa, Mastercard, American Express, Stripe, Adyen, Google, AWS, Shopify, Circle, Cloudflare, and Coinbase. The protocol moves to neutral, vendor-independent governance. |
| September 15, 2026 | Cloudflare default bot policy changes | New Cloudflare defaults block AI training and agent crawlers on ad-supported sites. Paying for access via x402 becomes the sanctioned path for agents to reach a large share of the web. |
Sources: Cloudflare (Sept 23, 2025), Cloudflare Monetization Gateway (July 2026), Linux Foundation press release (July 14, 2026). Read our full analysis: Linux Foundation takes over x402 →
How big is the x402 ecosystem?
ForgeMesh runs an independent crawler of the x402 Bazaar discovery catalog three times a day. As of July 18, 2026, from our own measurements:
distinct paid x402 resources cataloged by our crawler since tracking began
live listings in the Bazaar discovery catalog at any given time
unique sellers — up from 1,100 on July 15, 2026 (+3% in three days)
Source: ForgeMesh Bazaar crawler (original data, refreshed 3× daily). Institutional adoption is moving equally fast: the x402 Foundation launched with 40 member organizations, and both Cloudflare and AWS now embed x402 at the edge.
x402 vs API keys vs Stripe MPP
| x402 | API keys + cards | Stripe MPP | |
|---|---|---|---|
| Payment trigger | HTTP 402 response with machine-readable payment requirements | Signup form, dashboard, manually provisioned API key | Stripe-managed machine payment flow (MPP) |
| Account required | None — a funded wallet is the only prerequisite | Account, billing profile, card on file | Stripe relationship for the seller |
| Minimum viable price | $0.001 or lower (stablecoin settlement) | Card fees make sub-$0.30 uneconomical | Sub-cent possible on stablecoin rails |
| Settlement | Atomic, on-chain (USDC on Base, Solana, and others) | Monthly invoice or card batch | Stripe rails: cards or stablecoins |
| Agent-friendly | Yes — designed for autonomous clients | No — checkout flows require a human | Yes — Stripe-centric |
| Governance | x402 Foundation under the Linux Foundation (40 members) | Per-vendor | Stripe |
See x402 in production
The fastest way to understand x402 is to trigger a real payment challenge. Every ForgeMesh endpoint answers unauthenticated requests with a live, spec-compliant 402:
curl -X POST https://x402.forgemesh.io/current-time \
-H 'Content-Type: application/json' -d '{}'
# → HTTP 402 Payment Required
# → price, network, input schema, worked example,
# and payment instructions — all machine-readablex402: frequently asked questions
What is x402 in one sentence?
x402 is an open protocol that lets software — especially AI agents — pay for web resources at request time over plain HTTP, using the 402 Payment Required status code to communicate the price and stablecoins or other rails to settle it.
Who created x402?
Coinbase created x402 and released it as open source in May 2025. In September 2025 Coinbase and Cloudflare announced the x402 Foundation, and on July 14, 2026 the Linux Foundation launched the foundation operationally with 40 member organizations, moving the protocol to neutral community governance.
Is x402 only for crypto payments?
No. Most production traffic today settles in USDC on networks like Base, but the protocol is payment-type agnostic by design, and the x402 Foundation explicitly supports multiple payment types from traditional cards to stablecoins. Cloudflare’s deferred scheme separates verification from settlement so traditional rails can participate.
What does an x402 payment cost?
Whatever the seller sets — there is no protocol-imposed minimum. In practice, live x402 endpoints price from $0.001 per call upward. ForgeMesh’s own 500+ paid endpoints range from $0.001 to $0.75 per request.
How is x402 related to HTTP error 402?
HTTP 402 Payment Required was reserved in the HTTP specification in 1997 "for future use" and sat mostly unused for nearly three decades. x402 is the first widely adopted standard to activate it: the 402 response carries structured payment requirements that a client can fulfill programmatically.
How many x402 services exist today?
ForgeMesh’s independent crawler has cataloged over 27,000 distinct paid x402 resources, with the live Bazaar discovery catalog fluctuating around 25,000 listings from more than 1,130 unique sellers as of July 18, 2026 — up from 1,100 sellers on July 15, 2026.
Do I need an API key to call an x402 API?
No. That is the point: an agent hits the endpoint, receives a 402 challenge describing the price and payment address, pays it (typically USDC), retries with the payment proof header, and gets the resource. No account, no signup, no key management.
Go deeper: the 30-year history of HTTP 402 Payment Required · ForgeMesh blog · official x402 specification