Onchain data API with most networks supported
Number of blockchains each major onchain data provider officially supports.
This benchmark counts how many blockchains each major onchain data API officially supports, audited live from each provider's own "supported networks" endpoint every six hours. The number is what a builder integrating an SDK actually cares about. how many chains can I query without rolling my own indexer. Provider marketing pages quote round numbers (250+, 100+, 50+ chains) without a list a reader can verify; this benchmark reads the list from the API itself and publishes the unique-chain count, refreshed against the source of truth. Mainnets only. Testnets are excluded because providers list them inconsistently and a builder shipping to production needs the mainnet count, not a longer list inflated with chains nobody trades on. Coverage breadth is one dimension of a data API's product; head lag and metadata completeness sit on separate benches (№ 001 and № 004) so a provider strong on raw count can be checked against the quality dimensions too.
Methodology
We benchmark how many networks each major onchain data provider lists in its public "supported networks" endpoint. The harness fetches the official listing every six hours from GeckoTerminal, Codex and Mobula, deduplicates by chain id and counts. Mainnet only, testnets are excluded because providers list them inconsistently and the comparison is meant to reflect what a builder can integrate against in production. Coverage breadth is one dimension of a data provider's product, not a ranking on quality. Latency, freshness and metadata completeness are measured separately by benches № 001 and № 004.
Frequently asked
Which crypto data API supports the most blockchains?
GeckoTerminal currently leads at 266 mainnets across 3 measured providers. The count is read every six hours directly from each provider's own supported-networks endpoint and deduplicated by chain id, so the leaderboard reflects what each API actually publishes as queryable, not a claim from a marketing page.
Does Mobula support more chains than CoinGecko's GeckoTerminal?
On this benchmark Mobula returns 78 mainnets and GeckoTerminal returns 266 mainnets. The two have different coverage philosophies. Mobula indexes EVM, Solana, Bitcoin and a long tail of non-EVM chains under a single API. GeckoTerminal grows alongside CoinGecko's DEX rollout, which is deep on the major chains and slower on niche L2s.
Why doesn't this benchmark include testnets?
Testnet listings are inconsistent across providers. Some list every devnet the engineering team ever spun up, others list none. Mainnets are what a builder shipping to production actually integrates against, so the comparison is restricted to mainnets only. The harness reads the full network list from each API and filters server-side.
Is having more chains supported always better?
Breadth and depth are independent dimensions. A provider with 200 chains might only index price ticks on most of them and full DEX swap history on a dozen. A provider with 60 chains might cover every chain end-to-end (pools, swaps, holders, metadata). Use this benchmark for the breadth question; head lag (bench № 001) and metadata coverage (bench № 004) answer the depth question. A serious integration decision reads all three.
How often is the network count refreshed?
Every six hours. The harness hits each provider's supported-networks endpoint, parses the response, deduplicates by chain id 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 queryable production environment, identified by a unique chain id. Ethereum mainnet, Solana mainnet, Base, Arbitrum, BNB Chain, Bitcoin and so on each count once regardless of how the provider labels them internally. Bridged variants of a token on different chains are not the same chain. The chain id is the deduplication key.
Source code github.com/OpenChainBench/OpenChainBench/tree/main/harnesses/network-coverage
