API v2 is in beta — new endpoints and indicators are added continuously.
See the Changelog for what’s new.
status/result response envelope, Bearer
token authentication, and the window/from/to time convention — and adds three layers:
curated, research-grade indicators (the metrics CryptoQuant’s research team actually uses
to call market cycles), market data (exchange-level and aggregated spot & derivatives
time-series), and on-chain data (network activity, exchange flows, and supply — one path
per metric, with the asset as a query parameter).
How v2 relates to v1
v2 does not replace v1 — it adds a new layer on top of it. v2 has three families of endpoints: community indicators (curated research-grade signals), market data (normalized exchange & aggregated time-series), and on-chain data (the v1 network, flow, and supply metrics, re-cut so one path serves every asset).Endpoint structure
v2 has three families of endpoints:- Community indicators — browse them in the v2 Metric Catalog.
- Market data — see the Market Data Overview for the
origin/instrument/metricstructure, symbol conventions, and discovery endpoints. - On-chain data — see the On-chain Data Overview for the asset-class axis, per-class windows, and the v1 → v2 path mapping.
How much history v2 keeps
The same rule applies to every v2 family — market data, on-chain data, and community indicators — so you can rely on it when choosing awindow:
A
from older than the window keeps returns 400 with a message that names the retention
window and suggests window=day. Use day for long-range history and the finer windows for
recent detail.
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) 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