cmc-api-dex_skill

This skill provides a comprehensive reference to CoinMarketCap's DEX API endpoints for on-chain token data and security checks.

Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill cmc-api-dex

_meta.json303 B
SKILL.md5.9 KB

Overview

This skill is the definitive reference for CoinMarketCap DEX API endpoints covering token lookup, prices, pools, transactions, trending, and security analysis. It helps developers and analysts query on-chain DEX data, check token risk signals, and integrate DEX functionality into applications. Use it for contract-address lookups, liquidity and trade monitoring, and pre-trade security checks.

How this skill works

The skill documents each DEX endpoint, required headers (X-CMC_PRO_API_KEY), base URL, HTTP method (GET vs POST), and common parameters like network_slug and contract_address. It explains workflows for token discovery, price/batch queries, pool and liquidity history, trending tokens, and security detail lookups. Examples of response format, error codes, and rate-limit headers are included to help build robust integrations.

When to use it

Looking up a token by contract address or network (token by contract address)
Fetching latest DEX price(s) or batch token prices
Finding liquidity pools and liquidity history for a token
Monitoring recent DEX transactions or pair quotes
Checking token security/risk signals before trading (CMC security API)
Building or testing DEX integrations that query supported platforms

Best practices

Always include X-CMC_PRO_API_KEY in request headers and confirm your plan supports the endpoint
Use GET for simple queries and POST (JSON body) for complex or batch requests
Validate network_slug or platform_crypto_id using /v1/dex/platform/list before querying
Handle rate limits and errors: check X-CMC_PRO_API_KEY_CREDITS_REMAINING and standard HTTP error codes
Combine /v1/dex/token with /v1/dex/security/detail to perform pre-trade safety checks
Cache batch responses where possible to reduce credits and latency

Example use cases

Resolve a token contract to on-chain metadata and latest DEX price using /v1/dex/token and /v1/dex/token/price
Detect unusual liquidity changes or possible rug pulls with /v1/dex/liquidity-change/list and /v1/dex/token-liquidity/query
Fetch trending DEX tokens and top gainers for a discovery dashboard using /v1/dex/tokens/trending/list and /v1/dex/gainer-loser/list
Retrieve recent trades and pair quotes to power a swaps UI with /v1/dex/tokens/transactions and /v4/dex/pairs/quotes/latest
Run batch price and metadata checks for portfolio monitoring via /v1/dex/token/price/batch and /v1/dex/tokens/batch-query

FAQ

Include X-CMC_PRO_API_KEY with your API key in every request header.

When should I use POST instead of GET?

Use POST for complex or batch queries that require a JSON request body; use GET for simple query-string parameters.

How do I find valid network identifiers?

Call /v1/dex/platform/list to retrieve supported network_slug values and platform_crypto_id mappings.