CoinMarketCap Skills Marketplace: Skill Pipelines For Crypto AI Agents

An AI agent should not have to reinvent its crypto-data workflow for every request.

A market brief, a token-research task, a DEX query and a backend integration require different execution paths. Without defined workflows, an agent can waste context, select the wrong access method or produce an answer that is difficult to reproduce.

CoinMarketCap Skills Marketplace gives agents a clearer route into CMC data. It connects common crypto tasks to reusable skill pipelines built for terminal workflows, MCP-based agents, x402 pay-per-request calls and direct REST API integrations.

The goal is precise execution: choose the skill route that fits the task, then build the response from CoinMarketCap data through a repeatable workflow.

Choose The Route Before Calling The Data

CoinMarketCap AI Agent Skills are organised around four routes.

Route:CLI Skills
Start Here When You Need: Repeatable workflows on top of the CoinMarketCap CLI
Best Fit: Shell-first agents, market reports and single-asset research

Route:MCP Skills
Start Here When You Need: Structured workflows using live CMC MCP tools
Best Fit: Market reports, token research and MCP-compatible agents

Route:x402 Skills
Start Here When You Need: Pay-per-request access without an API key
Best Fit: Experimental agent workflows and on-chain payment flows

Route:API Integration Skills
Start Here When You Need: Direct REST implementation guidance
Best Fit: Custom applications, backends and production logic

These are not competing versions of the same workflow. They answer different implementation questions.

Use CLI Skills when the agent already belongs in the terminal. Use MCP Skills when the agent needs structured CMC tool calls. Use x402 when request-level payment fits the experiment. Use API Integration Skills when the application owns the full REST integration.

CLI Skills: Structured Workflows On Top Of The CMC CLI

CMC CLI is the terminal-native runtime. CLI Skills provide reusable workflow guidance on top of that runtime.

Install and authenticate the CLI:

brew install coinmarketcap-official/CoinMarketCap-CLI/cmc
cmc auth
cmc status -o json

The CLI route supports terminal workflows that benefit from stable command output, scripting, JSON output and CSV export.

The current CLI Skills set covers three workflow types:

Skill: CMC CLI
Workflow: Command selection, output rules, execution ordering and common mistakes

Skill: Market Skill
Workflow: Market snapshots, movers, BTC/ETH anchors and report-style workflows using cmc commands

Skill: Coin Research
Workflow: Single-asset analysis across identity, quotes, history, pairs, market context and sentiment

This route fits a terminal agent producing a morning market brief, a research script retrieving a structured asset snapshot or an internal workflow that needs consistent machine-readable output.

The distinction matters: the CLI is the runtime; the skills tell an agent how to use that runtime consistently.

MCP Skills: Live CMC Tools For Structured Agent Tasks

MCP Skills are designed for agents that call CoinMarketCap tools through a Model Context Protocol connection.

A standard CMC MCP configuration uses:

{
"mcpServers": {
"cmc-mcp": {
"url": "https://mcp.coinmarketcap.com/mcp",
"headers": {
"X-CMC-MCP-API-KEY": "your-api-key"
}
}
}
}

The central workflow rule is identity first.

When a user asks about a cryptocurrency by name or symbol, the agent should search for the asset, retrieve its CMC ID and use that stable identifier in subsequent tool calls.

For example:

User asks: “How is Solana doing?”

Agent workflow:
1. Search for Solana.
2. Resolve CMC ID 5426.
3. Retrieve relevant quotes, metadata, technical signals, news or metrics using the ID.

For multi-asset comparisons, resolve each asset and batch quote requests where supported.

What CMC MCP Can Retrieve

CoinMarketCap MCP currently provides 12 documented tools for crypto-market analysis.

Tool: search_cryptos
Primary Output: Search by asset name or symbol and resolve CMC IDs

Tool: get_crypto_quotes_latest
Primary Output: Price, market cap, volume, percentage changes, supply and dominance

Tool: get_crypto_info
Primary Output: Description, links, tags, explorer URLs and launch date

Tool: get_crypto_metrics
Primary Output: Address and holder-distribution metrics

Tool: get_crypto_technical_analysis
Primary Output: SMA, EMA, MACD, RSI, Fibonacci levels and pivot points

Tool: get_crypto_latest_news
Primary Output: Recent asset news and publication details

Tool: search_crypto_info
Primary Output: Semantic search across crypto concepts, whitepapers and FAQs

Tool: get_global_metrics_latest
Primary Output: Total market cap, volume, dominance, Fear and Greed, Altcoin Season and ETF-flow context

Tool: get_global_crypto_derivatives_metrics
Primary Output: Open interest, funding, liquidations and derivatives context

