On-Chain DEX Data Source the Industry Trusts

On-chain token, pair, liquidity, and holder intelligence in one API.

CoinMarketCap DEX API delivers standardized on-chain market data across decentralized ecosystems, including Ethereum, Solana, and BNB Chain, with endpoint families for discovery, pricing, security signals, holders, and pair-level OHLCV/trade analytics.

16Token Endpoints

2Platforms Endpoints

5Holder Endpoints

2K-line & OHLCV Endpoints

What teams build with CMC DEX data

The API is built for real products that need reliable on-chain token and pair intelligence, not ad hoc scraping.

Alpha Discovery PipelinesTrack trending, new, and high-momentum tokens to power discovery tools and alpha feeds.

Pair-level market analyticsAnalyze quotes, trades, and OHLCV data across DEX pairs with network-aware filtering.

Liquidity & Pool MonitorMonitor liquidity, pool changes, and swap activity for risk and execution insights.

Batch queries at scaleFetch token prices and metadata for multiple addresses in a single request.

Holder analysisUnderstand holder concentration and tagged wallets for deeper risk signals.

Security contextAccess contract and pair-level security data, including integrated scan results where available.

DEX API Families at a Glance

Coverage is split by job-to-be-done so teams can integrate incrementally.

DEX Tokens

/dex/token/*

Token lookup, batch query, token price, pools, liquidity query, transactions, discovery lists, and security detail.

Platform & Networks

/dex/platform/*

Supported DEX platforms and network metadata, including stable identifiers and explorer URL fields.

Holders

/dex/holders/*

Holder count, holder list/detail, tag distribution, and holder trend metrics for concentration analysis.

OHLCV & K-line

/k-line/*

K-line points/candles and pair-level OHLCV latest/historical for chart display and backtesting.

View All DEX APIs

Integration Model Developers Need to Know

Core Request Model

Most DEX workflows pivot on two identifiers: network_slug (or platform_crypto_id) and contract_address. GET routes cover direct lookup patterns; POST routes handle complex filter logic and batch payloads. Operationally useful flags in v4 pair endpoints include skip_invalid, reverse_order, and aux fields such as holders and security_scan.

GET /v4/dex/pairs/quotes/latest
Required identity context:
- network_slug or network_id
- contract_address

Advanced controls:
- aux=holders,security_scan,buy_tax,sell_tax
- skip_invalid=true - reverse_order=true

Use case:
Pair quotes and enriched risk context in one request path.

Security & Forensics Signals

A clear path from initial integration to scalable, production-grade DEX products.

Go+ Scan IntegrationSupported v4 pair endpoints expose security_scan in aux fields, documented as security scan by Go+.

Tagged Holder CohortsHolder endpoints support tags such as tag_sniper, tag_dev, whale, bot, and smart-money cohorts.

Concentration MetricsTrack concentration using holdingRatioOfTop10, holdingRatioOfTop50, and holdingRatioOfTop100.

High-throughput Endpoints for Production Systems

These routes are especially useful when reducing request count and controlling latency under load.

Batch Token Price

/dex/token/price/batch

Batch get token prices for multiple platform-address pairs in one request.

Batch Query

/dex/tokens/batch-query

Batch query token metadata and market context across multiple addresses.

Transactions

/dex/tokens/transactions

Filter swaps by transaction type, maker addresses, and min/max USD volume thresholds.

Build Path for DEX ProductsA clear progression from initial integration to high-volume production systems.

STEP 01Resolve Network ScopeStart with platform/network endpoints and normalize the network identifiers your app will support.

STEP 02Establish Token GraphUse search plus token/token-price/token-pools to build the core token and pool graph for your products.

STEP 03Add Risk & Holder LensesLayer security/detail and holder analytics to detect concentration and token-level risk changes.

STEP 04Expand to Pair AnalyticsAdopt v4 pair quotes/trades/OHLCV endpoints for execution monitoring, charting, and strategy research.

Optional x402 access for DEX routes

For pay-per-request workflows, x402 routes support DEX search and pair quotes with on-chain USDC payment, including no API key flow for agent-driven use cases.

DEX Search

/x402/v1/dex/search

Search for DEX tokens by keyword (name, symbol, or contract address).

DEX Token Quotes

/x402/v3/cryptocurrency/quotes

Get the latest market quotes for one or more cryptocurrencies.

DEX Token List

/x402/v3/cryptocurrency/listings

Get a paginated list of all active cryptocurrencies with latest market data, ranked by market cap.

DEX Pair Quotes

/x402/v4/dex/pairs/quotes

Supported DEX platforms and network metadata, including stable identifiers and explorer URL fields.

View x402 Docs

DEX API FAQ

What are the minimum parameters for most DEX calls?

For core DEX token and pair workflows, you should expect to provide network context with network_slug (or platform_crypto_id) plus a contract_address.

When should we use GET versus POST?

Use GET for direct lookup patterns and use POST for complex filters and batch-style requests where payload shape is easier to express in JSON.

Which batch endpoints should we use first?

Start with /v1/dex/token/price/batch for multi-token pricing and /v1/dex/tokens/batch-query for multi-token metadata retrieval.

How do we avoid failed multi-pair queries?

In v4 pair endpoints, use skip_invalid=true to skip invalid pair lookups and still return valid results in the same request.

Can we filter swaps beyond simple latest trades?

Yes. The transactions endpoint supports filters for buy/sell type, maker address lists, and minimum/maximum USD volume ranges.

Can we enrich pair data with risk and holder context?

Yes. Use the aux parameter to request additional fields such as holder counts and security scan-related outputs on supported v4 pair endpoints.

Do holder endpoints expose concentration signals?

Yes. Holder trend responses include concentration ratios for top holder buckets and support tagged cohort analysis such as sniper and dev tags.

Do we need an API key for every DEX integration path?

No. You can use x402 routes for selected DEX flows and pay per request in USDC instead of managing an API key for that access path.

Ship DEX Intelligence with Fewer Moving Parts

Integrate standardized on-chain token and pair data, then scale into holder, security, and OHLCV workflows using the same CoinMarketCap API surface.