01 / The catalog
Read-only, API-compatible replicas of the developer tools you already use — same paths, same JSON, same headers — all preloaded with one simulated data set whose story is the same on every host. Coverage below is counted from the conformance manifest on this build, never hand-set.
Providers
21
Across 7 categories, each on its own hostname. Adoption is a base-URL swap.
Read surfaces
3,377
REST endpoints, GraphQL entities and git-transport routes in the manifest — 2,033 served and verified today, the rest answering with an explicit coverage error.
Pinned snapshots
127
Frozen, byte-reproducible universes on their own hosts, so CI never flakes on the data.
02 / Find your provider
21 of 21 providers shown
Not seeing the git host API you need? Request one
Not seeing the issue tracker API you need? Request one
Not seeing the AI telemetry API you need? Request one
Not seeing the messaging API you need? Request one
Not seeing the CI/CD API you need? Request one
Not seeing the observability API you need? Request one
Not seeing the CRM/support API you need? Request one
The badge
The word on each card is the share of that provider's read rows that have reached a terminal answer — served and verified against the vendor's spec, marked a deviation, retired upstream while our pinned snapshots still answer it, or a reviewed empty/refuse carrying a written reason and a review date. It is computed in the coverage manifest, never hand-set, and this page copies it.
Not the same number as the bar. “Served & verified” counts only the rows answering with real universe data that a conformance test checked (2,033 of 3,352 across every provider). The badge counts those and the rows whose final answer is an honest empty, a documented refusal, or an endpoint the provider itself removed — so a badge reads at or above its bar, and only Full means there is nothing left to answer. The 3 cuts below it are provisional and may be retuned.
REST + GraphQL + git rows that are not `excluded`. Write operations are NOT rows (DECISIONS 2026-09-01 decision 9): they are counted in meta.write_operations and never enter this ratio.
03 / What is not here yet
2 categories are named above with nothing in them — infra, registry. They are the lanes the provider-expansion program opens next, and they are listed rather than hidden so this page reports what we do not serve as plainly as what we do.
Need a provider that is not on this page?
Tell us which API and which client you would point at it. What people ask for is what gets built next — the queue is ordered by demand, never by which spec was easiest to vendor.
04 / How to read the numbers
404 with an X-SandboxAPIs-Coverage header, GraphQL returns an entry in errors rather than a silent null. That is what makes partial coverage safe to build against: your integration fails loudly instead of passing on invented data.