agentleFS
Sign inStart free
OpenCMCOpenCMC/skills-for-ai-agents-by-CoinMarketCap/skills/cmc-api-market/SKILL.md

cmc-api-market

Skill75 starsChanged 24 days agoMITView on GitHub

API reference for CoinMarketCap market-wide endpoints including global metrics, fear/greed, indices, trending topics, and charts. Use this skill whenever the user mentions market API, asks about fear/greed index, wants global metrics or BTC dominance data, needs k-line charts, or is working with market sentiment. This is the complete reference for CMC market-wide API questions. Trigger: "market API", "fear greed API", "global metrics API", "CMC charts API", "/cmc-api-market"

  • Reads credentials

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All requests require the X-CMC_PRO_API_KEY header.

    line 19
  2. Distinctive:

    Check API usage and limits

    line 51
  3. Very specific:

    Check trending tokens: /v1/community/trending/token

    line 126
  4. Very specific:

    Read latest posts: /v1/content/posts/top

    line 128
  5. Distinctive:

    Use interval parameter for timeframe (1h, 4h, 1d)

    line 133
  6. Distinctive:

    Check these response headers to monitor usage:

    line 164
  7. Distinctive:

    All endpoints return JSON with this structure:

    line 172
  8. Very specific:

    Use the /v1/key/info endpoint to check your plan limits before heavy usage

    line 188

≈ “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 Market API Skill

This skill covers market-wide cryptocurrency data including global metrics, sentiment indicators, market indices, community activity, news content, charting data, and utility endpoints.

Authentication

All requests require the X-CMC_PRO_API_KEY header.

curl -X GET "https://pro-api.coinmarketcap.com/v1/global-metrics/quotes/latest" \
  -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

Common Use Cases

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

  1. Get current market sentiment (Fear & Greed)
  2. Get total crypto market cap
  3. Get BTC dominance
  4. Track market cap history
  5. Track Fear & Greed history
  6. Get CMC100 index performance
  7. Compare CMC100 vs CMC20
  8. Get OHLCV candlestick data for charts
  9. Get simple price time series
  10. Get community trending tokens
  11. Get trending discussion topics
  12. Get latest crypto news
  13. Convert currency amounts
  14. Check API usage and limits
  15. Get fiat currency IDs

API Overview

Global Metrics

EndpointDescriptionReference
GET /v1/global-metrics/quotes/historicalHistorical global market metricsglobal-metrics.md
GET /v1/global-metrics/quotes/latestLatest total market cap, BTC dominanceglobal-metrics.md

Fear and Greed Index

EndpointDescriptionReference
GET /v3/fear-and-greed/historicalHistorical fear/greed valuesfear-greed.md
GET /v3/fear-and-greed/latestCurrent market sentiment scorefear-greed.md

Market Indices

EndpointDescriptionReference
GET /v3/index/cmc100-historicalCMC100 index historyindices.md
GET /v3/index/cmc100-latestCMC100 current valueindices.md
GET /v3/index/cmc20-historicalCMC20 index historyindices.md
GET /v3/index/cmc20-latestCMC20 current valueindices.md

Community

EndpointDescriptionReference
GET /v1/community/trending/tokenTrending tokens by community activitycommunity.md
GET /v1/community/trending/topicTrending discussion topicscommunity.md

Content

EndpointDescriptionReference
GET /v1/content/latestLatest news and Alexandria articlescontent.md
GET /v1/content/posts/commentsComments on a specific postcontent.md
GET /v1/content/posts/latestLatest community postscontent.md
GET /v1/content/posts/topTop ranked community postscontent.md

K-Line Charts

EndpointDescriptionReference
GET /v1/k-line/candlesOHLCV candlestick datakline.md
GET /v1/k-line/pointsTime series price/market cap pointskline.md

Tools

EndpointDescriptionReference
GET /v1/fiat/mapMap fiat currencies to CMC IDstools.md
GET /v1/key/infoAPI key usage and plan detailstools.md
GET /v2/tools/price-conversionConvert between currenciestools.md

Common Workflows

Get Market Sentiment Overview

  1. Fetch fear/greed index: /v3/fear-and-greed/latest
  2. Get global metrics: /v1/global-metrics/quotes/latest
  3. Combine for sentiment analysis with market cap context

Track Market Index Performance

  1. Get current CMC100 value: /v3/index/cmc100-latest
  2. Fetch historical data: /v3/index/cmc100-historical
  3. Compare performance over time

Monitor Community Activity

  1. Check trending tokens: /v1/community/trending/token
  2. Review trending topics: /v1/community/trending/topic
  3. Read latest posts: /v1/content/posts/top

Build Price Charts

  1. Fetch OHLCV candles: /v1/k-line/candles
  2. Use interval parameter for timeframe (1h, 4h, 1d)
  3. Plot candlestick chart with returned data

Currency Conversion

  1. Get fiat currency IDs: /v1/fiat/map
  2. Convert amounts: /v2/tools/price-conversion

Error Handling

Status CodeMeaningAction
400Bad RequestCheck parameter values and format
401UnauthorizedVerify API key is valid
403ForbiddenEndpoint not available on your plan
429Rate LimitedWait and retry with backoff
500Server ErrorRetry after delay

Error Response Format

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

Rate Limit Headers

Check these response headers to monitor usage:

  1. X-CMC_PRO_API_KEY_CREDITS_USED - Credits consumed
  2. X-CMC_PRO_API_KEY_CREDITS_REMAINING - Credits left
  3. X-CMC_PRO_API_KEY_RATE_LIMIT - Requests per minute limit

Response Format

All endpoints return JSON with this structure:

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

Tips

  1. Use the /v1/key/info endpoint to check your plan limits before heavy usage
  2. Cache global metrics data as it updates every few minutes
  3. Fear/greed index updates daily, no need for frequent polling
  4. K-line data supports multiple intervals for different chart timeframes
  5. Community trending data refreshes periodically throughout the day

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.

Check your setup, free