Tool: get_crypto_marketcap_technical_analysis
Primary Output: Technical indicators for total crypto market capitalisation

Tool: trending_crypto_narratives
Primary Output: Trending themes with market data and associated assets

Tool: get_upcoming_macro_events
Primary Output: Scheduled macro and regulatory catalysts

MCP Skills add repeatable workflows above those tools:

MCP Skill: CMC MCP
What It Structures: General CMC MCP tool usage and data-rich answers

MCP Skill:Market Report
What It Structures: Daily or weekly reports using global metrics, sentiment, narratives, derivatives and catalysts

MCP Skill: Crypto Research
What It Structures: Token research across fundamentals, tokenomics, holder analysis, technicals and risk factors

Current MCP tools include holder and distribution metrics. The broader multi-market DEX and expanded on-chain capability described in the MCP documentation is still marked as work in progress, so it should not be presented as complete MCP coverage today.

x402 Skills: Pay Per Request Without An API Key

x402 Skills support CMC access through request-level USDC payments on Base.

The workflow is based on HTTP 402 payment handling:

The client requests an x402-enabled CMC endpoint.

The server returns payment requirements.

The wallet signs a USDC payment authorisation.

The client retries the original request with the signed payment header.

Payment executes only after successful data delivery.

Supported x402 REST paths currently include:

Workflow: DEX token search
Path: /x402/v1/dex/search

Workflow: Latest cryptocurrency quotes
Path: /x402/v3/cryptocurrency/quotes/latest

Workflow: Latest cryptocurrency listings
Path: /x402/v3/cryptocurrency/listings/latest

Workflow: Latest DEX pair quotes
Path: /x402/v4/dex/pairs/quotes/latest

x402 also exposes an MCP endpoint for agent clients using an x402-aware HTTP transport:

https://mcp.coinmarketcap.com/x402/mcp

This route fits agent experiments or episodic workflows where request-level payment is preferable to creating an API-key subscription workflow.

API Integration Skills: Build Directly With The REST API

API Integration Skills are designed for products that call CoinMarketCap REST endpoints directly and own their application logic.

Authenticated REST integrations use:

Base URL: https://pro-api.coinmarketcap.com

Header: X-CMC_PRO_API_KEY: your-api-key

The current API Integration Skills group the implementation surface into four areas:

Skill: Cryptocurrency API
Documented Scope: 16 endpoints
Product Workflows: Listings, quotes, OHLCV, categories, trending and market pairs

Skill:DEX API
Documented Scope: 18 endpoints
Product Workflows: On-chain token data, prices, pools, transactions and security analysis

Skill:Exchange API
Documented Scope: 7 endpoints
Product Workflows: Exchange information, listings, volume, market pairs and assets

Skill: Market API
Documented Scope: 19 endpoints
Product Workflows: Global metrics, Fear and Greed, CMC indices, community trends, content and charts

Choose this route when the product needs custom caching, backend scheduling, application-specific decision logic, monitoring, user interfaces or production control over requests and responses.

Match The Skill To The Task

A useful agent architecture does not start by forcing every problem through one access method.

Task: Produce a shell-native market snapshot
Recommended CMC Route: CLI Skills

Task: Run single-asset terminal research
Recommended CMC Route: Coin Research through CLI Skills

Task: Build an MCP-based market report
Recommended CMC Route: MCP Skills / Market Report

Task: Run a structured token research workflow through tools
Recommended CMC Route: MCP Skills / Crypto Research

Task: Test supported pay-per-request data access
Recommended CMC Route: x402 Skills

Task: Build a custom product or backend
Recommended CMC Route: API Integration Skills

A route should be chosen because it matches the execution environment, not because it is the only way to access data.

Design Agents To Fail Clearly

An agent workflow is only reliable if it handles incomplete results honestly.

For CMC tool-driven workflows:

• When asset search returns no result, report that the asset could not be resolved and request clarification where necessary.
• When a tool fails or times out, retry once, then state which information remains unavailable.
• When a request is rate limited, report the limit rather than filling missing data with assumptions.
• When a task requires a different skill route, switch to the appropriate CMC workflow instead of forcing an unsuitable tool.

That behaviour matters for market reports and token research because confidence in an answer depends on knowing what data was actually retrieved.

Where Skills Marketplace Fits In The CMC Developer Stack

CoinMarketCap Skills Marketplace is the workflow layer for agents building on CMC data.

The value is not only access to crypto prices. It is the ability to route a task through the right CMC execution model:

A market-report agent, a token-research assistant, a DEX-analysis workflow and a production application should not all be built through the same improvised request pattern.

Skills Marketplace gives each of those tasks a clearer path through CoinMarketCap data, reducing unnecessary reasoning and helping developers build repeatable crypto-agent workflows around CMC.