cmc-api-exchange

API reference for CoinMarketCap exchange endpoints including exchange info, volume, market pairs, and assets. Use this skill whenever the user mentions exchange API, asks about exchange volumes, wants trading pair data, needs proof-of-reserves info, or is building exchange integrations. This is the authoritative reference for CMC exchange API questions. Trigger: "exchange API", "CMC exchange data", "trading pairs API", "exchange volume API", "/cmc-api-exchange"

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "cmc-api-exchange" with this command: npx skills add coinmarketcap-official/skills-for-ai-agents-by-coinmarketcap/coinmarketcap-official-skills-for-ai-agents-by-coinmarketcap-cmc-api-exchange

CoinMarketCap Exchange API Skill

This skill covers CoinMarketCap APIs for centralized cryptocurrency exchanges (Binance, Coinbase, Kraken, etc.). Use these endpoints to retrieve exchange metadata, trading volumes, market pairs, and asset holdings.

Authentication

All requests require an API key in the header.

  1. Get your API key at https://pro.coinmarketcap.com/login
  2. Include the header X-CMC_PRO_API_KEY: your-api-key in all requests
curl -X GET "https://pro-api.coinmarketcap.com/v1/exchange/map" \
  -H "X-CMC_PRO_API_KEY: your-api-key"

Base URL

https://pro-api.coinmarketcap.com

Common Use Cases

See use-cases.md for goal-based guidance on which endpoint to use:

  1. Get exchange information by name
  2. Find an exchange's CMC ID
  3. Get top exchanges by volume
  4. Get only spot exchanges (or only derivatives)
  5. Get current volume for a specific exchange
  6. Compare volume across multiple exchanges
  7. Get historical volume for an exchange
  8. Get all trading pairs on an exchange
  9. Find BTC pairs on an exchange
  10. Get perpetual/futures pairs on an exchange
  11. Check exchange reserves (proof-of-reserves)
  12. Find exchanges that list a specific coin

API Overview

EndpointDescriptionReference
GET /v1/exchange/mapMap exchange names to CMC IDsreferences/info.md
GET /v1/exchange/infoExchange metadata (logo, URLs, description)references/info.md
GET /v1/exchange/listings/latestList all exchanges with market datareferences/listings.md
GET /v1/exchange/quotes/latestLatest exchange volume and metricsreferences/quotes.md
GET /v1/exchange/quotes/historicalHistorical exchange volume datareferences/quotes.md
GET /v1/exchange/market-pairs/latestTrading pairs on an exchangereferences/market-pairs.md
GET /v1/exchange/assetsAssets held by an exchangereferences/assets.md

Common Workflows

Get Exchange Information

Why: Most endpoints require CMC exchange IDs, not names. The map endpoint translates human-readable slugs to IDs.

  1. Call /v1/exchange/map with slug=binance to get the exchange ID
  2. Call /v1/exchange/info with the ID to get full metadata

Compare Exchange Volumes

Why: Volume indicates liquidity and trustworthiness. Higher volume means better price execution and lower slippage.

  1. Call /v1/exchange/listings/latest to get all exchanges ranked by volume
  2. Use sort=volume_24h and sort_dir=desc for descending order

Analyze Trading Pairs

Why: Understanding available pairs helps users find where to trade specific assets and compare liquidity across venues.

  1. Get the exchange ID from /v1/exchange/map
  2. Call /v1/exchange/market-pairs/latest with that ID
  3. Filter by category=spot or category=derivatives as needed

Track Volume History

Why: Historical volume reveals trends. Declining volume may signal user exodus. Spikes may indicate wash trading or news events.

  1. Get the exchange ID from /v1/exchange/map
  2. Call /v1/exchange/quotes/historical with date range parameters

Query Parameters

Most endpoints accept these common parameters:

ParameterTypeDescription
idstringCMC exchange ID (comma-separated for multiple)
slugstringExchange slug (e.g., "binance")
convertstringCurrency for price conversion (default: USD)
auxstringAdditional fields to include in response

Error Handling

All responses include a status object:

{
  "status": {
    "timestamp": "2024-01-15T12:00:00.000Z",
    "error_code": 0,
    "error_message": null,
    "credit_count": 1
  },
  "data": { }
}

Common Error Codes

CodeMeaning
0Success
400Bad request (invalid parameters)
401Unauthorized (invalid API key)
403Forbidden (plan limit exceeded)
429Rate limit exceeded
500Internal server error

Rate Limits

Rate limits depend on your subscription plan. Check the credit_count in responses to track API credit usage. The X-CMC_PRO_API_KEY header must be present on every request.

Response Format

All responses return JSON with this structure:

{
  "status": { },
  "data": { }
}

The data field contains either an object (single item) or array (multiple items) depending on the endpoint.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

cmc-x402

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

cmc-mcp

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

market-report

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

cmc-api-dex

No summary provided by upstream source.

Repository SourceNeeds Review