x402 Publisher Registry
A daily crawl of the x402 publisher manifests we track, read from each domain's /.well-known/x402 manifest, falling back to /.well-known/x402.json for hosts that only serve the extension form. Status, payment networks, endpoint counts, and federation flags in one normalized, dated snapshot.
Scope: this is a seeded registry, not an ecosystem-wide catalog. It covers the AFTA federation plus domains submitted to us, and the count below is the entire universe it tracks. For ecosystem-wide x402 discovery the canonical catalog is Coinbase CDP's Bazaar index at api.cdp.coinbase.com/platform/v2/x402/discovery/resources.
How this differs from a curated awesome-list
Curated readmes are useful but stale within weeks. The x402 spec already defines a discovery manifest at /.well-known/x402. We crawl that. Every publisher self-publishes their own data; we surface it normalized and dated. The canonical source of truth is the publisher's manifest, not a maintainer's taste. What we give up for that is breadth: a readme can name hundreds of projects from hearsay, while this page only shows domains we actually crawl and can date.
- ·Auto-refreshed: daily crawl at 02:15 UTC, status per entry preserved in the snapshot.
- ·Open data: the JSON at
/api/x402-registry/snapshotis the same data this page renders, free, no auth, no rate limit beyond the standard edge cache. - ·Structurally agent-friendly: one call returns every publisher this registry tracks, already normalized, so an agent does not have to fetch and parse each manifest itself.
- ·Not an endorsement: inclusion means the publisher exposes a valid
/.well-known/x402. Agents must still verify wallet addresses on-chain against the publisher's ownpublisher.validation.publishedAtlocations before sending funds.
Get your site listed
The seed list grows organically. To get added:
- Publish a valid x402 V2 manifest at
/.well-known/x402on your domain. See the x402 glossary or the Coinbase x402 V2 spec. - Send the domain to contact@tensorfeed.ai with subject "x402 Registry Submission".
- We add it to the seed list. The next daily crawl picks up the manifest and the entry appears here automatically.
No PR review, no curatorial gatekeeping on signal-or-vibes. The canonical x402 manifest is the submission. We just index it.
AFTA federation membership
The Agent Fair-Trade Agreement is an open spec for how machine-payable APIs should behave toward agents: code-enforced no-charge on schema failures, breaker trips, or stale data; Ed25519-signed receipts on every paid response; on-chain rail for verifiable settlement. Federation members serve /api/afta-certify/check?domain= and score 6/6 on the canonical checks.
Federation membership is a separate signal from x402 compatibility. A site can be x402-compatible without being in the AFTA federation. The federation flag in the snapshot above is a TF assertion made on the registry side, not a manifest-level claim.