> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cryptoquant.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API v2 Overview

> What's new in CryptoQuant API v2 — community indicators and market data endpoints in one curated layer.

<Note>
  API v2 is in beta — new endpoints and indicators are added continuously.
  See the [Changelog](/guides/changelog) for what's new.
</Note>

API v2 keeps everything that works in v1 — the `status`/`result` response envelope, Bearer
token authentication, and the `window`/`from`/`to` time convention — and adds two new layers:
**curated, research-grade indicators** (the metrics CryptoQuant's research team actually uses
to call market cycles) and **market data** (exchange-level and aggregated spot & derivatives
time-series).

## How v2 relates to v1

v2 does not replace v1 — it adds a new layer on top of it. v2 has two families of
endpoints: **community indicators** (curated research-grade signals) and **market data**
(normalized exchange & aggregated time-series). v1 stays the right choice for building your
own models from raw on-chain data.

|                          | API v1                                                                      | API v2                                                                                                                                                             |
| ------------------------ | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Scope**                | Raw on-chain, market, and flow data across BTC/ETH/XRP/TRX/Stablecoin/ERC20 | Curated research-grade indicators (demand, valuation, price models, P\&L, risk) **and** normalized market data (OHLCV, trade, funding, open interest, liquidation) |
| **Path scheme**          | `/v1/{asset}/{category}/{metric}`                                           | `/v2/community/{metric}`<br />`/v2/market/{origin}/{instrument}/{metric}`                                                                                          |
| **Max rows per request** | `limit` up to 100,000                                                       | `limit` up to 10,000                                                                                                                                               |
| **Best for**             | Building your own models from raw on-chain data                             | Consuming battle-tested signals with documented thresholds, and normalized market time-series                                                                      |

## Endpoint structure

v2 has two families of endpoints:

```text theme={null}
https://api.cryptoquant.com/v2/

├── community/                        // curated research-grade indicators
│   ├── bitcoin-mvrv-z-score          //   valuation
│   ├── bitcoin-metcalfe-price        //   price models
│   ├── bitcoin-op-return-count       //   on-chain activity
│   └── ...                           //   demand, P&L, risk
│
└── market/{origin}/{instrument}/{metric}   // exchange & aggregated market data
    ├── exchange/spot/ohlcv           //   per-exchange prices
    ├── cq/swap/funding-rate          //   aggregated derivatives
    └── ...                           //   trade, open interest, liquidation
```

* **Community indicators** — browse them in the [v2 Metric Catalog](/v2/catalog).
* **Market data** — see the [Market Data Overview](/v2/market/overview) for the
  `origin`/`instrument`/`metric` structure, symbol conventions, and discovery endpoints.

## Every community metric ships with an interpretation guide

Each v2 community indicator is documented for decision-making, not just data access. Every
community endpoint page (e.g. [MVRV Z-score](/v2/community/bitcoin-mvrv-z-score)) includes,
right below the API reference:

* **What it measures** — the precise definition of the signal
* **How to interpret it** — what rising/falling values mean for market structure
* **Key thresholds** — the levels that have historically marked cycle tops and bottoms
* **How to use it** — which metrics to combine it with for high-conviction signals

This structure is intentional: AI agents reading these docs (or connecting through the
[MCP server](/guides/mcp-server)) get the full analytical context, not just numbers.

## What stays the same

| Convention        | v1                                           | v2   |
| ----------------- | -------------------------------------------- | ---- |
| Response envelope | `status` / `result`                          | Same |
| Authentication    | Bearer token or `api_key`                    | Same |
| Time parameters   | `window`, `from`, `to`                       | Same |
| Error codes       | [Status & Error Codes](/guides/status-codes) | Same |

## Deprecation

v1 remains fully supported. Any future deprecation will be announced in the
[changelog](/guides/changelog) well in advance.