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

cmc-api-dex

Skill75 starsChanged 24 days agoMITView on GitHub

API reference for CoinMarketCap DEX endpoints including token lookup, pools, transactions, trending, and security analysis. Use this skill whenever the user mentions DEX API, asks about on-chain token data, wants to look up tokens by contract address, needs security/rug risk checks, or is building DEX integrations. This is the definitive reference for CMC DEX API questions. Trigger: "DEX API", "token by contract address", "CMC security API", "liquidity pool API", "/cmc-api-dex"

  • Reads credentials

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 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.

  • 3

    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 token security before trading

    line 48
  3. Very specific:

    Search for token: /v1/dex/search?keyword=PEPE

    line 85
  4. Very specific:

    Check security risks: /v1/dex/security/detail?network_slug=ethereum&contract_address=0x...

    line 87
  5. Very specific:

    Use /v1/dex/platform/list to get valid network slugs and platform IDs.

    line 112
  6. Distinctive:

    All responses follow this structure:

    line 144

≈ “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 DEX API

This skill covers CoinMarketCap's DEX (Decentralized Exchange) APIs for on-chain token data. Unlike CEX endpoints, these APIs fetch data directly from blockchain DEXs like Uniswap, PancakeSwap, and Raydium.

Authentication

All requests require an API key in the header:

curl -X GET "https://pro-api.coinmarketcap.com/v1/dex/platform/list" \
  -H "X-CMC_PRO_API_KEY: your-api-key"

Get your API key at: https://pro.coinmarketcap.com/login

Base URL

https://pro-api.coinmarketcap.com

POST vs GET Endpoints

Many DEX endpoints use POST for complex queries with body parameters. Always check the method:

  1. GET endpoints pass parameters as query strings
  2. POST endpoints pass parameters in JSON body with Content-Type: application/json

Common Use Cases

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

  1. Get DEX token price by contract address
  2. Find a token's contract address by name
  3. Get prices for multiple tokens at once
  4. Check token security before trading
  5. Find liquidity pools for a token
  6. Find trending DEX tokens
  7. Find today's biggest DEX gainers
  8. Find newly launched tokens
  9. Detect potential rug pulls (liquidity removal)
  10. Get recent trades for a token
  11. Get supported networks and DEXs
  12. Get meme coins

API Overview

EndpointMethodDescriptionReference
/v1/dex/tokenGETToken details by platform/addresstokens.md
/v1/dex/token/priceGETLatest DEX price for a tokentokens.md
/v1/dex/token/price/batchPOSTBatch token pricestokens.md
/v1/dex/token/poolsGETLiquidity pools for a tokentokens.md
/v1/dex/token-liquidity/queryGETToken liquidity over timetokens.md
/v1/dex/tokens/batch-queryPOSTBatch token metadatatokens.md
/v1/dex/tokens/transactionsGETRecent DEX transactionstokens.md
/v1/dex/tokens/trending/listPOSTTrending DEX tokenstokens.md
/v4/dex/pairs/quotes/latestGETLatest DEX pair quotespairs.md
/v4/dex/spot-pairs/latestGETDEX spot pairs listingpairs.md
/v1/dex/platform/listGETList supported DEX platformsplatforms.md
/v1/dex/platform/detailGETPlatform detailsplatforms.md
/v1/dex/searchGETSearch DEX tokens/pairsplatforms.md
/v1/dex/gainer-loser/listPOSTTop DEX gainers/losersdiscovery.md
/v1/dex/liquidity-change/listGETTokens with liquidity changesdiscovery.md
/v1/dex/meme/listPOSTMeme tokens on DEXdiscovery.md
/v1/dex/new/listPOSTNewly discovered DEX tokensdiscovery.md
/v1/dex/security/detailGETToken security/risk signalssecurity.md

Common Workflows

Get DEX Token Information

  1. Search for token: /v1/dex/search?keyword=PEPE
  2. Get token details: /v1/dex/token?network_slug=ethereum&contract_address=0x...
  3. Check security risks: /v1/dex/security/detail?network_slug=ethereum&contract_address=0x...

Analyze Token Liquidity

  1. Get token pools: /v1/dex/token/pools?network_slug=ethereum&contract_address=0x...
  2. Get liquidity history: /v1/dex/token-liquidity/query?network_slug=ethereum&contract_address=0x...

Find Trending Tokens

  1. Get trending tokens: POST /v1/dex/tokens/trending/list with filters
  2. Get gainers/losers: POST /v1/dex/gainer-loser/list
  3. Find new tokens: POST /v1/dex/new/list

Monitor DEX Activity

  1. Get recent transactions: /v1/dex/tokens/transactions?network_slug=ethereum&contract_address=0x...
  2. Get pair quotes: /v4/dex/pairs/quotes/latest?network_slug=ethereum&contract_address=0x...

Key Parameters

Most DEX endpoints require:

  1. network_slug or platform_crypto_id: Identifies the blockchain (ethereum, solana, bsc)
  2. contract_address: The token's on-chain contract address

Use /v1/dex/platform/list to get valid network slugs and platform IDs.

Error Handling

CodeMeaning
400Bad request (invalid parameters)
401Unauthorized (invalid or missing API key)
403Forbidden (endpoint not in your plan)
429Rate limit exceeded
500Server error

Example error response:

{
  "status": {
    "error_code": 400,
    "error_message": "Invalid value for 'contract_address'"
  }
}

Rate Limits

Rate limits depend on your API plan. Check response headers:

  1. X-CMC_PRO_API_KEY_CREDITS_REMAINING: Credits left
  2. X-CMC_PRO_API_KEY_CREDITS_RESET: Reset timestamp

Response Format

All responses follow this structure:

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

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.