Crypto Market Data APIs

A crypto market data API supplies price, market-cap, exchange, liquidity, volume, or protocol-market context for products and AI agents that need market state alongside on-chain facts. This page is a comparison surface for market-data sources, not a claim that every market-data provider has live PubFi gateway support

Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows

At a glance

Category summary

Primary query: crypto market data API
Definition: Crypto market data API sources for prices, market context, exchanges, and asset metadata.
Sources: 8
Capabilities: 10
Chain hubs: 3
Use-case groups: 16
Last verified: 2026-06-02
PubFi status: Discovery comparison and request-routing surface; individual source pages carry claim-safe integration status.

Official-source citations

CoinGecko API Primary coverage: Crypto asset prices, market data, exchanges, and metadata Source
CoinGecko API Discovery category: Market data Source
CoinMarketCap API Primary coverage: Crypto asset prices, market capitalization, rankings, and metadata Source
CoinMarketCap API Fixture coverage: Market data coverage for the multichain fixture target Source
CryptoCompare Primary coverage: Digital asset prices, exchanges, order books, and historical crypto data Source
CryptoCompare Fixture coverage: Market data coverage for the multichain fixture target Source
Kaiko Primary coverage: Institutional crypto trades, order books, reference rates, and exchange analytics Source
Kaiko Fixture coverage: Market data coverage for the multichain fixture target Source
Amberdata Primary coverage: Market, DeFi, NFT, and on-chain digital asset datasets Source
Amberdata Fixture coverage: Market data and on-chain state coverage for the multichain fixture target Source
Dune API Primary coverage: Queryable crypto analytics datasets authored by community and team workflows Source
Dune API Fixture coverage: On-chain state and market data coverage for Ethereum and multichain fixture targets Source
DeFiLlama Primary coverage: Protocol TVL, stablecoins, yields, fees, volumes, and chain metrics Source
DeFiLlama Fixture coverage: Market data coverage for the multichain fixture target Source
Hello Moon Primary coverage: Solana token, NFT, wallet, market activity, and analytics data Source
Hello Moon Fixture coverage: Market data and NFT coverage for the Solana fixture target Source

Editorial overview

Market data is one of the easiest categories to overstate because provider coverage, freshness, redistribution rights, and plan-specific quotas vary widely. CoinGecko and CoinMarketCap are useful broad retail and developer benchmarks. DeFiLlama adds protocol and DeFi market context. Kaiko and Amberdata are more institutional or product-scoped comparison points. The buyer should decide first whether the application needs broad asset metadata, exchange/liquidity context, DeFi protocol metrics, or paid institutional feeds.

Start here recommendations

CoinGecko API

Why start here: Start here when the team needs broad asset price, market, exchange, and metadata context with public docs and pricing evidence.
Best for: Broad crypto market context

CoinMarketCap API

Why start here: Compare when rankings, market capitalization context, and familiar market-data taxonomy matter to the application.
Best for: Rankings and market-cap context

DeFiLlama

Why start here: Use when the market-data requirement is closer to DeFi protocol TVL, yields, fees, volumes, or chain metrics.
Best for: Open DeFi market context

Decision criteria and landscape gaps

Evaluation criteria

Define whether the product needs prices, market-cap rankings, exchange data, liquidity depth, DeFi protocol metrics, or institutional feeds.
Use only official pricing and quota evidence for rate-limit and starting-price claims.
Check licensing, redistribution, and commercial-use constraints before embedding data in user-facing products.
For agent workflows, confirm freshness expectations and fallback behavior when a market-data source is unavailable or delayed.

Provider landscape gaps

Public pricing pages do not always make commercial-use rights and redistribution limits as visible as raw call quotas.
Broad market-data providers and DeFi-specific data providers are often compared as if they solve the same job.
Many provider pages make asset breadth visible but leave normalization, symbol mapping, and stale-price behavior for implementers to discover.