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
In this repository7 other files it gives its agents.
- cmc-api-cryptoSkill
- cmc-api-exchangeSkill
- cmc-api-marketSkill
- cmc-mcpSkill
- cmc-x402Skill
- crypto-researchSkill
- market-reportSkill
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
- Distinctive: line 19
All requests require an API key in the header:
- Distinctive: line 48
Check token security before trading
- Very specific: line 85
Search for token: /v1/dex/search?keyword=PEPE
- Very specific: line 87
Check security risks: /v1/dex/security/detail?network_slug=ethereum&contract_address=0x...
- Very specific: line 112
Use /v1/dex/platform/list to get valid network slugs and platform IDs.
- Distinctive: line 144
All responses follow this structure:
≈ “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.
Files
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.comPOST vs GET Endpoints
Many DEX endpoints use POST for complex queries with body parameters. Always check the method:
- GET endpoints pass parameters as query strings
- 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:
- Get DEX token price by contract address
- Find a token's contract address by name
- Get prices for multiple tokens at once
- Check token security before trading
- Find liquidity pools for a token
- Find trending DEX tokens
- Find today's biggest DEX gainers
- Find newly launched tokens
- Detect potential rug pulls (liquidity removal)
- Get recent trades for a token
- Get supported networks and DEXs
- Get meme coins
API Overview
| Endpoint | Method | Description | Reference |
| /v1/dex/token | GET | Token details by platform/address | tokens.md |
| /v1/dex/token/price | GET | Latest DEX price for a token | tokens.md |
| /v1/dex/token/price/batch | POST | Batch token prices | tokens.md |
| /v1/dex/token/pools | GET | Liquidity pools for a token | tokens.md |
| /v1/dex/token-liquidity/query | GET | Token liquidity over time | tokens.md |
| /v1/dex/tokens/batch-query | POST | Batch token metadata | tokens.md |
| /v1/dex/tokens/transactions | GET | Recent DEX transactions | tokens.md |
| /v1/dex/tokens/trending/list | POST | Trending DEX tokens | tokens.md |
| /v4/dex/pairs/quotes/latest | GET | Latest DEX pair quotes | pairs.md |
| /v4/dex/spot-pairs/latest | GET | DEX spot pairs listing | pairs.md |
| /v1/dex/platform/list | GET | List supported DEX platforms | platforms.md |
| /v1/dex/platform/detail | GET | Platform details | platforms.md |
| /v1/dex/search | GET | Search DEX tokens/pairs | platforms.md |
| /v1/dex/gainer-loser/list | POST | Top DEX gainers/losers | discovery.md |
| /v1/dex/liquidity-change/list | GET | Tokens with liquidity changes | discovery.md |
| /v1/dex/meme/list | POST | Meme tokens on DEX | discovery.md |
| /v1/dex/new/list | POST | Newly discovered DEX tokens | discovery.md |
| /v1/dex/security/detail | GET | Token security/risk signals | security.md |
Common Workflows
Get DEX Token Information
- Search for token:
/v1/dex/search?keyword=PEPE - Get token details:
/v1/dex/token?network_slug=ethereum&contract_address=0x... - Check security risks:
/v1/dex/security/detail?network_slug=ethereum&contract_address=0x...
Analyze Token Liquidity
- Get token pools:
/v1/dex/token/pools?network_slug=ethereum&contract_address=0x... - Get liquidity history:
/v1/dex/token-liquidity/query?network_slug=ethereum&contract_address=0x...
Find Trending Tokens
- Get trending tokens: POST
/v1/dex/tokens/trending/listwith filters - Get gainers/losers: POST
/v1/dex/gainer-loser/list - Find new tokens: POST
/v1/dex/new/list
Monitor DEX Activity
- Get recent transactions:
/v1/dex/tokens/transactions?network_slug=ethereum&contract_address=0x... - Get pair quotes:
/v4/dex/pairs/quotes/latest?network_slug=ethereum&contract_address=0x...
Key Parameters
Most DEX endpoints require:
network_slugorplatform_crypto_id: Identifies the blockchain (ethereum, solana, bsc)contract_address: The token's on-chain contract address
Use /v1/dex/platform/list to get valid network slugs and platform IDs.
Error Handling
| Code | Meaning |
| 400 | Bad request (invalid parameters) |
| 401 | Unauthorized (invalid or missing API key) |
| 403 | Forbidden (endpoint not in your plan) |
| 429 | Rate limit exceeded |
| 500 | Server 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:
X-CMC_PRO_API_KEY_CREDITS_REMAINING: Credits leftX-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": { ... }
}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
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.

