Chain coverage
What we actually serve, per chain.
Every chain below is probed on a schedule and rated by what answered, not by
what a provider lists. An endpoint a chain cannot serve returns 501 with the
evidence — never a 200 full of zeros.
The matrix
Filter by capability to see exactly which chains answer a given endpoint.
| Chain | Key | ID | Tier | Capabilities | Try it |
|---|
The ladder
“Supported” is not one boolean. Each rung is assigned only by measured evidence — the predicates below are served verbatim by the API, so this page and the code cannot disagree.
Why a chain can be listed and still refuse
Market-data providers keep answering 200 for chains they have stopped indexing.
Measured on 2026‑08‑31: one provider returned a live-looking price for Story with a newest
trade 101 days old, zkSync 187 days, Conflux 200 days. It is not confined to small chains —
on 2026‑09‑02 the same provider served USDC on Base with a 22‑hour‑old record and zero trades
in every window it reports.
So every response carries a freshness block with the upstream data’s own age, and
a provider whose answer is too old loses to one that has not been asked yet. When that
happens the response says so in degraded.