agentic‑readiness docs
/
Scan at scale Blog Build one › Run a scan ›

DocsCommercex402

x402

Paying for a request with the HTTP 402 status code, so an agent can settle a charge inline.

adoption Early productiontrend ▲ risingchecked on every pagestatus watchedverified 2026-10-05

Why an agent cares

It is the only agentic-payment approach with real transaction volume, and it turns metered access into something an agent can handle without a human. The signal is a response to a request we do not make, not a document we can fetch.

Why we do not score it

A crawl sees x402 only on a 402 response to a paid resource, which a page crawl rarely requests, and there is no per-host document to fetch. Scoring it would mean probing other people's paid endpoints.

Adoption

Early production. Several independent organisations run it in production, though it is still niche on the open web.

Direction of travel: ▲ rising, as at .

AWS shipped general availability in CloudFront and WAF, and governance moved from Coinbase to a Linux Foundation project with 40 members in July 2026. Chainalysis has measured over 100 million transactions, though it attributes much of that growth to meme-coin farming.

Specifications

DocumentRevisionKind
x402 specification v2Version 2specification
x402Living documentguidance

Last re-read against the published documents: .