API v2 is in preview. Endpoints and schemas may change before general availability.
status/result response envelope, Bearer
token authentication, and the window/from/to time convention — and adds a new layer of
curated, research-grade indicators: the metrics CryptoQuant’s research team actually uses
to call market cycles.
Endpoint structure
v2 metrics are organized by domain:
https://api.cryptoquant.com/v2/
├── indicator/ // research-grade indicators
│ ├── demand-monitor/ // apparent demand, ETF demand
│ ├── valuation/ // MVRV Z-score
│ ├── price-models/ // trader realized price bands, Metcalfe price
│ ├── pnl/ // realized P&L, unrealized profit margin, P&L index
│ └── risk/ // Bull Score Index, bull-bear indicator
├── onchain/ // raw on-chain data (OP_RETURN count, ...)
└── cohort/ // cohort-level data (Satoshi-era miners, ...)
Every metric ships with an interpretation guide
Each v2 metric is documented for decision-making, not just data access. Every endpoint
page (e.g. 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) 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 | Same |
