Methodology
How x402all decides what enters the catalog
x402all is a public catalog of x402-protected HTTP resources. The goal is to make agent-buyable APIs easier to inspect without inventing quality signals that have not been measured yet.
Discovery
Facilitator discovery responses, public endpoint declarations, operator submissions, and direct probes provide the raw catalog surface.
Enrichment
Titles, summaries, use cases, and categories are written from public-safe source material and internal probe output.
Publication
Every indexable detail page ships with a JSON twin so agent buyers can inspect the same record shown in the page.
Public safety
No fabricated confidence
The catalog prefers a missing field to a confident-looking placeholder. When an endpoint has not been revalidated or a metric has not been observed, the public page says less.
- Seed-only copy is not rendered as public page text.
- Unmeasured uptime, latency, and success rates are omitted instead of estimated.
- Pricing is shown from declared x402 payment requirements and marked for review when it looks unusual.
- Listings can be refreshed or removed when discovery, validation, or operator evidence changes.
Freshness model
Discovery, evidence, validation
Tier A
Facilitator discovery
Pull current resource declarations, payment requirements, and facilitator routing data.
Tier B
Settlement evidence
Add measured usage and payment signals when they are available from trustworthy sources.
Tier D
Endpoint revalidation
Probe listed origins for live 402 behavior, response shape, and material drift.