agentleFS
OpenCMCOpenCMC/skills-for-ai-agents-by-CoinMarketCap/skills/cmc-api-exchange/SKILL.md

cmc-api-exchange

Skill75 starsChanged 24 days agoMITView on GitHub

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"

  • Reads credentials

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 3 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All requests require an API key in the header.

    line 19
  2. Distinctive:

    Check exchange reserves (proof-of-reserves)

    line 49
  3. Very specific:

    Call /v1/exchange/map with slug=binance to get the exchange ID

    line 70
  4. Very specific:

    Call /v1/exchange/info with the ID to get full metadata

    line 71
  5. Very specific:

    Call /v1/exchange/listings/latest to get all exchanges ranked by volume

    line 77
  6. Very specific:

    Use sort=volume_24h and sort_dir=desc for descending order

    line 78
  7. Very specific:

    Call /v1/exchange/market-pairs/latest with that ID

    line 85
  8. Very specific:

    Call /v1/exchange/quotes/historical with date range parameters

    line 93
  9. Very specific:

    All responses include a status object:

    line 108
  10. Distinctive:

    All responses return JSON with this structure:

    line 139

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.