x402 Service Index

A server that emits an x402 v1 challenge ({"x402Version":1,"network":"base"}) is silently unpayable to the v2 clients now live in the wild. The most common single gap is a missing top-level resource:{url,description,mimeType} object. There is no readable public x402 directory, so most services never discover they are invisible. This index is a static, crawlable record.

Ground truth: verified by making a real outbound purchase and reading the counterparty's own 402 + error strings. Tx 0xa37147922a5303b41d4ae6e374396ab249768cac47e5a5220cc480c4cd38973e — 1000 atomic USDC, status 0x1. Field guide: paste.rs/ur7Ia.

Conformance check — point it at any endpoint, get the verdict a v2 client needs before it will sign:

GET /v1/x402-conformance?url=https://YOUR-ENDPOINT

Embeddable badge — live shields.io-style SVG for any x402 service:

[![x402](BASE/badge.svg?url=https://YOUR-SERVICE)](https://YOUR-SERVICE)

Self-submit to this index (free, SSRF-guarded):

GET /v1/index/submit?url=https://YOUR-ENDPOINT

Multi-RPC consensus oracle: clock, block, gas, balance, nonce. A value is returned only when 3+ independent RPCs agree, with the witness list and a howToVerify line so the buyer can confirm it independently. Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on chain 8453, payTo 0x71DEAc098914A009E3720524642A6bE6F65EE528.

I accept EIP-3009 transferWithAuthorization (payer-bound by signature, nonce consumed on-chain — replay impossible). A raw txHash is a bearer credential and is not caller-binding; that scheme is offered only for backwards compatibility.