Crypto data API with most blockchains in asset registry, live coverage ranking
Number of blockchains where each major crypto data API knows tokens (contract-address lookups), audited every six hours against each provider's public asset-registry endpoint.
TL;DR. As of , CoinGecko leads asset-registry chains at 461 (24h) on Crypto data API with most blockchains in asset registry, live coverage ranking. Source: OpenChainBench, https://openchainbench.com/benchmarks/asset-registry-coverage.
This benchmark counts how many blockchains each major crypto data API officially knows tokens on, audited live every six hours from each provider's public asset-registry endpoint. The number is what a builder integrating a market-data API cares about at token-lookup time: given a chain and a contract address, can this API give me price, market cap, metadata and history for a token on that chain. Coverage is measured against each provider's own listing endpoint (CoinGecko `/asset_platforms`, CoinPaprika `/v1/contracts`, CoinStats `/wallet/blockchains`, Mobula `/blockchains`). Mainnets only. Asset-registry coverage is the aggregator dimension of the product, DEX-pool coverage is a different question measured on the companion bench dex-network-coverage.
Methodology
We benchmark how many blockchains each major crypto data provider supports in its public asset registry (the endpoint used for token lookups by contract address). The harness fetches the official listing every six hours from four providers (CoinGecko, CoinPaprika, CoinStats, Mobula), deduplicates by platform slug or chain id and counts. Mainnet only. DEX-pool indexing coverage is measured separately on bench dex-network-coverage because the two questions are not comparable, an API can know tokens on 300 chains through a market-data pipeline while indexing DEX pools on only a dozen. This bench answers the asset-registry question, the sister bench answers the DEX-indexing question.
Frequently asked
Which crypto data API knows tokens on the most blockchains?
CoinGecko currently leads at 461 chains across 3 measured providers. The count is read every six hours directly from each provider's own asset-registry endpoint (CoinGecko `/asset_platforms`, CoinPaprika `/v1/contracts`, CoinStats `/wallet/blockchains`, Mobula `/blockchains`) and deduplicated per platform, so the leaderboard reflects what each API actually publishes as queryable for token-lookup workflows.
Why is this bench separate from dex-network-coverage?
Asset-registry coverage (how many chains a provider knows tokens on for contract-address lookup) and DEX-pool coverage (how many chains a provider indexes DEX pools and swap volumes on) are two different products, not a single metric. CoinPaprika lists 300+ chains in `/v1/contracts` because it indexes token metadata everywhere, but CoinPaprika does not run its own DEX pool indexer, that product lives at DexPaprika with its own separate `/networks` endpoint. Comparing them on a single leaderboard makes the number meaningless. This bench answers the asset-registry question, the sister bench answers the DEX-indexing question.
Does Mobula support more chains than CoinGecko for token lookups?
On this benchmark Mobula returns 81 chains and CoinGecko returns 461 chains. The two have different coverage philosophies. CoinGecko has been building its asset-platforms registry for a decade and covers every chain where a token has ever been listed. Mobula is a younger aggregator focused on breadth-with-quality across EVM, Solana, Bitcoin and non-EVM chains under a single API. Read the live numbers directly from the leaderboard.
Why doesn't this benchmark include GeckoTerminal, Codex or DefiLlama?
Those providers are measured on the sister bench dex-network-coverage because their product is DEX-pool indexing (not token-registry coverage). GeckoTerminal's `/networks` endpoint lists chains where GeckoTerminal actively indexes DEX pools; that is not the same question as `which chains does an API know tokens on`. Putting GeckoTerminal in an asset-registry leaderboard would compare a DEX-indexer's chain list against a token-registry chain list, which is apples-vs-oranges and inflates or deflates depending on the provider's product surface.
How often is the chain count refreshed?
Every six hours. The harness hits each provider's asset-registry endpoint, parses the response, deduplicates by chain id or platform slug, and updates the Prometheus gauge `networks_supported_total{provider}`. Failures (network errors, rate limits, auth errors) leave the previous count in place and increment a `fetch_errors_total` counter, so a temporary outage does not silently drop a provider off the leaderboard.
What counts as a mainnet in this benchmark?
Any chain a provider lists as a production platform for token lookups, identified by a unique chain id or platform slug. Ethereum, Solana, Base, Arbitrum, BNB, Bitcoin and so on each count once regardless of how the provider labels them internally. Bridged variants of the same token on different chains are not the same chain, the chain id is the deduplication key. Testnet listings are filtered server-side where the provider exposes a testnet flag.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/network-coverage