diff --git a/src/content/reports/data-api/2026-08-state-of-crypto-data-apis.mdx b/src/content/reports/data-api/2026-08-state-of-crypto-data-apis.mdx index b6d3c4f3..6caa7829 100644 --- a/src/content/reports/data-api/2026-08-state-of-crypto-data-apis.mdx +++ b/src/content/reports/data-api/2026-08-state-of-crypto-data-apis.mdx @@ -4,85 +4,85 @@ category: "data-api" slug: "2026-08-state-of-crypto-data-apis" publishedAt: "2026-08-04" period: "August 2026" -summary: "Seven live benchmarks across six categories reveal a fragmented market: no single provider leads price feeds, token metadata, DEX coverage, NFT data, asset registry, and wallet labeling simultaneously. This report maps where each provider wins, where it falls short, and why." -heroFinding: "GeckoTerminal indexes 253 blockchains for DEX data but publishes prices 12 seconds after they move. The fastest price aggregators close that gap to under one second — but cover a fraction of those chains. No provider in this cohort leads more than two of the six categories measured." +summary: "Seven live benchmarks across seven categories show a market where no two category leaders are the same provider. This report maps where each provider wins, where it falls short, and what the data actually says about causation." +heroFinding: "GeckoTerminal indexes 253 blockchains for DEX data but publishes prices 12 seconds after they move. The fastest price aggregators publish in under one second on some chains — but the driver is integration depth, not the chain's block time. Seven benchmarks, seven different category leaders, zero overlap." author: "OpenChainBench Research" readingTime: 14 canonical: "https://openchainbench.com/reports/data-api/2026-08-state-of-crypto-data-apis" --- -- Seven independent benchmarks across price feeds, token metadata, asset registry, DEX coverage, NFT data, and wallet labeling covering 15+ providers. -- No provider leads all six categories. The market is structurally fragmented by use case. -- Price aggregators: p50 head lag ranges from 707 ms to over 12 seconds depending on architecture. The gap widens to 7.9x on Solana. -- Token metadata coverage is a statistical tie at the top: two providers within 0.6 percentage points of each other. -- Asset registry breadth spans 81 to 461 chains — a 5.7x range reflecting a decade-scale difference in onboarding investment. -- Wallet labeling is dominated by chain-native specialists: coverage drops sharply for any provider working across multiple chains simultaneously. -- NFT metadata shows the widest intra-cohort gap of any category: 23 percentage points between leader and the largest general-purpose provider. +- Seven independent benchmarks, seven distinct category leaders. No provider leads more than one of the seven categories measured. +- Price aggregator head lag spans 98 ms (Mobula on Solana) to over 12 seconds (GeckoTerminal). The per-chain spread matters more than any single headline number. +- Head lag on a chain reflects integration depth, not block speed: Robinhood Chain (100 ms blocks) produces 881 ms lag; Solana (400 ms blocks) produces 98 ms. Block time and head lag are anti-correlated across the four chains measured. +- Token metadata coverage: the top two providers are within 0.6 pp of each other and both under 65%. More than one in three newly-launched tokens are missing at least one metadata field across all providers. +- Asset registry breadth: CoinGecko (461 chains) leads CoinPaprika (307 chains) by 1.5x and Mobula (81 chains) by 5.7x. +- NFT metadata: the gap between leader Moralis (97.1%) and Alchemy (74.3%) is the largest between a cohort leader and a major general-purpose incumbent in any category in this report. +- Wallet labeling: chain-native specialists (Helius 84.1%, XRPScan 80.0%, StellarExpert 79.9%) outpace every multi-chain provider by more than 30 percentage points. - + ## Methodology -Every number in this report is derived from OpenChainBench's live Prometheus instance and bench blob CDN. The seven benchmarks in scope run independent harnesses at the cadences described below. No numbers come from provider marketing pages or self-reported latency figures. +Every number in this report is derived from OpenChainBench's live Prometheus instance and bench blob CDN. The seven benchmarks in scope run independent harnesses at the cadences listed below. No numbers come from provider marketing pages or self-reported latency figures. All figures in this report reflect the 24-hour rolling window ending August 5, 2026 unless noted. Benchmarks in scope: [aggregator-head-lag](/benchmarks/aggregator-head-lag), [metadata-coverage](/benchmarks/metadata-coverage), [asset-registry-coverage](/benchmarks/asset-registry-coverage), [token-quote-coverage](/benchmarks/token-quote-coverage), [wallet-labels-coverage](/benchmarks/wallet-labels-coverage), [dex-network-coverage](/benchmarks/dex-network-coverage), [nft-collection-metadata](/benchmarks/nft-collection-metadata). -The aggregator head-lag harness samples every 15 seconds from three geographic regions (US East, EU West, Singapore). All price-feed latency figures are p50 over a 24-hour rolling window. Coverage benches (metadata, asset registry, DEX, NFT) check a fixed test set on cadences ranging from every 30 minutes to every 6 hours. All harnesses are open source at [github.com/ChainBench/OpenChainBench](https://github.com/ChainBench/OpenChainBench/tree/main/harnesses). +The aggregator head-lag harness samples every 15 seconds from three geographic regions (US East, EU West, Singapore) across four chains (Solana, Base, Robinhood Chain, BNB). The cross-chain headline figure is the cross-region average of per-chain p50s; the per-chain table in the next section is the more actionable signal for builders choosing a provider for a specific chain. Coverage benches run every 30 minutes to every 6 hours depending on bench. All harnesses are open source at [github.com/ChainBench/OpenChainBench](https://github.com/ChainBench/OpenChainBench/tree/main/harnesses). -## The Six-Category Divide +## The Seven-Category Divide -The crypto data API market is frequently described as a competitive space with a handful of dominant players. The benchmark data tells a different story: no single provider leads more than two of the six categories measured in this report. +The crypto data API market is frequently described as competitive, with a handful of dominant players. The benchmark data tells a different story: seven benchmarks produce seven distinct category leaders — no provider leads more than one. Category leaders as of August 2026: | Category | Benchmark | Leader | Value | |---|---|---|---| -| Price Feeds | aggregator-head-lag | Mobula | 707 ms | +| Price Feeds | aggregator-head-lag | Mobula | 677 ms | | Token Metadata | metadata-coverage | Codex | 64.3% | | Asset Registry | asset-registry-coverage | CoinGecko | 461 chains | -| Token Quotes | token-quote-coverage | Jupiter | 96.6% | +| Token Quotes | token-quote-coverage | Jupiter | 97.1% | | DEX Coverage | dex-network-coverage | GeckoTerminal | 253 chains | | NFT Data | nft-collection-metadata | Moralis | 97.1% | | Wallet Labels | wallet-labels-coverage | Helius | 84.1% | -Seven distinct providers occupy the seven category-leader slots above. This fragmentation is structural, not accidental. Price feed freshness, asset registry breadth, DEX indexing, and wallet labeling require different infrastructure investments, different data pipelines, and different trade-offs between depth and breadth. The market has not yet produced a provider who executes well across all of them simultaneously. +This fragmentation is structural, not accidental. Price feed freshness, asset registry breadth, DEX indexing, and wallet labeling require different infrastructure investments, different data pipelines, and different trade-offs between depth and breadth. The market has not yet produced a provider who leads more than one of the seven simultaneously. ## Price Feed Head Lag - + -The headline figure — 707 ms for Mobula — is a cross-chain, cross-region median. The distribution underneath it matters more than the single number. +The cross-chain headline is an average of per-chain p50s across all three probe regions: Mobula 677 ms, Codex 1,059 ms, GeckoTerminal 12,340 ms. The ratio between chains matters far more than the single aggregate. The next section breaks down each chain individually. -Codex trails by 1.65x globally. That gap widens to 7.9x on Solana and narrows to near-zero on Base, where the two providers differ by only 20 ms. The chain you're pricing determines whether the ranking matters. +GeckoTerminal is in a separate category entirely. Its p50 of 12,340 ms is not a latency ranking failure — it reflects a batch-sync pipeline architecture that enables 253-chain DEX coverage (the widest in the industry, as shown below). GeckoTerminal does not compete as a real-time price feed and its benchmark position reflects that trade-off, not a product deficiency. -GeckoTerminal is in a separate category entirely. Its p50 of 12,489 ms — over twelve seconds — is not a latency ranking failure. It reflects a fundamentally different data pipeline architecture. GeckoTerminal does not attempt to be a real-time price feed in the sense that Mobula or Codex do. Its DEX indexing product (the best in coverage, as shown below) operates on a model where pool state is synced in batches, not streamed event by event. The head lag figure is a consequence of that architecture choice, not a quality deficit in isolation. +The practical line to draw: if a 12-second delay between an on-chain price event and your UI is visible to users, GeckoTerminal's price endpoint is not viable for that use case. For DEX pool metadata, pool history, or multi-chain analytics where lag is irrelevant, GeckoTerminal is the strongest option. -The practical implication: if your application displays prices and a 12-second delay between on-chain events and your UI is visible to users, GeckoTerminal's price endpoint is not viable for that use case. If you need DEX pool metadata, pool history, or the deepest chain coverage for off-chain analytics, GeckoTerminal is the strongest option in the field. +## Head Lag Reflects Integration Depth, Not Block Speed -### Regional variance +The per-chain breakdown produces the sharpest finding in this report. -Mobula's regional spread is remarkably tight: 717 ms from US East versus 709 ms from EU West — an 8 ms difference. This consistency suggests Mobula distributes its indexing pipeline geographically rather than running from a single origin. Codex shows a similar pattern (1,169 ms US vs 1,178 ms EU). Neither provider penalizes European users meaningfully relative to US users. Singapore data was unavailable in this report cycle. +**Head lag by chain (p50, 24 h)** -## Solana: Block Architecture and Its Consequences +| Chain | Block time | Mobula | Codex | GeckoTerminal | +|---|---:|---:|---:|---:| +| Solana | ~400 ms | **98 ms** | 808 ms | 13,566 ms | +| Base | ~200 ms¹ | 773 ms | 831 ms | 12,516 ms | +| Robinhood Chain | ~100 ms² | 881 ms | 1,106 ms | 11,085 ms | +| BNB Chain | ~450 ms³ | 961 ms | 1,490 ms | 12,110 ms | -The most striking figure in the price feed bench is Mobula's head lag on Solana: **99 ms**. A tenth of a second from on-chain event to API emission. +¹ Base activated Flashblocks in 2025, enabling 200 ms sub-blocks over WebSocket alongside standard 2 s blocks. ² Robinhood Chain mainnet launched July 1, 2026, 34 days before this report. ³ BNB's Fermi hard fork (January 2026) reduced block time from 750 ms to ~450 ms. -Codex reaches the same chain in 779 ms. The 7.9x gap is not a Codex failure — it is a reflection of what Solana's architecture makes possible. Solana's block time is approximately 400 ms, versus Base and BNB where blocks land every 2 and 3 seconds respectively. An aggregator that subscribes to Solana's native websocket feed and processes confirmations in real time can publish prices faster than any EVM chain allows, because the chain itself confirms faster. +The block time column makes the causal claim uncomfortable: block speed and head lag are anti-correlated across the four chains measured. Robinhood Chain has the fastest blocks (100 ms) and the second-slowest head lag (881 ms). Base has 200 ms Flashblocks and sits at 773 ms. Solana has 400 ms slots — slower than both — yet records 98 ms head lag. BNB at 450 ms produces 961 ms lag. -**Head lag by chain (p50, 24 h)** +The ranking (Solana fastest, BNB slowest) is the inverse of what a block-time explanation predicts. The data points instead to integration depth: how each provider subscribes to on-chain events on that specific chain. -| Chain | Mobula | Codex | GeckoTerminal | -|---|---:|---:|---:| -| Solana | 99 ms | 779 ms | 13,433 ms | -| Base | 826 ms | 846 ms | 12,217 ms | -| Robinhood Chain | 891 ms | 1,092 ms | 10,640 ms | -| BNB Chain | 1,032 ms | 1,970 ms | 13,703 ms | +Mobula's 98 ms on Solana is consistent with a native program subscription to Solana's transaction or vote stream — receiving data pre-block-finalization through Solana's streaming RPC. Its EVM chain lags (773–961 ms) are consistent with block-polling: waiting for a full block header, then resolving prices. The 8.2x gap between Solana and Mobula's next-fastest chain (Base) is not a Solana property — it is the signal of different integration investments per chain. -BNB Chain is the slowest chain for every provider in the cohort. BNB's block time is nominally 3 seconds but can vary; its validator set and consensus mechanism create additional confirmation latency that EVM aggregators must wait for before emitting a confirmed price. Mobula's BNB lag (1,032 ms) is 10x its Solana lag despite running on the same indexing infrastructure. +Codex shows the same structural pattern at different absolute values. Base 831 ms is close to Mobula; Solana 808 ms is 8.2x Mobula's Solana figure. Codex's Solana integration extracts less of the chain's latency advantage. -The implication for builders: a "sub-second price feed" claim means different things on different chains. Verify the per-chain figures before assuming a provider's headline latency applies to your chain. +Robinhood Chain carries an additional caveat: it launched July 1, 2026, 34 days before this measurement. Both Mobula (881 ms) and Codex (1,106 ms) lag behind Base despite RH Chain's 4x faster blocks, which suggests early-stage EVM-polling integrations not yet optimized for RH Chain's sub-second slot cadence. Treat the RH Chain figures as initial baselines, not settled rankings. ## Token Metadata Coverage @@ -90,31 +90,29 @@ The implication for builders: a "sub-second price feed" claim means different th The metadata bench is one of the few categories where the ranking is genuinely ambiguous. Codex leads at 64.3%, Mobula follows at 63.7%. The gap is 0.6 percentage points — within normal measurement noise for this bench. Both providers are effectively tied on metadata coverage for newly-launched tokens. -Jupiter's 24.9% requires context. Jupiter is Solana-only; it returns zero coverage on EVM chains (Base, BNB) by construction. The bench scores it on the full multi-chain sample set, so Jupiter's 24.9% headline undercounts its actual performance on Solana-only tokens. The cross-chain headline is the correct figure for any builder working with EVM tokens or multi-chain applications; for Solana-native metadata, consult the per-chain breakdown on the bench page. +Jupiter's 24.9% requires context. Jupiter is Solana-only; it returns zero coverage on EVM chains (Base, BNB) by construction. The bench scores it on the full multi-chain sample set, so Jupiter's 24.9% headline undercounts its actual performance on Solana tokens. The cross-chain figure is correct for any builder working with EVM or multi-chain tokens; for Solana-native metadata, consult the per-chain breakdown on the bench page. -The more important observation in this category: both leading providers are under 65%. Fully one-third of newly-launched tokens have incomplete metadata across all providers in the cohort. Logo, description, Twitter, or website fields are missing for most new tokens regardless of which aggregator you use. Applications that need metadata for brand-new tokens should design for missing fields as the default case, not the exception. +The more important observation: both leading providers are under 65%. More than one in three newly-launched tokens are missing at least one of the four metadata fields across all providers in the cohort. Applications that need metadata for brand-new tokens should design for missing fields as the default case, not the exception. ## Asset Registry Breadth -CoinGecko's 461-chain registry is more than twice as wide as CoinPaprika's 307 chains and nearly six times Mobula's 81. This is the clearest expression of the breadth-versus-depth trade-off in the data API market. - -CoinGecko's registry breadth reflects a decade of manual chain onboarding and a community-submission model. Reaching 461 chains means accepting chains with thin liquidity, inactive validators, and minimal trading activity. The registry count measures scope, not data quality. A chain with one active token and a single liquidity pool is still counted. +CoinGecko's 461-chain registry leads CoinPaprika's 307 chains by 1.5x and Mobula's 81 chains by 5.7x. This is the clearest expression of the breadth-versus-depth trade-off in the data API market. CoinGecko's breadth reflects a decade of manual chain onboarding and community submissions — reaching 461 chains means accepting chains with thin liquidity, inactive validators, and minimal trading activity. The registry count measures scope, not data quality. -CoinGecko's registry breadth does not correlate with real-time price freshness — CoinGecko has no entry in the aggregator-head-lag bench. The asset registry and the price feed are different products serving different use cases: token discovery and contract-address lookup versus live market data. A builder who needs both must combine providers. +Registry breadth and real-time price freshness are different products serving different use cases. CoinGecko has no entry in the aggregator-head-lag bench. A builder who needs both must combine providers. -The practical decision: if you need to answer "does this contract exist on chain X", CoinGecko's registry is the deepest lookup available. If you need a real-time price for a token on that chain, you need a provider with both registry coverage and a live price pipeline. +If you need to answer "does this contract exist on chain X", CoinGecko's registry is the deepest lookup available. If you need a live price for a token on that chain, you need a provider with both registry coverage and a streaming price pipeline. ## Quote Coverage for New Tokens -The token quote bench measures something different from all other coverage benches: it tests providers on tokens created within the last hour, sourced from live launchpad feeds. This is the hardest case — the token may have no liquidity on major venues, no metadata, and may exist only on a single chain. +The token quote bench tests providers on tokens created within the last hour, sourced from live launchpad feeds — the hardest case for routing coverage. A token may have no liquidity on major venues, no metadata, and may exist only on a single chain. -Jupiter's 96.6% is the strongest absolute figure in the entire data API cohort across all seven benchmarks. On Solana, where the majority of its probe tokens live, Jupiter routes nearly every token successfully. Jupiter quotes 96 of 100 freshly launched tokens, a direct consequence of its native integration with Solana's pool infrastructure — it sees new pools seconds after creation. +Jupiter (97.1%) and Moralis NFT (97.1%) share the highest coverage figure in the entire cohort across all seven benchmarks. Jupiter's score reflects its native integration with Solana's pool infrastructure — it discovers new pools seconds after creation. KyberSwap at 87.8% covers EVM chains competently. Mobula at 71.3% means roughly one in three newly-launched tokens across chains cannot be quoted. -KyberSwap at 92.9% covers EVM chains competently. Mobula at 76.4% trails both, meaning roughly one in four new tokens across chains cannot be quoted. For applications that handle established tokens only (top-1,000 by market cap), all three providers will perform near 100%. The quote-coverage bench is specifically relevant for launchpad analytics, meme-token apps, or any product that needs to quote tokens within minutes of their creation. +For applications handling established tokens (top-1,000 by market cap), all three providers will perform near 100%. The quote-coverage bench is specifically relevant for launchpad analytics, meme-token apps, or any product that needs to quote tokens within minutes of creation. ## DEX Coverage: Breadth vs. Freshness @@ -122,96 +120,97 @@ KyberSwap at 92.9% covers EVM chains competently. Mobula at 76.4% trails both, m GeckoTerminal's 253 chains is a market-leading figure by a wide margin. Codex's 122 chains is the next closest at roughly half. Sim by Dune at 64 covers EVM mainnets only. DexPaprika at 36 is the narrowest in the cohort. -The juxtaposition with the head-lag bench is the clearest illustration of the breadth-freshness trade-off in the entire dataset. GeckoTerminal leads DEX coverage by 2x and trails on price freshness by 17x. These are not separate failures — they are the same architecture decision viewed from two angles. Indexing 253 chains with a streaming price pipeline is not technically feasible on a data API provider's infrastructure budget in 2026. The choice to cover more chains is the choice to accept a longer synchronization cycle. +The juxtaposition with the head-lag bench illustrates the breadth-freshness trade-off. GeckoTerminal leads DEX coverage by 2x and trails on price freshness by 18x. These are the same architecture decision seen from two angles. A batch-sync pipeline can cover 253 chains; a streaming pipeline cannot — not at current infrastructure costs. -For DEX analytics, backtesting, chain comparisons, or any use case that does not require sub-second prices, GeckoTerminal's breadth is the correct trade-off. For applications that need current prices on a specific chain, providers in the head-lag bench offer far fresher data on their supported chains, with DEX chain count as the cost. +For DEX analytics, backtesting, or chain comparisons, GeckoTerminal's breadth is the correct trade-off. For applications requiring current prices on a specific chain, providers in the head-lag bench offer far fresher data, with DEX chain count as the cost. ## NFT Metadata: The Alchemy Gap -The NFT metadata bench has the narrowest competitive field in this report: three providers, all benchmarked against a fixed set of 50 Ethereum blue-chip collections. All three return 100% API availability — the ranking is driven entirely by coverage completeness. +The NFT metadata bench has the narrowest competitive field in this report: three providers benchmarked against a fixed set of 50 Ethereum blue-chip collections. All three return 100% API availability — the ranking is driven entirely by field coverage. -Moralis leads at 97.1%, OpenSea at 93.2%, and Alchemy at 73.7%. The 23-percentage-point gap between Moralis and Alchemy is the largest spread between a cohort leader and a major incumbent in any category in this report. +Moralis leads at 97.1%, OpenSea at 93.8%, and Alchemy at 74.3%. The 22.8-percentage-point gap between Moralis and Alchemy is the largest between a cohort leader and a major general-purpose incumbent in any single category in this report. -Alchemy's gap is specific to the `floor_eth` field. Alchemy's `getContractMetadata` endpoint focuses on on-chain collection metadata — name, image, external URL — rather than marketplace-sourced order book data. Delivering a live floor price requires actively polling or subscribing to marketplace orders, which is not the primary function of Alchemy's contract metadata endpoint. OpenSea, which operates its own marketplace, surfaces floor prices naturally — though the bench notes this costs two API calls per collection versus one for Moralis. +Alchemy's gap is specific to the `floor_eth` field. Alchemy's `getContractMetadata` endpoint focuses on on-chain collection metadata — name, image, external URL — not marketplace-sourced order book data. Delivering a live floor price requires actively polling marketplace orders, which is not its primary function. OpenSea surfaces floor prices naturally as a marketplace operator, though at the cost of two API calls per collection versus one for Moralis. -For builders who need collection-level metadata plus floor prices from a single endpoint, Moralis is the clear choice. For on-chain metadata only (name, image, external URL), Alchemy is competitive despite the lower headline figure — the gap collapses when `floor_eth` is excluded from the score. +For builders needing collection metadata plus floor prices from a single call, Moralis is the clear choice. For on-chain metadata only (name, image, external URL), Alchemy is competitive — the gap collapses when `floor_eth` is excluded from the score. ## Wallet Labels: No One Owns the Graph -The wallet labeling bench has the most providers of any category in this report: nine across eleven chains. The leaderboard structure is clear: chain-native specialists occupy the top three positions. +The wallet labeling bench has the most providers of any category in this report: nine across eleven chains. Chain-native specialists occupy the top three positions by more than 28 percentage points over the next tier. | Provider | Coverage | Primary Chain | |---|---:|---| | Helius | 84.1% | Solana | -| StellarExpert | 80.0% | Stellar | -| XRPScan | 79.8% | XRP | -| Blockscout | 55.9% | EVM (explorer) | -| OLI | 50.4% | EVM (standard) | -| Mobula | 43.5% | Multi-chain | -| TonAPI | 35.4% | TON | -| WalletExplorer | 19.9% | Bitcoin / EVM | +| XRPScan | 80.0% | XRP | +| StellarExpert | 79.9% | Stellar | +| Blockscout | 55.6% | EVM (explorer) | +| OLI | 50.2% | EVM (standard) | +| Moralis | 44.4% | Multi-chain | +| Mobula | 43.7% | Multi-chain | +| TonAPI | 35.6% | TON | +| WalletExplorer | 19.8% | Bitcoin / EVM | -Helius (Solana), StellarExpert (Stellar), and XRPScan (XRP) each maintain manually curated entity graphs for their specific chain. Their coverage is built on years of chain-specific research, community tagging, and validator partnerships — not algorithmic entity resolution. The result is a 40-percentage-point lead over general-purpose multi-chain providers. +Helius (Solana), XRPScan (XRP), and StellarExpert (Stellar) each maintain manually curated entity graphs for their specific chain, built on years of chain-specific research, community tagging, and validator partnerships. Their lead over general-purpose providers is editorial, not algorithmic. -This is not a quality failure by multi-chain providers. It reflects the fundamental difficulty of maintaining a curated entity graph across many chains simultaneously. Wallet labeling is editorial work at scale — someone must decide that address 0x... is "Binance Hot Wallet 14" — and chain-native teams have the ecosystem context and community relationships to do that work accurately and quickly. +This is not a quality failure by multi-chain providers. Wallet labeling is editorial work at scale — someone must decide that address 0x... is "Binance Hot Wallet 14" — and chain-native teams have the ecosystem context to do that work accurately. No tooling shortcut replaces it. -OLI (Open Labels Initiative), which attempts a decentralized labeling standard on EVM chains, sits at 50.4% — marginally ahead of Blockscout but not dramatically better than general-purpose providers. The curation problem is harder than the coordination problem: even with a shared protocol, high-coverage entity resolution requires significant editorial investment. +OLI (Open Labels Initiative) sits at 50.2%, below Blockscout (55.6%). A shared decentralized labeling protocol does not automatically produce higher-coverage entity graphs; the curation problem is harder than the coordination problem. -TonAPI at 35.4% reflects TON's still-developing ecosystem tooling. WalletExplorer at 19.9% has near-perfect API availability (99.8%) but the narrowest entity graph in the cohort — it has labels, just very few of them. +TonAPI at 35.6% reflects TON's still-developing ecosystem tooling. WalletExplorer at 19.8% has strong API availability (99.6%) but the narrowest entity graph in the cohort. ## Cross-Provider Scorecard Across seven benchmarks, the competitive landscape resolves into four archetypes. -**Speed specialists** optimize for real-time data at the cost of breadth. Mobula (707 ms head lag on cross-chain p50) and Codex lead their primary category and support a narrower set of chains than the broadest players. +**Speed specialists** optimize for real-time data at the cost of breadth. Mobula (677 ms cross-chain average, 98 ms on Solana) leads the price feed category. Codex is competitive on Base (831 ms, within 60 ms of Mobula) while trailing significantly on Solana. -**Coverage maximalists** maximize breadth at the cost of freshness. GeckoTerminal (253 DEX chains, 12.5 s head lag) and CoinGecko (461 asset registry chains, no real-time price bench) define this archetype. Their value is "find any chain, any token" rather than "get the latest price fast." +**Coverage maximalists** maximize breadth at the cost of freshness. GeckoTerminal (253 DEX chains, 12,340 ms head lag) and CoinGecko (461 asset registry chains, no real-time price bench) define this archetype. Their value is depth of catalog, not speed of emission. -**Vertical specialists** dominate a single chain or use case. Jupiter (96.6% Solana quote coverage), Helius (84.1% Solana wallet labels), and Moralis (97.1% NFT metadata) each lead in a category where their infrastructure confers a structural advantage. None of them lead in a second category. +**Vertical specialists** dominate a single chain or use case. Jupiter (97.1% Solana quote coverage), Helius (84.1% Solana wallet labels), and Moralis (97.1% NFT metadata) each lead in a category where their infrastructure or editorial investment confers a structural advantage. -**Generalists** achieve mid-table finishes across multiple categories. Codex appears in multiple benches with competitive but rarely dominant scores — it leads token metadata by 0.6 pp and indexes 122 DEX chains. No generalist is the obvious answer for an application that needs everything, because no single-provider answer exists yet. +**Generalists** appear in multiple benches without leading any outright. Codex leads token metadata by 0.6 pp over Mobula and indexes 122 DEX chains. Neither Codex nor any other provider is the obvious answer for an application that needs to lead across categories — because no such provider exists yet. ## Decision Framework -Price freshness is the primary constraint. Check the per-chain breakdown on the [aggregator-head-lag](/benchmarks/aggregator-head-lag) bench before committing to a provider — Base is a near coin-flip between the two leaders, Solana is not. Both top providers run near-100% success rates across their supported chains. +Price freshness is the primary constraint. Check the per-chain breakdown on the [aggregator-head-lag](/benchmarks/aggregator-head-lag) bench before committing — Base is a near coin-flip between Mobula (773 ms) and Codex (831 ms), Solana is not (98 ms vs 808 ms). Both providers run above 98% success rates. Verify the per-chain figure for your specific chain before assuming the headline aggregate applies. -Quote coverage on fresh tokens is the constraint. Jupiter is the only choice for Solana launchpad tokens (96.6%). For EVM chains (Base, BNB), KyberSwap (92.9%) leads. Build a fallback path for missing quotes — no provider in the cohort covers every freshly launched token across all chains. +Quote coverage on fresh tokens is the constraint. Jupiter is the only viable choice for Solana launchpad tokens (97.1%). For EVM chains, KyberSwap (87.8%) leads; Mobula (71.3%) covers more chains at the cost of a ~29% miss rate on brand-new tokens. Build a fallback path — no single provider routes every freshly launched token across all chains. -CoinGecko's 461-chain registry is the deepest single source for contract address lookup. For DEX pool metadata on niche chains, GeckoTerminal covers 253. Both are static or near-static lookups — safe to cache aggressively. Neither is a real-time price source. +CoinGecko's 461-chain registry is the deepest single source for contract address lookup. For DEX pool metadata on niche chains, GeckoTerminal covers 253. Both are near-static lookups — safe to cache aggressively. Neither is a real-time price source. -Moralis leads (97.1%) and delivers floor prices in a single API call. OpenSea is competitive (93.2%) but costs two calls per collection. Alchemy's 73.7% headline is largely driven by the floor-price gap — if you don't display floor prices, Alchemy is closer to parity on the remaining four fields. +Moralis leads (97.1%) and delivers floor prices in a single API call. OpenSea is competitive (93.8%) but costs two calls per collection. Alchemy's 74.3% headline is driven almost entirely by the floor-price gap — if floor price is not needed, Alchemy is close to parity on the remaining four fields. -Wallet labeling requires chain-native providers for maximum coverage. For Solana: Helius (84.1%). For XRP: XRPScan (79.8%). For Stellar: StellarExpert (80%). For EVM: Blockscout (55.9%) or OLI (50.4%). No single provider reaches above 85% across all eleven chains simultaneously — plan for missing labels on non-specialist chains as the baseline, not the edge case. +Chain-native providers are the only viable path to high coverage. For Solana: Helius (84.1%). For XRP: XRPScan (80.0%). For Stellar: StellarExpert (79.9%). For EVM: Blockscout (55.6%) or OLI (50.2%). No single provider reaches above 85% across all eleven chains — plan for missing labels on non-specialist chains as the baseline. -GeckoTerminal's 253-chain index is the only viable answer for breadth. Accept the 12-second price lag as a feature of the product architecture, not a bug. For analytics workloads running on historical or near-real-time data, the lag is irrelevant. For anything requiring current prices, use a provider from the head-lag bench on the subset of chains they support. +GeckoTerminal's 253-chain index is the only viable answer for breadth-first DEX analytics. The 12-second price lag is a consequence of the architecture that enables that breadth, not a deficiency. For workloads requiring current prices, use a provider from the head-lag bench on the supported subset of chains. ## Conclusion -The clearest finding across all seven benchmarks is that the crypto data API market has not converged. The providers who win on price freshness lose on chain breadth; the providers who win on chain breadth lose on price freshness. Chain-native specialists dominate their corner of the graph but fall to mid-table the moment you need coverage outside their primary ecosystem. +The clearest finding across all seven benchmarks is structural fragmentation without a clear convergence path. The providers who win on price freshness lose on chain breadth; those who win on chain breadth lose on price freshness. Chain-native specialists dominate their corner of the graph but fall to mid-table the moment you need coverage outside their primary ecosystem. The integration-depth finding in the price feed section reinforces this: leading on a specific chain requires sustained, chain-specific engineering investment that generalizes poorly across chains. -This fragmentation is not a market failure in the short-term sense. It is the expected outcome of an industry where the technical demands of each category — streaming price indexing, registry maintenance, DEX pool tracking, entity resolution — are genuinely different and resource-intensive. No provider has had the time or capital to lead across all of them. +The per-chain head lag data makes one thing concrete: the old narrative — "Solana is fast, EVM is slow" — does not explain what providers actually deliver. Robinhood Chain, the fastest-block chain in the cohort at 100 ms slots, produces the second-slowest head lag. A provider's performance on a chain reflects how much they have invested in that chain's integration, not the chain's architectural properties. Builders should evaluate providers per chain, not by headline aggregate. -The practical consequence for builders in 2026: most production applications using crypto data will need two or more providers simultaneously. A real-time price feed from a speed specialist, combined with a chain-agnostic registry from a breadth maximalist, is the pattern the benchmark data supports — not a single-vendor stack. The decision framework above maps which combination makes sense for each use case. +The practical consequence for production applications: most applications using live crypto data will need two or more providers simultaneously. A real-time price feed from a speed specialist, combined with a chain-agnostic registry from a coverage maximalist, is the pattern the benchmark data supports. The decision framework above maps which combination fits each use case. ## Sources -All data in this report is derived from OpenChainBench's live benchmarks. Figures are p50 over a 24-hour rolling window unless noted. Bench data is live and updates continuously — figures in this report reflect the state as of August 4, 2026. +All data is derived from OpenChainBench's live benchmarks. Figures are p50 over a 24-hour rolling window unless noted. Figures reflect the state as of August 5, 2026 — bench data updates continuously and values will shift. - **Price feeds:** [aggregator-head-lag](/benchmarks/aggregator-head-lag) · [api/stat/aggregator-head-lag](/api/stat/aggregator-head-lag) - **Token metadata:** [metadata-coverage](/benchmarks/metadata-coverage) · [asset-registry-coverage](/benchmarks/asset-registry-coverage) · [token-quote-coverage](/benchmarks/token-quote-coverage) @@ -220,5 +219,5 @@ All data in this report is derived from OpenChainBench's live benchmarks. Figure - **NFT:** [nft-collection-metadata](/benchmarks/nft-collection-metadata) - **Data API hub:** [/data-api](/data-api) — live cross-bench rankings, updated every 60 seconds - **Harness source:** [github.com/ChainBench/OpenChainBench/harnesses](https://github.com/ChainBench/OpenChainBench/tree/main/harnesses) -- **License:** All data and figures in this report are published under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). You may reproduce them with attribution to OpenChainBench and a link to the canonical URL. +- **License:** All data and figures are published under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). You may reproduce them with attribution to OpenChainBench and a link to the canonical URL. - **Corrections:** File a [GitHub issue](https://github.com/ChainBench/OpenChainBench/issues/new). Material corrections are applied in place with a dated note.