Connect AI agents to live CoinMarketCap crypto data through six access paths: the free Keyless Public API, MCP, x402 pay-per-call, CMC CLI, Skills, and REST. Start with no key and no signup.
Last updated July 15, 2026 · Endpoints, limits and pricing verified against CoinMarketCap's official API documentation.
- Six ways to connect an agent to live CMC data: Keyless Public API, keyed REST, MCP, x402, CMC CLI, and Skills.
- Start free with no key or signup: the Keyless Public API serves supported REST endpoints from the
/public-apibase path. - Two no-key routes exist, but only Keyless REST is free; x402 is no-key yet pay-per-call at 0.01 USDC per request on Base.
- Standard MCP (
mcp.coinmarketcap.com/mcp, 12 tools) needs an API key and works with Claude Code, Cursor, Claude Desktop and Cline. - Resolve symbols to stable CoinMarketCap IDs via
/v1/cryptocurrency/map(Bitcoin = 1, Ethereum = 1027).
Build with an agent-native crypto data stack
CoinMarketCap gives developers multiple ways to connect AI agents to live crypto data. Markets move too quickly for static knowledge; agents need a live data layer for prices, rankings, market metrics, DEX data, narratives, news, technical signals, and repeatable research workflows.
Fast no-key REST prototypes on supported endpoints, no signup.
Live CMC tools for AI-agent and IDE workflows.
No-key, pay-per-call access for supported requests.
Terminal-native automation with stable output.
Reusable market-report, token-research, and API workflows.
Custom apps, dashboards, backends, and data pipelines.
Why AI agents need better crypto data
AI agents can summarize markets, compare tokens, build dashboards, research assets, and monitor narratives. The problem is that crypto data changes constantly.
Prices move minute by minute
An LLM can explain what Bitcoin is, but it cannot reliably answer what is happening in the market right now without live, structured data.
Liquidity shifts constantly
Liquidity moves across exchanges and DEX pools, and sentiment changes when macro data, exchange flows, liquidations, or major news hits.
Narratives rotate quickly
Sectors rotate fast between AI, RWA, DePIN, memes, Layer 2s, stablecoins, and new ecosystems. Static training data is not enough for crypto.
The fix: instead of scraping pages, guessing from stale context, or stitching together disconnected feeds, an agent can call CoinMarketCap directly through MCP, x402, CLI, Skills, REST, or the Keyless Public API depending on the workflow.
Machine-readable access summary
If you are an AI agent or automated client, this block lists every CoinMarketCap access path, base URL, auth model and cost. All values are verified against CoinMarketCap's official documentation. For the full LLM-friendly index, load https://pro.coinmarketcap.com/llms.txt.
Choose an access path
Different AI-agent workflows need different access paths, and CoinMarketCap supports more than one. The Keyless Public API is the fastest way in: no account, no key, no cost. Add a key or per-call payment only when a workflow needs more.
Tool and endpoint coverage differs by access path. Use the linked MCP, x402, CLI, Skills, REST, and Keyless docs for current availability and setup details.
Canonical machine index for LLMs and agents: https://pro.coinmarketcap.com/llms.txt
Connect an agent to CoinMarketCap
Copy/paste starters to test the main CoinMarketCap AI-agent access paths. Start with the keyless call, then add a key, MCP, or x402 as the workflow grows. The response shape is identical across keyless and keyed, so nothing needs a rewrite.
These are quick starts, not complete implementation guides. Use the linked spoke pages for production setup, authentication, payment handling, retries, schemas, and client-specific configuration.
1. Keyless REST quick test
Start here. The Keyless Public API is the fastest no-key, no-signup way to pull live data into an agent or prototype: copy, paste, run. Prefix any supported endpoint with /public-api. This requests current USD prices for Bitcoin (1) and Ethereum (1027).
2. Optional Python keyless test
A small no-key Python example with no external packages. Keep the full helper, backoff, quote parsing, and CSV export in the dedicated Keyless API Python guide.
3. Standard CoinMarketCap MCP
Use standard MCP when your MCP-compatible client should access CoinMarketCap through an API-key-based workflow: recurring agent workflows, IDE integrations, and internal research assistants. The same config works across Claude Code, Cursor, Claude Desktop, Cline and other MCP clients. Configure the server as type "http" (Streamable HTTP), never type "sse". Standard MCP also supports OAuth 2.0 (Authorization Code with PKCE) using an Authorization: Bearer token; if a request carries both a key and a token, the API key takes priority.
4. CoinMarketCap x402 MCP
Use x402 MCP when your client supports x402 payment handling and you want no-key, pay-per-call access. This route does not use a CoinMarketCap API key.
5. CMC CLI quickstart
Use CMC CLI when the workflow belongs in a terminal, automation script, or agent run that benefits from stable command output. Use explicit CoinMarketCap IDs when determinism matters, Bitcoin is ID 1.
Ready-made agent prompts
Use these prompts inside an agent that already has access to CoinMarketCap MCP, x402, CLI, Skills, REST, or Keyless Public API documentation.
Pay-per-call access, no subscription
x402 swaps the API key and monthly plan for per-request payment. There is no key to manage because the payment itself authenticates the call: an x402-aware client signs a small USDC payment on Base for each supported request and gets the data back. Good for agents and prototypes with occasional or unpredictable usage; it is not free.
When to use x402
- Experiments and hackathons
- Occasional agent calls and episodic research
- No-API-key MCP workflows (pay-per-call)
- Lightweight AI-agent prototypes
- Agent workflows that prefer per-call payment
x402 MCP setup
Point any MCP client with an x402-aware transport at the x402 MCP server. No API-key header; the client signs a USDC payment per call.
x402 MCP vs standard MCP
| Standard MCP Recurring agent workflows |
CoinMarketCap MCP API key |
| x402 MCP No API key, pay-per-call |
USDC payment through x402 |
How a call resolves
- First request returns HTTP 402 with payment details (USDC on Base)
- The x402 client signs a USDC authorization and retries
- Server verifies and returns the data; payment settles only on success
- Current price: $0.01 USDC per supported request, subject to change
x402 is no-API-key, not free. It replaces API-key authentication with payment for supported requests. x402 is not part of the MCP standard, so standard agents such as Claude Code, Cursor, Claude Desktop and Cline do not handle the 402 payment flow automatically; the x402 endpoints are for clients that implement x402 or for programmatic use. For production workloads with predictable scale, broader endpoint access, and account-managed usage, a standard CoinMarketCap API plan may be the better fit.
Live crypto data for AI tools
MCP lets AI agents discover and call CoinMarketCap tools inside compatible clients and IDEs, a strong fit for Claude and Claude Code, Cursor, Claude Desktop, Cline / Roo Code, ChatGPT-compatible MCP workflows where available, and other MCP-compatible environments.
A tool layer, not raw endpoints
The agent does not need to manually construct every REST endpoint. It discovers the available tools and calls the one that matches the user's request.
Register the hosted server with one command for terminal-based crypto intelligence inside an agentic coding workflow. Then verify: What tools do you have available?
Add the hosted server to your mcp.json. The same config works across Cursor, Claude Desktop, Cline, and any client that supports hosted MCP servers with custom headers. Set type "http", never "sse".
Use CoinMarketCap MCP in ChatGPT-compatible MCP workflows where supported. Exact setup depends on the client; use the standard endpoint and header only when your workflow supports hosted MCP servers and custom headers.
Terminal automation and pre-built workflows
CMC CLI: terminal-native automation
A shell-native way to work with CoinMarketCap data: repeatable commands, stable output, JSON, tables, CSV export, dry-run previews, and deterministic terminal behavior.
- Quick price checks and scripted market scans
- Terminal-based market reports and CSV exports
- Agent-driven terminal workflows and repeatable commands
Skills: pre-built crypto workflows
Reusable workflows built on top of CoinMarketCap data access. Instead of asking an agent to invent a process each time, a Skill gives it a workflow pattern: what to do first, what data to fetch, and which mistakes to avoid. Skills are served over the Skill Hub at mcp.coinmarketcap.com/skill-hub/stream (API key or OAuth), with a keyless, free Skill Hub Trial at mcp.coinmarketcap.com/skill-hub-trial/stream (IP rate-limited, whitelisted skills).
- Market reports, coin research, and DEX analysis
- MCP, x402, CLI, and REST API integration workflows
- Due-diligence and daily or weekly recaps
For agents in developer terminals, CLI can be easier than writing custom REST code for every first test. For production services, REST may still be better because application code usually needs stronger control over retries, storage, transformations, and response handling.
What agents can build with CoinMarketCap
CoinMarketCap data can support a wide range of agent workflows.
AI market analyst
Generate daily or weekly market reports using live prices, global metrics, movers, trending narratives, news, derivatives context, and macro-event awareness.
Token research agent
Research a token by combining identity resolution, price data, market cap, volume, metadata, holder context, technical indicators, market pairs, and recent news.
Crypto morning brief
A structured brief covering BTC, ETH, top movers, Fear & Greed, Altcoin Season, trending narratives, and major upcoming catalysts.
Portfolio-monitoring assistant
Monitor assets in a watchlist or portfolio, explain major price moves, and surface changes in market context.
DEX liquidity & risk monitor
Track token activity, liquidity, pair data, pools, holder distribution, and token security where available using DEX and on-chain surfaces.
Narrative tracker
Track sectors such as AI, RWA, DePIN, memes, Layer 2s, stablecoins, and new ecosystems against market performance, trending data, and news.
Market regime dashboard
Identify whether the market looks risk-on or risk-off using live prices, global metrics, Fear & Greed, Altcoin Season, derivatives context, and breadth.
Trading dashboard
Live prices, volume, market cap, market pairs, technical indicators, and market-wide metrics. Use REST when the backend needs storage and scheduled updates.
A market-intelligence layer, not just prices
Generic crypto APIs can provide price data. CoinMarketCap gives agents a broader crypto market-intelligence layer: live prices and listings, market-wide context (global metrics, the Fear and Greed Index, Altcoin Season, CMC indices, derivatives), DEX and on-chain data, and agent-native access through MCP, x402, CLI and Skills, so an agent can ground on live data across a whole workflow rather than a single lookup.
Live prices and market data
Latest quotes, listings, market cap, volume, exchange context, global metrics, and historical context where available by endpoint and plan.
Market-wide context
Global metrics, Fear & Greed, Altcoin Season, CMC indices, derivatives data, trending topics, news, and macro-event context.
DEX and on-chain intelligence
DEX tokens, pairs, platforms, liquidity, pools, holders, transactions, security analysis, and OHLCV data where supported.
Agent-native access paths
Connect agents through MCP, pay per request through x402, automate terminal workflows through CMC CLI, and reuse Skills, not only a REST API.
Reusable workflows
Skills help agents produce consistent outputs, market reports, token research, CLI, MCP, x402, and API integration, instead of improvising each time.
Developer trust signals
Public API docs, AI Agent Hub, MCP, x402, CLI, and Skills docs, setup guides, pricing, status, changelog, and methodology resources.
Keyless REST across your AI tools
There is one genuinely free, no-key path: the Keyless Public API over REST at /public-api, no account, no key, no payment. Any agent, script or IDE assistant that can make an HTTP request can use it. Standard MCP uses an API key; the no-API-key x402 MCP route is pay-per-call. Response shapes are identical across all three, so there is nothing to rewrite as you move between them.
Keyless REST (free, no key)
The genuinely keyless path. Prefix any supported endpoint with /public-api: no account, no key, no headers, no payment. Same JSON envelope as the keyed Pro API.
Same shape, add a key later
For higher limits or the full Pro and DEX catalog, drop the /public-api prefix and add your key as the X-CMC_PRO_API_KEY header. The response is identical.
Three access models, one hub. Keyless REST is free (no key, no pay). Standard MCP and the keyed REST/CLI setups use a free or paid API key for higher limits, the full Pro and DEX catalog, and account-managed usage. The no-API-key x402 MCP route is pay-per-call in USDC. Response shapes are identical, so there is nothing to rewrite as you move between them.
CoinMarketCap vs generic crypto APIs for agents
Generic crypto APIs usually start with price data. That is useful, but AI agents need more than a price feed.
The stronger point is not that every developer must use the same path; it is that CoinMarketCap gives AI-agent builders more ways to connect the right workflow to the right data surface.
Developer trust and resources
AI-agent builders need data sources, docs, setup paths, and production signals. Use these CoinMarketCap resources when moving from prototype to production.
Build & Access
IDE Setup & Docs
Where public uptime, latency, or benchmark data is unavailable, performance claims stay tied to public status, docs, endpoint behavior, and plan-specific limits.
Frequently asked questions
What builders ask most before connecting an agent to CoinMarketCap.
Build AI agents with live CoinMarketCap data
Start with the free Keyless Public API, add a key for higher limits, or connect agents through MCP, x402, CLI and Skills.


