Skip to main content

​
Getting started

​
What is the CryptoQuant API?

The CryptoQuant API provides on-chain data, market data, and aggregate blockchain statistics through simple REST endpoints. It covers 245+ metrics across Bitcoin, Ethereum, XRP, TRX, stablecoins, ERC20 tokens, and other altcoins — including exchange flows, MVRV, SOPR, funding rates, and miner activity. See the Metric Catalog for the full list.

​
How do I get an API key?

API access is available on CryptoQuant pricing plans. Once you subscribe, your access token appears in your account settings. See the Quickstart to make your first call.

​
What are the base URLs?

The stable v1 API is at https://api.cryptoquant.com/v1/ and the beta v2 API is at https://api.cryptoquant.com/v2/.

​
Authentication

​
How do I authenticate API requests?

Send your access token in the Authorization header as Bearer {access_token}, or pass it as an api_key query parameter. The header method is recommended because URLs are often logged by proxies and can leak keys. See Authentication.

​
Why am I getting a 401 or 403 error?

A 401 unauthorized means your credentials are missing or wrong. A 403 forbidden means your plan does not include access to that endpoint. See Status & Error Codes.

​
Rate limits & errors

​
What are the API rate limits?

Rate limits are set per pricing plan. If you exceed your limit you receive a 429 too_many_requests response — back off and retry after a short delay. Using an API key with the MCP server gives you a dedicated rate limit instead of the shared keyless pool.

​
What do the response status codes mean?

200 is success, 4xx is a client/credential error, and 5xx is a server-side problem. Every response also carries a status object with a code and a human-readable message. The full table is in Status & Error Codes.

​
Data & response format

​
What does an API response look like?

Every response wraps data in a status / result envelope:

​
What time intervals (windows) are available?

The window parameter controls aggregation: block, min (market data only), hour, and day. Each metric supports different windows. Use from and to (format YYYYMMDDTHHMMSS) to bound the range. See Time Convention.

​
When is end-of-day data final?

End-of-day exchange, miner, and inter-entity flow data starts serving from UTC 00:00 and may take up to an hour to finalize as blocks confirm. The safe time to query a complete day is UTC 01:00. Top-10 data returns null until block confirmation completes.

​
Which assets and metrics are supported?

Bitcoin, Ethereum, XRP, TRX, BNB, SOL, DOGE, ADA, AVAX, SUI, stablecoins, and ERC20 tokens. Coverage varies by asset — browse the Metric Catalog or the machine-readable /catalog/catalog.json.

​
AI agents & MCP

​
Can AI agents use the CryptoQuant API?

Yes. CryptoQuant hosts an MCP (Model Context Protocol) server at https://mcp.cryptoquant.com/mcp that lets Claude, Cursor, and other MCP clients query on-chain data in natural language. See MCP Server and the For AI Agents map.

​
How do I get the docs in a machine-readable format?

Append .md to any page URL for raw Markdown, use /llms.txt and /llms-full.txt for the docs index and full content, and use /catalog/catalog.json plus the OpenAPI specs for endpoint definitions. Details on the For AI Agents page.

​
What does each metric actually mean?

See the On-Chain Metrics Glossary for quick definitions, or the Data Guide for full formulas and interpretation of every metric.