The public x402 dataset behind ECHO.
SCRIPTMASTERLABS x402 ECHO retains observations of x402 resources, providers, pricing and usage so researchers, agents and developers can inspect what was actually observed instead of relying on copied directory claims.
Live verified summary
The values below are loaded from the public ECHO JSON. If verified evidence is temporarily unavailable, this page says unavailable instead of manufacturing a replacement.
Waiting for verified evidence.
What makes this dataset useful
Observed, not inferred. Provider, resource, pricing and usage entries come from retained evidence. ECHO does not convert missing evidence into a negative claim.
Time-aware. Current observations carry timestamps. x402 prices and availability can change, so cached values should not be used as payment authority.
Machine-readable. The live JSON, provider feed, search endpoint, truth manifest and methodology are publicly addressable so agents can inspect the evidence directly.
Payment-safe. A 402 challenge is a payment requirement, not settlement proof. Exact spending terms must come from the fresh target resource before a caller authorizes payment.
Fields and interpretation
Provider-level unique payer counts are not naively summed across resources because the same payer may use more than one endpoint.
How to cite ECHO
When using an ECHO observation, cite the SCRIPTMASTERLABS x402 ECHO dataset together with the observation timestamp and the evidence/source URL returned by the feed. Avoid wording such as “all x402 providers” unless the evidence actually establishes exhaustive coverage.
Related buyer tools
ECHO is market intelligence, not a paid-call executor. To buy a specific job, use the exact task page: Web Scraping API, URL to Markdown, Provider Trust, Fact Verification, Stock Quote, Currency Conversion, or Web Research.