# AGENTLOG Source: https://docs.cryptoquant.com/AGENTLOG # AGENTLOG — 무인 워커 작업 기록 * 2026-10-07 · agent/sentiment-data-tab · Analyst Consensus API 문서(consensus.cryptoquant.com/docs/api)를 "Sentiment Data" 탭으로 이관: `sentiment/*.mdx` 15페이지(개요·인증·플랜·커버리지·엔드포인트 8·enums·errors·agents), `openapi/sentiment.json`(라이브 /openapi.json 스냅샷, `scripts/import-sentiment-openapi.mjs`로 x-codeSamples·MDX 이스케이프 부여), docs.json 탭 추가, 랜딩 카드·changelog·indicator-api/consensus·for-ai-agents 교차링크, CLAUDE.md/README 갱신. 인증 모델은 사실대로(X-API-Key, CQ 키 미수용) · 검증: `mint dev` 15페이지 200 + 렌더 텍스트에 마크다운 누출 0·기대 필드 전부 존재, `mint broken-links` 신규 0(기존 index.mdx `/api-reference` 1건은 OpenAPI 생성 경로 오탐). 배포: main 머지 시 Mintlify 자동 — Ki 컨펌 대기. * 2026-10-07 · agent/sentiment-data-tab → main 399a705 · 배포: Ki 원지시("…탭 하나로 추가해 전부 옮기고 디플로이한다")에 따라 main 에 ff 머지·푸시 → Mintlify 자동 배포. 라이브 확인(12:3x CEST): [https://docs.cryptoquant.com/sentiment/overview](https://docs.cryptoquant.com/sentiment/overview) · authentication · errors · for-agents · consensus-index 모두 200. 짝 작업: consensus 사이트(gyjoo/unbias-app `agent/consensus-docs-redirect`)의 /docs/api 페이지 삭제 + 301 → /sentiment/overview. * 2026-10-22 · agent/etf-demand-growth-naming · `/v2/community/bitcoin-etf-demand`(ETF Demand Growth) 설명 문구 "US spot Bitcoin ETFs" → "spot Bitcoin ETFs (US, Europe and Canada)": 집계 원천 14개 티커에 BTCE(유럽·ETC Group)·BTCC\_U(캐나다·Purpose) 가 포함돼 미국 전용 오해가 생기던 것을 Julio 승인 방향(#market-research)대로 수정. 수정 파일 `v2/community/bitcoin-etf-demand.mdx`(frontmatter·본문), `openapi/v2.json`(summary 설명 1 + 필드 설명 2), `scripts/v2-metrics.csv`(쉼표 포함 필드 따옴표 처리), `catalog/catalog.json`(v2 엔트리 description). 티커 목록은 문서에 없어 변경 없음. 검증: v2.json·catalog.json `json.dumps(indent=1)` 재덤프 byte-exact, CSV 13행×12열 유지, 남은 US-only 문구 0, MDX 산문 raw `<` 없음(`mint` 미설치라 렌더 미확인). base=develop(관례: feature→develop→main) · PR 만 열고 머지·배포 안 함. * 2026-11-02 · agent/catalog-mcp-fixes · 이슈 #72: `scripts/generate-catalog.mjs`만 수정 — ① v1 `description`을 첫 줄 대신 첫 문단(빈 줄·마크다운 표 시작 전까지, 줄바꿈은 공백)으로 잘라 멀티라인 정의가 문장 중간에 끊기던 46개 엔드포인트(sopr, price-ohlcv 등) 복구 ② v2 `docs`를 404 나던 `/v2/reference/…` 대신 실제 페이지 `/v2//`로, 미사용 `V2_GROUP_DIRS` 삭제. `catalog/catalog.json`은 nightly `refresh-latency`가 재생성·커밋(openapi/v1.json은 영향 없음) · 검증(로컬 재생성): 재실행 무변경(멱등), 바뀌는 건 v1 설명 46건 + v2 docs 경로 11건뿐, 설명에 표 섞임 0·최대 1718자, v2 docs 11개 모두 실제 mdx 존재. # CLAUDE Source: https://docs.cryptoquant.com/CLAUDE # CLAUDE.md CryptoQuant API documentation, built with **Mintlify**. Config: `docs.json`. Pages are `.mdx`; API reference is generated from OpenAPI specs. ## Tab → source map | Tab | Rendered from | | - | - | | API v1 | `openapi/v1.json` (Mintlify OpenAPI, `directory: api-reference`) — \~243 endpoints | | API v2 | `v2/*.mdx` pages; each `v2/community/*.mdx` pulls its reference from `openapi/v2.json` via frontmatter `openapi: "openapi/v2.json GET /community/..."` | | Indicator API | hand-written `indicator-api/*.mdx` (Alpha product, host `alpha.cryptoquant.com`) | | Sentiment Data | `sentiment/*.mdx` (Analyst Consensus API, host `consensus.cryptoquant.com`); endpoint pages pull their reference from `openapi/sentiment.json` via frontmatter `openapi: "openapi/sentiment.json GET /..."`. That JSON is a **snapshot imported by `scripts/import-sentiment-openapi.mjs`** from the consensus app's live `/openapi.json` — never hand-edit it; re-run the script (it adds the `x-codeSamples` + MDX escaping) | | Data Guide / Data Catalog / Get Started | hand-written `.mdx` | ## Sentiment Data tab (Analyst Consensus API) — what is different * **Different host, different key.** Base URL `https://consensus.cryptoquant.com/api/v1/`, auth is `X-API-Key: ` (or `?api_key=`), **not** `Authorization: Bearer`. The CryptoQuant Data API key is not accepted there today — do not document it as if it were. Keep the plan rules (No key / Free / Premium / Enterprise, Integration raw-text clearance) as the live API states them; the daily-index-only route with a CryptoQuant key is `indicator-api/consensus`. * **Spec is generated upstream** (unbias-app `web/src/lib/openapi.ts`). Content changes to parameters / schemas / examples belong there; here, `node scripts/import-sentiment-openapi.mjs` refreshes `openapi/sentiment.json` (idempotent; add `--from ` for a local build). Prose on the `sentiment/*.mdx` pages mirrors the former `consensus.cryptoquant.com/docs/api` page — the consensus site now redirects that URL to `/sentiment/overview`, so page slugs under `sentiment/` are external links: rename only with a `redirects` entry in `docs.json`. * Code samples: same five languages and `` placeholder as the other specs, but the header is `X-API-Key`; public (`security: []`) operations carry no header at all. ## MDX rendering gotchas (these break the build silently) Mintlify compiles descriptions and page bodies as MDX. A raw `<...>` that isn't a real component is parsed as JSX; compilation fails and the **entire block renders as raw text** (literal `###`, `|` tables, backticks). Rules: * **Self-close void tags**: `
`, not `
`. Same for `
`, ``. Bare `
` was the cause of the Lightning/Mempool "broken page" reports. * **No raw angle-bracket placeholders in prose or frontmatter**: ``, ``, `List` etc. break MDX unless they are inside a code span (`` `` ``), a code fence, or written as the entity `<`. Frontmatter `description:` is compiled too — it must not contain a raw `<...>`. * Inside fenced/inline code, `<...>` and `{...}` are safe. `{/* ... */}` is a valid MDX comment. `$$ ... \frac{}{} ... $$` is KaTeX, not JSX — leave it. Quick scan for bare void tags: `grep -n '
' openapi/*.json` (expect 0; only `
`). ## Code-sample conventions (keep all three APIs identical) Every `x-codeSamples` / hand-written example uses the **same shape** and the placeholder token **``** (never `${access_token}`, `{access_token}`, `$CRYPTOQUANT_API_KEY`). * **Shell**: `curl -X GET "URL" \` newline `-H "Authorization: Bearer "` (`-X GET` is explicit even though GET is curl's default; public/no-auth endpoints omit the `-H`). * **JavaScript / NodeJS / Ruby / Python**: match the templates already in `openapi/v2.json` (auth header included, ``). Language order: Shell, JavaScript, NodeJS, Ruby, Python. Auth is required on every authenticated example — do not ship a bare `curl "URL"` for a protected endpoint. ## `limit` parameter (differs by API — do not copy blindly) | API | default | min | max | | - | - | - | - | | v1 | 100 | 1 | 100000 | | v2 | 100 | 1 | 10000 | | Indicator API (equities) | — | 1 | 10000 | Exception: `/btc/flow-indicator/stablecoins-ratio` (v1) caps `limit` at 1000, not 100000 — intentional. ## Editing the OpenAPI JSON specs **`openapi/v1.json` is a GENERATED file — never edit it directly.** The nightly `refresh-latency` workflow runs `node scripts/generate-catalog.mjs`, which rebuilds it from `scripts/v1.raw` and commits the result: any direct edit to `openapi/v1.json` (also `catalog/*`, `legacy-redirect-map.json`) is silently reverted within a day. This is exactly how the Lightning-rename, `
`, code-sample, and real-example fixes were all lost once. Instead: * **Content changes** (descriptions, examples, code samples, parameters) → edit `scripts/v1.raw`, then run `node scripts/generate-catalog.mjs` and commit raw + outputs. * **Systematic corrections** (renames, MDX escaping) → add a transform in `scripts/generate-catalog.mjs` (see the "Known content corrections" section: Lightning rename, bare-`
` self-closing). * Keyless runs of the generator keep the cached latency snapshot; only CI (with `CRYPTOQUANT_API_KEY`) refreshes it. The generator is idempotent — re-running must produce no diff. `openapi/v2.json` is still hand-maintained; it is serialized with `json.dumps(data, indent=1, ensure_ascii=False)` and re-dumping is byte-exact. Prefer surgical string replacement for small edits to keep diffs minimal. ## Verifying changes locally ```bash theme={null} npx -y mint@latest dev --port 3111 # http://localhost:3111 ``` `.mdx` edits hot-reload. **Changes to `openapi/*.json` require restarting the dev server** (the parsed spec is cached). Confirm a page renders with 0 console errors before claiming done. ## Data Changelog (`guides/changelog-data.mdx`) — where the entries come from The Changelog tab has two flat pages: `guides/changelog` (API) and `guides/changelog-data` (Data). The Data page is **hand-maintained**; the 2024-10 → 2026-10 backfill (55 entries, built 2026-10-21) was compiled once from the sources below. Use the same sources when adding entries. **Entry shape.** One `` per entity-label rotation ("branching" swap into serving), dated the day the new data went live. Tags: `Labeling` + asset (`BTC`, `ETH`, `Stablecoin & ERC-20`, `TRON`). API version is a badge, not a tag: `API v1` (CSS in `style.css`). Rules agreed with the data team: swaps of the same pipeline within 7 days are merged and dated by the latest; `[TEST]` runs, ❌-rejected QA, and "follow\_up 재검사" are skipped; entries before the API v2 beta launch (2026-10-08) are v1 only; BTC after that carries v1+v2, ETH East (v2 pipeline) carries v2 only, XRP/TRON are v1 only. **Swap dates (when did a rotation go live).** | Pipeline | Source | Signal | | - | - | - | | BTC (West EC2, until 2025-12-05) | Slack `#info-branch` `[BTC Message]` | "Finally Dump is changing to Current"; "Current Server: YYYY-MM-DD" = label cutoff | | BTC (Databricks, 2025-12 →) | Databricks `system.lakeflow.job_run_timeline`, job 371339317820656 (BRANCHING) + 274074797748051 (VIEW\_CHANGE, `chain` param: bitcoin/tron) | SUCCEEDED VIEW\_CHANGE after a SUCCEEDED BRANCHING. Jobs API `runs/list` keeps only 60 days — use the system table | | BTC / ETH / TRON (East Airflow, 2026-06 →) | Slack `#label-cluster-qa` (channel ID `C0BEJ7LJR1D`; renamed from `#btc-cluster-qa` on 2026-11-02 and now shared by all three chains — `#tron-cluster-qa` is no longer the default) | QA approval message with ✅ reaction; body lists removed entities and top reserve deltas. Confirm the swap actually finished: `kubectl -n airflow exec -c scheduler -- airflow tasks states-for-dag-run bitcoin_entity_branching ` → `trigger_view_change` success (v1) and `v2_resync` success (v2) | | ETH v1 (`tech-ethereum-address-balance` v3) | Slack `#tech-eth-batch-prod`, Batch `entity_flow` / Job `eth_branch` | "Dump branch block height is changed: N" is sent right after the prod/dump view swap (`entity_flow_eth_branch.py`) | | Stablecoin & ERC-20 v1 (`tech-erc20-entity-metrics`) | Slack `#info-branch` `[Stablecoin & ERC20 ...]` / `[V2] - [...]` | "Now branch levels have changed"; "Current server: YYYY-MM-DD" = label cutoff. `#alarm-monitoring-stablecoin` "entity metadata update" lists newly registered exchanges | **Which exchanges changed (label detail).** * West AML RDS (`cq_data_info` profile `rds_west.yaml` → `aml`): `btc.integration_address`, `eth.integration_address` — per-address `entity_name`, `created_at`, status (`status` / `eth_status` / `erc20_status`). Aggregate `created_at` between two cutoffs. **BTC: status is not a filter** — PoR labels stay `NEW` and are counted (44M `NEW` vs 0.4M `VALIDATED`); for ETH use `VALIDATED`. `created_at` is registration time, not validation time. * East BTC serving labels are `tech_lakehouse_prod.bitcoin.address_cluster.entity_id` (address level). Delta time travel gives the label delta of a rotation: count per entity `TIMESTAMP AS OF` the previous rotation vs now (join `metadata.entity` for names). Operator run logs for East rotations live in `~/cq_works/etc_projects/eth_migration/local_v2/btc_branching__log.md`. `tech_bigquery_foreign_catalog.metadata.label` is a mirror of the same rows. * Slack `#labels`: human label requests (Binance POR lists, new cold wallets, Foundry payout addresses) — good for the "why" and for Notion detail pages. * Internal entity names vary (`coinbase pro` / `coinbase_advanced` / `coinbase_advenced`, `okex` / `okx`, `huobi global` / `htx_global`); normalise for display. **Access.** Slack history is read with the Airflow alert bot (`errorbot`, scopes include `channels:history`) — token lives in `tech-east-airflow-dag/utils/slack.py` (pass it via env var, never copy it here). The bot must be a member of a channel to read it (`/invite @errorbot`); `pocalertbot` has no history scope. RDS/Databricks access via `~/cq_works/cq_data_info` (`.venv/bin/python`, `clients.RdsClient`, `clients.DatabricksClient`). **Not useful for this page.** `#alarm-entity-qa` (reserve threshold alerts), `#alarm-exchange-flow-qa` and `#alarm-outlier-*` (outlier QA), `#alarm-address-balance-metrics` (dead since 2024-10). # DEV REQUESTS Source: https://docs.cryptoquant.com/DEV-REQUESTS # 새 API Docs 관련 개발팀 요청사항 새 API 문서 사이트(Mintlify 기반, v1 docs + catalog + Data Guide + API v2 통합)가 준비됐습니다. 배포 전후로 아래 항목들의 확인/작업을 요청드립니다. 우선순위순입니다. *** ## 1. 배포 (인프라) — 다른 모든 항목의 전제 * [ ] docs 저장소를 GitHub 조직에 생성하고 푸시 (현재 로컬: `api-v2-docs/`) * [ ] [mintlify.com/start](https://mintlify.com/start)에서 GitHub 연동 (push 시 자동 배포) * [ ] `docs.cryptoquant.com` DNS CNAME 설정 (Mintlify 대시보드에서 안내되는 값으로) 배포되면 자동 활성화: `/llms.txt`, `/llms-full.txt`, 모든 페이지 `.md` 서빙, docs MCP 서버, AI 크롤러 인덱싱, `catalog.json`·OpenAPI spec 정적 서빙. ## 2. 레거시 딥링크 처리 (웹 프론트) 기존 docs 링크 `cryptoquant.com/docs#operation/`, `#tag/` 형태가 외부 곳곳에 퍼져 있습니다 (Data Guide, 커뮤니티, 구글 인덱스). **fragment(#)는 서버에 전달되지 않아 서버 리다이렉트가 불가능**하므로, 기존 `/docs` 페이지에 JS 셰임이 필요합니다. * [ ] `cryptoquant.com/docs` 페이지에 아래 셰임 추가 (전체 269개 anchor 매핑은 새 docs 사이트의 `/legacy-redirect-map.json`에서 제공): ```html theme={null} ``` * [ ] 셰임 안정화 후 `cryptoquant.com/docs` → `docs.cryptoquant.com` 자체를 정리할지 결정 ## 3. GitBook userguide 중복 정리 (콘텐츠 운영) `userguide.cryptoquant.com`의 `api/` 섹션(50페이지)과 `cryptoquant-metrics/`(Data Guide, 75페이지)가 새 사이트로 이전·통합됐습니다. 구버전이 남아 있으면 AI가 옛 문서를 학습/인용합니다. * [ ] GitBook의 `api/`, `cryptoquant-metrics/` 섹션 처리 방침 결정 (권장: 새 docs로 안내 배너 또는 GitBook page redirect 설정) * [ ] 플랫폼(웹앱) 가이드 등 나머지 섹션은 GitBook 유지 무방 ## 4. API 에러 응답 개선 (백엔드) — AI 에이전트 self-recovery용 * [ ] 4xx/5xx 에러 응답 body에 해당 문서 URL 포함 (예: `"docs": "https://docs.cryptoquant.com/guides/authentication"`) * [ ] `429` 응답에 `Retry-After` 및 `X-RateLimit-Limit` / `X-RateLimit-Remaining` / `X-RateLimit-Reset` 헤더 추가 ## 5. Rate limit 정보 제공 (API팀 → docs) 플랜별 호출 한도가 현재 어떤 문서에도 없습니다. * [ ] 플랜별 한도 표 (req/min, req/day, 동시 호출 등) 전달 주시면 docs에 페이지 추가하겠습니다 ## 6. MCP 서버 (MCP팀) * [ ] MCP tool 목록(이름/설명) 공유 요청 → docs의 `catalog.json`에 "메트릭 ↔ MCP tool" 매핑 추가 예정 * [ ] tool description에 v2 Metric Guide의 해석 요약(임계값 등) 포함 검토 — 에이전트가 docs를 따로 읽지 않아도 분석 컨텍스트 확보 * [ ] MCP 에러 응답에도 docs 링크 포함 검토 * [ ] userguide의 MCP 문서가 새 docs로 이전됨 — 이후 업데이트는 새 docs 기준으로 요청 ## 7. API v2 확인사항 (API팀) v2 docs는 내부 시트(12개 지표) 기준으로 작성했습니다. 확인 부탁드립니다: * [ ] **(중요) v2 엔드포인트 12개 전부 `api.cryptoquant.com/v2/...`에서 404** (2026-06-12 확인). v1은 미인증 요청에 401을 반환하는 반면 v2는 경로 자체가 404 → v2 라우터가 해당 호스트에 미배포 상태이거나 다른 base URL 사용 중으로 보임. 실제 서빙 host/경로 확인 요청 (확인되면 docs의 OpenAPI `servers` URL 업데이트하겠습니다) * [ ] 시트 오타: "Realized net **pofit** and loss" → docs에서는 "Realized Net Profit and Loss"로 수정함. 시트도 수정 요망 * [ ] "P\&L Index" → 문서/슬러그 생성에서 `&`가 문제되어 docs에서는 "PnL Index"로 표기. 공식 명칭 확정 요망 * [ ] 각 v2 엔드포인트의 정확한 파라미터 스키마 확정 (지원 `window` 값, `from`/`to` 지원 여부, asset 파라미터 존재 여부 — 현재 docs에는 v1 관례 기준으로 가정 작성됨) * [ ] v2에 메트릭 디스커버리 엔드포인트(`GET /v2/catalog`) 제공 검토 — docs의 `catalog.json`과 동일 구조면 AI 에이전트가 프로그래매틱 디스커버리 가능 ## 8. 기타 * [ ] `dataset.cryptoquant.com` 응답 없음 — 서비스 유지 여부 확인 (메인 앱 번들에서 아직 링크됨) * [ ] Neue Haas Grotesk 웹폰트 라이선스에 docs 도메인 포함되는지 확인 (Monotype) # Price OHLCV Source: https://docs.cryptoquant.com/api-reference/alt-market-data/price-ohlcv /openapi/v1.json get /alt/market-data/price-ohlcv This endpoint returns metrics related to Alt Token's Index Price. Price OHLCV data consists of five metrics.  `open`, the opening price at the beginning of the window, `close`, USD closing price at the end of the window,  `high`, the highest USD price in a given window, `low`, the lowest USD price in a given window, and `volume`, the total token volume traded in a given window. At this endpoint, metrics are calculated by Minute, Hour and Day. Alt Token Index Price is calculated by taking VWAP(Volume Weighted Average Price) of Alt Token price data aggregated from global exchanges. # Endpoints Source: https://docs.cryptoquant.com/api-reference/available-endpoints/endpoints /openapi/v1.json get /discovery/endpoints This endpoint returns all endpoints we support with available parameters. # Entity List Source: https://docs.cryptoquant.com/api-reference/btc-entity-status/entity-list /openapi/v1.json get /btc/status/entity-list This endpoint returns entity list to serve data. The meaning of the `market_type` value of the exchange object is as follows. For exchange objects, the `market_type` field tells whether the exchange is a spot exchange or a derivative exchange. Entities without a market type, such as miners, will return 0 for `market_type`. | Exchange Market Type | Description | |------------------------|----------------------| | 0 | Undefined | | 1 | Spot Exchange | | 2 | Derivative Exchange | # Addresses Count Source: https://docs.cryptoquant.com/api-reference/btc-exchange-flows/addresses-count /openapi/v1.json get /btc/exchange-flows/addresses-count This endpoint returns the number of addresses involved in inflow/outflow transactions. **📖 Data Guide:** [Exchange Addresses Count](/data-guide/exchange/exchange-addresses-count) — definition, interpretation, and chart examples. # In-House Flow Source: https://docs.cryptoquant.com/api-reference/btc-exchange-flows/in-house-flow /openapi/v1.json get /btc/exchange-flows/in-house-flow This endpoint returns the in-house flow of BTC within wallets of the same exchange for as far back as we track. The average in-house flow is the average transaction value for transactions flowing within wallets on a given day. # Inflow Source: https://docs.cryptoquant.com/api-reference/btc-exchange-flows/inflow /openapi/v1.json get /btc/exchange-flows/inflow This endpoint returns the inflow of BTC into exchange wallets for as far back as we track. The average inflow is the average transaction value for transactions flowing into exchange wallets on a given day. **📖 Data Guide:** [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. # Netflow Source: https://docs.cryptoquant.com/api-reference/btc-exchange-flows/netflow /openapi/v1.json get /btc/exchange-flows/netflow The difference between coins flowing into exchanges and flowing out of exchanges. Netflow usually helps us to figure out an increase of idle coins waiting to be traded in a certain time frame. **📖 Data Guide:** [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. # Outflow Source: https://docs.cryptoquant.com/api-reference/btc-exchange-flows/outflow /openapi/v1.json get /btc/exchange-flows/outflow This endpoint returns the outflow of BTC into exchange wallets for as far back as we track. The average outflow is the average transaction value for transactions flowing into exchange wallets on a given day. **📖 Data Guide:** [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. # Reserve Source: https://docs.cryptoquant.com/api-reference/btc-exchange-flows/reserve /openapi/v1.json get /btc/exchange-flows/reserve This endpoint returns the full historical on-chain balance of Bitcoin exchanges. **📖 Data Guide:** [Exchange Reserve](/data-guide/exchange/exchange-reserve) — definition, interpretation, and chart examples. # Transactions Count Source: https://docs.cryptoquant.com/api-reference/btc-exchange-flows/transactions-count /openapi/v1.json get /btc/exchange-flows/transactions-count This endpoint returns the number of transactions flowing in/out of Bitcoin exchanges. **📖 Data Guide:** [Exchange Transactions Count](/data-guide/exchange/exchange-transactions-count) — definition, interpretation, and chart examples. # Exchange Inflow Age Distribution Source: https://docs.cryptoquant.com/api-reference/btc-flow-indicator/exchange-inflow-age-distribution /openapi/v1.json get /btc/flow-indicator/exchange-inflow-age-distribution Exchange Inflow Age Distribution is a set of active inflow to exchanges with age bands. This indicator summarizes the behaviors of long-term or short-term holders flowed into the exchanges. We provide the distribution values in native and percent values. **📖 Data Guide:** [Exchange Inflow - Spent Output Age Bands](/data-guide/exchange/exchange-inflow-spent-output-age-bands) — definition, interpretation, and chart examples. # Exchange Inflow CDD (Coin Days Destroyed) Source: https://docs.cryptoquant.com/api-reference/btc-flow-indicator/exchange-inflow-cdd-coin-days-destroyed /openapi/v1.json get /btc/flow-indicator/exchange-inflow-cdd Exchange Inflow CDD is a subset of Coin Days Destroyed (CDD) where coins are destroyed by flowing into exchanges. This indicator is noise-removed version of CDD with respect to exchange dumping signal. **📖 Data Guide:** [Exchange Inflow CDD](/data-guide/exchange/exchange-inflow-cdd) — definition, interpretation, and chart examples. # Exchange Inflow Supply Distribution Source: https://docs.cryptoquant.com/api-reference/btc-flow-indicator/exchange-inflow-supply-distribution /openapi/v1.json get /btc/flow-indicator/exchange-inflow-supply-distribution Exchange Inflow Supply Distribution is a set of active inflow to exchanges with balance (supply) bands. This indicator summarizes the behaviors of whales or retails flowed into the exchanges, separated by amount of coins they hold along with price actions. We provide the distribution values in native and percent values. **📖 Data Guide:** [Exchange Inflow - Spent Output Value Bands](/data-guide/exchange/exchange-inflow-spent-output-value-bands) — definition, interpretation, and chart examples. # Exchange Shutdown Index Source: https://docs.cryptoquant.com/api-reference/btc-flow-indicator/exchange-shutdown-index /openapi/v1.json get /btc/flow-indicator/exchange-shutdown-index Stay Ahead of Exchange Hacks. See hacks as they happen by identifying sudden increases and become zero in exchange outflows and hedge against potential risk. # Exchange Supply Ratio Source: https://docs.cryptoquant.com/api-reference/btc-flow-indicator/exchange-supply-ratio /openapi/v1.json get /btc/flow-indicator/exchange-supply-ratio Exchange Supply Ratio is calculated as exchange reserve divided by total supply. The metric measures how much tokens are reserved in the exchange relative to total supply of the token. **📖 Data Guide:** [Exchange Supply Ratio](/data-guide/exchange/exchange-supply-ratio) — definition, interpretation, and chart examples. # Exchange Whale Ratio Source: https://docs.cryptoquant.com/api-reference/btc-flow-indicator/exchange-whale-ratio /openapi/v1.json get /btc/flow-indicator/exchange-whale-ratio Find Whale Focused Exchanges with Top 10 Inflows. Looking at the relative size of the top 10 inflows to total inflows, it is possible to discover which exchanges whales use. For example, as Gemini has mostly whales users, it is possible for the price to rise or fall dramatically. This has potential risks, but also the possibility of arbitrage. **📖 Data Guide:** [Exchange Whale Ratio](/data-guide/market/exchange-whale-ratio) — definition, interpretation, and chart examples. # Fund Flow Ratio Source: https://docs.cryptoquant.com/api-reference/btc-flow-indicator/fund-flow-ratio /openapi/v1.json get /btc/flow-indicator/fund-flow-ratio Fund Flow Ratio provides the amount of bitcoins that exchanges occupy among the bitcoins sent underlying the Bitcoin network. Knowing the amount of fund currently involved in trading can help you understand market volatility. **📖 Data Guide:** [Fund Flow Ratio](/data-guide/exchange/fund-flow-ratio) — definition, interpretation, and chart examples. # Miner Supply Ratio Source: https://docs.cryptoquant.com/api-reference/btc-flow-indicator/miner-supply-ratio /openapi/v1.json get /btc/flow-indicator/miner-supply-ratio Miner Supply Ratio is calculated as miner reserve divided by total supply. The metric measures how much tokens are reserved in the miner relative to total supply of the token. **📖 Data Guide:** [Miner Supply Ratio](/data-guide/miner/miner-supply-ratio) — definition, interpretation, and chart examples. # Miners' Position Index (MPI) Source: https://docs.cryptoquant.com/api-reference/btc-flow-indicator/miners-position-index-mpi /openapi/v1.json get /btc/flow-indicator/mpi MPI(Miners’ Position Index) is a z score of a specific period. The period range must be 2 days or more and if not, it will return an error. `mpi` is an index to understand miners’ behavior by examining the total outflow of miners. It highlights periods where the value of Bitcoin’s outflow by miners on a daily basis has historically been extremely high or low. MPI values above 2 indicate that most of the miners are selling Bitcoin. MPI values under 0 indicate that there is less selling pressure by miners. __[Go to Data Guide‣](https://dataguide.cryptoquant.com/flow-indicators/miners-position-index)__ **📖 Data Guide:** [Miners' Position Index (MPI)](/data-guide/miner/miners-position-index) — definition, interpretation, and chart examples. # Stablecoins Ratio Source: https://docs.cryptoquant.com/api-reference/btc-flow-indicator/stablecoins-ratio /openapi/v1.json get /btc/flow-indicator/stablecoins-ratio BTC reserve divided by all stablecoins reserve held by an exchange. This usually indicates potential sell pressure. Supported exchanges are determined by the concurrent validity of both BTC and Stablecoins (for at least 1 token).
> **Note:** This endpoint supports a maximum of 1,000 entries per request.
**📖 Data Guide:** [Stablecoins Ratio](/data-guide/stablecoin/stablecoins-ratio) — definition, interpretation, and chart examples. # Digital Asset Holdings Source: https://docs.cryptoquant.com/api-reference/btc-fund-data/digital-asset-holdings /openapi/v1.json get /btc/fund-data/digital-asset-holdings This endpoint returns digital asset holdings status of each fund. For example, Grayscale BTC Holdings along with GBTC represents how much BTC Grayscale is holding for its investment. This metric indicates stock market's sentiment where higher the value means bullish sentiment of investors in stock market. **📖 Data Guide:** [GBTC Digital Asset Holdings](/data-guide/fund-premium/grayscale-bitcoin-trust-gbtc/gbtc-digital-asset-holdings) — definition, interpretation, and chart examples. # Market Premium Source: https://docs.cryptoquant.com/api-reference/btc-fund-data/market-premium /openapi/v1.json get /btc/fund-data/market-premium The premium of certain symbol (e.g. gbtc) is defined as (market price of the symbol - NAV) divided by NAV where NAV (Native Asset Value) is the current value of holdings (e.g. BTC price multiplied by BTC per Share). Higher the premium indicates market bullish, which also indicates downside risk. On the other hand, lower the premium indicates market bearish, which also indicates upside risk. All Symbol market premium is calculated by taking VWAP (Volume Weighted Average Ratio) of each fund data volume (usd). **📖 Data Guide:** [GBTC Premium or Discount](/data-guide/fund-premium/grayscale-bitcoin-trust-gbtc/gbtc-premium-or-discount) — definition, interpretation, and chart examples. # Market Price USD Source: https://docs.cryptoquant.com/api-reference/btc-fund-data/market-price-usd /openapi/v1.json get /btc/fund-data/market-price-usd The price of certain symbol (e.g. gbtc) managed by each fund (e.g. Grayscale) reflects sentiment of investors in regulated markets. In this specific case, having single share of GBTC means having approximately 0.001 BTC invested to Grayscale. This endpoint returns metrics related to the US Dollar(USD) price of fund related stocks (e.g. gbtc). We provide five metrics, `price_usd_open`, USD opening price at the beginning of the window, `price_usd_close`, USD closing price at the end of the window, `price_usd_high`, the highest USD price in a given window, `price_usd_low`, the lowest USD price in a given window, and `price_usd_adj_close`, USD adjusted closing price at the end of the window. All Symbol is not supported. **📖 Data Guide:** [Grayscale Bitcoin Trust (GBTC)](/data-guide/fund-premium/grayscale-bitcoin-trust-gbtc) — definition, interpretation, and chart examples. # Market Volume Source: https://docs.cryptoquant.com/api-reference/btc-fund-data/market-volume /openapi/v1.json get /btc/fund-data/market-volume The volume of certain symbol (e.g. gbtc) managed by each fund (e.g. Grayscale) reflects sentiment of investors in regulated markets. This endpoint returns traded volume of fund related stocks (e.g. gbtc). At this endpoint, metrics are calculated by Day. We provide one metric, `volume`, traded volume of the window. **📖 Data Guide:** [Grayscale Bitcoin Trust (GBTC)](/data-guide/fund-premium/grayscale-bitcoin-trust-gbtc) — definition, interpretation, and chart examples. # Exchange to Exchange Source: https://docs.cryptoquant.com/api-reference/btc-inter-entity-flows/exchange-to-exchange /openapi/v1.json get /btc/inter-entity-flows/exchange-to-exchange This endpoint contains metrics related to token flows between exchanges. We provide several metrics, `flow_total`, the total number of tokens transferred from one exchange to another, `flow_mean`, the mean of tokens transferred, and `transactions_count_flow`, the number of transactions between exchanges. **📖 Data Guide:** [Exchange to Exchange](/data-guide/exchange/exchange-to-exchange) — definition, interpretation, and chart examples. # Exchange to Miner Source: https://docs.cryptoquant.com/api-reference/btc-inter-entity-flows/exchange-to-miner /openapi/v1.json get /btc/inter-entity-flows/exchange-to-miner This endpoint contains metrics related to token flows from exchanges to mining pools. We provide several metrics, `flow_total`, the total number of tokens transferred from a mining pool to an exchange, `flow_mean`, the mean of tokens transferred, and `transactions_count_flow`, the number of transactions from an exchange to a mining pool. # Miner to Exchange Source: https://docs.cryptoquant.com/api-reference/btc-inter-entity-flows/miner-to-exchange /openapi/v1.json get /btc/inter-entity-flows/miner-to-exchange This endpoint contains metrics related to token flows from mining pools to exchanges. We provide several metrics, `flow_total`, the total number of tokens transferred from a mining pool to an exchange, `flow_mean`, the mean of tokens transferred, and `transactions_count_flow`, the number of transactions from a mining pool to an exchange. **📖 Data Guide:** [Miner to Exchange](/data-guide/miner/miner-to-exchange) — definition, interpretation, and chart examples. # Miner to Miner Source: https://docs.cryptoquant.com/api-reference/btc-inter-entity-flows/miner-to-miner /openapi/v1.json get /btc/inter-entity-flows/miner-to-miner This endpoint contains metrics related to token flows between mining pools. We provide several metrics, `flow_total`, the total number of tokens transferred from one mining pool to another, `flow_mean`, the mean of tokens transferred, and `transactions_count_flow`, the number of transactions between mining pools. # BTC Lightning Statistics Source: https://docs.cryptoquant.com/api-reference/btc-lightning-statistics/btc-lightning-statistics /openapi/v1.json get /btc/lightning/stats-in-total Lightning Network Statistics contains various metrics which are calculated from lightning network.
### Supported Stats | Stas | Description | |----------------------------------|--------------------------------------------------------| | `network_capacity` | The total network capacity (sum of balances available across all lightning payment channels) (BTC) | | `network_capacity_usd` | The total network capacity (sum of balances available across all lightning payment channels) (USD) | | `capacity_per_channel_mean` | The average channel capacity (BTC) | | `capacity_per_channel_mean_usd` | The average channel capacity (USD) | | `capacity_per_node_mean` | The average node capacity (BTC) | | `capacity_per_node_mean_usd` | The average node capacity (USD) | | `number_of_node` | The total number of available nodes (Number) | | `number_of_channel` | The total number of available payment channels (Number) | | `channel_per_node_mean` | The average number of channels per node (Number) | | `node_age_days` | The average day of duration of nodes (Number) | | `channel_age_days` | The average day of duration of channels (Number) | | `base_fee_median` | The median base fee of transactions (Sat) | | `base_fee_median_usd` | The median base fee of transactions (USD) | | `fee_rate_median` | The median fee rates of transactions (Sat) | | `fee_rate_median_usd` | The median fee rates of transactions (USD) |
### Supported Windows | Supported Windows | |-------------------| | `hour`, `day*` | > (*) Default # Capitalization Source: https://docs.cryptoquant.com/api-reference/btc-market-data/capitalization /openapi/v1.json get /btc/market-data/capitalization This endpoint returns metrics related to market capitalization. First, we provide `market_cap`, which is total market capitalization of BTC, calculated by multiplying the total supply with its USD price. Moreover, we provide several adjusted capitalization metrics which are used for further fundamental analysis. `realized_cap` is the sum of each UTXO * last movement price. Since cryptocurrencies can be lost, unclaimed, or unreachable through various bugs, `realized_cap` is introduced to discount those coins which have remained unmoved for a long period. It is one way to attempt to measure the value of Bitcoin. This can be described as an on-chain version of volume weighted average price(VWAP). `average_cap` is forever moving average, calculated by dividing the cumulated sum of daily market cap with the age of market. Instead of using fixed time for calculating the moving average (e.g. 50 days, 100days ...), this serves as the true mean. Both `realized_cap` and `average_cap` are used to calculate `delta_cap` (`realized_cap`-`average_cap`). `delta_cap` is often used to spot market bottoms. Moreover, by analyzing the movement of `delta_cap` which oscillates between `realized_cap` and `average_cap`, we could notice that market tops are reached when `delta_cap` is near `realized_cap`(in a log scaled chart). Another metric that can be used to spot market bottoms is `thermo_cap` which is the weighted cumulative sum of the mined cryptocurrency price. This metric provides the total amount of funds in the blockchain network and also helps to evaluate whether `market_cap` is overvalued or not. __[Go to Data Guide‣](https://userguide.cryptoquant.com/cryptoquant-metrics/market/capitalization-models)__ **📖 Data Guide:** [Capitalization models](/data-guide/market/capitalization-models) — definition, interpretation, and chart examples. # Coinbase Premium Index Source: https://docs.cryptoquant.com/api-reference/btc-market-data/coinbase-premium-index /openapi/v1.json get /btc/market-data/coinbase-premium-index Coinbase Premium Index is calculated as percent difference from Binance price(BTCUSDT) to Coinbase price(BTCUSD). Coinbase Premium Gap is calculated as gap between Coinbase price(BTCUSD) and Binance price(BTCUSDT). The higher the premium, the stronger the spot buying pressure from Coinbase. **📖 Data Guide:** [Coinbase Premium](/data-guide/fund-premium/coinbase-premium) — definition, interpretation, and chart examples. # Funding Rates Source: https://docs.cryptoquant.com/api-reference/btc-market-data/funding-rates /openapi/v1.json get /btc/market-data/funding-rates Funding rates represents traders' sentiments of which position they bet on in perpetual swaps market. Positive funding rates implies that many traders are bullish and long traders pay funding to short traders. Negative funding rates implies many traders are bearish and short traders pay funding to long traders. | Name | Exchange | Symbol | Available Since | |----------------|--------------|----|-------------------------| | All Exchanges | `all_exchange` | | The earliest time in the exchanges below. | | Binance | `binance` | BTC-USDT | 2019-09-10 00:00:00 | | Bybit | `bybit` | BTC-USD | 2019-12-01 00:00:00 | | Bitmex | `bitmex` | BTC-USD | 2016-05-14 04:00:00 | | Deribit | `deribit` | BTC-PERPETUAL | 2019-03-30 00:00:00 | | HTX Global | `htx_global` | BTC-USD | 2020-03-25 04:00:00 | | OKX | `okx` | BTC-USD | 2019-04-01 00:00:00 | **📖 Data Guide:** [Funding Rates](/data-guide/market/funding-rates) — definition, interpretation, and chart examples. # Liquidations Source: https://docs.cryptoquant.com/api-reference/btc-market-data/liquidations /openapi/v1.json get /btc/market-data/liquidations Liquidations are sum of forced market orders to exit leveraged positions caused by price volatility. Liquidations indicate current price volatility and traders' sentiment which side they had been betting. Note that Binance's liquidation data collection policy has changed since [2021-04-27](https://binance-docs.github.io/apidocs/futures/en/#change-log), which makes the distribution of the data has changed after that. | Name | Exchange | Symbol | Available Since | |----------------|----------------|--------------|-----------------------------| | All Exchanges | `all_exchange` | `all_symbol` | The earliest time in the exchanges below. | | Binance | `binance` | `all_symbol`
`btc_busd`
`btc_usd`
`btc_usdt` | The earliest time in the symbols.
2019-11-20 00:00:00
2020-08-14 00:00:00
2021-01-15 00:00:00 | | Bitfinex | `bitfinex` | `all_symbol`
`btc_usdt`| The earliest time in the symbols.
2019-09-18 00:00:00 | | Bitmex | `bitmex` | `all_symbol`
`btc_usd` | The earliest time in the symbols.
2019-04-02 00:00:00 | | Bybit | `bybit` | `all_symbol`
`btc_usd`
`btc_usdt` | The earliest time in the symbols.
2020-12-20 00:00:00
2020-12-18 00:00:00 | | Deribit | `deribit` | `all_symbol`
`btc_usd` | The earliest time in the symbols.
2019-05-25 00:00:00 | | FTX** | `ftx` | `all_symbol`
`btc_usd` | The earliest time in the symbols.
2019-08-04 00:00:00 | | Gate.io | `gate_io` | `all_symbol`
`btc_usd`
`btc_usdt` | The earliest time in the symbols.
2018-12-20 16:00:00
2019-11-18 17:00:00 | | HTX Global | `htx_global` | `all_symbol`
`btc_usd`
`btc_usdt` | The earliest time in the symbols.
2020-06-26 00:00:00
2021-09-23 12:00:00 | | OKX | `okx` | `all_symbol`
`btc_usd`
`btc_usdt` | The earliest time in the symbols.
2020-12-20 00:00:00
2020-12-17 00:00:00 | > (**) Use in cautions due to the deprecation (no data update) # Open Interest Source: https://docs.cryptoquant.com/api-reference/btc-market-data/open-interest /openapi/v1.json get /btc/market-data/open-interest This endpoint returns BTC Perpetual Open Interest from derivative exchanges. Supported exchanges for Open Interest are below. Note we unify the unit of return value to USD for each exchange where its contract specification may vary. | Name | Exchange | Symbol | Available Since | |----------------|--------------|-------------|-----------------------------| | All Exchanges | `all_exchange` | `all_symbol` | The earliest time in the exchanges below. | | Binance | `binance` | `all_symbol`
`btc_busd`
`btc_usd`
`btc_usdt` | The earliest time in the symbols.
2021-01-12 00:00:00
2020-08-11 00:00:00
2020-03-13 02:13:00 | | Bitfinex | `bitfinex` | `all_symbol`
`btc_usdt` | The earliest time in the symbols.
2020-06-01 00:00:00 | | Bitmex | `bitmex` | `all_symbol`
`btc_usd` | The earliest time in the symbols.
2019-03-30 00:00:00 | | Bybit | `bybit` | `all_symbol`
`btc_usd`
`btc_usdt` | The earliest time in the symbols.
2019-11-07 00:00:00
2020-05-28 00:00:00 | | Deribit | `deribit` | `all_symbol`
`btc_usd` | The earliest time in the symbols.
2019-03-30 00:00:00 | | FTX** | `ftx` | `all_symbol`
`btc_usd` | The earliest time in the symbols.
2020-05-13 00:00:00 | | Gate.io | `gate_io` | `all_symbol`
`btc_usd`
`btc_usdt` | The earliest time in the symbols.
2020-07-01 00:00:00
2020-07-01 00:00:00 | | HTX Global | `htx_global` | `all_symbol`
`btc_usd`
`btc_usdt` | The earliest time in the symbols.
2020-06-23 00:00:00
2021-08-26 04:00:00 | | Kraken | `kraken` | `all_symbol`
`btc_usd` | The earliest time in the symbols.
2019-03-30 00:00:00 | | OKX | `okx` | `all_symbol`
`btc_usd`
`btc_usdt` | The earliest time in the symbols.
2019-09-05 23:59:00
2020-01-01 00:00:00 | > (**) Use in cautions due to the deprecation (no data update) **📖 Data Guide:** [Open Interest](/data-guide/market/open-interest) — definition, interpretation, and chart examples. # Price OHLCV Source: https://docs.cryptoquant.com/api-reference/btc-market-data/price-ohlcv /openapi/v1.json get /btc/market-data/price-ohlcv This endpoint returns metrics related to BTC price. We provide two types of price, CryptoQuant's BTC Index Price and USD or USDT price of BTC of global exchanges. Price OHLCV data consists of five metrics.  `open`, the opening price at the beginning of the window, `close`, USD closing price at the end of the window,  `high`, the highest USD price in a given window, `low`, the lowest USD price in a given window, and `volume`, the total volume traded in a given window. At this endpoint, metrics are calculated by Minute, Hour and Day. BTC Index Price is calculated by taking VWAP(Volume Weighted Average Price) of BTC price data aggregated from all exchanges we provide. The exchanges we provide are as follows.
### Supported Exchanges By Market | Name | Market | Supported Exchanges | |--------|---------|----------------------------| | Spot | `spot` | All Exchange*, Binance, Binance US, Bitfinex, Bittrex, Coinbase Advanced, FTX**, Gemini, HTX Global, Kraken, OKX | | Perpetual | `perpetual` | All Exchange*, Binance, Bitmex, Bybit, Deribit, FTX**, HTX Global, OKX | > (*) Default exchange
> (**) Use in cautions due to the deprecation (no data update) In order to get USD or USDT price of BTC of specific exchange from above (eg. `btcusdt` pair of `binance`), you must specify `market`, `exchange` and `symbol` of BTC pair. For `volume` metric, the unit of volume could be USD, USDT or BTC. This is because exchanges have their own price data policy. All Exchange's `volume` is in BTC and available since the earliest time of exchanges. Please refer to volume unit of each exchange from below table.
### Supported Pairs By Exchange #### ◦ Spot | Name | Exchange | Symbol | Volume Unit | Available Since | |----------------|------------------|-----------------------------|--------------|-------------------------------| | All Exchange | `all_exchange` | `btc_usd`* | BTC | 2009-01-03 18:15:00 | | Binance | `binance` | `btc_usdt`* | BTC | 2017-08-17 04:00:00 | | Binance US | `binance_us` | `btc_usd`*
`btc_usdt` | BTC | 2019-09-17 10:17:00
2019-09-23 08:34:00 | | Bitfinex | `bitfinex` | `btc_usd`*
`btc_usdt` | BTC | 2013-04-01 00:07:00
2019-03-11 10:05:00 | | Bittrex | `bittrex` | `btc_usd`*
`btc_usdt` | USD
USDT | 2018-05-31 16:26:00
2015-12-12 14:59:00 | | Coinbase Advanced | `coinbase_advanced` | `btc_usd`* | BTC | 2015-07-20 21:37:00 | FTX** | `ftx` | `btc_usd`*
`btc_usdt` | USD
USDT | 2019-07-21 13:11:00
2020-03-28 14:40:00 | | Gemini | `gemini` | `btc_usd`* | BTC | 2019-08-30 00:00:00 | | HTX Global | `htx_global` | `btc_usdt`* | BTC | 2019-11-19 00:00:00 | | Kraken | `kraken` | `btc_usd`*
`btc_usdt` | BTC | 2013-10-06 21:34:00
2019-12-19 18:06:00 | | OKX | `okx` | `btc_usdt`* | BTC | 2019-10-01 00:00:00 | #### ◦ Perpetual | Exchange | Exchange Symbol | Pair Symbol | Volume | Historical Starting Point | |----------------|------------------|-------------------------------|-------------------|--------------------------------| | All Exchange | `all_exchange` | `btc_usd`* | BTC | The earliest time in the exchanges below. | | Binance | `binance` | `btc_usd`*
`btc_usdt` | Cont
BTC | 2020-08-11 07:02:00
2019-09-08 17:57:00 | | Bitmex | `bitmex` | `btc_usd`* | USD | 2015-09-25 12:34:00 | | Bybit | `bybit` | `btc_usd`*
`btc_usdt` | USD
BTC | 2018-11-14 16:00:00
2020-03-25 10:36:00 | | Deribit | `deribit` | `btc_usd`* | USD | 2018-08-14 10:34:00 | | FTX** | `ftx` | `btc_usd`* | USD | 2019-07-20 12:35:00 | | HTX Global | `htx_global` | `btc_usd`*
`btc_usdt` | Cont
BTC | 2020-03-25 09:45:00
2020-10-21 09:08:00 | | OKX | `okx` | `btc_usd`*
`btc_usdt` | Cont
BTC | 2019-03-30 00:00:00
2019-12-25 00:00:00 | > (*) Default exchange
> (**) Use in cautions due to the deprecation (no data update) > We calculate the OHLCV data of a day from the beginning of UTC 00:00:00. > However, the OHLCV data in official sites of HTX and OKX are calculated from the beginning of UTC 16:00:00. > Thus, be aware that there may be some intended discrepancy between those.
### Supported Windows By Market | Market | Supported Windows | |-----------|-------------------------------| | Spot | `min`, `hour`, `day*` | | Perpetual | `min`, `hour`, `day*` | > (*) Default exchange # Taker Buy Sell Stats Source: https://docs.cryptoquant.com/api-reference/btc-market-data/taker-buy-sell-stats /openapi/v1.json get /btc/market-data/taker-buy-sell-stats Taker Buy/Sell Stats represent takers' sentiment of which position they are taking in the market. This metric is calculated with perpetual swap trades in each exchange. `taker_buy_volume` is volume that takers buy. `taker_sell_volume` is volume that takers sell. `taker_total_volume` is the sum of `taker_buy_volume` and `taker_sell_volume`. `taker_buy_ratio` is the ratio of `taker_buy_volume` divided by `taker_total_volume`. `taker_sell_ratio` is the ratio of `taker_sell_volume` divided by `taker_total_volume`. `taker_buy_sell_ratio` is the ratio of `taker_buy_volume` divided by `taker_sell_volume`. Note we unify the unit of return value to USD for each exchange where its contract specification may vary. | Name | Exchange | Symbol | Available Since | |----------------|--------------|------|-----------------------------| | All Exchanges | `all_exchange` | | The earliest time in the exchanges below. | | Binance | `binance` | BTC-USDT | 2019-09-08 17:57:00 | | Bybit | `bybit` | BTC-USD | 2019-11-07 00:00:00 | | Bitmex | `bitmex` | BTC-USD | 2015-09-25 12:34:00 | | Deribit | `deribit` | BTC-PERPETUAL | 2019-03-30 00:00:00 | | HTX Global | `htx_global` | BTC-USD | 2020-03-28 00:00:00 | | OKX | `okx` | BTC-USD | 2019-03-30 00:00:00 | **📖 Data Guide:** [Taker Buy Sell Volume/Ratio](/data-guide/market/taker-buy-sell-volume-ratio) — definition, interpretation, and chart examples. # Estimated Leverage Ratio Source: https://docs.cryptoquant.com/api-reference/btc-market-indicator/estimated-leverage-ratio /openapi/v1.json get /btc/market-indicator/estimated-leverage-ratio By dividing the open interest of an exchange by their BTC reserve, you can estimate a relative average user leverage. Whenever the leverage value reaches a high, there is rapid volatility. Similar to Open Interest, but more accurate because it reflects the growth of the exchange itself. This is experimental indicator but it seems this reflects market sentiment. You can see how aggressive people are and how conservative they are in terms of investment. For 'In Progress' exchanges, estimated leverage ratio is not supported yet even though they provide open interest. __[Go to Data Guide‣](https://dataguide.cryptoquant.com/market-indicators/estimated-leverage-ratio)__
> **Note:** This endpoint does not support Point-In-Time (PIT) accuracy due to periodic updates to wallet address clustering. Historical data may change as new exchange wallets are discovered, added, and validated.
**📖 Data Guide:** [Estimated Leverage Ratio](/data-guide/market/estimated-leverage-ratio) — definition, interpretation, and chart examples. # MVRV Source: https://docs.cryptoquant.com/api-reference/btc-market-indicator/mvrv /openapi/v1.json get /btc/market-indicator/mvrv MVRV(Market-Value-to-Realized-Value) is a ratio of `market_cap` divided by `realized_cap`. It can be interpreted as the relationship between short-term and long-term investors (i.e. speculators vs hodlers). When this value is too high, BTC price may be overvalued, and if it is too low, there is a possibility that the price is undervalued. __[Go to Data Guide‣](https://dataguide.cryptoquant.com/market-indicators/mvrv-ratio)__ **📖 Data Guide:** [MVRV (Market Value to Realized Value) Ratio](/data-guide/market/mvrv-ratio) — definition, interpretation, and chart examples. # Realized Price Source: https://docs.cryptoquant.com/api-reference/btc-market-indicator/realized-price /openapi/v1.json get /btc/market-indicator/realized-price Realized Price is calculated as Realized Cap divided by the total coin supply. It measures the average price weighted by the supply of what the entire market participants paid for their coins. It sometimes can be interpreted as the on-chain support or resistance price. **📖 Data Guide:** [Realized Price](/data-guide/market/realized-price) — definition, interpretation, and chart examples. # SOPR Ratio Source: https://docs.cryptoquant.com/api-reference/btc-market-indicator/sopr-ratio /openapi/v1.json get /btc/market-indicator/sopr-ratio SOPR Ratio is calculated as long term holders' SOPR divided by short term holders' SOPR. Higher value of the ratio means higher spent profit of LTH over STH, which is usually useful for spotting market tops. **📖 Data Guide:** [SOPR Ratio (LTH-SOPR/STH-SOPR)](/data-guide/utxo/spent-output-profit-ratio-sopr/sopr-ratio-lth-sopr-sth-sopr) — definition, interpretation, and chart examples. # Spent Output Profit Ratio Source: https://docs.cryptoquant.com/api-reference/btc-market-indicator/spent-output-profit-ratio /openapi/v1.json get /btc/market-indicator/sopr `sopr` is abbreviation of Spent Output Profit Ratio. Spent Output Profit Ratio evaluates the profit ratio of the whole market participants by comparing the value of outputs at spent time to created time. `sopr` is a ratio that is calculated as the USD value of spent outputs at the spent time divided by the USD value of spent outputs at the created time. So you can see the value when UTxO destroyed. In a simple way, you can estimate the distribution of spent transaction output are in profit or not. **📖 Data Guide:** [Spent Output Profit Ratio (SOPR)](/data-guide/utxo/spent-output-profit-ratio-sopr) · [aSOPR (Adjusted SOPR)](/data-guide/utxo/spent-output-profit-ratio-sopr/asopr-adjusted-sopr) · [STH-SOPR](/data-guide/utxo/spent-output-profit-ratio-sopr/sth-sopr) · [LTH-SOPR](/data-guide/utxo/spent-output-profit-ratio-sopr/lth-sopr) — definition, interpretation, and chart examples. # Stablecoin Supply Ratio Source: https://docs.cryptoquant.com/api-reference/btc-market-indicator/stablecoin-supply-ratio /openapi/v1.json get /btc/market-indicator/stablecoin-supply-ratio SSR(Stablecoin Supply Ratio) is a ratio of stablecoin supply in the whole cryptocurrency market where stablecoin is used as fiat substitute for trading. This means that the supply of stablecoin can be used to assess the potential buying pressure for bitcoin. The historical starting point is 2017-11-28 00:00:00. __[Go to Data Guide‣](https://dataguide.cryptoquant.com/market-indicators/stablecoin-supply-ratio)__ **📖 Data Guide:** [Stablecoin Supply Ratio (SSR)](/data-guide/stablecoin/stablecoin-supply-ratio) — definition, interpretation, and chart examples. # UTxO Realized Price Age Distribution Source: https://docs.cryptoquant.com/api-reference/btc-market-indicator/utxo-realized-price-age-distribution /openapi/v1.json get /btc/market-indicator/utxo-realized-price-age-distribution UTxO Realized Price Age Distribution is a set of realized prices along with age bands. The metrics help us to overview each cohort’s holding behavior by overlaying a set of different realized prices. **📖 Data Guide:** [Realized Price - UTXO Age Bands](/data-guide/utxo/utxo-bands-age/realized-price-utxo-age-bands) — definition, interpretation, and chart examples. # BTC Memory pool Statistics by relative fee range Source: https://docs.cryptoquant.com/api-reference/btc-mempool-statistics/btc-memory-pool-statistics-by-relative-fee-range /openapi/v1.json get /btc/mempool/stats-by-relative-fee Mempool Statistics contains three metrics related to transactions waiting to be confirmed. You can see metrics for the number of transactions, the total amount of fees, and the aggregate size in bytes of transactions. Each metric was calculated based on fee level.
### Supported Metrics | Metric Type | Description | |--------------|--------------------------------------------------------| | `tx_count*` | The total number of unconfirmed transactions (Number) | | `total_size` | The aggregated size in bytes of transactions (Megabyte)| | `total_fee` | The total fee of unconfirmed transactions (BTC) | > (*) Default
### Supported Windows | Supported Windows | |-------------------| | `hour`, `day*` | > (*) Default # BTC Memory pool Statistics (Sum) Source: https://docs.cryptoquant.com/api-reference/btc-mempool-statistics/btc-memory-pool-statistics-sum /openapi/v1.json get /btc/mempool/stats-in-total Mempool Statistics contains three metrics related to transactions waiting to be confirmed. You can see metrics for the number of transactions, the total amount of fees, and the aggregate size in bytes of transactions.
### Supported Metrics | Metric Type | Description | |--------------|--------------------------------------------------------------------------------------| | `tx_count*` | The average number of unconfirmed transactions in selected time range (Number) | | `total_size` | The average aggregate size in bytes of transactions in selected time range (Megabyte)| | `total_fee` | The average total fee of unconfirmed transactions in selected time range (BTC) | > (*) Default
### Supported Windows | Supported Windows | |-------------------| | `hour`, `day*` | > (*) Default # Companies Source: https://docs.cryptoquant.com/api-reference/btc-miner-data/companies /openapi/v1.json get /btc/miner-data/companies This endpoint returns BTC mining company data. Company data consists of statistical metrics based on rewards and production data for each mining company. `coinbase_rewards`, The daily amount of Bitcoin mined directly from a coinbase transaction. And `coinbase_rewards` will only be added to `mara`. `other_mining_rewards`, The daily amount of Bitcoin received as payment from a mining pool. Tipically, mining pools pay miners with Bitcoin from a coinbase transaction. `total_rewards`, The daily sum of coinbase rewards and other mining rewards (in number of Bitcoin). `accumulated_monthly_rewards`, The daily running sum of total rewards in each month (in number of Bitcoin). `unique_txn`, The total number of Bitcoin transactions involving a mining reward. `active_address_count`, The number of addresses from a company that received a block reward each day. `reported_production`, The company's reported total monthly production (in number of Bitcoin). `report_accuracy`, The ratio of accumulated monthly rewards to reported production times 100. It represents the % of total reported production captured by On-chain transactions. `closing_usd`, The daily closing price of Bitcoin in USD. `total_daily_rewards_closing_usd`, Daily total rewards in USD using the closing usd price. `accumulated_monthly_rewards_closing_usd`, accumulated monthly rewards in usd using the closing usd price. | Name | Miner | |--------------|--------------| | MARA | `mara` | | RIOT | `riot` | | CORE | `core` | | HIVE | `hive` | | CLSK | `clsk` | | BITF | `bitf` | | CIPHER | `cipher` | | WULF | `wulf` | | IREN | `iren` | # Addresses Count Source: https://docs.cryptoquant.com/api-reference/btc-miner-flows/addresses-count /openapi/v1.json get /btc/miner-flows/addresses-count This endpoint returns the number of addresses involved in inflow/outflow transactions. # In-House Flow Source: https://docs.cryptoquant.com/api-reference/btc-miner-flows/in-house-flow /openapi/v1.json get /btc/miner-flows/in-house-flow This endpoint returns the in-house flow of BTC within wallets of the same miner for as far back as we track. The average in-house flow is the average transaction value for transactions flowing within wallets on a given day. # Inflow Source: https://docs.cryptoquant.com/api-reference/btc-miner-flows/inflow /openapi/v1.json get /btc/miner-flows/inflow This endpoint returns the inflow of BTC into mining pool wallets for as far back as we track. The average inflow is the average transaction value for transactions flowing into mining pool wallets on a given day. # Netflow Source: https://docs.cryptoquant.com/api-reference/btc-miner-flows/netflow /openapi/v1.json get /btc/miner-flows/netflow The difference between coins flowing into mining pools and flowing out of mining pools. Netflow usually helps us to figure out an increase of idle coins waiting to be traded in a certain time frame. # Outflow Source: https://docs.cryptoquant.com/api-reference/btc-miner-flows/outflow /openapi/v1.json get /btc/miner-flows/outflow This endpoint returns the outflow of BTC into mining pool wallets for as far back as we track. The average outflow is the average transaction value for transactions flowing out of mining pool wallets on a given day. **📖 Data Guide:** [Miner Outflow](/data-guide/miner/miner-outflow) — definition, interpretation, and chart examples. # Reserve Source: https://docs.cryptoquant.com/api-reference/btc-miner-flows/reserve /openapi/v1.json get /btc/miner-flows/reserve This endpoint returns the full historical on-chain balance of Bitcoin mining pools. # Transactions Count Source: https://docs.cryptoquant.com/api-reference/btc-miner-flows/transactions-count /openapi/v1.json get /btc/miner-flows/transactions-count This endpoint returns the number of transactions flowing in/out of Bitcoin miners. # Addresses Count Source: https://docs.cryptoquant.com/api-reference/btc-network-data/addresses-count /openapi/v1.json get /btc/network-data/addresses-count This endpoint returns metrics relating to the number of used bitcoin addresses. We provide several metrics, `addresses_count_active`, the total number of unique addresses that were active (either sender or receiver) on the blockchain, `addresses_count_sender`, the number of addresses that were active as a sender, and `addresses_count_receiver`, the number of addresses that were active as a receiver. # Block Bytes Source: https://docs.cryptoquant.com/api-reference/btc-network-data/block-bytes /openapi/v1.json get /btc/network-data/block-bytes The mean size(in bytes) of all blocks generated. # Block Count Source: https://docs.cryptoquant.com/api-reference/btc-network-data/block-count /openapi/v1.json get /btc/network-data/block-count The number of blocks generated in a given window. # Block Interval Source: https://docs.cryptoquant.com/api-reference/btc-network-data/block-interval /openapi/v1.json get /btc/network-data/block-interval The average time between blocks generated displayed in seconds. # Blockreward Source: https://docs.cryptoquant.com/api-reference/btc-network-data/blockreward /openapi/v1.json get /btc/network-data/blockreward The sum of block rewards (including mining or staking rewards and transaction fees). We also provide this value in usd. # Difficulty Source: https://docs.cryptoquant.com/api-reference/btc-network-data/difficulty /openapi/v1.json get /btc/network-data/difficulty The mean difficulty of mining a new block. # Fees Source: https://docs.cryptoquant.com/api-reference/btc-network-data/fees /openapi/v1.json get /btc/network-data/fees This endpoint returns the statistics related to fees that are paid to bitcoin miners. In general, fees are calculated by subtracting the newly issued bitcoin from the total block reward of each blocks. We provide three statistics, `fees_total`, the sum of all fees, `fees_block_mean`, the average fee per block, and `fees_reward_percent`, the percentage of fees relative to the total block reward. Additionally, these can be viewed in terms of USD. # Fees Transaction Source: https://docs.cryptoquant.com/api-reference/btc-network-data/fees-transaction /openapi/v1.json get /btc/network-data/fees-transaction This endpoint returns the statistics related to fees per transaction that are paid to bitcoin miners. In general, fees are calculated by subtracting the newly issued bitcoin from the total block reward of each blocks, and this is divided by the number of transactions to calculate the average fee per transaction in each block. We provide two statistics, `fees_transaction_mean`, the average fee per transaction, `fees_transaction_median,` the median fee per transaction. Additionally, these values can be calculated in USD. # Hashrate Source: https://docs.cryptoquant.com/api-reference/btc-network-data/hashrate /openapi/v1.json get /btc/network-data/hashrate The mean speed at which miners in the network are solving hash problems. It is displayed as hashes (Gigabytes) per second. # Supply Source: https://docs.cryptoquant.com/api-reference/btc-network-data/supply /openapi/v1.json get /btc/network-data/supply This endpoint returns metrics related to bitcoin supply, i.e. the amount of bitcoin in existence. We currently provide two metrics, `supply_total` , the total amount of bitcoins in existence (sum of all bitcoins issued by the coinbase reward), and `supply_new`, the amount of newly issued tokens in a given window. # Tokens Transferred Source: https://docs.cryptoquant.com/api-reference/btc-network-data/tokens-transferred /openapi/v1.json get /btc/network-data/tokens-transferred This endpoint returns metrics related to the number of tokens transferred, i.e transaction volume. We provide several metrics, `tokens_transferred_total`, the total number of transferred tokens, `tokens_transferred_mean`, the mean of number of transferred tokens per transaction, and `tokens_transferred_median`, the median of tokens transferred per transaction. # Transactions Count Source: https://docs.cryptoquant.com/api-reference/btc-network-data/transactions-count /openapi/v1.json get /btc/network-data/transactions-count This endpoint returns metrics related to the number of transactions. We provide several metrics, `transactions_count_total`, the total number of transactions, and `transactions_count_mean`, the mean number of transactions. # UTXO Count Source: https://docs.cryptoquant.com/api-reference/btc-network-data/utxo-count /openapi/v1.json get /btc/network-data/utxo-count The number of total number of unspent transaction outputs existing at the specified point. # Velocity Source: https://docs.cryptoquant.com/api-reference/btc-network-data/velocity /openapi/v1.json get /btc/network-data/velocity This endpoint returns metrics related to the velocity of bitcoin. Bitcoin's velocity is calculated by dividing the trailing 1 year estimated transaction volume(the cumulated sum of transferred tokens) by current supply. Velocity is a metric that explains how actively is money circulating in the market. # Coin Days Destroyed Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/coin-days-destroyed /openapi/v1.json get /btc/network-indicator/cdd Coin Days Destroyed reflects market participants who have been in the bitcoin on-chain for longer. This indicator gives more weight to long-term-holder position. `cdd` is the sum of products of spent transaction output alive days and its value. `sa_cdd` is abbreviation of supply-adjusted cdd. Since `cdd` increases as the newly created block mined, we need an indicator which normalize `cdd` value. `sa_cdd` is calculated by `cdd` over `supply_total`. `average_sa_cdd` is the average value of `sa_cdd` since genesis block. `binary_cdd` is the signal whether current `sa_cdd` is larger than `average_sa_cdd` or not. If `sa_cdd` > `average_sa_cdd`, then `binary_cdd` is 1. In conclusion, these indicators help us to estimate how whale's moving. **📖 Data Guide:** [Coin Days Destroyed (CDD)](/data-guide/utxo/coin-days-destroyed-cdd) · [Binary CDD](/data-guide/utxo/binary-cdd) — definition, interpretation, and chart examples. # Dormancy Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/dormancy /openapi/v1.json get /btc/network-indicator/dormancy Average Dormancy (`average_dormancy`) is the average number of days destroyed per coin transacted. Supply-Adjusted Average Dormancy (`sa_average_dormancy`) is the average dormancy normalized by supply total, where supply total increases as more blocks mined. # Mean Coin Age Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/mean-coin-age /openapi/v1.json get /btc/network-indicator/mca Mean Coin Age is the mean value of products of bitcoin unspent transaction output alive days and its value. It is basically similar to `cdd`. But `mca` focuses on unspent transaction output. Mean Coin Dollar Age is the sum value of products of bitcoin unspent transaction output alive days, value, and price at the created time. **📖 Data Guide:** [Mean Coin Age (MCA)](/data-guide/utxo/mean-coin-age-mca) — definition, interpretation, and chart examples. # Net Realized Profit and Loss Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/net-realized-profit-and-loss /openapi/v1.json get /btc/network-indicator/nrpl Net Realized Profit/Loss metric presenting the net magnitude of profit, or loss realized by all holders spending coins. Realized Profit/Loss is assessed relative to the price when a coin last moved. # Net Unrealized Profit and Loss Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/net-unrealized-profit-and-loss /openapi/v1.json get /btc/network-indicator/nupl Net Unrealized Profit and Loss shows how different between `market_cap` and `realized_cap`. `nupl` is calculated as difference between `market_cap` and `realized_cap` divided by `market_cap`. If `market_cap` > `realized_cap`, then `nupl` > 0, which means bitcoin on-chain expected value is less than what they actually have. So this value will give selling pressure. `nup` is net unrealized profit, which is calculated as sum of products of UTxO's value and price difference between created and destroyed, divided by `market_cap`. `nup` only contains UTxOs in profit. `nul` is net unrealized loss. This is opposite indicator of `nup`. It only contains UTxOs in loss. **📖 Data Guide:** [Net Unrealized Profit/Loss (NUPL)](/data-guide/utxo/net-unrealized-profit-and-loss-nupl) — definition, interpretation, and chart examples. # NVM Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/nvm /openapi/v1.json get /btc/network-indicator/nvm NVM(Network Value to Metcalfe Ratio) is a metric based on Metcalfe’s law; the value of a network is proportional to the square of its nodes or user. NVM is a ratio of market cap divided by daily active address. Based on Metcalfe’s law, the value of bitcoin rises if the daily active addresses increase. Therefore, if the NVM value is relatively small, it means that the value of the network is underestimated and if the value is relatively high, it means that the value of the network is overestimated. __[Go to Data Guide‣](https://dataguide.cryptoquant.com/network-indicators/nvm-ratio)__ **📖 Data Guide:** [NVM Ratio](/data-guide/network/nvm-ratio) — definition, interpretation, and chart examples. # NVT Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/nvt /openapi/v1.json get /btc/network-indicator/nvt NVT(Network Value to Transaction) ratio is the network value(`supply_total` * `price_usd`) divided by `tokens_transferred_total`. `nvt` is a metric often used to determine whether Bitcoin price is overvalued or not. The theory behind this indicator is that the value of the token depends on how actively transactions take place on the network. __[Go to Data Guide‣](https://dataguide.cryptoquant.com/network-indicators/nvt-ratio)__ **📖 Data Guide:** [NVT Ratio](/data-guide/network/nvt-ratio) — definition, interpretation, and chart examples. # NVT Golden Cross Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/nvt-golden-cross /openapi/v1.json get /btc/network-indicator/nvt-golden-cross NVT Golden Cross is a modified index of NVT that provides local tops and bottoms. NVT Golden Cross values above 2.2 indicate that downside risk goes up. NVT Golden Cross values below -1.6 mean huge upside potential will occur. __[Go to Data Guide‣](https://dataguide.cryptoquant.com/network-indicators/nvt-golden-cross)__ **📖 Data Guide:** [NVT Golden Cross](/data-guide/network/nvt-golden-cross) — definition, interpretation, and chart examples. # Profit and Loss (Supply) Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/profit-and-loss-supply /openapi/v1.json get /btc/network-indicator/pnl-supply Profit and Loss (Supply) evaluates the sum of UTxOs being in profit or not by comparing the price between created and destroyed. These metrics are similar to the ones in Profit and Loss (UTxO) but differ from putting more weight on each UTxO with its value. Sometimes we want to know the exact alive bitcoin transaction output value in profit. `pnl-supply` will show it accuretely. `pnl-supply` is calculated as the sum of UTxO value. **📖 Data Guide:** [Profit and Loss (Supply)](/data-guide/utxo/profit-and-loss-supply) — definition, interpretation, and chart examples. # Profit and Loss (UTxO) Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/profit-and-loss-utxo /openapi/v1.json get /btc/network-indicator/pnl-utxo Profit and Loss (UTxO) evaluates the number of UTxOs being in profit or not by comparing the price between created and destroyed. When the price at destroyed time is higher than created, this transaction is in profit. **📖 Data Guide:** [Profit and Loss (UTxO)](/data-guide/utxo/profit-and-loss-utxo) — definition, interpretation, and chart examples. # Puell Multiple Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/puell-multiple /openapi/v1.json get /btc/network-indicator/puell-multiple Puell Multiple is the mining revenue usd divided by MA 365 mining revenue usd. `puell_multiple` is a metric shows the historically low and high periods of the value of bitcoin issued daily, and at what point investors should buy bitcoin to get high returns. This indicator was created by David Puell. __[Go to Data Guide‣](https://dataguide.cryptoquant.com/network-indicators/puell-multiple)__ **📖 Data Guide:** [Puell Multiple](/data-guide/network/puell-multiple) — definition, interpretation, and chart examples. # Spent Output Age Distribution Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/spent-output-age-distribution /openapi/v1.json get /btc/network-indicator/spent-output-age-distribution Spent Output Age Distribution is a set of active sum of spent outputs with age bands. This indicator summarizes how much UTxOs are destroyed by long-term or short-term holders (each band). We provide the distribution values in native, USD, and percent values. **📖 Data Guide:** [Spent Output Age Bands](/data-guide/utxo/utxo-bands-age/spent-output-age-bands) — definition, interpretation, and chart examples. # Spent Output Supply Distribution Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/spent-output-supply-distribution /openapi/v1.json get /btc/network-indicator/spent-output-supply-distribution Spent Output Supply Distribution is a set of active sum of spent outputs with balance (supply) bands. This indicator summarizes how much UTxOs are destroyed by whales or retails (each band). We provide the distribution values in native, USD, and percent values. **📖 Data Guide:** [Spent Output Value Bands](/data-guide/utxo/utxo-bands-value/spent-output-value-bands) — definition, interpretation, and chart examples. # Stock to Flow Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/stock-to-flow /openapi/v1.json get /btc/network-indicator/stock-to-flow Stock to Flow is a metric used to assume bitcoin price based on its scarcity just like gold, silver, and other valuable objects that are limited in amount and costly to earn. The same model for evaluating the value of those objects can be adopted to assess the value of bitcoin. The scarcity is calculated by dividing currently circulating coins in the blockchain network to newly supplied coins. __[Go to Data Guide‣](https://dataguide.cryptoquant.com/network-indicators/stock-to-flow-ratio)__ **📖 Data Guide:** [Stock to Flow Ratio](/data-guide/network/stock-to-flow-ratio) · [Stock to Flow Reversion](/data-guide/network/stock-to-flow-reversion) — definition, interpretation, and chart examples. # Sum Coin Age Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/sum-coin-age /openapi/v1.json get /btc/network-indicator/sca Sum Coin Age is the sum value of products of bitcoin unspent transaction output alive days and its value. It is basically similar to `cdd`. But `sca` focuses on unspent transaction output. Sum Coin Dollar Age is the sum value of products of bitcoin unspent transaction output alive days, value, and price at the created time. **📖 Data Guide:** [Sum Coin Age (SCA)](/data-guide/utxo/sum-coin-age-sca) — definition, interpretation, and chart examples. # Sum Coin Age Distribution Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/sum-coin-age-distribution /openapi/v1.json get /btc/network-indicator/sca-distribution This indicator shows the distribution of long-term holder and short-term holder with UTxO data. It is similar to UTxO distribution, but weighted by alive days to highlight long-term holder's distribution in different ranges. Each field is calculated as the sum of the products of bitcoin unspent transaction output alive days and its value in a given period, divided by their sum. If long-term SCA distribution ratio increases, then we can interpret this as one of bullish moment. **📖 Data Guide:** [Sum Coin Age Distribution (SCA Distribution)](/data-guide/utxo/sum-coin-age-distribution-sca-distribution) — definition, interpretation, and chart examples. # UTxO Age Distribution Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/utxo-age-distribution /openapi/v1.json get /btc/network-indicator/utxo-age-distribution UTxO Age Distribution is a set of active supply with age bands. This indicator summarizes the behaviors of long-term or short-term holders along with price actions. We provide the distribution values in native, USD, and percent values. **📖 Data Guide:** [UTXO Age Bands](/data-guide/utxo/utxo-bands-age/utxo-age-bands) — definition, interpretation, and chart examples. # UTxO Count Age Distribution Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/utxo-count-age-distribution /openapi/v1.json get /btc/network-indicator/utxo-count-age-distribution UTxO Count Age Distribution is a set of active number of holders with age bands. This indicator summarizes how many long-term or short-term holders exist by each band. We provide the distribution values in native, and percent values. **📖 Data Guide:** [UTXO Count - Age Bands](/data-guide/utxo/utxo-bands-age/utxo-count-age-bands) — definition, interpretation, and chart examples. # UTxO Count Supply Distribution Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/utxo-count-supply-distribution /openapi/v1.json get /btc/network-indicator/utxo-count-supply-distribution UTxO Count Supply Distribution is a set of active number of holders with balance (supply) bands. This indicator summarizes how many whales and retails exist by each band. We provide the distribution values in native, and percent values. **📖 Data Guide:** [UTXO Count - Value Bands](/data-guide/utxo/utxo-bands-value/utxo-count-value-bands) — definition, interpretation, and chart examples. # UTxO Realized Age Distribution Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/utxo-realized-age-distribution /openapi/v1.json get /btc/network-indicator/utxo-realized-age-distribution UTxO Realized Age Distribution is a set of active supply with age bands weighted by the price at UTxO created time. Similar to Realized Cap, this indicator summarizes the capitalization held by long-term or short-term holders (each band). We provide the distribution values in native, USD, and percent values. **📖 Data Guide:** [Realized Cap - UTXO Age Bands](/data-guide/utxo/utxo-bands-age/realized-cap-utxo-age-bands) — definition, interpretation, and chart examples. # UTxO Realized Supply Distribution Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/utxo-realized-supply-distribution /openapi/v1.json get /btc/network-indicator/utxo-realized-supply-distribution UTxO Realized Supply Distribution is a set of active supply with balance (supply) bands weighted by the price at UTxO created time. Similar to Realized Cap, this indicator summarizes the capitalization held by whales or retails (each band). We provide the distribution values in USD, and percent values. **📖 Data Guide:** [Realized Cap - UTXO Value Bands USD](/data-guide/utxo/utxo-bands-value/realized-cap-utxo-value-bands-usd) — definition, interpretation, and chart examples. # UTxO Supply Distribution Source: https://docs.cryptoquant.com/api-reference/btc-network-indicator/utxo-supply-distribution /openapi/v1.json get /btc/network-indicator/utxo-supply-distribution UTxO Supply Distribution is a set of active supply with balance (supply) bands. This indicator summarizes the behaviors of whales or retails separated by amount of coins they hold along with price actions. We provide the distribution values in native, and percent values. **📖 Data Guide:** [UTXO Value Bands](/data-guide/utxo/utxo-bands-value/utxo-value-bands) — definition, interpretation, and chart examples. # Entity List Source: https://docs.cryptoquant.com/api-reference/erc20-entity-status/entity-list /openapi/v1.json get /erc20/status/entity-list This endpoint returns entity list to serve data. The meaning of the `market_type` value of the exchange object is as follows. For exchange objects, the `market_type` field tells whether the exchange is a spot exchange or a derivative exchange. Entities without a market type, such as miners or banks, will return 0 for `market_type`. | Exchange Market Type | Description | |------------------------|----------------------| | 0 | Undefined | | 1 | Spot Exchange | | 2 | Derivative Exchange | # Addresses Count Source: https://docs.cryptoquant.com/api-reference/erc20-exchange-flows/addresses-count /openapi/v1.json get /erc20/exchange-flows/addresses-count This endpoint returns the number of addresses involved in inflow/outflow transactions. **📖 Data Guide:** [Exchange Addresses Count](/data-guide/exchange/exchange-addresses-count) — definition, interpretation, and chart examples. # Inflow Source: https://docs.cryptoquant.com/api-reference/erc20-exchange-flows/inflow /openapi/v1.json get /erc20/exchange-flows/inflow This endpoint returns the inflow of ERC20 token into exchange wallets for as far back as we track. The average inflow is the average transaction value for transactions flowing into exchange wallets on a given day. **📖 Data Guide:** [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. # Netflow Source: https://docs.cryptoquant.com/api-reference/erc20-exchange-flows/netflow /openapi/v1.json get /erc20/exchange-flows/netflow The difference between coins flowing into exchanges and flowing out of exchanges. Netflow usually helps us to figure out an increase of idle coins waiting to be traded in a certain time frame. **📖 Data Guide:** [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. # Outflow Source: https://docs.cryptoquant.com/api-reference/erc20-exchange-flows/outflow /openapi/v1.json get /erc20/exchange-flows/outflow This endpoint returns the outflow of ERC20 token into exchange wallets for as far back as we track. The average outflow is the average transaction value for transactions flowing into exchange wallets on a given day. **📖 Data Guide:** [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. # Reserve Source: https://docs.cryptoquant.com/api-reference/erc20-exchange-flows/reserve /openapi/v1.json get /erc20/exchange-flows/reserve This endpoint returns the full historical on-chain ERC20 token balance of exchanges. **📖 Data Guide:** [Exchange Reserve](/data-guide/exchange/exchange-reserve) — definition, interpretation, and chart examples. # Transactions Count Source: https://docs.cryptoquant.com/api-reference/erc20-exchange-flows/transactions-count /openapi/v1.json get /erc20/exchange-flows/transactions-count This endpoint returns the number of transactions flowing in/out of ERC20 token exchanges. **📖 Data Guide:** [Exchange Transactions Count](/data-guide/exchange/exchange-transactions-count) — definition, interpretation, and chart examples. # Exchange Supply Ratio Source: https://docs.cryptoquant.com/api-reference/erc20-flow-indicator/exchange-supply-ratio /openapi/v1.json get /erc20/flow-indicator/exchange-supply-ratio Exchange Supply Ratio is calculated as exchange reserve divided by total supply. The metric measures how much tokens are reserved in the exchange relative to total supply of the token. **📖 Data Guide:** [Exchange Supply Ratio](/data-guide/exchange/exchange-supply-ratio) — definition, interpretation, and chart examples. # Price OHLCV Source: https://docs.cryptoquant.com/api-reference/erc20-market-data/price-ohlcv /openapi/v1.json get /erc20/market-data/price-ohlcv This endpoint returns metrics related to ERC20 Token's Index Price. Price OHLCV data consists of five metrics.  `open`, the opening price at the beginning of the window, `close`, USD closing price at the end of the window,  `high`, the highest USD price in a given window, `low`, the lowest USD price in a given window, and `volume`, the total token volume traded in a given window. At this endpoint, metrics are calculated by Minute, Hour and Day. ERC20 Token Index Price is calculated by taking VWAP(Volume Weighted Average Price) of ERC20 Token price data aggregated from global exchanges. You can check supported exchanges [here](https://www.notion.so/cqlive/Stablecoins-ERC20-Exchange-List-e33b9baeae094fb090983dc1e1183b05). # Addresses Count Source: https://docs.cryptoquant.com/api-reference/erc20-network-data/addresses-count /openapi/v1.json get /erc20/network-data/addresses-count This endpoint returns metrics relating to the number of used to transfer the tokens. We provide several metrics, `addresses_count_active`, the total number of unique addresses that were active (either sender or receiver) on the blockchain in a given window, `addresses_count_sender`, the number of addresses that were active as a sender, and `addresses_count_receiver`, the number of addresses that were active as a receiver. # Supply Source: https://docs.cryptoquant.com/api-reference/erc20-network-data/supply /openapi/v1.json get /erc20/network-data/supply This endpoint returns metrics related to the supply of ERC20 tokens, i.e. the amount of ERC20s tokens in existence. We currently provide three metrics, `supply_total`, the total amount of ERC20 tokens in existence, `supply_minted`, the amount of newly issued tokens, and `supply_burned`, the amount of newly burnt tokens in a given window. # Tokens Transferred Source: https://docs.cryptoquant.com/api-reference/erc20-network-data/tokens-transferred /openapi/v1.json get /erc20/network-data/tokens-transferred This endpoint returns metrics related to the number of tokens transferred, i.e transaction volume. We provide several metrics, `tokens_transferred_total`, the total number of transferred tokens in that window, `tokens_transferred_mean`, the mean of transferred tokens per transaction in that window, and `tokens_transferred_median`, the median of tokens transferred per transaction. # Tokens Transferred Count Source: https://docs.cryptoquant.com/api-reference/erc20-network-data/tokens-transferred-count /openapi/v1.json get /erc20/network-data/tokens-transferred-count This endpoint returns metrics related to the number of tokens transferred executed. We provide several metrics, `tokens_transferred_count_total`, the total number of executed tokens transferred, and `tokens_transferred_count_mean`, the mean number of executed tokens transferred. Note only successful transfers (value > 0) are counted. # Transactions Count Source: https://docs.cryptoquant.com/api-reference/erc20-network-data/transactions-count /openapi/v1.json get /erc20/network-data/transactions-count This endpoint returns metrics related to the number of transactions. We provide several metrics, `transactions_count_total`, the total number of transactions, `transactions_count_mean`, the mean number of transactions. Note all events executed by the ERC20 contract are counted. # Velocity Source: https://docs.cryptoquant.com/api-reference/erc20-network-data/velocity /openapi/v1.json get /erc20/network-data/velocity This endpoint returns metrics related to the velocity of ERC20 tokens. Velocity is calculated by dividing the trailing 1 year estimated transaction volume(the cumulated sum of transferred tokens) by current supply. Velocity is a metric that explains how actively is money circulating in the market. # Depositor Count New Source: https://docs.cryptoquant.com/api-reference/eth-20/depositor-count-new /openapi/v1.json get /eth/eth2/depositor-count-new This endpoint returns the number of new unique accounts who deposited over 32 ETH to the deposit contract. # Depositor Count Total Source: https://docs.cryptoquant.com/api-reference/eth-20/depositor-count-total /openapi/v1.json get /eth/eth2/depositor-count-total This endpoint returns the number of unique accounts who deposited over 32 ETH to the deposit contract. # Phase 0 Success Rate Source: https://docs.cryptoquant.com/api-reference/eth-20/phase-0-success-rate /openapi/v1.json get /eth/eth2/phase0-success-rate This endpoint returns the percentage of the valid ETH balance of the deposit contract to 524,288 ETH. # Staking Inflow Total Source: https://docs.cryptoquant.com/api-reference/eth-20/staking-inflow-total /openapi/v1.json get /eth/eth2/staking-inflow-total This endpoint returns the valid ETH inflow into the deposit contract. # Staking Rate Source: https://docs.cryptoquant.com/api-reference/eth-20/staking-rate /openapi/v1.json get /eth/eth2/staking-rate This endpoint returns the percentage of the balance of the ETH 2.0 deposit contract to the total supply. # Staking Transaction Count Source: https://docs.cryptoquant.com/api-reference/eth-20/staking-transaction-count /openapi/v1.json get /eth/eth2/staking-transaction-count This endpoint returns the number of valid transactions to the deposit contract. # Staking Validator Total Source: https://docs.cryptoquant.com/api-reference/eth-20/staking-validator-total /openapi/v1.json get /eth/eth2/staking-validator-total This endpoint returns the number of total validators. # Total Value Staked Source: https://docs.cryptoquant.com/api-reference/eth-20/total-value-staked /openapi/v1.json get /eth/eth2/total-value-staked This endpoint returns the valid ETH balance of the deposit contract. # Entity List Source: https://docs.cryptoquant.com/api-reference/eth-entity-status/entity-list /openapi/v1.json get /eth/status/entity-list This endpoint returns entity list to serve data. The meaning of the `market_type` value of the exchange object is as follows. For exchange objects, the `market_type` field tells whether the exchange is a spot exchange or a derivative exchange. Entities without a market type, such as miners or banks, will return 0 for `market_type`. | Exchange Market Type | Description | |------------------------|----------------------| | 0 | Undefined | | 1 | Spot Exchange | | 2 | Derivative Exchange | # Addresses Count Source: https://docs.cryptoquant.com/api-reference/eth-exchange-flows/addresses-count /openapi/v1.json get /eth/exchange-flows/addresses-count This endpoint returns the number of addresses involved in inflow/outflow transactions. **📖 Data Guide:** [Exchange Addresses Count](/data-guide/exchange/exchange-addresses-count) — definition, interpretation, and chart examples. # Inflow Source: https://docs.cryptoquant.com/api-reference/eth-exchange-flows/inflow /openapi/v1.json get /eth/exchange-flows/inflow This endpoint returns the inflow of ETH into exchange wallets for as far back as we track. The average inflow is the average transaction value for transactions flowing into exchange wallets on a given day. **📖 Data Guide:** [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. # Netflow Source: https://docs.cryptoquant.com/api-reference/eth-exchange-flows/netflow /openapi/v1.json get /eth/exchange-flows/netflow The difference between coins flowing into exchanges and flowing out of exchanges. Netflow usually helps us to figure out an increase of idle coins waiting to be traded in a certain time frame. **📖 Data Guide:** [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. # Outflow Source: https://docs.cryptoquant.com/api-reference/eth-exchange-flows/outflow /openapi/v1.json get /eth/exchange-flows/outflow This endpoint returns the outflow of ETH into exchange wallets for as far back as we track. The average outflow is the average transaction value for transactions flowing into exchange wallets on a given day. **📖 Data Guide:** [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. # Reserve Source: https://docs.cryptoquant.com/api-reference/eth-exchange-flows/reserve /openapi/v1.json get /eth/exchange-flows/reserve This endpoint returns the full historical on-chain balance of Ethereum exchanges. **📖 Data Guide:** [Exchange Reserve](/data-guide/exchange/exchange-reserve) — definition, interpretation, and chart examples. # Transactions Count Source: https://docs.cryptoquant.com/api-reference/eth-exchange-flows/transactions-count /openapi/v1.json get /eth/exchange-flows/transactions-count This endpoint returns the number of transactions flowing in/out of Ethereum exchanges. **📖 Data Guide:** [Exchange Transactions Count](/data-guide/exchange/exchange-transactions-count) — definition, interpretation, and chart examples. # Exchange Supply Ratio Source: https://docs.cryptoquant.com/api-reference/eth-flow-indicator/exchange-supply-ratio /openapi/v1.json get /eth/flow-indicator/exchange-supply-ratio Exchange Supply Ratio is calculated as exchange reserve divided by total supply. The metric measures how much tokens are reserved in the exchange relative to total supply of the token. **📖 Data Guide:** [Exchange Supply Ratio](/data-guide/exchange/exchange-supply-ratio) — definition, interpretation, and chart examples. # Digital Asset Holdings Source: https://docs.cryptoquant.com/api-reference/eth-fund-data/digital-asset-holdings /openapi/v1.json get /eth/fund-data/digital-asset-holdings This endpoint returns digital asset holdings status of each fund. For example, Grayscale ETH Holdings along with ETHE represents how much ETH Grayscale is holding for its investment. This metric indicates stock market's sentiment where higher the value means bullish sentiment of investors in stock market. **📖 Data Guide:** [ETHE Digital Asset Holdings](/data-guide/fund-premium/grayscale-ethereum-trust-ethe/ethe-digital-asset-holdings) — definition, interpretation, and chart examples. # Market Premium Source: https://docs.cryptoquant.com/api-reference/eth-fund-data/market-premium /openapi/v1.json get /eth/fund-data/market-premium The premium of certain symbol (e.g. ethe) is defined as (market price of the symbol - NAV) divided by NAV where NAV (Native Asset Value) is the current value of holdings (e.g. ETH price multiplied by ETH per Share). Higher the premium indicates market bullish, which also indicates downside risk. On the other hand, lower the premium indicates market bearish, which also indicates upside risk. All Symbol market premium is calculated by taking VWAP (Volume Weighted Average Ratio) of each fund data volume (usd). **📖 Data Guide:** [ETHE Premium or Discount](/data-guide/fund-premium/grayscale-ethereum-trust-ethe/ethe-premium-or-discount) — definition, interpretation, and chart examples. # Market Price USD Source: https://docs.cryptoquant.com/api-reference/eth-fund-data/market-price-usd /openapi/v1.json get /eth/fund-data/market-price-usd The price of certain symbol (e.g. ethe) managed by each fund (e.g. Grayscale) reflects sentiment of investors in regulated markets. In this specific case, having single share of ETHE means having approximately 0.01 ETH invested to Grayscale. This endpoint returns metrics related to the US Dollar(USD) price of fund related stocks (e.g. ethe). We provide five metrics, `price_usd_open`, USD opening price at the beginning of the window, `price_usd_close`, USD closing price at the end of the window, `price_usd_high`, the highest USD price in a given window, `price_usd_low`, the lowest USD price in a given window, and `price_usd_adj_close`, USD adjusted closing price at the end of the window. All Symbol is not supported. **📖 Data Guide:** [Grayscale Ethereum Trust (ETHE)](/data-guide/fund-premium/grayscale-ethereum-trust-ethe) — definition, interpretation, and chart examples. # Market Volume Source: https://docs.cryptoquant.com/api-reference/eth-fund-data/market-volume /openapi/v1.json get /eth/fund-data/market-volume The volume of certain symbol (e.g. ethe) managed by each fund (e.g. Grayscale) reflects sentiment of investors in regulated markets. This endpoint returns traded volume of fund related stocks (e.g. ethe). At this endpoint, metrics are calculated by Day. We provide one metric, `volume`, traded volume of the window. **📖 Data Guide:** [Grayscale Ethereum Trust (ETHE)](/data-guide/fund-premium/grayscale-ethereum-trust-ethe) — definition, interpretation, and chart examples. # Capitalization Source: https://docs.cryptoquant.com/api-reference/eth-market-data/capitalization /openapi/v1.json get /eth/market-data/capitalization This endpoint returns metrics related to market capitalization. We provide `market_cap`, which is total market capitalization of ETH, calculated by multiplying the circulating supply with its USD price. **📖 Data Guide:** [Capitalization models](/data-guide/market/capitalization-models) — definition, interpretation, and chart examples. # Coinbase Premium Index Source: https://docs.cryptoquant.com/api-reference/eth-market-data/coinbase-premium-index /openapi/v1.json get /eth/market-data/coinbase-premium-index Coinbase Premium Index is calculated as percent difference from Binance price(ETHUSDT) to Coinbase price(ETHUSD). Coinbase Premium Gap is calculated as gap between Coinbase price(ETHUSD) and Binance price(ETHUSDT). The higher the premium, the stronger the spot buying pressure from Coinbase. **📖 Data Guide:** [Coinbase Premium](/data-guide/fund-premium/coinbase-premium) — definition, interpretation, and chart examples. # Funding Rates Source: https://docs.cryptoquant.com/api-reference/eth-market-data/funding-rates /openapi/v1.json get /eth/market-data/funding-rates Funding rates represents traders' sentiments of which position they bet on in perpetual swaps market. Positive funding rates implies that many traders are bullish and long traders pay funding to short traders. Negative funding rates implies many traders are bearish and short traders pay funding to long traders. | Name | Exchange | Symbol | Available Since | |----------------|--------------|----|-------------------------| | All Exchanges | `all_exchange` | | The earliest time in the exchanges below. | | Binance | `binance` | ETH-USDT | 2019-11-29 00:00:00 | | Bybit | `bybit` | ETH-USD | 2019-01-25 08:00:00 | | Bitmex | `bitmex` | ETH-USD | 2018-08-02 12:00:00 | | Deribit | `deribit` | ETH-PERPETUAL | 2019-10-04 00:00:00 | | HTX Global | `htx_global` | ETH-USD | 2020-07-04 00:01:00 | | OKX | `okx` | ETH-USD | 2019-04-02 02:00:00 | **📖 Data Guide:** [Funding Rates](/data-guide/market/funding-rates) — definition, interpretation, and chart examples. # Liquidations Source: https://docs.cryptoquant.com/api-reference/eth-market-data/liquidations /openapi/v1.json get /eth/market-data/liquidations Liquidations are sum of forced market orders to exit leveraged positions caused by price volatility. Liquidations indicate current price volatility and traders' sentiment which side they had been betting. Note that Binance's liquidation data collection policy has changed since [2021-04-27](https://binance-docs.github.io/apidocs/futures/en/#change-log), which makes the distribution of the data has changed after that. | Name | Exchange | Symbol | Available Since | |----------------|----------------|--------------|-----------------------------| | All Exchanges | `all_exchange` | `all_symbol` | The earliest time in the exchanges below. | | Binance | `binance` | `all_symbol`
`eth_usdt`
`eth_usd` | The earliest time in the symbols.
2019-11-30 00:00:00
2020-08-21 00:00:00 | | Bitfinex | `bitfinex` | `all_symbol`
`eth_usdt` | The earliest time in the symbols.
2019-09-17 00:00:00 | | Bitmex | `bitmex` | `all_symbol`
`eth_usd` | The earliest time in the symbols.
2019-04-02 00:00:00 | | Bybit | `bybit` | `all_symbol`
`eth_usd`
`eth_usdt` | The earliest time in the symbols.
2020-12-20 00:00:00
2020-12-18 00:00:00 | | Deribit | `deribit` | `all_symbol`
`eth_usd` | The earliest time in the symbols.
2019-05-25 00:00:00 | | FTX** | `ftx` | `all_symbol`
`eth_usd` | The earliest time in the symbols.
2019-08-04 00:00:00 | | Gate.io | `gate_io` | `all_symbol`
`eth_usd`
`eth_usdt` | The earliest time in the symbols.
2018-12-28 11:00:00
2019-11-21 11:00:00 | | HTX Global | `htx_global` | `all_symbol`
`eth_usd`
`eth_usdt` | The earliest time in the symbols.
2020-06-26 00:00:00
2021-09-23 14:00:00 | | OKX | `okx` | `all_symbol`
`eth_usd`
`eth_usdt` | The earliest time in the symbols.
2020-12-20 00:00:00
2020-12-17 00:00:00 | > (**) Use in cautions due to the deprecation (no data update) # Open Interest Source: https://docs.cryptoquant.com/api-reference/eth-market-data/open-interest /openapi/v1.json get /eth/market-data/open-interest This endpoint returns ETH Perpetual Open Interest from derivative exchanges. Supported exchanges for Open Interest are below. Note we unify the unit of return value to USD for each exchange where its contract specification may vary. | Name | Exchange | Symbol | Available Since | |----------------|--------------|-------------|-----------------------------| | All Exchanges | `all_exchange` | `all_symbol` | The earliest time in the exchanges below. | | Binance | `binance` | `all_symbol`
`eth_usd`
`eth_usdt` | The earliest time in the symbols.
2020-08-18 00:00:00
2020-05-14 00:00:00 | | Bitfinex | `bitfinex` | `all_symbol`
`eth_usdt` | The earliest time in the symbols.
2020-06-01 00:00:00 | | Bitmex | `bitmex` | `all_symbol`
`eth_usd` | The earliest time in the symbols.
2019-03-30 00:00:00 | | Bybit | `bybit` | `all_symbol`
`eth_usd`
`eth_usdt` | The earliest time in the symbols.
2019-11-07 00:00:00
2020-10-21 00:00:00 | | Deribit | `deribit` | `all_symbol`
`eth_usd` | The earliest time in the symbols.
2019-03-31 00:00:00 | | FTX** | `ftx` | `all_symbol`
`eth_usd` | The earliest time in the symbols.
2020-05-09 00:00:00 | | Gate.io | `gate_io` | `all_symbol`
`eth_usd`
`eth_usdt` | The earliest time in the symbols.
2020-07-01 00:00:00
2020-07-01 00:00:00 | | HTX | `htx_global` | `all_symbol`
`eth_usd`
`eth_usdt` | The earliest time in the symbols.
2020-06-24 00:00:00
2021-08-26 05:00:00 | | Kraken | `kraken` | `all_symbol`
`eth_usd` | The earliest time in the symbols.
2019-03-30 00:00:00 | | OKX | `okx` | `all_symbol`
`eth_usd`
`eth_usdt` | The earliest time in the symbols.
2019-09-05 00:00:00
2020-01-01 00:00:00 | > (**) Use in cautions due to the deprecation (no data update) **📖 Data Guide:** [Open Interest](/data-guide/market/open-interest) — definition, interpretation, and chart examples. # Price OHLCV Source: https://docs.cryptoquant.com/api-reference/eth-market-data/price-ohlcv /openapi/v1.json get /eth/market-data/price-ohlcv This endpoint returns metrics related to ETH price. We provide two types of price, CryptoQuant's ETH Index Price and USD or USDT price of ETH of global exchanges. Price OHLCV data consists of five metrics.  `open`, the opening price at the beginning of the window, `close`, USD closing price at the end of the window,  `high`, the highest USD price in a given window, `low`, the lowest USD price in a given window, and `volume`, the total volume traded in a given window. At this endpoint, metrics are calculated by Minute, Hour and Day. ETH Index Price is calculated by taking VWAP(Volume Weighted Average Price) of ETH price data aggregated from all exchanges we provide. The exchanges we provide are as follows.
### Supported Exchanges By Market | Name | Market | Supported Exchanges | |--------|---------|----------------------------| | Spot | `spot` | All Exchange*, Binance, Binance US, Bitfinex, Bittrex, Coinbase Advanced, FTX**, Gemini, HTX Global, Kraken, OKX | | Perpetual | `perpetual` | All Exchange*, Binance, Bitmex, Bybit, Deribit, FTX**, HTX Global, OKX | > (*) Default exchange
> (**) Use in cautions due to the deprecation (no data update) In order to get USD or USDT price of ETH of specific exchange from above (eg. `ethusdt` pair of `binance`), you must specify `market`, `exchange` and `symbol` of ETH pair. For `volume` metric, the unit of volume could be USD, USDT or ETH. This is because exchanges have their own price data policy. All Exchange's `volume` is in ETH. Please refer to volume unit of each exchange from below table.
### Supported Pairs By Exchange #### ◦ Spot | Name | Exchange | Symbol | Volume Unit | Available Since | |----------------|------------------|---------------------------|--------------|-------------------------------| | All Exchange | `all_exchange` | `eth_usd`* | ETH | The earliest time in the exchanges below. | | Binance | `binance` | `eth_usdt`* | ETH | 2017-08-17 04:00:00 | | Binance US | `binance_us` | `eth_usd`*
`eth_usdt` | ETH | 2019-09-18 14:58:00
2019-09-23 08:36:00 | | Bitfinex | `bitfinex` | `eth_usd`*
`eth_usdt` | ETH | 2016-03-09 16:04:00
2019-03-11 10:03:00 | | Bittrex | `bittrex` | `eth_usd`*
`eth_usdt` | USD
USDT | 2018-06-21 02:17:00
2017-04-21 13:30:00 | | Coinbase Advanced | `coinbase_advanced` | `eth_usd`* | ETH | 2016-05-18 00:14:00
| FTX** | `ftx` | `eth_usd`*
`eth_usdt` | USD
USDT | 2019-09-14 21:07:00
2020-03-28 14:40:00 | | Gemini | `gemini` | `eth_usd`* | ETH | 2019-08-30 00:00:00 | | HTX Global | `htx_global` | `eth_usdt`* | ETH | 2019-11-19 00:00:00 | | Kraken | `kraken` | `eth_usd`*
`eth_usdt` | ETH | 2015-08-07 14:03:00
2019-12-19 16:49:00 | | OKX | `okx` | `eth_usdt`* | ETH | 2019-10-01 00:00:00 | #### ◦ Perpetual | Exchange | Exchange Symbol | Pair Symbol | Volume | Historical Starting Point | |----------------|------------------|-------------------------------|-------------------|--------------------------------| | All Exchange | `all_exchange` | `eth_usd`* | ETH | The earliest time in the exchanges below. | | Binance | `binance` | `eth_usd`*
`eth_usdt` | Cont
ETH | 2020-08-11 07:02:00
2019-09-08 17:57:00 | | Bitmex | `bitmex` | `eth_usd`* | Cont | 2015-09-25 12:34:00 | | Bybit | `bybit` | `eth_usd`*
`eth_usdt` | USD
ETH | 2018-11-14 16:00:00
2020-03-25 10:36:00 | | Deribit | `deribit` | `eth_usd`* | USD | 2018-08-14 10:34:00 | | FTX** | `ftx` | `eth_usd`* | USD | 2019-07-20 12:35:00 | | HTX Global | `htx_global` | `eth_usd`*
`eth_usdt` | Cont
ETH | 2020-03-25 09:45:00
2020-10-21 09:08:00 | | OKX | `okx` | `eth_usd`*
`eth_usdt` | Cont
ETH | 2019-03-30 00:00:00
2019-12-25 00:00:00 | > (*) Default exchange
> (**) Use in cautions due to the deprecation (no data update) > We calculate the OHLCV data of a day from the beginning of UTC 00:00:00. > However, the OHLCV data in official sites of HTX and OKX are calculated from the beginning of UTC 16:00:00. > Thus, be aware that there may be some intended discrepancy between those.
### Supported Windows By Market | Market | Supported Windows | |-----------|-------------------------------| | Spot | `min`, `hour`, `day*` | | Perpetual | `min`, `hour`, `day*` | > (*) Default symbol # Taker Buy Sell Stats Source: https://docs.cryptoquant.com/api-reference/eth-market-data/taker-buy-sell-stats /openapi/v1.json get /eth/market-data/taker-buy-sell-stats Taker Buy/Sell Stats represent takers' sentiment of which position they are taking in the market. This metric is calculated with perpetual swap trades in each exchange. `taker_buy_volume` is volume that takers buy. `taker_sell_volume` is volume that takers sell. `taker_total_volume` is the sum of `taker_buy_volume` and `taker_sell_volume`. `taker_buy_ratio` is the ratio of `taker_buy_volume` divided by `taker_total_volume`. `taker_sell_ratio` is the ratio of `taker_sell_volume` divided by `taker_total_volume`. `taker_buy_sell_ratio` is the ratio of `taker_buy_volume` divided by `taker_sell_volume`. Note we unify the unit of return value to USD for each exchange where its contract specification may vary. | Name | Exchange | Symbol | Available Since | |----------------|--------------|------|-----------------------------| | All Exchanges | `all_exchange` | | The earliest time in the exchanges below. | | Binance | `binance` | ETH-USDT | 2019-12-04 00:00:00 | | Bybit | `bybit` | ETH-USD | 2019-12-04 00:00:00 | | Bitmex | `bitmex` | ETH-USD | 2018-09-01 00:00:00 | | Deribit | `deribit` | ETH-PERPETUAL | 2019-09-04 00:00:00 | | HTX Global | `htx_global` | ETH-USD | 2020-04-18 00:00:00 | | OKX | `okx` | ETH-USD | 2019-08-04 00:00:00 | **📖 Data Guide:** [Taker Buy Sell Volume/Ratio](/data-guide/market/taker-buy-sell-volume-ratio) — definition, interpretation, and chart examples. # Estimated Leverage Ratio Source: https://docs.cryptoquant.com/api-reference/eth-market-indicator/estimated-leverage-ratio /openapi/v1.json get /eth/market-indicator/estimated-leverage-ratio By dividing the open interest of an exchange by their ETH reserve, you can estimate a relative average user leverage. Whenever the leverage value reaches a high, there is rapid volatility. Similar to Open Interest, but more accurate because it reflects the growth of the exchange itself. This is experimental indicator but it seems this reflects market sentiment. You can see how aggressive people are and how conservative they are in terms of investment. For 'In Progress' exchanges, estimated leverage ratio is not supported yet even though they provide open interest. __[Go to Data Guide‣](https://dataguide.cryptoquant.com/market-indicators/estimated-leverage-ratio)__ **📖 Data Guide:** [Estimated Leverage Ratio](/data-guide/market/estimated-leverage-ratio) — definition, interpretation, and chart examples. # Addresses Count Source: https://docs.cryptoquant.com/api-reference/eth-network-data/addresses-count /openapi/v1.json get /eth/network-data/addresses-count This endpoint returns metrics relating to the number of used Ethereum addresses. We provide several metrics, `addresses_count_active`, the total number of unique addresses that were active (either sender or receiver) on the blockchain in a given window, `addresses_count_sender`, the number of addresses that were active as a sender, and `addresses_count_receiver`, the number of addresses that were active as a receiver. # Addresses Count All Source: https://docs.cryptoquant.com/api-reference/eth-network-data/addresses-count-all /openapi/v1.json get /eth/network-data/addresses-count-all This endpoint returns metrics related to the number of used Ethereum addresses including internal contract calls. We provide several metrics, `addresses_count_active`, the total number of unique addresses that were active (either sender or receiver) on the blockchain, `addresses_count_sender`, the number of addresses that were active as a sender, and `addresses_count_receiver`, the number of addresses that were active as a receiver. # Base Fee Source: https://docs.cryptoquant.com/api-reference/eth-network-data/base-fee /openapi/v1.json get /eth/network-data/base-fee Base Fee represents the base fee per gas used to burn the fees in Ethereum chain, introduced after London upgrade. `base_fee_mean` is the average value of the base fee per gas over the blocks in Gwei. # Block Bytes Source: https://docs.cryptoquant.com/api-reference/eth-network-data/block-bytes /openapi/v1.json get /eth/network-data/block-bytes The mean size(in bytes) of all blocks generated. # Block Count Source: https://docs.cryptoquant.com/api-reference/eth-network-data/block-count /openapi/v1.json get /eth/network-data/block-count The number of blocks generated in a given window. # Block Interval Source: https://docs.cryptoquant.com/api-reference/eth-network-data/block-interval /openapi/v1.json get /eth/network-data/block-interval The average time between blocks generated displayed in seconds. # Blockreward Source: https://docs.cryptoquant.com/api-reference/eth-network-data/blockreward /openapi/v1.json get /eth/network-data/blockreward The sum of block rewards (including mining or staking rewards and transaction fees). We also provide this value in USD units. # Blockreward Except Uncle Source: https://docs.cryptoquant.com/api-reference/eth-network-data/blockreward-except-uncle /openapi/v1.json get /eth/network-data/blockreward-except-uncle The sum of block rewards except uncle blocks. We also provide this value in USD units. # Contract Calls Count Source: https://docs.cryptoquant.com/api-reference/eth-network-data/contract-calls-count /openapi/v1.json get /eth/network-data/contract-calls-count This endpoint returns metrics related to the number of contract calls including both internal and external calls. # Contract Calls Count External Source: https://docs.cryptoquant.com/api-reference/eth-network-data/contract-calls-count-external /openapi/v1.json get /eth/network-data/contract-calls-count-external This endpoint returns metrics related to the number of external contract calls. # Contract Calls Count Internal Source: https://docs.cryptoquant.com/api-reference/eth-network-data/contract-calls-count-internal /openapi/v1.json get /eth/network-data/contract-calls-count-internal This endpoint returns metrics related to the number of internal contract calls. # Contracts Count Source: https://docs.cryptoquant.com/api-reference/eth-network-data/contracts-count /openapi/v1.json get /eth/network-data/contracts-count This endpoint returns metrics related to the number of contracts. We provide `contracts_created_new` representing the number of contracts created, `contracts_destroyed_new` representing the number of contracts destroyed, and `contracts_count_total` representing the unique number of contracts. # Difficulty Source: https://docs.cryptoquant.com/api-reference/eth-network-data/difficulty /openapi/v1.json get /eth/network-data/difficulty The mean difficulty of mining a new block. # Failed Tokens Transferred Count Source: https://docs.cryptoquant.com/api-reference/eth-network-data/failed-tokens-transferred-count /openapi/v1.json get /eth/network-data/failed-tokens-transferred-count This endpoint returns metrics related to the number of failed transactions with tokens transferred. We provide `failed_tokens_transferred_count_total` metric, the total number of failed transactions with tokens transferred. # Failed Transactions Count Source: https://docs.cryptoquant.com/api-reference/eth-network-data/failed-transactions-count /openapi/v1.json get /eth/network-data/failed-transactions-count This endpoint returns metrics related to the number of failed transactions. We provide `failed_transactions_count_total` metric, the total number of failed transactions. # Fees Source: https://docs.cryptoquant.com/api-reference/eth-network-data/fees /openapi/v1.json get /eth/network-data/fees This endpoint returns the statistics related to fees paid from executing transactions. We provide the following statistics, `fees_total`, the sum of all fees, `fees_block_mean`, the average fee per block, and `fees_reward_percent`, the percentage of fees relative to the total block reward. We provide the metrics in both ETH and USD units. # Fees Burnt Source: https://docs.cryptoquant.com/api-reference/eth-network-data/fees-burnt /openapi/v1.json get /eth/network-data/fees-burnt This endpoint returns the statistics related to fees burnt in Ethereum chain by executing transactions, introduced after London upgrade. We provide the total amount of burnt fees as `fees_burnt_total` in ETH and `fees_burnt_total_usd` in USD units. These metrics have data entries starting post to London upgrade (block height `12965000`, datetime `2021-08-05 12:33:42`). # Fees Burnt Transaction Source: https://docs.cryptoquant.com/api-reference/eth-network-data/fees-burnt-transaction /openapi/v1.json get /eth/network-data/fees-burnt-transaction This endpoint returns the statistics related to fees per transaction burnt in Ethereum chain by executing transactions, introduced after London upgrade. We provide the average amount of burnt fees per transaction as `fees_burnt_transaction_mean` and the median amount as `fees_burnt_transaction_median`. We provide the metrics in both ETH and USD units. These metrics have data entries starting post to London upgrade (block height `12965000`, datetime `2021-08-05 12:33:42`). # Fees Tips Source: https://docs.cryptoquant.com/api-reference/eth-network-data/fees-tips /openapi/v1.json get /eth/network-data/fees-tips This endpoint returns the statistics related to fees directly paid to Ethereum miners, introduced after London upgrade. We provide the total amount of fees as tips as `fees_tips_total` in ETH and `fees_tips_total_usd` in USD units. These metrics have data entries starting post to London upgrade (block height `12965000`, datetime `2021-08-05 12:33:42`). # Fees Tips Transaction Source: https://docs.cryptoquant.com/api-reference/eth-network-data/fees-tips-transaction /openapi/v1.json get /eth/network-data/fees-tips-transaction This endpoint returns the statistics related to fees per transaction directly paid to Ethereum miners, introduced after London upgrade. We provide the average amount of fees tips per transaction as `fees_tips_transaction_mean` and the median amount as `fees_tips_transaction_median`. We provide the metrics in both ETH and USD units. These metrics have data entries starting post to London upgrade (block height `12965000`, datetime `2021-08-05 12:33:42`). # Fees Transaction Source: https://docs.cryptoquant.com/api-reference/eth-network-data/fees-transaction /openapi/v1.json get /eth/network-data/fees-transaction This endpoint returns the statistics related to fees per transaction that are paid from executing transactions. We provide the following statistics, `fees_transaction_mean`, the average fee per transaction, `fees_transaction_median`, the median fee per transaction. We provide the metrics in both ETH and USD units. # Gas Source: https://docs.cryptoquant.com/api-reference/eth-network-data/gas /openapi/v1.json get /eth/network-data/gas This endpoint returns the statistics related to gas used in all transactions. We provide the total amount of gas used as `gas_used_total`, the average amount of gas used as `gas_used_mean`, the average gas price as `gas_price_mean` in Gwei per gas, and the average gas limit as `gas_limit_mean`. # Hashrate Source: https://docs.cryptoquant.com/api-reference/eth-network-data/hashrate /openapi/v1.json get /eth/network-data/hashrate The mean speed at which miners in the network are solving hash problems. It is displayed as hashes (GigaBytes) per second. # Max Fee Source: https://docs.cryptoquant.com/api-reference/eth-network-data/max-fee /openapi/v1.json get /eth/network-data/max-fee Max Fee represents the fee per gas that the user can maximally admit when submitting the transaction, introduced after London upgrade. `max_fee_mean` is the average value of the max fee per gas over the transactions in Gwei. # Max Priority Fee Source: https://docs.cryptoquant.com/api-reference/eth-network-data/max-priority-fee /openapi/v1.json get /eth/network-data/max-priority-fee Max Priority Fee represents the fee per gas used to provide tips (fees) to the miner, introduced after London upgrade. `max_priority_fee_mean` is the average value of the max priority fee per gas over the transactions in Gwei. # Supply Source: https://docs.cryptoquant.com/api-reference/eth-network-data/supply /openapi/v1.json get /eth/network-data/supply This endpoint returns metrics related to Ethereum supply, i.e. the amount of Ethereum in existence. We currently provide two metrics, `supply_total`, the total amount of Ethereum in existence (sum of all Ethereum issued by the block rewards), and `supply_new`, the amount of newly issued tokens in a given window. # Tokens Transferred Source: https://docs.cryptoquant.com/api-reference/eth-network-data/tokens-transferred /openapi/v1.json get /eth/network-data/tokens-transferred This endpoint returns metrics related to the number of tokens transferred, i.e transaction volume. We provide several metrics, `tokens_transferred_total`, the total number of transferred tokens in that window, `tokens_transferred_mean`, the mean of transferred tokens per transaction in that window, and `tokens_transferred_median`, the median of tokens transferred per transaction. We also provide this value in USD units. # Tokens Transferred All Source: https://docs.cryptoquant.com/api-reference/eth-network-data/tokens-transferred-all /openapi/v1.json get /eth/network-data/tokens-transferred-all This endpoint returns metrics related to the number of tokens transferred, i.e transaction volume. Note these metrics include internal contract calls. # Tokens Transferred Between EOA Source: https://docs.cryptoquant.com/api-reference/eth-network-data/tokens-transferred-between-eoa /openapi/v1.json get /eth/network-data/tokens-transferred-between-eoa This endpoint returns metrics related to the number of tokens transferred, i.e transaction volume. Note these metrics include transactions with tokens transferred between externally owned accounts (EOAs). # Tokens Transferred By Contract Calls Source: https://docs.cryptoquant.com/api-reference/eth-network-data/tokens-transferred-by-contract-calls /openapi/v1.json get /eth/network-data/tokens-transferred-by-contract-calls This endpoint returns metrics related to the number of tokens transferred by contract calls including both internal and external calls, i.e transaction volume. # Tokens Transferred By Contract Calls External Source: https://docs.cryptoquant.com/api-reference/eth-network-data/tokens-transferred-by-contract-calls-external /openapi/v1.json get /eth/network-data/tokens-transferred-by-contract-calls-external This endpoint returns metrics related to the number of tokens transferred by external contract calls, i.e transaction volume. # Tokens Transferred By Contract Calls Internal Source: https://docs.cryptoquant.com/api-reference/eth-network-data/tokens-transferred-by-contract-calls-internal /openapi/v1.json get /eth/network-data/tokens-transferred-by-contract-calls-internal This endpoint returns metrics related to the number of tokens transferred by internal contract calls, i.e transaction volume. # Tokens Transferred Count Source: https://docs.cryptoquant.com/api-reference/eth-network-data/tokens-transferred-count /openapi/v1.json get /eth/network-data/tokens-transferred-count This endpoint returns metrics related to the number of tokens transferred executed. We provide several metrics, `tokens_transferred_count_total`, the total number of executed tokens transferred, and `tokens_transferred_count_mean`, the mean number of executed tokens transferred. # Tokens Transferred Count All Source: https://docs.cryptoquant.com/api-reference/eth-network-data/tokens-transferred-count-all /openapi/v1.json get /eth/network-data/tokens-transferred-count-all This endpoint returns metrics related to the number of tokens transferred executed including internal contract calls. # Tokens Transferred Count Between EOA Source: https://docs.cryptoquant.com/api-reference/eth-network-data/tokens-transferred-count-between-eoa /openapi/v1.json get /eth/network-data/tokens-transferred-count-between-eoa This endpoint returns metrics related to the number of tokens transferred executed between externally owned accounts (EOAs). # Tokens Transferred Count By Contract Calls Source: https://docs.cryptoquant.com/api-reference/eth-network-data/tokens-transferred-count-by-contract-calls /openapi/v1.json get /eth/network-data/tokens-transferred-count-by-contract-calls This endpoint returns metrics related to the number of tokens transferred executed by contract calls including both internal and external calls. # Tokens Transferred Count By Contract Calls External Source: https://docs.cryptoquant.com/api-reference/eth-network-data/tokens-transferred-count-by-contract-calls-external /openapi/v1.json get /eth/network-data/tokens-transferred-count-by-contract-calls-external This endpoint returns metrics related to the number of tokens transferred executed by external contract calls. # Tokens Transferred Count By Contract Calls Internal Source: https://docs.cryptoquant.com/api-reference/eth-network-data/tokens-transferred-count-by-contract-calls-internal /openapi/v1.json get /eth/network-data/tokens-transferred-count-by-contract-calls-internal This endpoint returns metrics related to the number of tokens transferred executed by internal contract calls. # Transactions Count Source: https://docs.cryptoquant.com/api-reference/eth-network-data/transactions-count /openapi/v1.json get /eth/network-data/transactions-count This endpoint returns metrics related to the number of transactions. We provide several metrics, `transactions_count_total`, the total number of transactions, `transactions_count_mean`, the mean number of transactions. # Transactions Count All Source: https://docs.cryptoquant.com/api-reference/eth-network-data/transactions-count-all /openapi/v1.json get /eth/network-data/transactions-count-all This endpoint returns metrics related to the number of transactions including internal contract calls. # Transactions Count Between EOA Source: https://docs.cryptoquant.com/api-reference/eth-network-data/transactions-count-between-eoa /openapi/v1.json get /eth/network-data/transactions-count-between-eoa This endpoint returns metrics related to the number of transactions between externally owned accounts (EOAs). # Uncle Block Count Source: https://docs.cryptoquant.com/api-reference/eth-network-data/uncle-block-count /openapi/v1.json get /eth/network-data/uncle-block-count The number of uncle blocks generated in a given window. # Uncle Blockreward Source: https://docs.cryptoquant.com/api-reference/eth-network-data/uncle-blockreward /openapi/v1.json get /eth/network-data/uncle-blockreward The sum of uncle block rewards (including mining or staking rewards and transaction fees). We also provide this value in USD units. # Velocity Source: https://docs.cryptoquant.com/api-reference/eth-network-data/velocity /openapi/v1.json get /eth/network-data/velocity This endpoint returns metrics related to the velocity of Ethereum. Ethereum's velocity is calculated by dividing the trailing 1 year estimated transaction volume(the cumulated sum of transferred tokens) by current supply. Velocity is a metric that explains how actively is money circulating in the market. # Reserve Latency Source: https://docs.cryptoquant.com/api-reference/latency/reserve-latency /openapi/v1.json get /btc/exchange-flows/reserve/latency Reports how fresh this metric's data is. **Append `/latency` to ANY v1 data endpoint** (e.g. `/btc/network-data/hashrate/latency`) to get the same shape for that metric. - `block` — seconds from a block until the data point is **collectable**. - `process` — seconds from a block until the data point is **fully processed and queryable**. - `mutable` — whether already-served values may still be revised. Values are reported per resolution (`block` / `hour` / `day` / `min`) and averaging window. See the [Data Latency guide](/guides/data-latency) for how to read them. # Entity List Source: https://docs.cryptoquant.com/api-reference/stablecoin-entity-status/entity-list /openapi/v1.json get /stablecoin/status/entity-list This endpoint returns entity list to serve data. Please note that `all_token` will return bad request for this endpoint. Make sure to use a specific stablecoin symbol. The meaning of the `market_type` value of the exchange object is as follows. For exchange objects, the `market_type` field tells whether the exchange is a spot exchange or a derivative exchange. Entities without a market type, such as miners or banks, will return 0 for `market_type`. | Exchange Market Type | Description | |------------------------|----------------------| | 0 | Undefined | | 1 | Spot Exchange | | 2 | Derivative Exchange | # Addresses Count Source: https://docs.cryptoquant.com/api-reference/stablecoin-exchange-flows/addresses-count /openapi/v1.json get /stablecoin/exchange-flows/addresses-count This endpoint returns the number of addresses involved in inflow/outflow transactions. **📖 Data Guide:** [Stablecoin Exchange Addresses Count](/data-guide/stablecoin/stablecoin-exchange-addresses-count) — definition, interpretation, and chart examples. # Inflow Source: https://docs.cryptoquant.com/api-reference/stablecoin-exchange-flows/inflow /openapi/v1.json get /stablecoin/exchange-flows/inflow This endpoint returns the inflow of Stablecoin into exchange wallets for as far back as we track. The average inflow is the average transaction value for transactions flowing into exchange wallets on a given day. **📖 Data Guide:** [Stablecoin Exchange In/Outflow & Netflow](/data-guide/stablecoin/stablecoin-exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. # Netflow Source: https://docs.cryptoquant.com/api-reference/stablecoin-exchange-flows/netflow /openapi/v1.json get /stablecoin/exchange-flows/netflow The difference between coins flowing into exchanges and flowing out of exchanges. Netflow usually helps us to figure out an increase of idle coins waiting to be traded in a certain time frame. **📖 Data Guide:** [Stablecoin Exchange In/Outflow & Netflow](/data-guide/stablecoin/stablecoin-exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. # Outflow Source: https://docs.cryptoquant.com/api-reference/stablecoin-exchange-flows/outflow /openapi/v1.json get /stablecoin/exchange-flows/outflow This endpoint returns the outflow of Stablecoin into exchange wallets for as far back as we track. The average outflow is the average transaction value for transactions flowing into exchange wallets on a given day. **📖 Data Guide:** [Stablecoin Exchange In/Outflow & Netflow](/data-guide/stablecoin/stablecoin-exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. # Reserve Source: https://docs.cryptoquant.com/api-reference/stablecoin-exchange-flows/reserve /openapi/v1.json get /stablecoin/exchange-flows/reserve This endpoint returns the full historical on-chain balance of Stablecoin exchanges. **📖 Data Guide:** [Stablecoin Exchange Reserve](/data-guide/stablecoin/stablecoins-exchange-reserve) — definition, interpretation, and chart examples. # Transactions Count Source: https://docs.cryptoquant.com/api-reference/stablecoin-exchange-flows/transactions-count /openapi/v1.json get /stablecoin/exchange-flows/transactions-count This endpoint returns the number of transactions flowing in/out of Stablecoin exchanges. **📖 Data Guide:** [Stablecoin Exchange Transactions Count](/data-guide/stablecoin/stablecoin-exchange-transactions-count) — definition, interpretation, and chart examples. # Exchange Supply Ratio Source: https://docs.cryptoquant.com/api-reference/stablecoin-flow-indicator/exchange-supply-ratio /openapi/v1.json get /stablecoin/flow-indicator/exchange-supply-ratio Exchange Supply Ratio is calculated as exchange reserve divided by total supply. The metric measures how much tokens are reserved in the exchange relative to total supply of the token. **📖 Data Guide:** [Exchange Supply Ratio](/data-guide/exchange/exchange-supply-ratio) — definition, interpretation, and chart examples. # Capitalization Source: https://docs.cryptoquant.com/api-reference/stablecoin-market-data/capitalization /openapi/v1.json get /stablecoin/market-data/capitalization This endpoint returns metrics related to market capitalization. We currently provide market_cap, which is total market capitalization of the token, calculated by multiplying the circulating supply with its USD price(circulating_supply * price_usd_close). **📖 Data Guide:** [Capitalization models](/data-guide/market/capitalization-models) — definition, interpretation, and chart examples. # Price OHLCV Source: https://docs.cryptoquant.com/api-reference/stablecoin-market-data/price-ohlcv /openapi/v1.json get /stablecoin/market-data/price-ohlcv This endpoint returns metrics related to Stablecoin's Index Price. Price OHLCV data consists of five metrics.  `open`, the opening price at the beginning of the window, `close`, USD closing price at the end of the window,  `high`, the highest USD price in a given window, `low`, the lowest USD price in a given window, and `volume`, the total token volume traded in a given window. At this endpoint, metrics are calculated by Minute, Hour and Day. Stablecoin Index Price is calculated by taking VWAP(Volume Weighted Average Price) of Stablecoin price data aggregated from global exchanges. You can check supported exchanges [here](https://www.notion.so/cqlive/Stablecoins-ERC20-Exchange-List-e33b9baeae094fb090983dc1e1183b05). # Addresses Count Source: https://docs.cryptoquant.com/api-reference/stablecoin-network-data/addresses-count /openapi/v1.json get /stablecoin/network-data/addresses-count This endpoint returns metrics relating to the number of used addresses to transfer the token. We provide several metrics, `addresses_active_count`, the total number of unique addresses that were active (either sender or receiver) on the blockchain in a given window, `addresses_active_sender_count`, the number of addresses that were active as a sender, `addresses_active_receiver_count`, the number of addresses that were active as a receiver. **📖 Data Guide:** [Stablecoin Network Data](/data-guide/stablecoin/stablecoin-network-data) — definition, interpretation, and chart examples. # Events Count Source: https://docs.cryptoquant.com/api-reference/stablecoin-network-data/events-count /openapi/v1.json get /stablecoin/network-data/events-count This endpoint returns metrics related to the number of events. We provide several metrics. events_mint_count, events_issue_count, events_burn_count and events_redeem_count are metrics that represent the number of events related to each actions (mint, issue, burn, redeem). For further information about the actions, please refer to the section Stablecoin Issuing Mechanism. **📖 Data Guide:** [Stablecoin Network Data](/data-guide/stablecoin/stablecoin-network-data) — definition, interpretation, and chart examples. # Supply Source: https://docs.cryptoquant.com/api-reference/stablecoin-network-data/supply /openapi/v1.json get /stablecoin/network-data/supply This endpoint returns metrics related to token supply, i.e. the amount of tokens in existence. We currently provide six metrics. supply_total is the total amount of tokens in existence, and supply_circulating is an approximation of the amount of tokens that are circulating in the market(e.g. excluding tokens owned by the issuing company's treasury address). supply_minted and supply_burned represents how many tokens were added/subtracted from supply_total. supply_issued and supply_redeemed represents how many tokens were added/subtracted from supply_circulating. For some tokens, mint and issue(or redeem and burn) occurs simultaneously, and for others this does not. For further information, please refer to the section 'Stablecoin Issuing Mechanism'. **📖 Data Guide:** [Stablecoin Network Data](/data-guide/stablecoin/stablecoin-network-data) — definition, interpretation, and chart examples. # Tokens Transferred Source: https://docs.cryptoquant.com/api-reference/stablecoin-network-data/tokens-transferred /openapi/v1.json get /stablecoin/network-data/tokens-transferred This endpoint returns metrics related to the number of tokens transferred, i.e transaction volume. We provide several metrics, `tokens_transferred_total`, the total number of transferred tokens, and `tokens_transferred_mean`, the mean tokens transferred per transaction. **📖 Data Guide:** [Stablecoin Network Data](/data-guide/stablecoin/stablecoin-network-data) — definition, interpretation, and chart examples. # Sunpump Tokens Source: https://docs.cryptoquant.com/api-reference/trx-defi/sunpump-tokens /openapi/v1.json get /trx/defi/sunpump-tokens This endpoint returns metrics related to SunPump token creation on TRON. | Metric | Description | |--------|-------------| | `token_create_event_count` | The total number of tokens that have been created on the SunPump platform. | | `cumulative_count_create_events` | The cumulative number of token creation events on SunPump over time. | # Sunswap Activity Source: https://docs.cryptoquant.com/api-reference/trx-defi/sunswap-activity /openapi/v1.json get /trx/defi/sunswap-activity This endpoint returns metrics related to Sunswap activity on TRON. | Metric | Description | |--------|-------------| | `total_transaction_count` | The total number of transactions on Sunswap. | | `wtrx_transaction_count` | The number of transactions involving WTRX in the given window. | | `other_transaction_count` | The number of transactions involving other tokens in the given window. | | `wtrx_dominance` | The dominance of WTRX in the total transaction volume in the given window. | | `wtrx_amount` | The total amount of WTRX traded in the given window. | | `wtrx_amount_usd` | The total amount of WTRX traded in USD in the given window. | # Capitalization Source: https://docs.cryptoquant.com/api-reference/trx-market-data/capitalization /openapi/v1.json get /trx/market-data/capitalization This endpoint returns metrics related to market capitalization.
We provide `market_cap`, which is total market capitalization of TRX, calculated by multiplying the total supply with its USD price.
__[Go to Data Guide‣](https://userguide.cryptoquant.com/cryptoquant-metrics/market/capitalization-models)__ **📖 Data Guide:** [Capitalization models](/data-guide/market/capitalization-models) — definition, interpretation, and chart examples. # Price OHLCV Source: https://docs.cryptoquant.com/api-reference/trx-market-data/price-ohlcv /openapi/v1.json get /trx/market-data/price-ohlcv This endpoint returns metrics related to TRX's Price, Price OHLCV data consists of five metrics.
| Metric | Description | |--------|-------------| | `open` | The opening price at the beginning of the window. | | `close` | The USD closing price at the end of the window. | | `high` | The highest USD price in a given window. | | `low` | The lowest USD price in a given window. | | `volume` | The total volume traded in a given window. | > (*) Default exchange
### Supported Exchanges By Market | Name | Market | Supported Exchanges | |--------|---------|----------------------------| | Spot | `spot` | All Exchange* | ### Supported Pairs By Exchange | Name | Exchange | Symbol | |----------------|----------------|------------| | All Exchanges | `all_exchange` | `trx_usd`* | ### Supported Windows By Market | Market | Supported Windows | |-----------|-----------------------| | Spot | `day*` | # Addresses Count Source: https://docs.cryptoquant.com/api-reference/trx-network-data/addresses-count /openapi/v1.json get /trx/network-data/addresses-count This endpoint returns metrics relating to the number of used TRX addresses. | Metric | Description | |--------|-------------| | `addresses_count_active` | The total number of unique addresses that were active (either sender or receiver) on the blockchain in a given window. | | `addresses_count_sender` | The number of addresses that were active as a sender. | | `addresses_count_receiver` | The number of addresses that were active as a receiver. | # Block Count Source: https://docs.cryptoquant.com/api-reference/trx-network-data/block-count /openapi/v1.json get /trx/network-data/block-count The number of blocks generated in a given window. # Energy Stake Source: https://docs.cryptoquant.com/api-reference/trx-network-data/energy-stake /openapi/v1.json get /trx/network-data/energy-stake This endpoint returns the statistics related to the amount of TRX staked for Energy. | Metric | Description | |--------|-------------| | `total_energy_weight` | The total amount of TRX staked for Energy. | | `energy_rate` | The percentage of TRX staked for Energy. | # Fees Source: https://docs.cryptoquant.com/api-reference/trx-network-data/fees /openapi/v1.json get /trx/network-data/fees This endpoint returns the statistics related to fees paid from executing transactions | Metric | Description | |--------|-------------| | `fees_total` | The sum of all fees paid from executing transactions. | | `fees_total_usd` | The sum of all fees paid from executing transactions, calculated in USD. | | `fees_block_mean` | The average fee per block. | | `fees_block_mean_usd` | The average fee per block, calculated in USD. | # Staking Rate Source: https://docs.cryptoquant.com/api-reference/trx-network-data/staking-rate /openapi/v1.json get /trx/network-data/staking-rate This endpoint returns the staking rate of TRX. | Metric | Description | |--------|-------------| | `staking_rate` | The staking rate of TRX. | # Supply Source: https://docs.cryptoquant.com/api-reference/trx-network-data/supply /openapi/v1.json get /trx/network-data/supply This endpoint returns the metrics related to the supply of TRX. | Metric | Description | |--------|-------------| | `supply_total` | The total amount of tokens in existence. | | `supply_circulating` | The amount of tokens that are circulating in the market. | | `supply_minted` | The amount of tokens minted in the given window. | | `supply_burned` | The amount of tokens burned in the given window. | | `supply_staked` | The amount of tokens staked in Tron Super Representative members. | # Tokens Transferred Source: https://docs.cryptoquant.com/api-reference/trx-network-data/tokens-transferred /openapi/v1.json get /trx/network-data/tokens-transferred This endpoint returns metrics related to the number of tokens transferred. | Metric | Description | |--------|-------------| | `tokens_transferred_total` | The total number of transferred tokens in that window. | | `tokens_transferred_mean` | The mean of transferred tokens per transaction in that window. | | `tokens_transferred_median` | The median of tokens transferred per transaction in that window. | # Total Value Staked Source: https://docs.cryptoquant.com/api-reference/trx-network-data/total-value-staked /openapi/v1.json get /trx/network-data/total-value-staked This endpoint returns the total amount of TRX staked by staking model. (Stake 1.0, Stake 2.0) This metric reflects how much TRX has been locked to secure the network and obtain resources or staking rewards. | Metric | Description | |--------|-------------| | `v1_staking_amount` | The amount of TRX staked under Stake 1.0. (The legacy staking model on TRON) | | `v2_staking_amount` | The amount of TRX staked under Stake 2.0. (The newer staking model on TRON) | # TPS Source: https://docs.cryptoquant.com/api-reference/trx-network-data/tps /openapi/v1.json get /trx/network-data/tps This endpoint returns the statistics related to the number of transactions per second. | Metric | Description | |--------|-------------| | `tps` | The number of transactions per second. | # Transactions Count Source: https://docs.cryptoquant.com/api-reference/trx-network-data/transactions-count /openapi/v1.json get /trx/network-data/transactions-count This endpoint returns metrics related to the number of transactions. | Metric | Description | |--------|-------------| | `transactions_count_total` | The total number of transactions. | | `transactions_count_mean` | The mean number of transactions. | # Fee Source: https://docs.cryptoquant.com/api-reference/xrp-amm-data/fee /openapi/v1.json get /xrp/amm-data/fee This endpoint returns the trading fee on AMM. Currently, we only cover non-XRP/XRP pairs. # Liquidity Source: https://docs.cryptoquant.com/api-reference/xrp-amm-data/liquidity /openapi/v1.json get /xrp/amm-data/liquidity This endpoint returns the total amount of liquidity on AMM. Currently, we only cover non-XRP/XRP pairs. # Price Source: https://docs.cryptoquant.com/api-reference/xrp-amm-data/price /openapi/v1.json get /xrp/amm-data/price This endpoint returns XRP exchange rate on AMM. Currently, we only cover non-XRP/XRP pairs. # Swap Statistics Source: https://docs.cryptoquant.com/api-reference/xrp-amm-data/swap-statistics /openapi/v1.json get /xrp/amm-data/swap-stats This endpoint returns the swap statistics on AMM. Currently, we only cover non-XRP/XRP pairs. # Liquidity Source: https://docs.cryptoquant.com/api-reference/xrp-dex-data/liquidity /openapi/v1.json get /xrp/dex-data/liquidity USD Liquidity in DEX # Transaction count Source: https://docs.cryptoquant.com/api-reference/xrp-dex-data/transaction-count /openapi/v1.json get /xrp/dex-data/transactions-count XRP transaction count traded on XRPL DEX # Volume Source: https://docs.cryptoquant.com/api-reference/xrp-dex-data/volume /openapi/v1.json get /xrp/dex-data/volume XRP volume traded on XRPL DEX # XRP DEX Price Source: https://docs.cryptoquant.com/api-reference/xrp-dex-data/xrp-dex-price /openapi/v1.json get /xrp/dex-data/dex-price Price of XRP traded on DEX # Addresses Count Source: https://docs.cryptoquant.com/api-reference/xrp-entity-flows/addresses-count /openapi/v1.json get /xrp/entity-flows/addresses-count This endpoint returns the number of addresses involved in inflow/outflow transactions. # Inflow Source: https://docs.cryptoquant.com/api-reference/xrp-entity-flows/inflow /openapi/v1.json get /xrp/entity-flows/inflow This endpoint returns the inflow of XRP into entity address for as far back as we track. # Outflow Source: https://docs.cryptoquant.com/api-reference/xrp-entity-flows/outflow /openapi/v1.json get /xrp/entity-flows/outflow This endpoint returns the outflow of XRP out of entity address for as far back as we track. # Reserve Source: https://docs.cryptoquant.com/api-reference/xrp-entity-flows/reserve /openapi/v1.json get /xrp/entity-flows/reserve This endpoint returns the full historical on-chain balance of xrp ledger entities. # Share Source: https://docs.cryptoquant.com/api-reference/xrp-entity-flows/share /openapi/v1.json get /xrp/entity-flows/share This metric is calculated by dividing XRP holdings of the entity by the total supply # Transactions Count Source: https://docs.cryptoquant.com/api-reference/xrp-entity-flows/transactions-count /openapi/v1.json get /xrp/entity-flows/transactions-count This endpoint returns the number of transactions flowing in/out of XRP Entities. # Whale Movements Source: https://docs.cryptoquant.com/api-reference/xrp-entity-flows/whale-movements /openapi/v1.json get /xrp/entity-flows/whale-movements This endpoint returns the number of transactions involved in inflow/outflow transactions and the transfer volume # Entity List Source: https://docs.cryptoquant.com/api-reference/xrp-entity-status/entity-list /openapi/v1.json get /xrp/entity-status/entity-list This endpoint returns entity list to serve data. | Entity Type | Description | |------------------------|----------------------| | exchange | centralized exchange | | builder | entities contributing to xrp ledger | | team | xrp project related team or related individuals| | foundation | xrp foundation | | custody | custody service | | otc | otc service | | bank | bank | | bridge | bridge | # Exchange Inflow Count Value Distribution Source: https://docs.cryptoquant.com/api-reference/xrp-flow-indicator/exchange-inflow-count-value-distribution /openapi/v1.json get /xrp/flow-indicator/exchange-inflow-count-value-distribution Exchange Inflow Count Value Distribution is a metric that shows the number of transactions of xrp tokens flowed into exchange wallets according to its value segment. # Exchange Inflow Value Distribution Source: https://docs.cryptoquant.com/api-reference/xrp-flow-indicator/exchange-inflow-value-distribution /openapi/v1.json get /xrp/flow-indicator/exchange-inflow-value-distribution Exchange Inflow Value Distribution is a metric that shows the amount distribution of xrp tokens flowed into exchange wallets according to its value. # Exchange Outflow Count Value Distribution Source: https://docs.cryptoquant.com/api-reference/xrp-flow-indicator/exchange-outflow-count-value-distribution /openapi/v1.json get /xrp/flow-indicator/exchange-outflow-count-value-distribution Exchange Outflow Count Value Distribution is a metric that shows the number of transactions of xrp tokens flowed into exchange wallets according to its value segment. # Exchange Outflow Value Distribution Source: https://docs.cryptoquant.com/api-reference/xrp-flow-indicator/exchange-outflow-value-distribution /openapi/v1.json get /xrp/flow-indicator/exchange-outflow-value-distribution Exchange Outflow Value Distribution is a metric that shows the amount distribution of xrp tokens flowed out from exchange wallets according to its value. # Exchange Supply Ratio Source: https://docs.cryptoquant.com/api-reference/xrp-flow-indicator/exchange-supply-ratio /openapi/v1.json get /xrp/flow-indicator/exchange-supply-ratio The ratio of exchange's xrp reserve compared to total supply of xrp. **📖 Data Guide:** [Exchange Supply Ratio](/data-guide/exchange/exchange-supply-ratio) — definition, interpretation, and chart examples. # Capitalization Source: https://docs.cryptoquant.com/api-reference/xrp-market-data/capitalization /openapi/v1.json get /xrp/market-data/capitalization This endpoint returns metrics related to market capitalization. First, we provide `market_cap`, which is total market capitalization of XRP, calculated by multiplying the total supply with its USD price. __[Go to Data Guide‣](https://userguide.cryptoquant.com/cryptoquant-metrics/market/capitalization-models)__ **📖 Data Guide:** [Capitalization models](/data-guide/market/capitalization-models) — definition, interpretation, and chart examples. # Estimated Leverage Ratio Source: https://docs.cryptoquant.com/api-reference/xrp-market-data/estimated-leverage-ratio /openapi/v1.json get /xrp/market-data/estimated-leverage-ratio Estimated Leverage Ratio indicates how much leverage is used by users on average. It is defined as the ratio of open interest divided by the reserve of an exchange. This information measures traders' sentiment whether they take a high risk or low risk. __[Go to User Guide‣](https://userguide.cryptoquant.com/cryptoquant-metrics/market/estimated-leverage-ratio)__
> **Note:** This endpoint does not support Point-In-Time (PIT) accuracy due to periodic updates to wallet address clustering. Historical data may change as new exchange wallets are discovered, added, and validated.
**📖 Data Guide:** [Estimated Leverage Ratio](/data-guide/market/estimated-leverage-ratio) — definition, interpretation, and chart examples. # Funding Rates Source: https://docs.cryptoquant.com/api-reference/xrp-market-data/funding-rates /openapi/v1.json get /xrp/market-data/funding-rates Funding rates represents traders' sentiments of which position they bet on in perpetual swaps market. Positive funding rates implies that many traders are bullish and long traders pay funding to short traders. Negative funding rates implies many traders are bearish and short traders pay funding to long traders. | Name | Exchange | Symbol | |----------------|--------------|----| | All Exchanges | `all_exchange` |`all_symbol`*| | Binance | `binance` | `xrp_usdt`
`xrp_usd`
`all_symbol`* | | Bybit | `bybit` | `xrp_usdt`
`xrp_usd`
`all_symbol`* | | Bitmex | `bitmex` | `xrp_usd`* | | HTX Global | `htx_global` | `xrp_usd`* | | OKX | `okx` | `xrp_usdt`
`xrp_usd`
`all_symbol`* | **📖 Data Guide:** [Funding Rates](/data-guide/market/funding-rates) — definition, interpretation, and chart examples. # Liquidations Source: https://docs.cryptoquant.com/api-reference/xrp-market-data/liquidations /openapi/v1.json get /xrp/market-data/liquidations Liquidations are sum of forced market orders to exit leveraged positions caused by price volatility. Liquidations indicate current price volatility and traders' sentiment which side they had been betting. Note that Binance's liquidation data collection policy has changed since [2021-04-27](https://binance-docs.github.io/apidocs/futures/en/#change-log), which makes the distribution of the data has changed after that. | Name | Exchange | Symbol | |----------------|--------------|----| | All Exchanges | `all_exchange` |`all_symbol`* | | Binance | `binance` | `xrp_usdt`
`xrp_usd`
`all_symbol`* | | Bybit | `bybit` | `xrp_usdt`
`xrp_usd`
`all_symbol`*| | Bitmex | `bitmex` | `xrp_usd`* | | HTX Global | `htx_global` | `xrp_usdt`*| | OKX | `okx` | `xrp_usdt`
`xrp_usd`
`all_symbol`*| | Bitfinex | `bitfinex` | `xrp_usdt`* | # Open Interest Source: https://docs.cryptoquant.com/api-reference/xrp-market-data/open-interest /openapi/v1.json get /xrp/market-data/open-interest This endpoint returns XRP Perpetual Open Interest from derivative exchanges. | Name | Exchange | Symbol | |----------------|--------------|----| | All Exchanges | `all_exchange` | `all_symbol`* | | Binance | `binance` | `xrp_usdt`
`xrp_usd`
`all_symbol`*| | Bybit | `bybit` | `xrp_usdt`
`xrp_usd`
`all_symbol`*| | Bitmex | `bitmex` | `xrp_usd`* | | HTX Global | `htx_global` | `xrp_usdt`* | | Kraken | `kraken` | `xrp_usd`* | | OKX | `okx` | `xrp_usdt`
`xrp_usd`
`all_symbol`* | | Bitfinex | `bitfinex` | `xrp_usdt`* | Supported exchanges for Open Interest are available in Discovery section. Note we unify the unit of return value to USD for each exchange where its contract specification may vary. **📖 Data Guide:** [Open Interest](/data-guide/market/open-interest) — definition, interpretation, and chart examples. # Price OHLCV Source: https://docs.cryptoquant.com/api-reference/xrp-market-data/price-ohlcv /openapi/v1.json get /xrp/market-data/price-ohlcv This endpoint returns metrics related to XRP's Price. Price OHLCV data consists of five metrics.  `open`, the opening price at the beginning of the window, `close`, USD closing price at the end of the window,  `high`, the highest USD price in a given window, `low`, the lowest USD price in a given window, and `volume`, the total token volume traded in 24h. ### Supported Exchanges By Market | Name | Market | Supported Exchanges | |--------|---------|----------------------------| | Spot | `spot` | All Exchange*, Binance, Binance US, Bitfinex, Kucoin, Coinbase Advanced, Kraken, HTX Global | | Perpetual | `perpetual` | All Exchange*, Binance, Deribit, Bitmex, OKX | > (*) Default exchange
### Supported Pairs By Exchange #### ◦ Spot | Name | Exchange | Symbol | |----------------|--------------|----| | All Exchanges | `all_exchange` | `xrp_usd`* | | Binance | `binance` | `xrp_usdt`*
`xrp_fdusd`
`xrp_btc`
`xrp_eth`
`xrp_bnb`
`xrp_rub`
`xrp_tusd`| | Binance US | `binance_us` | `xrp_usdt`* | | Coinbase Advanced | `coinbase_advanced` | `xrp_eur`
`xrp_usdt`
`xrp_usd`* | | Bitfinex | `bitfinex` | `xrp_usdt`
`xrp_btc`
`xrp_usd`* | | HTX Global | `htx_global` | `xrp_usdt`* | | Kucoin | `kucoin` | `xrp_usdc`
`xrp_tusd`
`xrp_btc`
`xrp_eth`
`xrp_usdt`* | | Kraken | `kraken` | `xrp_usdt`
`xrp_eur`
`xrp_aud`
`xrp_eth`
`xrp_btc`
`xrp_usd`* | #### ◦ Perpetual | Name | Exchange | Symbol | |----------------|--------------|----| | All Exchanges | `all_exchange` | `xrp_usd`*
`xrp_usdt`| | Binance | `binance` | `xrp_usd`*| | Deribit | `deribit` | `xrp_usdc`* | | Okx | `okx` | `xrp_usdt`* | | Bitmex | `bitmex` | `xrp_usdt`
`xrp_usd`* | ### Supported Windows By Market | Market | Supported Windows | |-----------|-------------------------------| | Spot | `min`, `hour`, `day*` | | Perpetual | `min`, `hour`, `day*` | # Taker Buy Sell Stats Source: https://docs.cryptoquant.com/api-reference/xrp-market-data/taker-buy-sell-stats /openapi/v1.json get /xrp/market-data/taker-buy-sell-stats Taker Buy/Sell Stats represent takers' sentiment of which position they are taking in the market. This metric is calculated with perpetual swap trades in each exchange. `taker_buy_volume` is volume that takers buy. `taker_sell_volume` is volume that takers sell. `taker_total_volume` is the sum of `taker_buy_volume` and `taker_sell_volume`. `taker_buy_ratio` is the ratio of `taker_buy_volume` divided by `taker_total_volume`. `taker_sell_ratio` is the ratio of `taker_sell_volume` divided by `taker_total_volume`. `taker_buy_sell_ratio` is the ratio of `taker_buy_volume` divided by `taker_sell_volume`. Note we unify the unit of return value to USD for each exchange where its contract specification may vary. | Name | Exchange | Symbol | |----------------|--------------|----| | All Exchanges | `all_exchange` | `all_symbol`* | | Binance | `binance` | `xrp_usdt`* | | Bybit | `bybit` | `xrp_usd`* | | Bitmex | `bitmex` | `xrp_usd`* | | HTX Global | `htx_global` | `xrp_usd`* | | OKX | `okx` | `xrp_usd`* | **📖 Data Guide:** [Taker Buy Sell Volume/Ratio](/data-guide/market/taker-buy-sell-volume-ratio) — definition, interpretation, and chart examples. # Addresses Count Source: https://docs.cryptoquant.com/api-reference/xrp-network-data/addresses-count /openapi/v1.json get /xrp/network-data/addresses-count This endpoint returns metrics relating to the number of used XRP addresses. | Metric | Description | |--------|-------------| | `addresses_count_active` | The total number of unique addresses that were active (either sender or receiver) on the blockchain in a given window. | | `addresses_count_sender` | The number of addresses that were active as a sender. | | `addresses_count_receiver` | The number of addresses that were active as a receiver. | # Block Interval Source: https://docs.cryptoquant.com/api-reference/xrp-network-data/block-interval /openapi/v1.json get /xrp/network-data/block-interval The average time between blocks generated displayed in seconds. # Fees Source: https://docs.cryptoquant.com/api-reference/xrp-network-data/fees /openapi/v1.json get /xrp/network-data/fees This endpoint returns the fees of xrpl chain # Ledger Count Source: https://docs.cryptoquant.com/api-reference/xrp-network-data/ledger-count /openapi/v1.json get /xrp/network-data/ledger-count The number of ledgers(XRPL version of 'block') created # Supply Source: https://docs.cryptoquant.com/api-reference/xrp-network-data/supply /openapi/v1.json get /xrp/network-data/supply This endpoint returns total supply of XRP. # Tokens Transferred Source: https://docs.cryptoquant.com/api-reference/xrp-network-data/tokens-transferred /openapi/v1.json get /xrp/network-data/tokens-transferred This endpoint returns metrics the number of tokens transferred. # Transactions Count Source: https://docs.cryptoquant.com/api-reference/xrp-network-data/transactions-count /openapi/v1.json get /xrp/network-data/transactions-count This endpoint returns metrics the total number of transactions. # Velocity Source: https://docs.cryptoquant.com/api-reference/xrp-network-data/velocity /openapi/v1.json get /xrp/network-data/velocity Velocity measures how quickly units circulate in the network. It is calculated by dividing on-chain transaction volume by market cap, effectively being the inverse of the NVT Ratio. # XRP Burnt Source: https://docs.cryptoquant.com/api-reference/xrp-network-data/xrp-burnt /openapi/v1.json get /xrp/network-data/xrp-burnt The amount of burnt XRP # NVT Source: https://docs.cryptoquant.com/api-reference/xrp-network-indicator/nvt /openapi/v1.json get /xrp/network-indicator/nvt NVT(Network Value to Transaction) ratio is the network value(`supply_total` * `price_usd`) divided by `tokens_transferred_total`. `nvt` is a metric often used to determine whether the price is overvalued or not. The theory behind this indicator is that the value of the token depends on how actively transactions take place on the network. **📖 Data Guide:** [NVT Ratio](/data-guide/network/nvt-ratio) — definition, interpretation, and chart examples. # Altcoins Source: https://docs.cryptoquant.com/catalog/alt All Altcoins metrics available in the CryptoQuant API — endpoints, parameters, response fields, and data latency. > Machine-readable version of this catalog: [catalog.json](/catalog/catalog.json) Each section lists its metrics; open **Data latency** under a section to see the block and process delay per resolution — see [how latency works](/guides/data-latency). ## Market Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Price OHLCV](/api-reference/alt-market-data/price-ohlcv) | `/alt/market-data/price-ohlcv` | `token` | `date` `datetime` `open` `high` `low` `close` `volume` | > [accordion] Data latency > > [Price OHLCV](/api-reference/alt-market-data/price-ohlcv)`/alt/market-data/price-ohlcv` > > > [tab] Day > > > > Windowblock?process?7day—281.55s30day—276.88s > > > [tab] Hour > > > > Windowblock?process?24hour—295.47s168hour—271.10s > > > [tab] Minute > > > > Windowblock?process?10min—235.68s60min—232.35s > > Mutable: no · measured 2026-11-10 # Bitcoin (BTC) Source: https://docs.cryptoquant.com/catalog/btc All BTC metrics available in the CryptoQuant API — endpoints, parameters, response fields, and data latency. > Machine-readable version of this catalog: [catalog.json](/catalog/catalog.json) Each section lists its metrics; open **Data latency** under a section to see the block and process delay per resolution — see [how latency works](/guides/data-latency). ## Entity Status | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Entity List](/api-reference/btc-entity-status/entity-list) | `/btc/status/entity-list` | `type` | `name` `symbol` `is_validated` `market_type` | ## Exchange Flows | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Reserve](/api-reference/btc-exchange-flows/reserve) | `/btc/exchange-flows/reserve` | `exchange` | `blockheight` `date` `datetime` `reserve` `reserve_usd` | | [Netflow](/api-reference/btc-exchange-flows/netflow) | `/btc/exchange-flows/netflow` | `exchange` | `blockheight` `date` `datetime` `netflow_total` | | [Inflow](/api-reference/btc-exchange-flows/inflow) | `/btc/exchange-flows/inflow` | `exchange` | `blockheight` `date` `datetime` `inflow_total` `inflow_top10` `inflow_mean` | | [Outflow](/api-reference/btc-exchange-flows/outflow) | `/btc/exchange-flows/outflow` | `exchange` | `blockheight` `date` `datetime` `outflow_total` `outflow_top10` `outflow_mean` | | [Transactions Count](/api-reference/btc-exchange-flows/transactions-count) | `/btc/exchange-flows/transactions-count` | `exchange` | `blockheight` `date` `datetime` `transactions_count_inflow` `transactions_count_outflow` | | [Addresses Count](/api-reference/btc-exchange-flows/addresses-count) | `/btc/exchange-flows/addresses-count` | `exchange` | `blockheight` `date` `datetime` `addresses_count_inflow` `addresses_count_outflow` | | [In-House Flow](/api-reference/btc-exchange-flows/in-house-flow) | `/btc/exchange-flows/in-house-flow` | `exchange` | `blockheight` `date` `datetime` `flow_total` `flow_mean` `transactions_count_flow` | > [accordion] Data latency > > [Reserve](/api-reference/btc-exchange-flows/reserve)`/btc/exchange-flows/reserve` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,837.30s30day643.03s1,827.49s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,754.65s168hour657.81s1,740.47s > > > [tab] Block > > > > Windowblock?process?10min671.50s1,028.00s60min696.67s1,042.67s > > Mutable: yes · measured 2026-07-08 > > [Netflow](/api-reference/btc-exchange-flows/netflow)`/btc/exchange-flows/netflow` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,837.30s30day643.03s1,827.49s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,754.65s168hour657.81s1,740.47s > > > [tab] Block > > > > Windowblock?process?10min671.50s1,028.00s60min696.67s1,042.67s > > Mutable: yes · measured 2026-07-08 > > [Inflow](/api-reference/btc-exchange-flows/inflow)`/btc/exchange-flows/inflow` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,837.30s30day643.03s1,827.49s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,754.65s168hour657.81s1,740.47s > > > [tab] Block > > > > Windowblock?process?10min671.50s1,028.00s60min696.67s1,042.67s > > Mutable: yes · measured 2026-07-08 > > [Outflow](/api-reference/btc-exchange-flows/outflow)`/btc/exchange-flows/outflow` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,837.30s30day643.03s1,827.49s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,754.65s168hour657.81s1,740.47s > > > [tab] Block > > > > Windowblock?process?10min671.50s1,028.00s60min696.67s1,042.67s > > Mutable: yes · measured 2026-07-08 > > [Transactions Count](/api-reference/btc-exchange-flows/transactions-count)`/btc/exchange-flows/transactions-count` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,837.30s30day643.03s1,827.49s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,754.65s168hour657.81s1,740.47s > > > [tab] Block > > > > Windowblock?process?10min671.50s1,028.00s60min696.67s1,042.67s > > Mutable: yes · measured 2026-07-08 > > [Addresses Count](/api-reference/btc-exchange-flows/addresses-count)`/btc/exchange-flows/addresses-count` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,837.30s30day643.03s1,827.49s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,754.65s168hour657.81s1,740.47s > > > [tab] Block > > > > Windowblock?process?10min671.50s1,028.00s60min696.67s1,042.67s > > Mutable: yes · measured 2026-07-08 > > [In-House Flow](/api-reference/btc-exchange-flows/in-house-flow)`/btc/exchange-flows/in-house-flow` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,837.30s30day643.03s1,827.49s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,754.65s168hour657.81s1,740.47s > > > [tab] Block > > > > Windowblock?process?10min671.50s1,028.00s60min696.67s1,042.67s > > Mutable: yes · measured 2026-07-08 ## Miner Flows | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Reserve](/api-reference/btc-miner-flows/reserve) | `/btc/miner-flows/reserve` | `miner` | `blockheight` `date` `datetime` `reserve` `reserve_usd` | | [Netflow](/api-reference/btc-miner-flows/netflow) | `/btc/miner-flows/netflow` | `miner` | `blockheight` `date` `datetime` `netflow_total` | | [Inflow](/api-reference/btc-miner-flows/inflow) | `/btc/miner-flows/inflow` | `miner` | `blockheight` `date` `datetime` `inflow_total` `inflow_top10` `inflow_mean` | | [Outflow](/api-reference/btc-miner-flows/outflow) | `/btc/miner-flows/outflow` | `miner` | `blockheight` `date` `datetime` `outflow_total` `outflow_top10` `outflow_mean` | | [Transactions Count](/api-reference/btc-miner-flows/transactions-count) | `/btc/miner-flows/transactions-count` | `miner` | `blockheight` `date` `datetime` `transactions_count_inflow` `transactions_count_outflow` | | [Addresses Count](/api-reference/btc-miner-flows/addresses-count) | `/btc/miner-flows/addresses-count` | `miner` | `blockheight` `date` `datetime` `addresses_count_inflow` `addresses_count_outflow` | | [In-House Flow](/api-reference/btc-miner-flows/in-house-flow) | `/btc/miner-flows/in-house-flow` | `miner` | `blockheight` `date` `datetime` `flow_total` `flow_mean` `transactions_count_flow` | > [accordion] Data latency > > [Reserve](/api-reference/btc-miner-flows/reserve)`/btc/miner-flows/reserve` > > > [tab] Day > > > > Windowblock?process?7day386.86s1,845.76s30day644.70s1,806.66s > > > [tab] Hour > > > > Windowblock?process?24hour838.22s1,685.00s168hour614.62s1,721.80s > > > [tab] Block > > > > Windowblock?process?10min757.00s940.50s60min503.14s1,086.14s > > Mutable: yes · measured 2026-07-07 > > [Netflow](/api-reference/btc-miner-flows/netflow)`/btc/miner-flows/netflow` > > > [tab] Day > > > > Windowblock?process?7day386.86s1,845.76s30day644.70s1,806.66s > > > [tab] Hour > > > > Windowblock?process?24hour838.22s1,685.00s168hour614.62s1,721.80s > > > [tab] Block > > > > Windowblock?process?10min757.00s940.50s60min503.14s1,086.14s > > Mutable: yes · measured 2026-07-07 > > [Inflow](/api-reference/btc-miner-flows/inflow)`/btc/miner-flows/inflow` > > > [tab] Day > > > > Windowblock?process?7day386.86s1,845.76s30day644.70s1,806.66s > > > [tab] Hour > > > > Windowblock?process?24hour838.22s1,685.00s168hour614.62s1,721.80s > > > [tab] Block > > > > Windowblock?process?10min757.00s940.50s60min503.14s1,086.14s > > Mutable: yes · measured 2026-07-07 > > [Outflow](/api-reference/btc-miner-flows/outflow)`/btc/miner-flows/outflow` > > > [tab] Day > > > > Windowblock?process?7day386.86s1,845.76s30day644.70s1,806.66s > > > [tab] Hour > > > > Windowblock?process?24hour838.22s1,685.00s168hour614.62s1,721.80s > > > [tab] Block > > > > Windowblock?process?10min757.00s940.50s60min503.14s1,086.14s > > Mutable: yes · measured 2026-07-07 > > [Transactions Count](/api-reference/btc-miner-flows/transactions-count)`/btc/miner-flows/transactions-count` > > > [tab] Day > > > > Windowblock?process?7day386.86s1,845.76s30day644.70s1,806.66s > > > [tab] Hour > > > > Windowblock?process?24hour838.22s1,685.00s168hour614.62s1,721.80s > > > [tab] Block > > > > Windowblock?process?10min757.00s940.50s60min503.14s1,086.14s > > Mutable: yes · measured 2026-07-07 > > [Addresses Count](/api-reference/btc-miner-flows/addresses-count)`/btc/miner-flows/addresses-count` > > > [tab] Day > > > > Windowblock?process?7day386.86s1,845.76s30day644.70s1,806.66s > > > [tab] Hour > > > > Windowblock?process?24hour838.22s1,685.00s168hour614.62s1,721.80s > > > [tab] Block > > > > Windowblock?process?10min757.00s940.50s60min503.14s1,086.14s > > Mutable: yes · measured 2026-07-07 > > [In-House Flow](/api-reference/btc-miner-flows/in-house-flow)`/btc/miner-flows/in-house-flow` > > > [tab] Day > > > > Windowblock?process?7day386.86s1,845.76s30day644.70s1,806.66s > > > [tab] Hour > > > > Windowblock?process?24hour838.22s1,685.00s168hour614.62s1,721.80s > > > [tab] Block > > > > Windowblock?process?10min757.00s940.50s60min503.14s1,086.14s > > Mutable: yes · measured 2026-07-07 ## Inter Entity Flows | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Exchange to Exchange](/api-reference/btc-inter-entity-flows/exchange-to-exchange) | `/btc/inter-entity-flows/exchange-to-exchange` | `from_exchange` `to_exchange` | `blockheight` `date` `datetime` `flow_total` `flow_mean` `transactions_count_flow` | | [Miner to Exchange](/api-reference/btc-inter-entity-flows/miner-to-exchange) | `/btc/inter-entity-flows/miner-to-exchange` | `from_miner` `to_exchange` | `blockheight` `date` `datetime` `flow_total` `flow_mean` `transactions_count_flow` | | [Exchange to Miner](/api-reference/btc-inter-entity-flows/exchange-to-miner) | `/btc/inter-entity-flows/exchange-to-miner` | `from_exchange` `to_miner` | `blockheight` `date` `datetime` `flow_total` `flow_mean` `transactions_count_flow` | | [Miner to Miner](/api-reference/btc-inter-entity-flows/miner-to-miner) | `/btc/inter-entity-flows/miner-to-miner` | `from_miner` `to_miner` | `blockheight` `date` `datetime` `flow_total` `flow_mean` `transactions_count_flow` | > [accordion] Data latency > > [Exchange to Exchange](/api-reference/btc-inter-entity-flows/exchange-to-exchange)`/btc/inter-entity-flows/exchange-to-exchange` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,839.09s30day643.03s1,989.01s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s2,073.54s168hour657.81s1,910.45s > > > [tab] Block > > > > Windowblock?process?10min863.00s1,056.00s60min740.00s1,051.20s > > Mutable: yes · measured 2026-07-08 > > [Miner to Exchange](/api-reference/btc-inter-entity-flows/miner-to-exchange)`/btc/inter-entity-flows/miner-to-exchange` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,782.19s30day643.03s1,932.33s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s2,017.53s168hour659.71s1,841.00s > > > [tab] Block > > > > Windowblock?process?10min203.00s1,480.00s60min664.60s1,122.80s > > Mutable: yes · measured 2026-07-08 > > [Exchange to Miner](/api-reference/btc-inter-entity-flows/exchange-to-miner)`/btc/inter-entity-flows/exchange-to-miner` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,838.65s30day643.03s1,988.64s > > > [tab] Hour > > > > Windowblock?process?24hour569.00s7,849,451.98s168hour498.50s7,957,522.47s > > > [tab] Block > > > > Windowblock?process?10min863.00s1,056.00s60min740.00s1,051.20s > > Mutable: yes · measured 2026-07-08 > > [Miner to Miner](/api-reference/btc-inter-entity-flows/miner-to-miner)`/btc/inter-entity-flows/miner-to-miner` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,781.81s30day643.03s1,931.98s > > > [tab] Hour > > > > Windowblock?process?24hour668.75s2,038.69s168hour673.73s1,840.39s > > > [tab] Block > > > > Windowblock?process?10min203.00s1,480.00s60min448.00s1,330.00s > > Mutable: yes · measured 2026-07-08 ## Network Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Supply](/api-reference/btc-network-data/supply) | `/btc/network-data/supply` | — | `blockheight` `date` `datetime` `supply_total` `supply_new` | | [Velocity](/api-reference/btc-network-data/velocity) | `/btc/network-data/velocity` | — | `blockheight` `date` `datetime` `velocity_supply_total` | | [Transactions Count](/api-reference/btc-network-data/transactions-count) | `/btc/network-data/transactions-count` | — | `blockheight` `date` `datetime` `transactions_count_total` `transactions_count_mean` | | [Addresses Count](/api-reference/btc-network-data/addresses-count) | `/btc/network-data/addresses-count` | — | `blockheight` `date` `datetime` `addresses_count_active` `addresses_count_sender` `addresses_count_receiver` | | [Tokens Transferred](/api-reference/btc-network-data/tokens-transferred) | `/btc/network-data/tokens-transferred` | — | `blockheight` `date` `datetime` `tokens_transferred_total` `tokens_transferred_mean` `tokens_transferred_median` | | [Block Bytes](/api-reference/btc-network-data/block-bytes) | `/btc/network-data/block-bytes` | — | `blockheight` `date` `datetime` `block_bytes` | | [Block Count](/api-reference/btc-network-data/block-count) | `/btc/network-data/block-count` | — | `blockheight` `date` `datetime` `block_count` | | [Block Interval](/api-reference/btc-network-data/block-interval) | `/btc/network-data/block-interval` | — | `blockheight` `date` `datetime` `block_interval` | | [UTXO Count](/api-reference/btc-network-data/utxo-count) | `/btc/network-data/utxo-count` | — | `blockheight` `date` `datetime` `utxo_count` | | [Fees](/api-reference/btc-network-data/fees) | `/btc/network-data/fees` | — | `blockheight` `date` `datetime` `fees_block_mean` `fees_block_mean_usd` `fees_total` `fees_total_usd` `fees_reward_percent` | | [Fees Transaction](/api-reference/btc-network-data/fees-transaction) | `/btc/network-data/fees-transaction` | — | `blockheight` `date` `datetime` `fees_transaction_mean` `fees_transaction_mean_usd` `fees_transaction_median` `fees_transaction_median_usd` | | [Blockreward](/api-reference/btc-network-data/blockreward) | `/btc/network-data/blockreward` | — | `blockheight` `date` `datetime` `blockreward` `blockreward_usd` | | [Difficulty](/api-reference/btc-network-data/difficulty) | `/btc/network-data/difficulty` | — | `blockheight` `date` `datetime` `difficulty` | | [Hashrate](/api-reference/btc-network-data/hashrate) | `/btc/network-data/hashrate` | — | `blockheight` `date` `datetime` `hashrate` | > [accordion] Data latency > > [Supply](/api-reference/btc-network-data/supply)`/btc/network-data/supply` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [Velocity](/api-reference/btc-network-data/velocity)`/btc/network-data/velocity` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [Transactions Count](/api-reference/btc-network-data/transactions-count)`/btc/network-data/transactions-count` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [Addresses Count](/api-reference/btc-network-data/addresses-count)`/btc/network-data/addresses-count` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [Tokens Transferred](/api-reference/btc-network-data/tokens-transferred)`/btc/network-data/tokens-transferred` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [Block Bytes](/api-reference/btc-network-data/block-bytes)`/btc/network-data/block-bytes` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [Block Count](/api-reference/btc-network-data/block-count)`/btc/network-data/block-count` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [Block Interval](/api-reference/btc-network-data/block-interval)`/btc/network-data/block-interval` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [UTXO Count](/api-reference/btc-network-data/utxo-count)`/btc/network-data/utxo-count` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [Fees](/api-reference/btc-network-data/fees)`/btc/network-data/fees` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [Fees Transaction](/api-reference/btc-network-data/fees-transaction)`/btc/network-data/fees-transaction` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [Blockreward](/api-reference/btc-network-data/blockreward)`/btc/network-data/blockreward` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [Difficulty](/api-reference/btc-network-data/difficulty)`/btc/network-data/difficulty` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [Hashrate](/api-reference/btc-network-data/hashrate)`/btc/network-data/hashrate` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 ## Market Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Price OHLCV](/api-reference/btc-market-data/price-ohlcv) | `/btc/market-data/price-ohlcv` | — | `blockheight` `date` `datetime` `open` `high` `low` `close` `volume` | | [Open Interest](/api-reference/btc-market-data/open-interest) | `/btc/market-data/open-interest` | `exchange` | `date` `datetime` `open_interest` | | [Funding Rates](/api-reference/btc-market-data/funding-rates) | `/btc/market-data/funding-rates` | `exchange` | `date` `datetime` `funding_rates` | | [Taker Buy Sell Stats](/api-reference/btc-market-data/taker-buy-sell-stats) | `/btc/market-data/taker-buy-sell-stats` | `exchange` | `date` `datetime` `taker_buy_volume` `taker_sell_volume` `taker_buy_ratio` `taker_sell_ratio` `taker_buy_sell_ratio` | | [Liquidations](/api-reference/btc-market-data/liquidations) | `/btc/market-data/liquidations` | `exchange` | `date` `datetime` `long_liquidations` `short_liquidations` `long_liquidations_usd` `short_liquidations_usd` | | [Capitalization](/api-reference/btc-market-data/capitalization) | `/btc/market-data/capitalization` | — | `blockheight` `date` `datetime` `market_cap` `realized_cap` `average_cap` `delta_cap` `thermo_cap` | | [Coinbase Premium Index](/api-reference/btc-market-data/coinbase-premium-index) | `/btc/market-data/coinbase-premium-index` | — | `date` `datetime` `coinbase_premium_gap` `coinbase_premium_index` | > [accordion] Data latency > > [Price OHLCV](/api-reference/btc-market-data/price-ohlcv)`/btc/market-data/price-ohlcv` > > > [tab] Day > > > > Windowblock?process?7day—269.28s30day—255.81s > > > [tab] Hour > > > > Windowblock?process?24hour—263.12s168hour—273.71s > > > [tab] Minute > > > > Windowblock?process?10min—66.42s60min—68.71s > > Mutable: no · measured 2026-11-10 > > [Open Interest](/api-reference/btc-market-data/open-interest)`/btc/market-data/open-interest` > > > [tab] Day > > > > Windowblock?process?7day—23.05s30day—22.57s > > > [tab] Hour > > > > Windowblock?process?24hour—16.75s168hour—16.89s > > > [tab] Minute > > > > Windowblock?process?10min—11.48s60min—11.10s > > Mutable: no · measured 2026-11-10 > > [Funding Rates](/api-reference/btc-market-data/funding-rates)`/btc/market-data/funding-rates` > > > [tab] Day > > > > Windowblock?process?7day—10.57s30day—10.57s > > > [tab] Hour > > > > Windowblock?process?24hour—8.07s168hour—6.64s > > > [tab] Minute > > > > Windowblock?process?10min—2.73s60min—2.73s > > Mutable: no · measured 2026-11-10 > > [Taker Buy Sell Stats](/api-reference/btc-market-data/taker-buy-sell-stats)`/btc/market-data/taker-buy-sell-stats` > > > [tab] Day > > > > Windowblock?process?7day—71.30s30day—71.17s > > > [tab] Hour > > > > Windowblock?process?24hour—8.11s168hour—8.81s > > > [tab] Minute > > > > Windowblock?process?10min—4.56s60min—4.57s > > Mutable: no · measured 2026-11-10 > > [Liquidations](/api-reference/btc-market-data/liquidations)`/btc/market-data/liquidations` > > > [tab] Day > > > > Windowblock?process?7day—23.05s30day—22.57s > > > [tab] Hour > > > > Windowblock?process?24hour—16.75s168hour—16.89s > > > [tab] Minute > > > > Windowblock?process?10min—11.48s60min—11.10s > > Mutable: no · measured 2026-11-10 > > [Capitalization](/api-reference/btc-market-data/capitalization)`/btc/market-data/capitalization` > > > [tab] Day > > > > Windowblock?process?7day505.29s1,181.10s30day639.93s1,198.82s > > > [tab] Block > > > > Windowblock?process?10min248.00s984.03s60min623.00s822.13s > > Mutable: no · measured 2026-07-10 > > [Coinbase Premium Index](/api-reference/btc-market-data/coinbase-premium-index)`/btc/market-data/coinbase-premium-index` > > > [tab] Day > > > > Windowblock?process?7day—245.08s30day—275.12s > > > [tab] Hour > > > > Windowblock?process?24hour—277.84s168hour—225.34s > > > [tab] Minute > > > > Windowblock?process?10min—192.61s60min—192.19s > > Mutable: no · measured 2026-11-10 ## Fund Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Market Price USD](/api-reference/btc-fund-data/market-price-usd) | `/btc/fund-data/market-price-usd` | `symbol` | `date` `price_usd_open` `price_usd_high` `price_usd_low` `price_usd_close` `price_usd_adj_close` | | [Market Volume](/api-reference/btc-fund-data/market-volume) | `/btc/fund-data/market-volume` | `symbol` | `date` `volume` | | [Market Premium](/api-reference/btc-fund-data/market-premium) | `/btc/fund-data/market-premium` | `symbol` | `date` `market_premium` | | [Digital Asset Holdings](/api-reference/btc-fund-data/digital-asset-holdings) | `/btc/fund-data/digital-asset-holdings` | `symbol` | `date` `digital_asset_holdings` | > [accordion] Data latency > > [Market Price USD](/api-reference/btc-fund-data/market-price-usd)`/btc/fund-data/market-price-usd` > > > [tab] Day > > > > Windowblock?process?7day—380,527.66s30day—168,860.56s > > Mutable: no · measured 2026-07-08 > > [Market Volume](/api-reference/btc-fund-data/market-volume)`/btc/fund-data/market-volume` > > > [tab] Day > > > > Windowblock?process?7day—380,527.66s30day—168,860.56s > > Mutable: no · measured 2026-07-08 > > [Market Premium](/api-reference/btc-fund-data/market-premium)`/btc/fund-data/market-premium` > > > [tab] Day > > > > Windowblock?process?7day—380,527.66s30day—168,860.56s > > Mutable: no · measured 2026-07-08 > > [Digital Asset Holdings](/api-reference/btc-fund-data/digital-asset-holdings)`/btc/fund-data/digital-asset-holdings` > > > [tab] Day > > > > Windowblock?process?7day178.40s376,781.55s30day452.67s175,709.04s > > Mutable: no · measured 2026-07-08 ## Network Indicator | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Stock to Flow](/api-reference/btc-network-indicator/stock-to-flow) | `/btc/network-indicator/stock-to-flow` | — | `blockheight` `date` `datetime` `stock_to_flow` `stock_to_flow_reversion` | | [NVT](/api-reference/btc-network-indicator/nvt) | `/btc/network-indicator/nvt` | — | `date` `nvt` | | [NVT Golden Cross](/api-reference/btc-network-indicator/nvt-golden-cross) | `/btc/network-indicator/nvt-golden-cross` | — | `date` `nvt_golden_cross` | | [NVM](/api-reference/btc-network-indicator/nvm) | `/btc/network-indicator/nvm` | — | `date` `nvm` | | [Puell Multiple](/api-reference/btc-network-indicator/puell-multiple) | `/btc/network-indicator/puell-multiple` | — | `date` `puell_multiple` | | [Coin Days Destroyed](/api-reference/btc-network-indicator/coin-days-destroyed) | `/btc/network-indicator/cdd` | — | `blockheight` `date` `datetime` `cdd` `sa_cdd` `average_sa_cdd` `binary_cdd` | | [Mean Coin Age](/api-reference/btc-network-indicator/mean-coin-age) | `/btc/network-indicator/mca` | — | `blockheight` `date` `datetime` `mca` `mcda` | | [Sum Coin Age](/api-reference/btc-network-indicator/sum-coin-age) | `/btc/network-indicator/sca` | — | `blockheight` `date` `datetime` `sca` `scda` | | [Sum Coin Age Distribution](/api-reference/btc-network-indicator/sum-coin-age-distribution) | `/btc/network-indicator/sca-distribution` | — | `blockheight` `date` `datetime` `range_0d_1d` `range_1d_1w` `range_1w_1m` `range_1m_3m` `range_3m_6m` +21 | | [Net Unrealized Profit and Loss](/api-reference/btc-network-indicator/net-unrealized-profit-and-loss) | `/btc/network-indicator/nupl` | — | `blockheight` `date` `datetime` `nupl` `nup` `nul` | | [Net Realized Profit and Loss](/api-reference/btc-network-indicator/net-realized-profit-and-loss) | `/btc/network-indicator/nrpl` | — | `blockheight` `date` `datetime` `nrpl` | | [Profit and Loss (UTxO)](/api-reference/btc-network-indicator/profit-and-loss-utxo) | `/btc/network-indicator/pnl-utxo` | — | `date` `profit_percent` `loss_percent` `profit_amount` `loss_amount` | | [Profit and Loss (Supply)](/api-reference/btc-network-indicator/profit-and-loss-supply) | `/btc/network-indicator/pnl-supply` | — | `blockheight` `date` `datetime` `profit_percent` `loss_percent` `profit_amount` `loss_amount` | | [Dormancy](/api-reference/btc-network-indicator/dormancy) | `/btc/network-indicator/dormancy` | — | `blockheight` `date` `datetime` `average_dormancy` `sa_average_dormancy` | | [UTxO Age Distribution](/api-reference/btc-network-indicator/utxo-age-distribution) | `/btc/network-indicator/utxo-age-distribution` | — | `blockheight` `date` `datetime` `range_0d_1d` `range_1d_1w` `range_1w_1m` `range_1m_3m` `range_3m_6m` +34 | | [UTxO Realized Age Distribution](/api-reference/btc-network-indicator/utxo-realized-age-distribution) | `/btc/network-indicator/utxo-realized-age-distribution` | — | `blockheight` `date` `datetime` `range_0d_1d_usd` `range_1d_1w_usd` `range_1w_1m_usd` `range_1m_3m_usd` `range_3m_6m_usd` +21 | | [UTxO Count Age Distribution](/api-reference/btc-network-indicator/utxo-count-age-distribution) | `/btc/network-indicator/utxo-count-age-distribution` | — | `blockheight` `date` `datetime` `range_0d_1d` `range_1d_1w` `range_1w_1m` `range_1m_3m` `range_3m_6m` +21 | | [Spent Output Age Distribution](/api-reference/btc-network-indicator/spent-output-age-distribution) | `/btc/network-indicator/spent-output-age-distribution` | — | `blockheight` `date` `datetime` `range_0d_1d` `range_1d_1w` `range_1w_1m` `range_1m_3m` `range_3m_6m` +34 | | [UTxO Supply Distribution](/api-reference/btc-network-indicator/utxo-supply-distribution) | `/btc/network-indicator/utxo-supply-distribution` | — | `blockheight` `date` `datetime` `range_0_001` `range_001_01` `range_01_1` `range_1_10` `range_10_100` +11 | | [UTxO Realized Supply Distribution](/api-reference/btc-network-indicator/utxo-realized-supply-distribution) | `/btc/network-indicator/utxo-realized-supply-distribution` | — | `blockheight` `date` `datetime` `range_0_1_usd` `range_1_10_usd` `range_10_100_usd` `range_100_1k_usd` `range_1k_10k_usd` +11 | | [UTxO Count Supply Distribution](/api-reference/btc-network-indicator/utxo-count-supply-distribution) | `/btc/network-indicator/utxo-count-supply-distribution` | — | `blockheight` `date` `datetime` `range_0_001` `range_001_01` `range_01_1` `range_1_10` `range_10_100` +11 | | [Spent Output Supply Distribution](/api-reference/btc-network-indicator/spent-output-supply-distribution) | `/btc/network-indicator/spent-output-supply-distribution` | — | `blockheight` `date` `datetime` `range_0_001` `range_001_01` `range_01_1` `range_1_10` `range_10_100` +19 | > [accordion] Data latency > > [Stock to Flow](/api-reference/btc-network-indicator/stock-to-flow)`/btc/network-indicator/stock-to-flow` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: no · measured 2026-07-08 > > [NVT](/api-reference/btc-network-indicator/nvt)`/btc/network-indicator/nvt` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,246.05s30day643.03s1,215.62s > > Mutable: no · measured 2026-07-08 > > [NVT Golden Cross](/api-reference/btc-network-indicator/nvt-golden-cross)`/btc/network-indicator/nvt-golden-cross` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > Mutable: no · measured 2026-07-08 > > [NVM](/api-reference/btc-network-indicator/nvm)`/btc/network-indicator/nvm` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,246.05s30day643.03s1,215.62s > > Mutable: no · measured 2026-07-08 > > [Puell Multiple](/api-reference/btc-network-indicator/puell-multiple)`/btc/network-indicator/puell-multiple` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > Mutable: no · measured 2026-07-08 > > [Coin Days Destroyed](/api-reference/btc-network-indicator/coin-days-destroyed)`/btc/network-indicator/cdd` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,246.05s30day643.03s1,215.62s > > > [tab] Block > > > > Windowblock?process?10min523.00s521.68s60min723.40s681.86s > > Mutable: no · measured 2026-07-08 > > [Mean Coin Age](/api-reference/btc-network-indicator/mean-coin-age)`/btc/network-indicator/mca` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,268.55s30day643.03s1,232.67s > > > [tab] Block > > > > Windowblock?process?10min523.00s540.07s60min723.40s700.34s > > Mutable: no · measured 2026-07-08 > > [Sum Coin Age](/api-reference/btc-network-indicator/sum-coin-age)`/btc/network-indicator/sca` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,268.55s30day643.03s1,232.67s > > > [tab] Block > > > > Windowblock?process?10min523.00s540.07s60min723.40s700.34s > > Mutable: no · measured 2026-07-08 > > [Sum Coin Age Distribution](/api-reference/btc-network-indicator/sum-coin-age-distribution)`/btc/network-indicator/sca-distribution` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,268.55s30day643.03s1,232.67s > > > [tab] Block > > > > Windowblock?process?10min523.00s540.07s60min723.40s700.34s > > Mutable: no · measured 2026-07-08 > > [Net Unrealized Profit and Loss](/api-reference/btc-network-indicator/net-unrealized-profit-and-loss)`/btc/network-indicator/nupl` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,268.55s30day643.03s1,232.67s > > > [tab] Block > > > > Windowblock?process?10min523.00s540.07s60min723.40s700.34s > > Mutable: no · measured 2026-07-08 > > [Net Realized Profit and Loss](/api-reference/btc-network-indicator/net-realized-profit-and-loss)`/btc/network-indicator/nrpl` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,246.05s30day643.03s1,215.62s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,203.77s168hour663.26s1,171.70s > > > [tab] Block > > > > Windowblock?process?10min523.00s521.68s60min723.40s681.86s > > Mutable: no · measured 2026-07-08 > > [Profit and Loss (UTxO)](/api-reference/btc-network-indicator/profit-and-loss-utxo)`/btc/network-indicator/pnl-utxo` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,268.55s30day643.03s1,232.67s > > Mutable: no · measured 2026-07-08 > > [Profit and Loss (Supply)](/api-reference/btc-network-indicator/profit-and-loss-supply)`/btc/network-indicator/pnl-supply` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,268.55s30day643.03s1,232.67s > > > [tab] Block > > > > Windowblock?process?10min523.00s540.07s60min723.40s700.34s > > Mutable: no · measured 2026-07-08 > > [Dormancy](/api-reference/btc-network-indicator/dormancy)`/btc/network-indicator/dormancy` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,246.05s30day643.03s1,215.62s > > > [tab] Block > > > > Windowblock?process?10min523.00s521.68s60min723.40s681.86s > > Mutable: no · measured 2026-07-08 > > [UTxO Age Distribution](/api-reference/btc-network-indicator/utxo-age-distribution)`/btc/network-indicator/utxo-age-distribution` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,268.55s30day643.03s1,232.67s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,219.60s168hour663.26s1,189.13s > > > [tab] Block > > > > Windowblock?process?10min523.00s540.07s60min723.40s700.34s > > Mutable: no · measured 2026-07-08 > > [UTxO Realized Age Distribution](/api-reference/btc-network-indicator/utxo-realized-age-distribution)`/btc/network-indicator/utxo-realized-age-distribution` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,268.55s30day643.03s1,232.67s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,219.60s168hour663.26s1,189.13s > > > [tab] Block > > > > Windowblock?process?10min523.00s540.07s60min723.40s700.34s > > Mutable: no · measured 2026-07-08 > > [UTxO Count Age Distribution](/api-reference/btc-network-indicator/utxo-count-age-distribution)`/btc/network-indicator/utxo-count-age-distribution` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,268.55s30day643.03s1,232.67s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,219.60s168hour663.26s1,189.13s > > > [tab] Block > > > > Windowblock?process?10min523.00s540.07s60min723.40s700.34s > > Mutable: no · measured 2026-07-08 > > [Spent Output Age Distribution](/api-reference/btc-network-indicator/spent-output-age-distribution)`/btc/network-indicator/spent-output-age-distribution` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,268.55s30day643.03s1,232.67s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,219.60s168hour663.26s1,189.13s > > > [tab] Block > > > > Windowblock?process?10min523.00s540.07s60min723.40s700.34s > > Mutable: no · measured 2026-07-08 > > [UTxO Supply Distribution](/api-reference/btc-network-indicator/utxo-supply-distribution)`/btc/network-indicator/utxo-supply-distribution` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,235.40s30day643.03s1,201.85s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,198.81s168hour663.26s1,162.52s > > > [tab] Block > > > > Windowblock?process?10min523.00s509.52s60min723.40s693.92s > > Mutable: no · measured 2026-07-08 > > [UTxO Realized Supply Distribution](/api-reference/btc-network-indicator/utxo-realized-supply-distribution)`/btc/network-indicator/utxo-realized-supply-distribution` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,234.88s30day643.03s1,201.31s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,192.96s168hour663.26s1,161.51s > > > [tab] Block > > > > Windowblock?process?10min523.00s509.28s60min723.40s669.51s > > Mutable: no · measured 2026-07-08 > > [UTxO Count Supply Distribution](/api-reference/btc-network-indicator/utxo-count-supply-distribution)`/btc/network-indicator/utxo-count-supply-distribution` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,235.40s30day643.03s1,201.85s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,198.81s168hour663.26s1,162.52s > > > [tab] Block > > > > Windowblock?process?10min523.00s509.52s60min723.40s693.92s > > Mutable: no · measured 2026-07-08 > > [Spent Output Supply Distribution](/api-reference/btc-network-indicator/spent-output-supply-distribution)`/btc/network-indicator/spent-output-supply-distribution` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,235.40s30day643.03s1,201.85s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,198.81s168hour663.26s1,162.52s > > > [tab] Block > > > > Windowblock?process?10min523.00s509.52s60min723.40s693.92s > > Mutable: no · measured 2026-07-08 ## Market Indicator | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Estimated Leverage Ratio](/api-reference/btc-market-indicator/estimated-leverage-ratio) | `/btc/market-indicator/estimated-leverage-ratio` | `exchange` | `blockheight` `date` `datetime` `estimated_leverage_ratio` | | [Stablecoin Supply Ratio](/api-reference/btc-market-indicator/stablecoin-supply-ratio) | `/btc/market-indicator/stablecoin-supply-ratio` | — | `date` `stablecoin_supply_ratio` | | [MVRV](/api-reference/btc-market-indicator/mvrv) | `/btc/market-indicator/mvrv` | — | `blockheight` `date` `datetime` `mvrv` | | [Spent Output Profit Ratio](/api-reference/btc-market-indicator/spent-output-profit-ratio) | `/btc/market-indicator/sopr` | — | `blockheight` `date` `datetime` `sopr` `a_sopr` `sth_sopr` `lth_sopr` | | [SOPR Ratio](/api-reference/btc-market-indicator/sopr-ratio) | `/btc/market-indicator/sopr-ratio` | — | `blockheight` `date` `datetime` `sopr_ratio` | | [Realized Price](/api-reference/btc-market-indicator/realized-price) | `/btc/market-indicator/realized-price` | — | `blockheight` `date` `datetime` `realized_price` | | [UTxO Realized Price Age Distribution](/api-reference/btc-market-indicator/utxo-realized-price-age-distribution) | `/btc/market-indicator/utxo-realized-price-age-distribution` | — | `blockheight` `date` `datetime` `range_0d_1d` `range_1d_1w` `range_1w_1m` `range_1m_3m` `range_3m_6m` +8 | > [accordion] Data latency > > [Estimated Leverage Ratio](/api-reference/btc-market-indicator/estimated-leverage-ratio)`/btc/market-indicator/estimated-leverage-ratio` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,837.30s30day643.03s1,827.49s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,754.65s168hour657.81s1,740.47s > > > [tab] Block > > > > Windowblock?process?10min671.50s1,028.00s60min696.67s1,042.67s > > Mutable: no · measured 2026-07-08 > > [Stablecoin Supply Ratio](/api-reference/btc-market-indicator/stablecoin-supply-ratio)`/btc/market-indicator/stablecoin-supply-ratio` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,246.05s30day643.03s1,215.62s > > Mutable: no · measured 2026-07-08 > > [MVRV](/api-reference/btc-market-indicator/mvrv)`/btc/market-indicator/mvrv` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,246.05s30day643.03s1,215.62s > > > [tab] Block > > > > Windowblock?process?10min523.00s521.68s60min723.40s681.86s > > Mutable: no · measured 2026-07-08 > > [Spent Output Profit Ratio](/api-reference/btc-market-indicator/spent-output-profit-ratio)`/btc/market-indicator/sopr` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,246.05s30day643.03s1,215.62s > > > [tab] Block > > > > Windowblock?process?10min523.00s521.68s60min723.40s681.86s > > Mutable: no · measured 2026-07-08 > > [SOPR Ratio](/api-reference/btc-market-indicator/sopr-ratio)`/btc/market-indicator/sopr-ratio` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,246.05s30day643.03s1,215.62s > > > [tab] Block > > > > Windowblock?process?10min523.00s521.68s60min723.40s681.86s > > Mutable: no · measured 2026-07-08 > > [Realized Price](/api-reference/btc-market-indicator/realized-price)`/btc/market-indicator/realized-price` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,246.05s30day643.03s1,215.62s > > > [tab] Block > > > > Windowblock?process?10min523.00s521.68s60min723.40s681.86s > > Mutable: no · measured 2026-07-08 > > [UTxO Realized Price Age Distribution](/api-reference/btc-market-indicator/utxo-realized-price-age-distribution)`/btc/market-indicator/utxo-realized-price-age-distribution` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,268.55s30day643.03s1,232.67s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,219.60s168hour663.26s1,189.13s > > > [tab] Block > > > > Windowblock?process?10min523.00s540.07s60min723.40s700.34s > > Mutable: no · measured 2026-07-08 ## Flow Indicator | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Miners' Position Index (MPI)](/api-reference/btc-flow-indicator/miners-position-index-mpi) | `/btc/flow-indicator/mpi` | — | `date` `mpi` | | [Exchange Shutdown Index](/api-reference/btc-flow-indicator/exchange-shutdown-index) | `/btc/flow-indicator/exchange-shutdown-index` | `exchange` | `blockheight` `date` `datetime` `is_shutdown` | | [Exchange Whale Ratio](/api-reference/btc-flow-indicator/exchange-whale-ratio) | `/btc/flow-indicator/exchange-whale-ratio` | `exchange` | `blockheight` `date` `datetime` `exchange_whale_ratio` | | [Fund Flow Ratio](/api-reference/btc-flow-indicator/fund-flow-ratio) | `/btc/flow-indicator/fund-flow-ratio` | `exchange` | `blockheight` `date` `datetime` `fund_flow_ratio` | | [Stablecoins Ratio](/api-reference/btc-flow-indicator/stablecoins-ratio) | `/btc/flow-indicator/stablecoins-ratio` | `exchange` | `blockheight` `date` `datetime` `stablecoins_ratio` `stablecoins_ratio_usd` | | [Exchange Inflow Age Distribution](/api-reference/btc-flow-indicator/exchange-inflow-age-distribution) | `/btc/flow-indicator/exchange-inflow-age-distribution` | `exchange` | `blockheight` `date` `datetime` `range_0d_1d` `range_1d_1w` `range_1w_1m` `range_1m_3m` `range_3m_6m` +21 | | [Exchange Inflow Supply Distribution](/api-reference/btc-flow-indicator/exchange-inflow-supply-distribution) | `/btc/flow-indicator/exchange-inflow-supply-distribution` | `exchange` | `blockheight` `date` `datetime` `range_0_001` `range_001_01` `range_01_1` `range_1_10` `range_10_100` +11 | | [Exchange Inflow CDD (Coin Days Destroyed)](/api-reference/btc-flow-indicator/exchange-inflow-cdd-coin-days-destroyed) | `/btc/flow-indicator/exchange-inflow-cdd` | `exchange` | `blockheight` `date` `datetime` `inflow_cdd` | | [Exchange Supply Ratio](/api-reference/btc-flow-indicator/exchange-supply-ratio) | `/btc/flow-indicator/exchange-supply-ratio` | `exchange` | `blockheight` `date` `datetime` `supply_ratio` | | [Miner Supply Ratio](/api-reference/btc-flow-indicator/miner-supply-ratio) | `/btc/flow-indicator/miner-supply-ratio` | `miner` | `blockheight` `date` `datetime` `supply_ratio` | > [accordion] Data latency > > [Miners' Position Index (MPI)](/api-reference/btc-flow-indicator/miners-position-index-mpi)`/btc/flow-indicator/mpi` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,780.49s30day643.03s1,774.52s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,707.85s168hour657.81s1,705.83s > > > [tab] Block > > > > Windowblock?process?10min671.50s1,028.00s60min696.67s1,042.67s > > Mutable: yes · measured 2026-07-08 > > [Exchange Shutdown Index](/api-reference/btc-flow-indicator/exchange-shutdown-index)`/btc/flow-indicator/exchange-shutdown-index` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,837.30s30day643.03s1,827.49s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,754.65s168hour657.81s1,740.47s > > > [tab] Block > > > > Windowblock?process?10min671.50s1,028.00s60min696.67s1,042.67s > > Mutable: yes · measured 2026-07-08 > > [Exchange Whale Ratio](/api-reference/btc-flow-indicator/exchange-whale-ratio)`/btc/flow-indicator/exchange-whale-ratio` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,837.30s30day643.03s1,827.49s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,754.65s168hour657.81s1,740.47s > > > [tab] Block > > > > Windowblock?process?10min671.50s1,028.00s60min696.67s1,042.67s > > Mutable: yes · measured 2026-07-08 > > [Fund Flow Ratio](/api-reference/btc-flow-indicator/fund-flow-ratio)`/btc/flow-indicator/fund-flow-ratio` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,837.30s30day643.03s1,827.49s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,754.65s168hour657.81s1,740.47s > > > [tab] Block > > > > Windowblock?process?10min671.50s1,028.00s60min696.67s1,042.67s > > Mutable: yes · measured 2026-07-08 > > [Stablecoins Ratio](/api-reference/btc-flow-indicator/stablecoins-ratio)`/btc/flow-indicator/stablecoins-ratio` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,837.30s30day643.03s1,827.49s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,754.65s168hour657.81s1,740.47s > > Mutable: yes · measured 2026-07-08 > > [Exchange Inflow Age Distribution](/api-reference/btc-flow-indicator/exchange-inflow-age-distribution)`/btc/flow-indicator/exchange-inflow-age-distribution` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,240.94s30day643.03s1,205.47s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,224.71s168hour657.81s1,168.77s > > > [tab] Block > > > > Windowblock?process?10min523.00s512.47s60min723.40s673.83s > > Mutable: yes · measured 2026-07-08 > > [Exchange Inflow Supply Distribution](/api-reference/btc-flow-indicator/exchange-inflow-supply-distribution)`/btc/flow-indicator/exchange-inflow-supply-distribution` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,240.94s30day643.03s1,205.47s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,224.71s168hour657.81s1,168.77s > > > [tab] Block > > > > Windowblock?process?10min523.00s512.47s60min723.40s673.83s > > Mutable: yes · measured 2026-07-08 > > [Exchange Inflow CDD (Coin Days Destroyed)](/api-reference/btc-flow-indicator/exchange-inflow-cdd-coin-days-destroyed)`/btc/flow-indicator/exchange-inflow-cdd` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,240.94s30day643.03s1,205.47s > > > [tab] Hour > > > > Windowblock?process?24hour724.09s1,224.71s168hour657.81s1,168.77s > > > [tab] Block > > > > Windowblock?process?10min523.00s512.47s60min723.40s673.83s > > Mutable: yes · measured 2026-07-08 > > [Exchange Supply Ratio](/api-reference/btc-flow-indicator/exchange-supply-ratio)`/btc/flow-indicator/exchange-supply-ratio` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: yes · measured 2026-07-08 > > [Miner Supply Ratio](/api-reference/btc-flow-indicator/miner-supply-ratio)`/btc/flow-indicator/miner-supply-ratio` > > > [tab] Day > > > > Windowblock?process?7day457.57s1,942.96s30day643.03s1,944.28s > > > [tab] Hour > > > > Windowblock?process?24hour706.75s1,157.41s168hour663.26s1,109.82s > > > [tab] Block > > > > Windowblock?process?10min523.00s516.40s60min723.40s605.12s > > Mutable: yes · measured 2026-07-08 ## Mempool Statistics | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [BTC Memory pool Statistics by relative fee range](/api-reference/btc-mempool-statistics/btc-memory-pool-statistics-by-relative-fee-range) | `/btc/mempool/stats-by-relative-fee` | — | `date` `metric_type` `metric_unit` `relative_fee_range_0_1` `relative_fee_range_1_2` `relative_fee_range_2_3` `relative_fee_range_3_4` `relative_fee_range_4_5` +41 | | [BTC Memory pool Statistics (Sum)](/api-reference/btc-mempool-statistics/btc-memory-pool-statistics-sum) | `/btc/mempool/stats-in-total` | — | `date` `metric_type` `metric_unit` `result` | ## Lightning Statistics | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [BTC Lightning Statistics](/api-reference/btc-lightning-statistics/btc-lightning-statistics) | `/btc/lightning/stats-in-total` | — | `date` `network_capacity` `network_capacity_usd` `capacity_per_channel_mean` `capacity_per_channel_mean_usd` `capacity_per_node_mean` `capacity_per_node_mean_usd` `number_of_node` +8 | ## Miner Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Companies](/api-reference/btc-miner-data/companies) | `/btc/miner-data/companies` | `miner` | `date` `coinbase_rewards` `other_mining_rewards` `total_rewards` `accumulated_monthly_rewards` `unique_txn` `active_address_count` `reported_production` +4 | # ERC-20 tokens Source: https://docs.cryptoquant.com/catalog/erc20 All ERC-20 metrics available in the CryptoQuant API — endpoints, parameters, response fields, and data latency. > Machine-readable version of this catalog: [catalog.json](/catalog/catalog.json) Each section lists its metrics; open **Data latency** under a section to see the block and process delay per resolution — see [how latency works](/guides/data-latency). ## Entity Status | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Entity List](/api-reference/erc20-entity-status/entity-list) | `/erc20/status/entity-list` | `token` `type` | `name` `symbol` `is_validated` `market_type` | ## Exchange Flows | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Reserve](/api-reference/erc20-exchange-flows/reserve) | `/erc20/exchange-flows/reserve` | `token` `exchange` | `blockheight` `date` `datetime` `reserve` `reserve_usd` | | [Netflow](/api-reference/erc20-exchange-flows/netflow) | `/erc20/exchange-flows/netflow` | `token` `exchange` | `blockheight` `date` `datetime` `netflow_total` | | [Inflow](/api-reference/erc20-exchange-flows/inflow) | `/erc20/exchange-flows/inflow` | `token` `exchange` | `blockheight` `date` `datetime` `inflow_total` `inflow_top10` `inflow_mean` | | [Outflow](/api-reference/erc20-exchange-flows/outflow) | `/erc20/exchange-flows/outflow` | `token` `exchange` | `blockheight` `date` `datetime` `outflow_total` `outflow_top10` `outflow_mean` | | [Transactions Count](/api-reference/erc20-exchange-flows/transactions-count) | `/erc20/exchange-flows/transactions-count` | `token` `exchange` | `blockheight` `date` `datetime` `transactions_count_inflow` `transactions_count_outflow` | | [Addresses Count](/api-reference/erc20-exchange-flows/addresses-count) | `/erc20/exchange-flows/addresses-count` | `token` `exchange` | `blockheight` `date` `datetime` `addresses_count_inflow` `addresses_count_outflow` | > [accordion] Data latency > > [Reserve](/api-reference/erc20-exchange-flows/reserve)`/erc20/exchange-flows/reserve` > > > [tab] Day > > > > Windowblock?process?7day11.00s1,715.26s30day11.40s1,610.14s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,714.23s168hour11.00s1,712.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,294.41s60min12.00s1,294.29s > > Mutable: no · measured 2026-11-10 > > [Netflow](/api-reference/erc20-exchange-flows/netflow)`/erc20/exchange-flows/netflow` > > > [tab] Day > > > > Windowblock?process?7day11.00s1,715.26s30day11.40s1,610.14s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,714.23s168hour11.00s1,712.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,294.41s60min12.00s1,294.29s > > Mutable: no · measured 2026-11-10 > > [Inflow](/api-reference/erc20-exchange-flows/inflow)`/erc20/exchange-flows/inflow` > > > [tab] Day > > > > Windowblock?process?7day11.00s1,715.26s30day11.40s1,610.14s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,714.23s168hour11.00s1,712.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,294.41s60min12.00s1,294.29s > > Mutable: no · measured 2026-11-10 > > [Outflow](/api-reference/erc20-exchange-flows/outflow)`/erc20/exchange-flows/outflow` > > > [tab] Day > > > > Windowblock?process?7day11.00s1,715.26s30day11.40s1,610.14s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,714.23s168hour11.00s1,712.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,294.41s60min12.00s1,294.29s > > Mutable: no · measured 2026-11-10 > > [Transactions Count](/api-reference/erc20-exchange-flows/transactions-count)`/erc20/exchange-flows/transactions-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s1,715.26s30day11.40s1,610.14s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,714.23s168hour11.00s1,712.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,294.41s60min12.00s1,294.29s > > Mutable: no · measured 2026-11-10 > > [Addresses Count](/api-reference/erc20-exchange-flows/addresses-count)`/erc20/exchange-flows/addresses-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s1,715.26s30day11.40s1,610.14s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,714.23s168hour11.00s1,712.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,294.41s60min12.00s1,294.29s > > Mutable: no · measured 2026-11-10 ## Network Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Supply](/api-reference/erc20-network-data/supply) | `/erc20/network-data/supply` | `token` | `blockheight` `date` `datetime` `supply_total` `supply_minted` `supply_burned` | | [Velocity](/api-reference/erc20-network-data/velocity) | `/erc20/network-data/velocity` | `token` | `blockheight` `date` `datetime` `velocity_supply_total` | | [Transactions Count](/api-reference/erc20-network-data/transactions-count) | `/erc20/network-data/transactions-count` | `token` | `blockheight` `date` `datetime` `transactions_count_total` `transactions_count_mean` | | [Tokens Transferred Count](/api-reference/erc20-network-data/tokens-transferred-count) | `/erc20/network-data/tokens-transferred-count` | `token` | `blockheight` `date` `datetime` `tokens_transferred_count_total` `tokens_transferred_count_mean` | | [Tokens Transferred](/api-reference/erc20-network-data/tokens-transferred) | `/erc20/network-data/tokens-transferred` | `token` | `blockheight` `date` `datetime` `tokens_transferred_total` `tokens_transferred_mean` `tokens_transferred_median` | | [Addresses Count](/api-reference/erc20-network-data/addresses-count) | `/erc20/network-data/addresses-count` | `token` | `blockheight` `date` `datetime` `addresses_count_active` `addresses_count_sender` `addresses_count_receiver` | > [accordion] Data latency > > [Supply](/api-reference/erc20-network-data/supply)`/erc20/network-data/supply` > > > [tab] Day > > > > Windowblock?process?7day11.00s839.82s30day11.40s840.73s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s824.82s168hour11.00s824.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s733.33s60min12.00s735.40s > > Mutable: no · measured 2026-11-10 > > [Velocity](/api-reference/erc20-network-data/velocity)`/erc20/network-data/velocity` > > > [tab] Day > > > > Windowblock?process?7day11.00s839.82s30day11.40s840.73s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s824.82s168hour11.00s824.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s733.33s60min12.00s735.40s > > Mutable: no · measured 2026-11-10 > > [Transactions Count](/api-reference/erc20-network-data/transactions-count)`/erc20/network-data/transactions-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s839.82s30day11.40s840.73s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s824.82s168hour11.00s824.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s733.33s60min12.00s735.40s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred Count](/api-reference/erc20-network-data/tokens-transferred-count)`/erc20/network-data/tokens-transferred-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s839.82s30day11.40s840.73s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s824.82s168hour11.00s824.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s733.33s60min12.00s735.40s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred](/api-reference/erc20-network-data/tokens-transferred)`/erc20/network-data/tokens-transferred` > > > [tab] Day > > > > Windowblock?process?7day11.00s839.82s30day11.40s840.73s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s824.82s168hour11.00s824.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s733.33s60min12.00s735.40s > > Mutable: no · measured 2026-11-10 > > [Addresses Count](/api-reference/erc20-network-data/addresses-count)`/erc20/network-data/addresses-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s839.82s30day11.40s840.73s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s824.82s168hour11.00s824.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s733.33s60min12.00s735.40s > > Mutable: no · measured 2026-11-10 ## Market Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Price OHLCV](/api-reference/erc20-market-data/price-ohlcv) | `/erc20/market-data/price-ohlcv` | `token` | `date` `blockheight` `datetime` `open` `high` `low` `close` `volume` | > [accordion] Data latency > > [Price OHLCV](/api-reference/erc20-market-data/price-ohlcv)`/erc20/market-data/price-ohlcv` > > > [tab] Day > > > > Windowblock?process?7day—284.57s30day—295.35s > > > [tab] Hour > > > > Windowblock?process?24hour—301.64s168hour—293.68s > > > [tab] Minute > > > > Windowblock?process?10min—227.26s60min—219.00s > > Mutable: no · measured 2026-11-10 ## Flow Indicator | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Exchange Supply Ratio](/api-reference/erc20-flow-indicator/exchange-supply-ratio) | `/erc20/flow-indicator/exchange-supply-ratio` | `token` `exchange` | `blockheight` `date` `datetime` `supply_ratio` | > [accordion] Data latency > > [Exchange Supply Ratio](/api-reference/erc20-flow-indicator/exchange-supply-ratio)`/erc20/flow-indicator/exchange-supply-ratio` > > > [tab] Day > > > > Windowblock?process?7day11.00s1,715.26s30day11.40s1,610.14s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,714.23s168hour11.00s1,712.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,294.41s60min12.00s1,294.29s > > Mutable: no · measured 2026-11-10 # Ethereum (ETH) Source: https://docs.cryptoquant.com/catalog/eth All ETH metrics available in the CryptoQuant API — endpoints, parameters, response fields, and data latency. > Machine-readable version of this catalog: [catalog.json](/catalog/catalog.json) Each section lists its metrics; open **Data latency** under a section to see the block and process delay per resolution — see [how latency works](/guides/data-latency). ## Network Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Supply](/api-reference/eth-network-data/supply) | `/eth/network-data/supply` | — | `blockheight` `date` `datetime` `supply_total` `supply_new` | | [Velocity](/api-reference/eth-network-data/velocity) | `/eth/network-data/velocity` | — | `blockheight` `date` `datetime` `velocity_supply_total` | | [Contracts Count](/api-reference/eth-network-data/contracts-count) | `/eth/network-data/contracts-count` | — | `blockheight` `date` `datetime` `contracts_created_new` `contracts_destroyed_new` `contracts_count_total` | | [Transactions Count](/api-reference/eth-network-data/transactions-count) | `/eth/network-data/transactions-count` | — | `blockheight` `date` `datetime` `transactions_count_total` `transactions_count_mean` | | [Transactions Count Between EOA](/api-reference/eth-network-data/transactions-count-between-eoa) | `/eth/network-data/transactions-count-between-eoa` | — | `blockheight` `date` `datetime` `transactions_count_total` `transactions_count_mean` | | [Contract Calls Count External](/api-reference/eth-network-data/contract-calls-count-external) | `/eth/network-data/contract-calls-count-external` | — | `blockheight` `date` `datetime` `contract_calls_count_total` `contract_calls_count_mean` | | [Contract Calls Count Internal](/api-reference/eth-network-data/contract-calls-count-internal) | `/eth/network-data/contract-calls-count-internal` | — | `blockheight` `date` `datetime` `contract_calls_count_total` `contract_calls_count_mean` | | [Contract Calls Count](/api-reference/eth-network-data/contract-calls-count) | `/eth/network-data/contract-calls-count` | — | `blockheight` `date` `datetime` `contract_calls_count_total` `contract_calls_count_mean` | | [Transactions Count All](/api-reference/eth-network-data/transactions-count-all) | `/eth/network-data/transactions-count-all` | — | `blockheight` `date` `datetime` `transactions_count_total` `transactions_count_mean` | | [Addresses Count](/api-reference/eth-network-data/addresses-count) | `/eth/network-data/addresses-count` | — | `blockheight` `date` `datetime` `addresses_count_active` `addresses_count_sender` `addresses_count_receiver` | | [Addresses Count All](/api-reference/eth-network-data/addresses-count-all) | `/eth/network-data/addresses-count-all` | — | `blockheight` `date` `datetime` `addresses_count_active` `addresses_count_sender` `addresses_count_receiver` | | [Tokens Transferred Count](/api-reference/eth-network-data/tokens-transferred-count) | `/eth/network-data/tokens-transferred-count` | — | `blockheight` `date` `datetime` `tokens_transferred_count_total` `tokens_transferred_count_mean` | | [Tokens Transferred Count Between EOA](/api-reference/eth-network-data/tokens-transferred-count-between-eoa) | `/eth/network-data/tokens-transferred-count-between-eoa` | — | `blockheight` `date` `datetime` `tokens_transferred_count_total` `tokens_transferred_count_mean` | | [Tokens Transferred Count By Contract Calls External](/api-reference/eth-network-data/tokens-transferred-count-by-contract-calls-external) | `/eth/network-data/tokens-transferred-count-by-contract-calls-external` | — | `blockheight` `date` `datetime` `tokens_transferred_count_total` `tokens_transferred_count_mean` | | [Tokens Transferred Count By Contract Calls Internal](/api-reference/eth-network-data/tokens-transferred-count-by-contract-calls-internal) | `/eth/network-data/tokens-transferred-count-by-contract-calls-internal` | — | `blockheight` `date` `datetime` `tokens_transferred_count_total` `tokens_transferred_count_mean` | | [Tokens Transferred Count By Contract Calls](/api-reference/eth-network-data/tokens-transferred-count-by-contract-calls) | `/eth/network-data/tokens-transferred-count-by-contract-calls` | — | `blockheight` `date` `datetime` `tokens_transferred_count_total` `tokens_transferred_count_mean` | | [Tokens Transferred Count All](/api-reference/eth-network-data/tokens-transferred-count-all) | `/eth/network-data/tokens-transferred-count-all` | — | `blockheight` `date` `datetime` `tokens_transferred_count_total` `tokens_transferred_count_mean` | | [Tokens Transferred](/api-reference/eth-network-data/tokens-transferred) | `/eth/network-data/tokens-transferred` | — | `blockheight` `date` `datetime` `tokens_transferred_total` `tokens_transferred_mean` `tokens_transferred_median` `tokens_transferred_total_usd` `tokens_transferred_mean_usd` +1 | | [Tokens Transferred Between EOA](/api-reference/eth-network-data/tokens-transferred-between-eoa) | `/eth/network-data/tokens-transferred-between-eoa` | — | `blockheight` `date` `datetime` `tokens_transferred_total` `tokens_transferred_mean` `tokens_transferred_median` `tokens_transferred_total_usd` `tokens_transferred_mean_usd` +1 | | [Tokens Transferred By Contract Calls External](/api-reference/eth-network-data/tokens-transferred-by-contract-calls-external) | `/eth/network-data/tokens-transferred-by-contract-calls-external` | — | `blockheight` `date` `datetime` `tokens_transferred_total` `tokens_transferred_mean` `tokens_transferred_median` `tokens_transferred_total_usd` `tokens_transferred_mean_usd` +1 | | [Tokens Transferred By Contract Calls Internal](/api-reference/eth-network-data/tokens-transferred-by-contract-calls-internal) | `/eth/network-data/tokens-transferred-by-contract-calls-internal` | — | `blockheight` `date` `datetime` `tokens_transferred_total` `tokens_transferred_mean` `tokens_transferred_median` `tokens_transferred_total_usd` `tokens_transferred_mean_usd` +1 | | [Tokens Transferred By Contract Calls](/api-reference/eth-network-data/tokens-transferred-by-contract-calls) | `/eth/network-data/tokens-transferred-by-contract-calls` | — | `blockheight` `date` `datetime` `tokens_transferred_total` `tokens_transferred_mean` `tokens_transferred_median` `tokens_transferred_total_usd` `tokens_transferred_mean_usd` +1 | | [Tokens Transferred All](/api-reference/eth-network-data/tokens-transferred-all) | `/eth/network-data/tokens-transferred-all` | — | `blockheight` `date` `datetime` `tokens_transferred_total` `tokens_transferred_mean` `tokens_transferred_median` `tokens_transferred_total_usd` `tokens_transferred_mean_usd` +1 | | [Failed Transactions Count](/api-reference/eth-network-data/failed-transactions-count) | `/eth/network-data/failed-transactions-count` | — | `blockheight` `date` `datetime` `failed_transactions_count_total` | | [Failed Tokens Transferred Count](/api-reference/eth-network-data/failed-tokens-transferred-count) | `/eth/network-data/failed-tokens-transferred-count` | — | `blockheight` `date` `datetime` `failed_tokens_transferred_count_total` | | [Block Bytes](/api-reference/eth-network-data/block-bytes) | `/eth/network-data/block-bytes` | — | `blockheight` `date` `datetime` `block_bytes` | | [Block Count](/api-reference/eth-network-data/block-count) | `/eth/network-data/block-count` | — | `date` `datetime` `block_count` | | [Block Interval](/api-reference/eth-network-data/block-interval) | `/eth/network-data/block-interval` | — | `blockheight` `date` `datetime` `block_interval` | | [Fees](/api-reference/eth-network-data/fees) | `/eth/network-data/fees` | — | `blockheight` `date` `datetime` `fees_block_mean` `fees_block_mean_usd` `fees_total` `fees_total_usd` `fees_reward_percent` | | [Fees Burnt](/api-reference/eth-network-data/fees-burnt) | `/eth/network-data/fees-burnt` | — | `blockheight` `date` `datetime` `fees_burnt_total` `fees_burnt_total_usd` | | [Fees Tips](/api-reference/eth-network-data/fees-tips) | `/eth/network-data/fees-tips` | — | `blockheight` `date` `datetime` `fees_tips_total` `fees_tips_total_usd` | | [Fees Transaction](/api-reference/eth-network-data/fees-transaction) | `/eth/network-data/fees-transaction` | — | `blockheight` `date` `datetime` `fees_transaction_mean` `fees_transaction_mean_usd` `fees_transaction_median` `fees_transaction_median_usd` | | [Fees Burnt Transaction](/api-reference/eth-network-data/fees-burnt-transaction) | `/eth/network-data/fees-burnt-transaction` | — | `blockheight` `date` `datetime` `fees_burnt_transaction_mean` `fees_burnt_transaction_mean_usd` `fees_burnt_transaction_median` `fees_burnt_transaction_median_usd` | | [Fees Tips Transaction](/api-reference/eth-network-data/fees-tips-transaction) | `/eth/network-data/fees-tips-transaction` | — | `blockheight` `date` `datetime` `fees_tips_transaction_mean` `fees_tips_transaction_mean_usd` `fees_tips_transaction_median` `fees_tips_transaction_median_usd` | | [Blockreward](/api-reference/eth-network-data/blockreward) | `/eth/network-data/blockreward` | — | `blockheight` `date` `datetime` `blockreward` `blockreward_usd` | | [Blockreward Except Uncle](/api-reference/eth-network-data/blockreward-except-uncle) | `/eth/network-data/blockreward-except-uncle` | — | `blockheight` `date` `datetime` `blockreward_except_uncle` `blockreward_except_uncle_usd` | | [Gas](/api-reference/eth-network-data/gas) | `/eth/network-data/gas` | — | `blockheight` `date` `datetime` `gas_used_total` `gas_used_mean` `gas_price_mean` `gas_limit_mean` | | [Base Fee](/api-reference/eth-network-data/base-fee) | `/eth/network-data/base-fee` | — | `blockheight` `date` `datetime` `base_fee_mean` | | [Max Fee](/api-reference/eth-network-data/max-fee) | `/eth/network-data/max-fee` | — | `blockheight` `date` `datetime` `max_fee_mean` | | [Max Priority Fee](/api-reference/eth-network-data/max-priority-fee) | `/eth/network-data/max-priority-fee` | — | `blockheight` `date` `datetime` `max_priority_fee_mean` | | [Difficulty](/api-reference/eth-network-data/difficulty) | `/eth/network-data/difficulty` | — | `blockheight` `date` `datetime` `difficulty` | | [Hashrate](/api-reference/eth-network-data/hashrate) | `/eth/network-data/hashrate` | — | `blockheight` `date` `datetime` `hashrate` | | [Uncle Block Count](/api-reference/eth-network-data/uncle-block-count) | `/eth/network-data/uncle-block-count` | — | `blockheight` `date` `datetime` `uncle_block_count` | | [Uncle Blockreward](/api-reference/eth-network-data/uncle-blockreward) | `/eth/network-data/uncle-blockreward` | — | `blockheight` `date` `datetime` `uncle_blockreward` `uncle_blockreward_usd` | > [accordion] Data latency > > [Supply](/api-reference/eth-network-data/supply)`/eth/network-data/supply` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Velocity](/api-reference/eth-network-data/velocity)`/eth/network-data/velocity` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Contracts Count](/api-reference/eth-network-data/contracts-count)`/eth/network-data/contracts-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Transactions Count](/api-reference/eth-network-data/transactions-count)`/eth/network-data/transactions-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Transactions Count Between EOA](/api-reference/eth-network-data/transactions-count-between-eoa)`/eth/network-data/transactions-count-between-eoa` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Contract Calls Count External](/api-reference/eth-network-data/contract-calls-count-external)`/eth/network-data/contract-calls-count-external` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Contract Calls Count Internal](/api-reference/eth-network-data/contract-calls-count-internal)`/eth/network-data/contract-calls-count-internal` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Contract Calls Count](/api-reference/eth-network-data/contract-calls-count)`/eth/network-data/contract-calls-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Transactions Count All](/api-reference/eth-network-data/transactions-count-all)`/eth/network-data/transactions-count-all` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Addresses Count](/api-reference/eth-network-data/addresses-count)`/eth/network-data/addresses-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Addresses Count All](/api-reference/eth-network-data/addresses-count-all)`/eth/network-data/addresses-count-all` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred Count](/api-reference/eth-network-data/tokens-transferred-count)`/eth/network-data/tokens-transferred-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred Count Between EOA](/api-reference/eth-network-data/tokens-transferred-count-between-eoa)`/eth/network-data/tokens-transferred-count-between-eoa` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred Count By Contract Calls External](/api-reference/eth-network-data/tokens-transferred-count-by-contract-calls-external)`/eth/network-data/tokens-transferred-count-by-contract-calls-external` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred Count By Contract Calls Internal](/api-reference/eth-network-data/tokens-transferred-count-by-contract-calls-internal)`/eth/network-data/tokens-transferred-count-by-contract-calls-internal` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred Count By Contract Calls](/api-reference/eth-network-data/tokens-transferred-count-by-contract-calls)`/eth/network-data/tokens-transferred-count-by-contract-calls` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred Count All](/api-reference/eth-network-data/tokens-transferred-count-all)`/eth/network-data/tokens-transferred-count-all` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred](/api-reference/eth-network-data/tokens-transferred)`/eth/network-data/tokens-transferred` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred Between EOA](/api-reference/eth-network-data/tokens-transferred-between-eoa)`/eth/network-data/tokens-transferred-between-eoa` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred By Contract Calls External](/api-reference/eth-network-data/tokens-transferred-by-contract-calls-external)`/eth/network-data/tokens-transferred-by-contract-calls-external` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred By Contract Calls Internal](/api-reference/eth-network-data/tokens-transferred-by-contract-calls-internal)`/eth/network-data/tokens-transferred-by-contract-calls-internal` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred By Contract Calls](/api-reference/eth-network-data/tokens-transferred-by-contract-calls)`/eth/network-data/tokens-transferred-by-contract-calls` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred All](/api-reference/eth-network-data/tokens-transferred-all)`/eth/network-data/tokens-transferred-all` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Failed Transactions Count](/api-reference/eth-network-data/failed-transactions-count)`/eth/network-data/failed-transactions-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Failed Tokens Transferred Count](/api-reference/eth-network-data/failed-tokens-transferred-count)`/eth/network-data/failed-tokens-transferred-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Block Bytes](/api-reference/eth-network-data/block-bytes)`/eth/network-data/block-bytes` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Block Count](/api-reference/eth-network-data/block-count)`/eth/network-data/block-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > Mutable: no · measured 2026-11-10 > > [Block Interval](/api-reference/eth-network-data/block-interval)`/eth/network-data/block-interval` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Fees](/api-reference/eth-network-data/fees)`/eth/network-data/fees` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Fees Burnt](/api-reference/eth-network-data/fees-burnt)`/eth/network-data/fees-burnt` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Fees Tips](/api-reference/eth-network-data/fees-tips)`/eth/network-data/fees-tips` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Fees Transaction](/api-reference/eth-network-data/fees-transaction)`/eth/network-data/fees-transaction` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Fees Burnt Transaction](/api-reference/eth-network-data/fees-burnt-transaction)`/eth/network-data/fees-burnt-transaction` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Fees Tips Transaction](/api-reference/eth-network-data/fees-tips-transaction)`/eth/network-data/fees-tips-transaction` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Blockreward](/api-reference/eth-network-data/blockreward)`/eth/network-data/blockreward` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Blockreward Except Uncle](/api-reference/eth-network-data/blockreward-except-uncle)`/eth/network-data/blockreward-except-uncle` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Gas](/api-reference/eth-network-data/gas)`/eth/network-data/gas` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Base Fee](/api-reference/eth-network-data/base-fee)`/eth/network-data/base-fee` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Max Fee](/api-reference/eth-network-data/max-fee)`/eth/network-data/max-fee` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Max Priority Fee](/api-reference/eth-network-data/max-priority-fee)`/eth/network-data/max-priority-fee` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Difficulty](/api-reference/eth-network-data/difficulty)`/eth/network-data/difficulty` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Hashrate](/api-reference/eth-network-data/hashrate)`/eth/network-data/hashrate` > > > [tab] Day > > > > Windowblock?process?7day11.00s765.98s30day11.40s761.37s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s738.69s168hour11.00s740.89s > > > [tab] Block > > > > Windowblock?process?10min12.00s676.48s60min12.00s686.96s > > Mutable: no · measured 2026-11-10 > > [Uncle Block Count](/api-reference/eth-network-data/uncle-block-count)`/eth/network-data/uncle-block-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 > > [Uncle Blockreward](/api-reference/eth-network-data/uncle-blockreward)`/eth/network-data/uncle-blockreward` > > > [tab] Day > > > > Windowblock?process?7day11.00s780.82s30day11.40s776.36s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s743.71s168hour11.00s745.90s > > > [tab] Block > > > > Windowblock?process?10min12.00s691.74s60min12.00s701.52s > > Mutable: no · measured 2026-11-10 ## Entity Status | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Entity List](/api-reference/eth-entity-status/entity-list) | `/eth/status/entity-list` | `type` | `name` `symbol` `is_validated` `market_type` | ## 2.0 | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Total Value Staked](/api-reference/eth-20/total-value-staked) | `/eth/eth2/total-value-staked` | — | `blockheight` `date` `datetime` `total_value_staked` | | [Staking Inflow Total](/api-reference/eth-20/staking-inflow-total) | `/eth/eth2/staking-inflow-total` | — | `blockheight` `date` `datetime` `staking_inflow_total` | | [Staking Transaction Count](/api-reference/eth-20/staking-transaction-count) | `/eth/eth2/staking-transaction-count` | — | `blockheight` `date` `datetime` `staking_transaction_count` | | [Staking Validator Total](/api-reference/eth-20/staking-validator-total) | `/eth/eth2/staking-validator-total` | — | `blockheight` `date` `datetime` `staking_validator_total` | | [Depositor Count Total](/api-reference/eth-20/depositor-count-total) | `/eth/eth2/depositor-count-total` | — | `blockheight` `date` `datetime` `depositor_count_total` | | [Depositor Count New](/api-reference/eth-20/depositor-count-new) | `/eth/eth2/depositor-count-new` | — | `blockheight` `date` `datetime` `depositor_count_new` | | [Staking Rate](/api-reference/eth-20/staking-rate) | `/eth/eth2/staking-rate` | — | `blockheight` `date` `datetime` `staking_rate` | | [Phase 0 Success Rate](/api-reference/eth-20/phase-0-success-rate) | `/eth/eth2/phase0-success-rate` | — | `blockheight` `date` `datetime` `phase0_success_rate` | > [accordion] Data latency > > [Total Value Staked](/api-reference/eth-20/total-value-staked)`/eth/eth2/total-value-staked` > > > [tab] Day > > > > Windowblock?process?7day11.00s751.22s30day11.40s734.63s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s772.03s168hour11.00s774.11s > > > [tab] Block > > > > Windowblock?process?10min12.00s735.38s60min12.00s745.93s > > Mutable: no · measured 2026-11-10 > > [Staking Inflow Total](/api-reference/eth-20/staking-inflow-total)`/eth/eth2/staking-inflow-total` > > > [tab] Day > > > > Windowblock?process?7day11.00s751.22s30day11.40s734.63s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s772.03s168hour11.00s774.11s > > > [tab] Block > > > > Windowblock?process?10min12.00s735.38s60min12.00s745.93s > > Mutable: no · measured 2026-11-10 > > [Staking Transaction Count](/api-reference/eth-20/staking-transaction-count)`/eth/eth2/staking-transaction-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s751.22s30day11.40s734.63s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s772.03s168hour11.00s774.11s > > > [tab] Block > > > > Windowblock?process?10min12.00s735.38s60min12.00s745.93s > > Mutable: no · measured 2026-11-10 > > [Staking Validator Total](/api-reference/eth-20/staking-validator-total)`/eth/eth2/staking-validator-total` > > > [tab] Day > > > > Windowblock?process?7day11.00s751.22s30day11.40s734.63s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s772.03s168hour11.00s774.11s > > > [tab] Block > > > > Windowblock?process?10min12.00s735.38s60min12.00s745.93s > > Mutable: no · measured 2026-11-10 > > [Depositor Count Total](/api-reference/eth-20/depositor-count-total)`/eth/eth2/depositor-count-total` > > > [tab] Day > > > > Windowblock?process?7day11.00s751.22s30day11.40s734.63s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s772.03s168hour11.00s774.11s > > > [tab] Block > > > > Windowblock?process?10min12.00s735.38s60min12.00s745.93s > > Mutable: no · measured 2026-11-10 > > [Depositor Count New](/api-reference/eth-20/depositor-count-new)`/eth/eth2/depositor-count-new` > > > [tab] Day > > > > Windowblock?process?7day11.00s751.22s30day11.40s734.63s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s772.03s168hour11.00s774.11s > > > [tab] Block > > > > Windowblock?process?10min12.00s735.38s60min12.00s745.93s > > Mutable: no · measured 2026-11-10 > > [Staking Rate](/api-reference/eth-20/staking-rate)`/eth/eth2/staking-rate` > > > [tab] Day > > > > Windowblock?process?7day11.00s751.22s30day11.40s734.63s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s772.03s168hour11.00s774.11s > > > [tab] Block > > > > Windowblock?process?10min12.00s735.38s60min12.00s745.93s > > Mutable: no · measured 2026-11-10 > > [Phase 0 Success Rate](/api-reference/eth-20/phase-0-success-rate)`/eth/eth2/phase0-success-rate` > > > [tab] Day > > > > Windowblock?process?7day11.00s751.22s30day11.40s734.63s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s772.03s168hour11.00s774.11s > > > [tab] Block > > > > Windowblock?process?10min12.00s735.38s60min12.00s745.93s > > Mutable: no · measured 2026-11-10 ## Exchange Flows | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Reserve](/api-reference/eth-exchange-flows/reserve) | `/eth/exchange-flows/reserve` | `exchange` | `blockheight` `date` `datetime` `reserve` `reserve_usd` | | [Netflow](/api-reference/eth-exchange-flows/netflow) | `/eth/exchange-flows/netflow` | `exchange` | `blockheight` `date` `datetime` `netflow_total` | | [Inflow](/api-reference/eth-exchange-flows/inflow) | `/eth/exchange-flows/inflow` | `exchange` | `blockheight` `date` `datetime` `inflow_total` `inflow_top10` `inflow_mean` | | [Outflow](/api-reference/eth-exchange-flows/outflow) | `/eth/exchange-flows/outflow` | `exchange` | `blockheight` `date` `datetime` `outflow_total` `outflow_top10` `outflow_mean` | | [Transactions Count](/api-reference/eth-exchange-flows/transactions-count) | `/eth/exchange-flows/transactions-count` | `exchange` | `blockheight` `date` `datetime` `transactions_count_inflow` `transactions_count_outflow` | | [Addresses Count](/api-reference/eth-exchange-flows/addresses-count) | `/eth/exchange-flows/addresses-count` | `exchange` | `blockheight` `date` `datetime` `addresses_count_inflow` `addresses_count_outflow` | > [accordion] Data latency > > [Reserve](/api-reference/eth-exchange-flows/reserve)`/eth/exchange-flows/reserve` > > > [tab] Day > > > > Windowblock?process?7day11.00s772.08s30day11.40s774.34s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s761.83s168hour11.00s763.25s > > > [tab] Block > > > > Windowblock?process?10min12.00s714.13s60min12.00s730.51s > > Mutable: no · measured 2026-11-10 > > [Netflow](/api-reference/eth-exchange-flows/netflow)`/eth/exchange-flows/netflow` > > > [tab] Day > > > > Windowblock?process?7day11.00s772.08s30day11.40s774.34s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s761.83s168hour11.00s763.25s > > > [tab] Block > > > > Windowblock?process?10min12.00s714.13s60min12.00s730.51s > > Mutable: no · measured 2026-11-10 > > [Inflow](/api-reference/eth-exchange-flows/inflow)`/eth/exchange-flows/inflow` > > > [tab] Day > > > > Windowblock?process?7day11.00s772.08s30day11.40s774.34s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s761.83s168hour11.00s763.25s > > > [tab] Block > > > > Windowblock?process?10min12.00s714.13s60min12.00s730.51s > > Mutable: no · measured 2026-11-10 > > [Outflow](/api-reference/eth-exchange-flows/outflow)`/eth/exchange-flows/outflow` > > > [tab] Day > > > > Windowblock?process?7day11.00s772.08s30day11.40s774.34s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s761.83s168hour11.00s763.25s > > > [tab] Block > > > > Windowblock?process?10min12.00s714.13s60min12.00s730.51s > > Mutable: no · measured 2026-11-10 > > [Transactions Count](/api-reference/eth-exchange-flows/transactions-count)`/eth/exchange-flows/transactions-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s772.08s30day11.40s774.34s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s761.83s168hour11.00s763.25s > > > [tab] Block > > > > Windowblock?process?10min12.00s714.13s60min12.00s730.51s > > Mutable: no · measured 2026-11-10 > > [Addresses Count](/api-reference/eth-exchange-flows/addresses-count)`/eth/exchange-flows/addresses-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s772.08s30day11.40s774.34s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s761.83s168hour11.00s763.25s > > > [tab] Block > > > > Windowblock?process?10min12.00s714.13s60min12.00s730.51s > > Mutable: no · measured 2026-11-10 ## Market Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Price OHLCV](/api-reference/eth-market-data/price-ohlcv) | `/eth/market-data/price-ohlcv` | — | `blockheight` `date` `datetime` `open` `high` `low` `close` `volume` | | [Open Interest](/api-reference/eth-market-data/open-interest) | `/eth/market-data/open-interest` | `exchange` | `date` `datetime` `open_interest` | | [Funding Rates](/api-reference/eth-market-data/funding-rates) | `/eth/market-data/funding-rates` | `exchange` | `date` `datetime` `funding_rates` | | [Taker Buy Sell Stats](/api-reference/eth-market-data/taker-buy-sell-stats) | `/eth/market-data/taker-buy-sell-stats` | `exchange` | `date` `datetime` `taker_buy_volume` `taker_sell_volume` `taker_buy_ratio` `taker_sell_ratio` `taker_buy_sell_ratio` | | [Liquidations](/api-reference/eth-market-data/liquidations) | `/eth/market-data/liquidations` | `exchange` | `date` `datetime` `long_liquidations` `short_liquidations` `long_liquidations_usd` `short_liquidations_usd` | | [Coinbase Premium Index](/api-reference/eth-market-data/coinbase-premium-index) | `/eth/market-data/coinbase-premium-index` | — | `date` `datetime` `coinbase_premium_gap` `coinbase_premium_index` | | [Capitalization](/api-reference/eth-market-data/capitalization) | `/eth/market-data/capitalization` | — | `blockheight` `date` `datetime` `market_cap` | > [accordion] Data latency > > [Price OHLCV](/api-reference/eth-market-data/price-ohlcv)`/eth/market-data/price-ohlcv` > > > [tab] Day > > > > Windowblock?process?7day—273.74s30day—260.26s > > > [tab] Hour > > > > Windowblock?process?24hour—267.39s168hour—277.98s > > > [tab] Minute > > > > Windowblock?process?10min—70.16s60min—72.43s > > Mutable: no · measured 2026-11-10 > > [Open Interest](/api-reference/eth-market-data/open-interest)`/eth/market-data/open-interest` > > > [tab] Day > > > > Windowblock?process?7day—21.91s30day—21.85s > > > [tab] Hour > > > > Windowblock?process?24hour—16.04s168hour—16.05s > > > [tab] Minute > > > > Windowblock?process?10min—10.12s60min—10.11s > > Mutable: no · measured 2026-11-10 > > [Funding Rates](/api-reference/eth-market-data/funding-rates)`/eth/market-data/funding-rates` > > > [tab] Day > > > > Windowblock?process?7day—10.56s30day—10.57s > > > [tab] Hour > > > > Windowblock?process?24hour—5.57s168hour—5.56s > > > [tab] Minute > > > > Windowblock?process?10min—1.05s60min—1.05s > > Mutable: no · measured 2026-11-10 > > [Taker Buy Sell Stats](/api-reference/eth-market-data/taker-buy-sell-stats)`/eth/market-data/taker-buy-sell-stats` > > > [tab] Day > > > > Windowblock?process?7day—71.29s30day—71.17s > > > [tab] Hour > > > > Windowblock?process?24hour—8.10s168hour—8.10s > > > [tab] Minute > > > > Windowblock?process?10min—4.47s60min—4.47s > > Mutable: no · measured 2026-11-10 > > [Liquidations](/api-reference/eth-market-data/liquidations)`/eth/market-data/liquidations` > > > [tab] Day > > > > Windowblock?process?7day—21.91s30day—21.85s > > > [tab] Hour > > > > Windowblock?process?24hour—16.04s168hour—16.05s > > > [tab] Minute > > > > Windowblock?process?10min—10.12s60min—10.11s > > Mutable: no · measured 2026-11-10 > > [Coinbase Premium Index](/api-reference/eth-market-data/coinbase-premium-index)`/eth/market-data/coinbase-premium-index` > > > [tab] Day > > > > Windowblock?process?7day—249.59s30day—254.01s > > > [tab] Hour > > > > Windowblock?process?24hour—249.77s168hour—197.23s > > > [tab] Minute > > > > Windowblock?process?10min—162.44s60min—162.46s > > Mutable: no · measured 2026-11-10 > > [Capitalization](/api-reference/eth-market-data/capitalization)`/eth/market-data/capitalization` > > > [tab] Day > > > > Windowblock?process?7day—309.54s30day—303.19s > > > [tab] Hour > > > > Windowblock?process?24hour—308.40s168hour—295.16s > > > [tab] Block > > > > Windowblock?process?10min—660.35s60min—665.14s > > Mutable: no · measured 2026-11-10 ## Fund Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Market Price USD](/api-reference/eth-fund-data/market-price-usd) | `/eth/fund-data/market-price-usd` | `symbol` | `date` `price_usd_open` `price_usd_high` `price_usd_low` `price_usd_close` `price_usd_adj_close` | | [Market Volume](/api-reference/eth-fund-data/market-volume) | `/eth/fund-data/market-volume` | `symbol` | `date` `volume` | | [Market Premium](/api-reference/eth-fund-data/market-premium) | `/eth/fund-data/market-premium` | `symbol` | `date` `market_premium` | | [Digital Asset Holdings](/api-reference/eth-fund-data/digital-asset-holdings) | `/eth/fund-data/digital-asset-holdings` | `symbol` | `date` `digital_asset_holdings` | > [accordion] Data latency > > [Market Price USD](/api-reference/eth-fund-data/market-price-usd)`/eth/fund-data/market-price-usd` > > > [tab] Day > > > > Windowblock?process?7day—294,356.18s30day—178,274.47s > > Mutable: no · measured 2026-11-10 > > [Market Volume](/api-reference/eth-fund-data/market-volume)`/eth/fund-data/market-volume` > > > [tab] Day > > > > Windowblock?process?7day—294,356.18s30day—178,274.47s > > Mutable: no · measured 2026-11-10 > > [Market Premium](/api-reference/eth-fund-data/market-premium)`/eth/fund-data/market-premium` > > > [tab] Day > > > > Windowblock?process?7day—294,356.18s30day—178,274.47s > > Mutable: no · measured 2026-11-10 > > [Digital Asset Holdings](/api-reference/eth-fund-data/digital-asset-holdings)`/eth/fund-data/digital-asset-holdings` > > > [tab] Day > > > > Windowblock?process?7day11.00s294,338.37s30day11.00s177,093.25s > > Mutable: no · measured 2026-11-10 ## Flow Indicator | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Exchange Supply Ratio](/api-reference/eth-flow-indicator/exchange-supply-ratio) | `/eth/flow-indicator/exchange-supply-ratio` | `exchange` | `blockheight` `date` `datetime` `supply_ratio` | > [accordion] Data latency > > [Exchange Supply Ratio](/api-reference/eth-flow-indicator/exchange-supply-ratio)`/eth/flow-indicator/exchange-supply-ratio` > > > [tab] Day > > > > Windowblock?process?7day11.00s751.22s30day11.40s734.63s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s772.03s168hour11.00s774.11s > > > [tab] Block > > > > Windowblock?process?10min12.00s735.38s60min12.00s745.93s > > Mutable: no · measured 2026-11-10 ## Market Indicator | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Estimated Leverage Ratio](/api-reference/eth-market-indicator/estimated-leverage-ratio) | `/eth/market-indicator/estimated-leverage-ratio` | `exchange` | `blockheight` `date` `datetime` `estimated_leverage_ratio` | > [accordion] Data latency > > [Estimated Leverage Ratio](/api-reference/eth-market-indicator/estimated-leverage-ratio)`/eth/market-indicator/estimated-leverage-ratio` > > > [tab] Day > > > > Windowblock?process?7day11.00s772.08s30day11.40s774.34s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s761.83s168hour11.00s763.25s > > > [tab] Block > > > > Windowblock?process?10min12.00s714.13s60min12.00s730.51s > > Mutable: no · measured 2026-11-10 # Catalog Overview Source: https://docs.cryptoquant.com/catalog/overview Browse every metric available in the CryptoQuant API, organized by asset and category. The catalog lists every metric available in the CryptoQuant API: its endpoint, required parameters, and the fields returned in the response. Pick an asset to browse its metrics, or grab the whole catalog as JSON for programmatic discovery. > [!NOTE] > > **For AI agents:** the complete catalog (v1 and v2) is available as machine-readable JSON > at [`/catalog/catalog.json`](/catalog/catalog.json). Each entry includes the category, > metric name, endpoint path, parameters (with required flags and defaults), response field > names, and a `docs` path to the page documenting it. > [card] [Bitcoin (BTC)](/catalog/btc) > > Exchange flows, miner flows, network & market indicators, mempool, Lightning Network. > [card] [Ethereum (ETH)](/catalog/eth) > > Exchange flows, ETH 2.0, fund data, market & network data. > [card] [XRP Ledger (XRP)](/catalog/xrp) > > XRP entity flows, DEX & AMM data, network indicators. > [card] [TRON (TRX)](/catalog/trx) > > TRX market data, TRON network data, DeFi. > [card] [Stablecoins](/catalog/stablecoin) > > USDT, USDC, DAI and more — flows, market & network data. > [card] [ERC-20 tokens](/catalog/erc20) > > Exchange flows, flow indicators, market & network data. > [card] [Altcoins](/catalog/alt) > > Market data for supported altcoin symbols. ## Supported token lists > [card] [Stablecoins](/catalog/supported-stablecoins) > [card] [ERC20 tokens](/catalog/supported-erc20-tokens) > [card] [Alt coins](/catalog/supported-alt-coins) # Stablecoins Source: https://docs.cryptoquant.com/catalog/stablecoin All Stablecoin metrics available in the CryptoQuant API — endpoints, parameters, response fields, and data latency. > Machine-readable version of this catalog: [catalog.json](/catalog/catalog.json) Each section lists its metrics; open **Data latency** under a section to see the block and process delay per resolution — see [how latency works](/guides/data-latency). ## Entity Status | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Entity List](/api-reference/stablecoin-entity-status/entity-list) | `/stablecoin/status/entity-list` | `token` `type` | `name` `symbol` `is_validated` `market_type` | ## Exchange Flows | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Reserve](/api-reference/stablecoin-exchange-flows/reserve) | `/stablecoin/exchange-flows/reserve` | `token` `exchange` | `blockheight` `date` `datetime` `reserve` | | [Netflow](/api-reference/stablecoin-exchange-flows/netflow) | `/stablecoin/exchange-flows/netflow` | `token` `exchange` | `blockheight` `date` `datetime` `netflow_total` | | [Inflow](/api-reference/stablecoin-exchange-flows/inflow) | `/stablecoin/exchange-flows/inflow` | `token` `exchange` | `blockheight` `date` `datetime` `inflow_total` `inflow_top10` `inflow_mean` | | [Outflow](/api-reference/stablecoin-exchange-flows/outflow) | `/stablecoin/exchange-flows/outflow` | `token` `exchange` | `blockheight` `date` `datetime` `outflow_total` `outflow_top10` `outflow_mean` | | [Transactions Count](/api-reference/stablecoin-exchange-flows/transactions-count) | `/stablecoin/exchange-flows/transactions-count` | `token` `exchange` | `blockheight` `date` `datetime` `transactions_count_inflow` `transactions_count_outflow` | | [Addresses Count](/api-reference/stablecoin-exchange-flows/addresses-count) | `/stablecoin/exchange-flows/addresses-count` | `token` `exchange` | `blockheight` `date` `datetime` `addresses_count_inflow` `addresses_count_outflow` | > [accordion] Data latency > > [Reserve](/api-reference/stablecoin-exchange-flows/reserve)`/stablecoin/exchange-flows/reserve` > > > [tab] Day > > > > Windowblock?process?7day11.00s274,306.29s30day11.40s1,267,905.89s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,713.57s168hour11.00s1,712.24s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,293.67s60min12.00s1,293.61s > > Mutable: no · measured 2026-11-10 > > [Netflow](/api-reference/stablecoin-exchange-flows/netflow)`/stablecoin/exchange-flows/netflow` > > > [tab] Day > > > > Windowblock?process?7day11.00s274,306.29s30day11.40s1,267,905.89s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,713.57s168hour11.00s1,712.24s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,293.67s60min12.00s1,293.61s > > Mutable: no · measured 2026-11-10 > > [Inflow](/api-reference/stablecoin-exchange-flows/inflow)`/stablecoin/exchange-flows/inflow` > > > [tab] Day > > > > Windowblock?process?7day11.00s274,306.29s30day11.40s1,267,905.89s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,713.57s168hour11.00s1,712.24s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,293.67s60min12.00s1,293.61s > > Mutable: no · measured 2026-11-10 > > [Outflow](/api-reference/stablecoin-exchange-flows/outflow)`/stablecoin/exchange-flows/outflow` > > > [tab] Day > > > > Windowblock?process?7day11.00s274,306.29s30day11.40s1,267,905.89s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,713.57s168hour11.00s1,712.24s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,293.67s60min12.00s1,293.61s > > Mutable: no · measured 2026-11-10 > > [Transactions Count](/api-reference/stablecoin-exchange-flows/transactions-count)`/stablecoin/exchange-flows/transactions-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s274,306.29s30day11.40s1,267,905.89s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,713.57s168hour11.00s1,712.24s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,293.67s60min12.00s1,293.61s > > Mutable: no · measured 2026-11-10 > > [Addresses Count](/api-reference/stablecoin-exchange-flows/addresses-count)`/stablecoin/exchange-flows/addresses-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s1,714.61s30day11.40s1,609.49s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,713.57s168hour11.00s1,712.24s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,293.67s60min12.00s1,293.61s > > Mutable: no · measured 2026-11-10 ## Network Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Supply](/api-reference/stablecoin-network-data/supply) | `/stablecoin/network-data/supply` | `token` | `datetime` `blockheight` `date` `supply_total` `supply_minted` `supply_burned` `supply_circulating` `supply_issued` +1 | | [Events Count](/api-reference/stablecoin-network-data/events-count) | `/stablecoin/network-data/events-count` | `token` | `datetime` `blockheight` `date` `events_transfer_count` `events_mint_count` `events_issue_count` `events_burn_count` `events_redeem_count` | | [Tokens Transferred](/api-reference/stablecoin-network-data/tokens-transferred) | `/stablecoin/network-data/tokens-transferred` | `token` | `datetime` `blockheight` `date` `tokens_transferred_total` `tokens_transferred_mean` | | [Addresses Count](/api-reference/stablecoin-network-data/addresses-count) | `/stablecoin/network-data/addresses-count` | `token` | `datetime` `blockheight` `date` `addresses_active_count` `addresses_active_sender_count` `addresses_active_receiver_count` `addresses_active_sender_percent` `addresses_active_receiver_percent` | > [accordion] Data latency > > [Supply](/api-reference/stablecoin-network-data/supply)`/stablecoin/network-data/supply` > > > [tab] Day > > > > Windowblock?process?7day11.00s719.47s30day11.40s753.06s > > > [tab] Block > > > > Windowblock?process?10min12.00s629.96s60min12.00s630.19s > > Mutable: no · measured 2026-11-10 > > [Events Count](/api-reference/stablecoin-network-data/events-count)`/stablecoin/network-data/events-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s719.47s30day11.40s753.06s > > > [tab] Block > > > > Windowblock?process?10min12.00s683.51s60min12.00s683.95s > > Mutable: no · measured 2026-11-10 > > [Tokens Transferred](/api-reference/stablecoin-network-data/tokens-transferred)`/stablecoin/network-data/tokens-transferred` > > > [tab] Day > > > > Windowblock?process?7day11.00s719.47s30day11.40s753.06s > > > [tab] Block > > > > Windowblock?process?10min12.00s683.51s60min12.00s683.95s > > Mutable: no · measured 2026-11-10 > > [Addresses Count](/api-reference/stablecoin-network-data/addresses-count)`/stablecoin/network-data/addresses-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s719.47s30day11.40s753.06s > > > [tab] Block > > > > Windowblock?process?10min12.00s683.51s60min12.00s683.95s > > Mutable: no · measured 2026-11-10 ## Market Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Price OHLCV](/api-reference/stablecoin-market-data/price-ohlcv) | `/stablecoin/market-data/price-ohlcv` | `token` | `date` `blockheight` `datetime` `open` `high` `low` `close` `volume` | | [Capitalization](/api-reference/stablecoin-market-data/capitalization) | `/stablecoin/market-data/capitalization` | `token` | `date` `blockheight` `datetime` `market_cap` | > [accordion] Data latency > > [Price OHLCV](/api-reference/stablecoin-market-data/price-ohlcv)`/stablecoin/market-data/price-ohlcv` > > > [tab] Day > > > > Windowblock?process?7day—268.08s30day—269.49s > > > [tab] Hour > > > > Windowblock?process?24hour—260.87s168hour—258.42s > > > [tab] Minute > > > > Windowblock?process?10min—153.44s60min—151.59s > > Mutable: no · measured 2026-11-10 > > [Capitalization](/api-reference/stablecoin-market-data/capitalization)`/stablecoin/market-data/capitalization` > > > [tab] Day > > > > Windowblock?process?7day11.00s719.49s30day11.40s753.08s > > > [tab] Block > > > > Windowblock?process?10min12.00s683.54s60min12.00s683.98s > > Mutable: no · measured 2026-11-10 ## Flow Indicator | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Exchange Supply Ratio](/api-reference/stablecoin-flow-indicator/exchange-supply-ratio) | `/stablecoin/flow-indicator/exchange-supply-ratio` | `token` `exchange` | `blockheight` `date` `datetime` `supply_ratio` | > [accordion] Data latency > > [Exchange Supply Ratio](/api-reference/stablecoin-flow-indicator/exchange-supply-ratio)`/stablecoin/flow-indicator/exchange-supply-ratio` > > > [tab] Day > > > > Windowblock?process?7day11.00s1,714.61s30day11.40s1,609.49s > > > [tab] Hour > > > > Windowblock?process?24hour11.00s1,713.57s168hour11.00s1,712.24s > > > [tab] Block > > > > Windowblock?process?10min12.00s1,293.67s60min12.00s1,293.61s > > Mutable: no · measured 2026-11-10 # Supported Alt List Source: https://docs.cryptoquant.com/catalog/supported-alt-coins Tokens supported by the CryptoQuant API. | Name | Token | Supported Categories | | - | - | - | | Cardano | `ada` | - Market Data | | Algorand | `algo` | - Market Data | | Arweave | `ar` | - Market Data | | Cosmos | `atom` | - Market Data | | Auto | `auto` | - Market Data | | Avalanche | `avax` | - Market Data | | BNB | `bnb` | - Market Data | | PancakeSwap | `cake` | - Market Data | | Celo | `celo` | - Market Data | | Dash | `dash` | - Market Data | | Decred | `dcr` | - Market Data | | Dogecoin | `doge` | - Market Data | | Polkadot | `dot` | - Market Data | | Elrond | `egld` | - Market Data | | Ethereum Classic | `etc` | - Market Data | | Filecoin | `fil` | - Market Data | | Flow | `flow` | - Market Data | | Fantom | `ftm` | - Market Data | | Hedera | `hbar` | - Market Data | | Helium | `hnt` | - Market Data | | Internet Computer | `icp` | - Market Data | | IOTA | `iota` | - Market Data | | IoTeX | `iotx` | - Market Data | | Kusama | `ksm` | - Market Data | | Terra | `luna` | - Market Data | | Mina | `mina` | - Market Data | | NEAR Protocol | `near` | - Market Data | | Neo | `neo` | - Market Data | | Harmony | `one` | - Market Data | | Qtum | `qtum` | - Market Data | | Oasis Network | `rose` | - Market Data | | THORChain | `rune` | - Market Data | | Ravencoin | `rvn` | - Market Data | | Solana | `sol` | - Market Data | | Stacks | `stx` | - Market Data | | Theta Fuel | `tfuel` | - Market Data | | Theta Nwetwork | `theta` | - Market Data | | TRON | `trx` | - Market Data | | VeChain | `vet` | - Market Data | | Waves | `waves` | - Market Data | | WAX | `waxp` | - Market Data | | eCash | `xec` | - Market Data | | NEM | `xem` | - Market Data | | Stellar | `xlm` | - Market Data | | Monero | `xmr` | - Market Data | | Tezos | `xtz` | - Market Data | | Zcash | `zec` | - Market Data | # Supported Assets Source: https://docs.cryptoquant.com/catalog/supported-assets Every asset covered by the CryptoQuant API — BTC, ETH, XRP, TRX, BNB, SOL, stablecoins, ERC20 tokens, and more — with their symbols and categories. List of assets supported by CryptoQuant. | Asset | Symbol | Category | Link | | - | - | - | - | | Bitcoin | `BTC` | BTC | [Link](https://cryptoquant.com/asset/btc/summary) | | Ethereum | `ETH` | ETH | [Link](https://cryptoquant.com/asset/eth/summary) | | XRP | `XRP` | XRP | [Link](https://cryptoquant.com/asset/xrp/summary) | | BNB | `BNB` | ALT | [Link](https://cryptoquant.com/asset/bnb/summary) | | Solana | `SOL` | ALT | [Link](https://cryptoquant.com/asset/sol/summary) | | Dogecoin | `DOGE` | ALT | [Link](https://cryptoquant.com/asset/doge/summary) | | Cardano | `ADA` | ALT | [Link](https://cryptoquant.com/asset/ada/summary) | | TRON | `TRX` | TRX | [Link](https://cryptoquant.com/asset/trx/summary) | | Wrapped BTC | `WBTC` | ERC20 | [Link](https://cryptoquant.com/asset/wbtc/summary) | | Avalanche | `AVAX` | ALT | [Link](https://cryptoquant.com/asset/avax/summary) | | Sui | `SUI` | ALT | [Link](https://cryptoquant.com/asset/sui/summary) | | All Stablecoins(ERC20) | \`\` | STABLECOIN | [Link](https://cryptoquant.com/asset/stablecoin/summary) | | Tether USD(ERC20) | `USDT(ETH)` | STABLECOIN | [Link](https://cryptoquant.com/asset/usdt_eth/summary) | | Tether USD(TRC20) | `USDT(TRX)` | STABLECOIN | [Link](https://cryptoquant.com/asset/usdt_trx/summary) | | Tether USD(Omni) | `USDT(Omni)` | STABLECOIN | [Link](https://cryptoquant.com/asset/usdt_omni/summary) | | USD Coin(ERC20) | `USDC` | STABLECOIN | [Link](https://cryptoquant.com/asset/usdc/summary) | | Dai(ERC20) | `DAI` | STABLECOIN | [Link](https://cryptoquant.com/asset/dai/summary) | | True USD(ERC20) | `TUSD` | STABLECOIN | [Link](https://cryptoquant.com/asset/tusd/summary) | | Pax Dollar(ERC20) | `USDP` | STABLECOIN | [Link](https://cryptoquant.com/asset/usdp/summary) | | Binance USD(ERC20) | `BUSD` | STABLECOIN | [Link](https://cryptoquant.com/asset/busd/summary) | | Gemini Dollar(ERC20) | `GUSD` | STABLECOIN | [Link](https://cryptoquant.com/asset/gusd/summary) | | sUSD(ERC20) | `SUSD` | STABLECOIN | [Link](https://cryptoquant.com/asset/susd/summary) | | Single Collateral Dai(ERC20) | `SAI` | STABLECOIN | [Link](https://cryptoquant.com/asset/sai/summary) | | USDK(ERC20) | `USDK` | STABLECOIN | [Link](https://cryptoquant.com/asset/usdk/summary) | | Huobi USD(ERC20) | `HUSD` | STABLECOIN | [Link](https://cryptoquant.com/asset/husd/summary) | | Bitcoin Cash | `BCH` | ALT | [Link](https://cryptoquant.com/asset/bch/summary) | | Monero | `XMR` | ALT | [Link](https://cryptoquant.com/asset/xmr/summary) | | Chainlink | `LINK` | ERC20 | [Link](https://cryptoquant.com/asset/link/summary) | | UNUS SED LEO | `LEO` | ALT | [Link](https://cryptoquant.com/asset/leo/summary) | | Stellar | `XLM` | ALT | [Link](https://cryptoquant.com/asset/xlm/summary) | | Ethena USDe | `USDE` | ALT | [Link](https://cryptoquant.com/asset/usde/summary) | | Hyperliquid | `HYPE` | ALT | [Link](https://cryptoquant.com/asset/hype/summary) | | Zcash | `ZEC` | ALT | [Link](https://cryptoquant.com/asset/zec/summary) | | Litecoin | `LTC` | ALT | [Link](https://cryptoquant.com/asset/ltc/summary) | | Hedera | `HBAR` | ALT | [Link](https://cryptoquant.com/asset/hbar/summary) | | SHIBA INU | `SHIB` | ERC20 | [Link](https://cryptoquant.com/asset/shib/summary) | | Toncoin | `TON` | ALT | [Link](https://cryptoquant.com/asset/ton/summary) | | Cronos | `CRO` | ERC20 | [Link](https://cryptoquant.com/asset/cro/summary) | | Polkadot | `DOT` | ALT | [Link](https://cryptoquant.com/asset/dot/summary) | | Uniswap | `UNI` | ERC20 | [Link](https://cryptoquant.com/asset/uni/summary) | | Mantle | `MNT` | ALT | [Link](https://cryptoquant.com/asset/mnt/summary) | | Bittensor | `TAO` | ALT | [Link](https://cryptoquant.com/asset/tao/summary) | | Bitget Token | `BGB` | ALT | [Link](https://cryptoquant.com/asset/bgb/summary) | | Aave | `AAVE` | ERC20 | [Link](https://cryptoquant.com/asset/aave/summary) | | Tether Gold | `XAUT` | ERC20 | [Link](https://cryptoquant.com/asset/xaut/summary) | | OKB | `OKB` | ERC20 | [Link](https://cryptoquant.com/asset/okb/summary) | | Pepe | `PEPE` | ALT | [Link](https://cryptoquant.com/asset/pepe/summary) | | Internet Computer | `ICP` | ALT | [Link](https://cryptoquant.com/asset/icp/summary) | | PAX Gold | `PAXG` | ERC20 | [Link](https://cryptoquant.com/asset/paxg/summary) | | NEAR Protocol | `NEAR` | ALT | [Link](https://cryptoquant.com/asset/near/summary) | | Ethereum Classic | `ETC` | ALT | [Link](https://cryptoquant.com/asset/etc/summary) | | Ondo | `ONDO` | ALT | [Link](https://cryptoquant.com/asset/ondo/summary) | | Pi | `PI` | ALT | [Link](https://cryptoquant.com/asset/pi/summary) | | Ethena | `ENA` | ERC20 | [Link](https://cryptoquant.com/asset/ena/summary) | | KuCoin Token | `KCS` | ERC20 | [Link](https://cryptoquant.com/asset/kcs/summary) | | POL (prev. MATIC) | `POL` | ALT | [Link](https://cryptoquant.com/asset/pol/summary) | | Worldcoin | `WLD` | ERC20 | [Link](https://cryptoquant.com/asset/wld/summary) | | Aptos | `APT` | ALT | [Link](https://cryptoquant.com/asset/apt/summary) | | Cosmos | `ATOM` | ALT | [Link](https://cryptoquant.com/asset/atom/summary) | | GateToken | `GT` | ERC20 | [Link](https://cryptoquant.com/asset/gt/summary) | | Kaspa | `KAS` | ALT | [Link](https://cryptoquant.com/asset/kas/summary) | | Algorand | `ALGO` | ALT | [Link](https://cryptoquant.com/asset/algo/summary) | | Render | `RENDER` | ALT | [Link](https://cryptoquant.com/asset/render/summary) | | Arbitrum | `ARB` | ALT | [Link](https://cryptoquant.com/asset/arb/summary) | | Filecoin | `FIL` | ALT | [Link](https://cryptoquant.com/asset/fil/summary) | | OFFICIAL TRUMP | `TRUMP` | ALT | [Link](https://cryptoquant.com/asset/trump/summary) | | Quant | `QNT` | ERC20 | [Link](https://cryptoquant.com/asset/qnt/summary) | | VeChain | `VET` | ALT | [Link](https://cryptoquant.com/asset/vet/summary) | | Flare | `FLR` | ALT | [Link](https://cryptoquant.com/asset/flr/summary) | | Dash | `DASH` | ALT | [Link](https://cryptoquant.com/asset/dash/summary) | | Story | `IP` | ALT | [Link](https://cryptoquant.com/asset/ip/summary) | | Bonk | `BONK` | ERC20 | [Link](https://cryptoquant.com/asset/bonk/summary) | | XDC Network | `XDC` | ALT | [Link](https://cryptoquant.com/asset/xdc/summary) | | LayerZero | `ZRO` | ERC20 | [Link](https://cryptoquant.com/asset/zro/summary) | | Sei | `SEI` | ALT | [Link](https://cryptoquant.com/asset/sei/summary) | | PancakeSwap | `CAKE` | ALT | [Link](https://cryptoquant.com/asset/cake/summary) | | Beldex | `BDX` | ALT | [Link](https://cryptoquant.com/asset/bdx/summary) | | Pudgy Penguins | `PENGU` | ALT | [Link](https://cryptoquant.com/asset/pengu/summary) | | Jupiter | `JUP` | ALT | [Link](https://cryptoquant.com/asset/jup/summary) | | Tezos | `XTZ` | ALT | [Link](https://cryptoquant.com/asset/xtz/summary) | | Optimism | `OP` | ALT | [Link](https://cryptoquant.com/asset/op/summary) | | Nexo | `NEXO` | ERC20 | [Link](https://cryptoquant.com/asset/nexo/summary) | | Stacks | `STX` | ALT | [Link](https://cryptoquant.com/asset/stx/summary) | | Virtuals Protocol | `VIRTUAL` | ERC20 | [Link](https://cryptoquant.com/asset/virtual/summary) | | Fetch.ai | `FET` | ERC20 | [Link](https://cryptoquant.com/asset/fet/summary) | | Curve DAO Token | `CRV` | ERC20 | [Link](https://cryptoquant.com/asset/crv/summary) | | Chiliz | `CHZ` | ERC20 | [Link](https://cryptoquant.com/asset/chz/summary) | | Immutable X | `IMX` | ERC20 | [Link](https://cryptoquant.com/asset/imx/summary) | | Fasttoken | `FTN` | ALT | [Link](https://cryptoquant.com/asset/ftn/summary) | | Injective | `INJ` | ERC20 | [Link](https://cryptoquant.com/asset/inj/summary) | | Morpho | `MORPHO` | ERC20 | [Link](https://cryptoquant.com/asset/morpho/summary) | | Axie Infinity | `AXS` | ERC20 | [Link](https://cryptoquant.com/asset/axs/summary) | | Lido DAO | `LDO` | ERC20 | [Link](https://cryptoquant.com/asset/ldo/summary) | | Aerodrome Finance | `AERO` | ALT | [Link](https://cryptoquant.com/asset/aero/summary) | | The Sandbox | `SAND` | ERC20 | [Link](https://cryptoquant.com/asset/sand/summary) | | ether.fi | `ETHFI` | ERC20 | [Link](https://cryptoquant.com/asset/ethfi/summary) | | FLOKI | `FLOKI` | ERC20 | [Link](https://cryptoquant.com/asset/floki/summary) | | Celestia | `TIA` | ALT | [Link](https://cryptoquant.com/asset/tia/summary) | | Sun \[New] | `SUN` | ALT | [Link](https://cryptoquant.com/asset/sun/summary) | | BitTorrent \[New] | `BTT` | ALT | [Link](https://cryptoquant.com/asset/btt/summary) | | The Graph | `GRT` | ERC20 | [Link](https://cryptoquant.com/asset/grt/summary) | | JUST | `JST` | ALT | [Link](https://cryptoquant.com/asset/jst/summary) | | Starknet | `STRK` | ERC20 | [Link](https://cryptoquant.com/asset/strk/summary) | | SPX6900 | `SPX` | ERC20 | [Link](https://cryptoquant.com/asset/spx/summary) | | Maple Finance | `SYRUP` | ERC20 | [Link](https://cryptoquant.com/asset/syrup/summary) | | IOTA | `IOTA` | ALT | [Link](https://cryptoquant.com/asset/iota/summary) | | Trust Wallet Token | `TWT` | ALT | [Link](https://cryptoquant.com/asset/twt/summary) | | Telcoin | `TEL` | ERC20 | [Link](https://cryptoquant.com/asset/tel/summary) | | Conflux | `CFX` | ALT | [Link](https://cryptoquant.com/asset/cfx/summary) | | JasmyCoin | `JASMY` | ERC20 | [Link](https://cryptoquant.com/asset/jasmy/summary) | | Pendle | `PENDLE` | ERC20 | [Link](https://cryptoquant.com/asset/pendle/summary) | | Gnosis | `GNO` | ERC20 | [Link](https://cryptoquant.com/asset/gno/summary) | | Bitcoin SV | `BSV` | ALT | [Link](https://cryptoquant.com/asset/bsv/summary) | | Kaia | `KAIA` | ALT | [Link](https://cryptoquant.com/asset/kaia/summary) | | APENFT | `NFT` | ERC20 | [Link](https://cryptoquant.com/asset/nft/summary) | | Ethereum Name Service | `ENS` | ERC20 | [Link](https://cryptoquant.com/asset/ens/summary) | | Decred | `DCR` | ALT | [Link](https://cryptoquant.com/asset/dcr/summary) | | Decentraland | `MANA` | ERC20 | [Link](https://cryptoquant.com/asset/mana/summary) | | dogwifhat | `WIF` | ALT | [Link](https://cryptoquant.com/asset/wif/summary) | | Pyth Network | `PYTH` | ALT | [Link](https://cryptoquant.com/asset/pyth/summary) | | Fartcoin | `FARTCOIN` | ALT | [Link](https://cryptoquant.com/asset/fartcoin/summary) | | Theta Network | `THETA` | ALT | [Link](https://cryptoquant.com/asset/theta/summary) | | Gala | `GALA` | ERC20 | [Link](https://cryptoquant.com/asset/gala/summary) | | Zebec Network | `ZBCN` | ALT | [Link](https://cryptoquant.com/asset/zbcn/summary) | | Basic Attention Token | `BAT` | ERC20 | [Link](https://cryptoquant.com/asset/bat/summary) | | Raydium | `RAY` | ALT | [Link](https://cryptoquant.com/asset/ray/summary) | | ZKsync | `ZK` | ALT | [Link](https://cryptoquant.com/asset/zk/summary) | | DeXe | `DEXE` | ERC20 | [Link](https://cryptoquant.com/asset/dexe/summary) | | Neo | `NEO` | ALT | [Link](https://cryptoquant.com/asset/neo/summary) | | Onyxcoin | `XCN` | ERC20 | [Link](https://cryptoquant.com/asset/xcn/summary) | | Compound | `COMP` | ERC20 | [Link](https://cryptoquant.com/asset/comp/summary) | | Arweave | `AR` | ALT | [Link](https://cryptoquant.com/asset/ar/summary) | | Golem | `GLM` | ERC20 | [Link](https://cryptoquant.com/asset/glm/summary) | | Helium | `HNT` | ALT | [Link](https://cryptoquant.com/asset/hnt/summary) | | Ultima | `ULTIMA` | ALT | [Link](https://cryptoquant.com/asset/ultima/summary) | | SwissBorg | `BORG` | ERC20 | [Link](https://cryptoquant.com/asset/borg/summary) | | Zeebu | `ZBU` | ERC20 | [Link](https://cryptoquant.com/asset/zbu/summary) | | Sonic (prev. FTM) | `S` | ALT | [Link](https://cryptoquant.com/asset/s/summary) | | eCash | `XEC` | ALT | [Link](https://cryptoquant.com/asset/xec/summary) | | THORChain | `RUNE` | ALT | [Link](https://cryptoquant.com/asset/rune/summary) | | Terra Classic | `LUNC` | ALT | [Link](https://cryptoquant.com/asset/lunc/summary) | | Convex Finance | `CVX` | ERC20 | [Link](https://cryptoquant.com/asset/cvx/summary) | | 1inch Network | `1INCH` | ERC20 | [Link](https://cryptoquant.com/asset/1inch/summary) | | Walrus | `WAL` | ALT | [Link](https://cryptoquant.com/asset/wal/summary) | | OriginTrail | `TRAC` | ERC20 | [Link](https://cryptoquant.com/asset/trac/summary) | | SafePal | `SFP` | ALT | [Link](https://cryptoquant.com/asset/sfp/summary) | | DeepBook Protocol | `DEEP` | ALT | [Link](https://cryptoquant.com/asset/deep/summary) | | EigenLayer | `EIGEN` | ERC20 | [Link](https://cryptoquant.com/asset/eigen/summary) | | Horizen | `ZEN` | ALT | [Link](https://cryptoquant.com/asset/zen/summary) | | MX Token | `MX` | ERC20 | [Link](https://cryptoquant.com/asset/mx/summary) | | Elrond | `EGLD` | ALT | [Link](https://cryptoquant.com/asset/egld/summary) | | Amp | `AMP` | ERC20 | [Link](https://cryptoquant.com/asset/amp/summary) | | Cheems (cheems.pet) | `CHEEMS` | ALT | [Link](https://cryptoquant.com/asset/cheems/summary) | | Wormhole | `W` | ERC20 | [Link](https://cryptoquant.com/asset/w/summary) | | FTX Token | `FTT` | ERC20 | [Link](https://cryptoquant.com/asset/ftt/summary) | | Aethir | `ATH` | ERC20 | [Link](https://cryptoquant.com/asset/ath/summary) | | Official Melania Meme | `MELANIA` | ALT | [Link](https://cryptoquant.com/asset/melania/summary) | | WEMIX | `WEMIX` | ALT | [Link](https://cryptoquant.com/asset/wemix/summary) | | Synthetix | `SNX` | ERC20 | [Link](https://cryptoquant.com/asset/snx/summary) | | Reserve Rights | `RSR` | ERC20 | [Link](https://cryptoquant.com/asset/rsr/summary) | | Beam | `BEAM` | ERC20 | [Link](https://cryptoquant.com/asset/beam/summary) | | dYdX | `DYDX` | ERC20 | [Link](https://cryptoquant.com/asset/dydx/summary) | | Oasis Network | `ROSE` | ALT | [Link](https://cryptoquant.com/asset/rose/summary) | | Concordium | `CCD` | ALT | [Link](https://cryptoquant.com/asset/ccd/summary) | | ApeCoin | `APE` | ERC20 | [Link](https://cryptoquant.com/asset/ape/summary) | | Jito | `JTO` | ALT | [Link](https://cryptoquant.com/asset/jto/summary) | | Flow | `FLOW` | ALT | [Link](https://cryptoquant.com/asset/flow/summary) | | Livepeer | `LPT` | ERC20 | [Link](https://cryptoquant.com/asset/lpt/summary) | | Zano | `ZANO` | ALT | [Link](https://cryptoquant.com/asset/zano/summary) | | Brett (Based) | `BRETT` | ALT | [Link](https://cryptoquant.com/asset/brett/summary) | | Creditcoin | `CTC` | ALT | [Link](https://cryptoquant.com/asset/ctc/summary) | | Qtum | `QTUM` | ALT | [Link](https://cryptoquant.com/asset/qtum/summary) | | Venice Token | `VVV` | ALT | [Link](https://cryptoquant.com/asset/vvv/summary) | | Open Campus | `EDU` | ALT | [Link](https://cryptoquant.com/asset/edu/summary) | | Dog (Bitcoin) | `DOG` | ALT | [Link](https://cryptoquant.com/asset/dog/summary) | | Safe | `SAFE` | ERC20 | [Link](https://cryptoquant.com/asset/safe/summary) | | Theta Fuel | `TFUEL` | ALT | [Link](https://cryptoquant.com/asset/tfuel/summary) | | Gas | `GAS` | ALT | [Link](https://cryptoquant.com/asset/gas/summary) | | Verge | `XVG` | ALT | [Link](https://cryptoquant.com/asset/xvg/summary) | | SuperVerse | `SUPER` | ERC20 | [Link](https://cryptoquant.com/asset/super/summary) | | Four | `FORM` | ALT | [Link](https://cryptoquant.com/asset/form/summary) | | Akash Network | `AKT` | ALT | [Link](https://cryptoquant.com/asset/akt/summary) | | Toshi | `TOSHI` | ALT | [Link](https://cryptoquant.com/asset/toshi/summary) | | Alchemy Pay | `ACH` | ERC20 | [Link](https://cryptoquant.com/asset/ach/summary) | | Core | `CORE` | ALT | [Link](https://cryptoquant.com/asset/core/summary) | | Kusama | `KSM` | ALT | [Link](https://cryptoquant.com/asset/ksm/summary) | | Yearn.finance | `YFI` | ERC20 | [Link](https://cryptoquant.com/asset/yfi/summary) | | Nervos Network | `CKB` | ALT | [Link](https://cryptoquant.com/asset/ckb/summary) | | CoW Protocol | `COW` | ERC20 | [Link](https://cryptoquant.com/asset/cow/summary) | | BitMart Token | `BMX` | ERC20 | [Link](https://cryptoquant.com/asset/bmx/summary) | | Ronin | `RON` | ALT | [Link](https://cryptoquant.com/asset/ron/summary) | | Mina | `MINA` | ALT | [Link](https://cryptoquant.com/asset/mina/summary) | | Berachain | `BERA` | ALT | [Link](https://cryptoquant.com/asset/bera/summary) | | Keep Network | `KEEP` | ERC20 | [Link](https://cryptoquant.com/asset/keep/summary) | | DigiByte | `DGB` | ALT | [Link](https://cryptoquant.com/asset/dgb/summary) | | Ravencoin | `RVN` | ALT | [Link](https://cryptoquant.com/asset/rvn/summary) | | AIOZ Network | `AIOZ` | ALT | [Link](https://cryptoquant.com/asset/aioz/summary) | | Baby Doge Coin | `BABYDOGE` | ALT | [Link](https://cryptoquant.com/asset/babydoge/summary) | | Movement | `MOVE` | ERC20 | [Link](https://cryptoquant.com/asset/move/summary) | | Turbo | `TURBO` | ERC20 | [Link](https://cryptoquant.com/asset/turbo/summary) | | 0x | `ZRX` | ERC20 | [Link](https://cryptoquant.com/asset/zrx/summary) | | Velo | `VELO` | ALT | [Link](https://cryptoquant.com/asset/velo/summary) | | STP | `STPT` | ERC20 | [Link](https://cryptoquant.com/asset/stpt/summary) | | Bio Protocol | `BIO` | ERC20 | [Link](https://cryptoquant.com/asset/bio/summary) | | Threshold | `T` | ERC20 | [Link](https://cryptoquant.com/asset/t/summary) | | Alchemist AI | `ALCH` | ALT | [Link](https://cryptoquant.com/asset/alch/summary) | | Fellaz | `FLZ` | ERC20 | [Link](https://cryptoquant.com/asset/flz/summary) | | Mog Coin | `MOG` | ERC20 | [Link](https://cryptoquant.com/asset/mog/summary) | | KAITO | `KAITO` | ALT | [Link](https://cryptoquant.com/asset/kaito/summary) | | Zilliqa | `ZIL` | ALT | [Link](https://cryptoquant.com/asset/zil/summary) | | Magic Eden | `ME` | ALT | [Link](https://cryptoquant.com/asset/me/summary) | | Frax Share | `FXS` | ERC20 | [Link](https://cryptoquant.com/asset/fxs/summary) | | Aleo | `ALEO` | ALT | [Link](https://cryptoquant.com/asset/aleo/summary) | | Nano | `XNO` | ALT | [Link](https://cryptoquant.com/asset/xno/summary) | | Sushiswap | `SUSHI` | ERC20 | [Link](https://cryptoquant.com/asset/sushi/summary) | | XPR Network | `XPR` | ALT | [Link](https://cryptoquant.com/asset/xpr/summary) | | Moca Network | `MOCA` | ERC20 | [Link](https://cryptoquant.com/asset/moca/summary) | | Astar | `ASTR` | ALT | [Link](https://cryptoquant.com/asset/astr/summary) | | SPACE ID | `ID` | ERC20 | [Link](https://cryptoquant.com/asset/id/summary) | | Kava | `KAVA` | ERC20 | [Link](https://cryptoquant.com/asset/kava/summary) | | ORDI | `ORDI` | ALT | [Link](https://cryptoquant.com/asset/ordi/summary) | | KUB Coin | `KUB` | ALT | [Link](https://cryptoquant.com/asset/kub/summary) | | ZetaChain | `ZETA` | ERC20 | [Link](https://cryptoquant.com/asset/zeta/summary) | | Blur | `BLUR` | ERC20 | [Link](https://cryptoquant.com/asset/blur/summary) | | Venus | `XVS` | ERC20 | [Link](https://cryptoquant.com/asset/xvs/summary) | | Siacoin | `SC` | ALT | [Link](https://cryptoquant.com/asset/sc/summary) | | Holo | `HOT` | ERC20 | [Link](https://cryptoquant.com/asset/hot/summary) | | Drift | `DRIFT` | ALT | [Link](https://cryptoquant.com/asset/drift/summary) | | Request | `REQ` | ERC20 | [Link](https://cryptoquant.com/asset/req/summary) | | Qubic | `QUBIC` | ALT | [Link](https://cryptoquant.com/asset/qubic/summary) | | cat in a dogs world | `MEW` | ALT | [Link](https://cryptoquant.com/asset/mew/summary) | | Paycoin | `PCI` | ALT | [Link](https://cryptoquant.com/asset/pci/summary) | | VVS Finance | `VVS` | ERC20 | [Link](https://cryptoquant.com/asset/vvs/summary) | | Waves | `WAVES` | ALT | [Link](https://cryptoquant.com/asset/waves/summary) | | Popcat (SOL) | `POPCAT` | ALT | [Link](https://cryptoquant.com/asset/popcat/summary) | | MANTRA | `OM` | ERC20 | [Link](https://cryptoquant.com/asset/om/summary) | | aelf | `ELF` | ALT | [Link](https://cryptoquant.com/asset/elf/summary) | | GMX | `GMX` | ALT | [Link](https://cryptoquant.com/asset/gmx/summary) | | VeThor Token | `VTHO` | ALT | [Link](https://cryptoquant.com/asset/vtho/summary) | | XYO | `XYO` | ERC20 | [Link](https://cryptoquant.com/asset/xyo/summary) | | IoTeX | `IOTX` | ALT | [Link](https://cryptoquant.com/asset/iotx/summary) | | Axelar | `AXL` | ERC20 | [Link](https://cryptoquant.com/asset/axl/summary) | | Peanut the Squirrel | `PNUT` | ALT | [Link](https://cryptoquant.com/asset/pnut/summary) | | Plume | `PLUME` | ERC20 | [Link](https://cryptoquant.com/asset/plume/summary) | | Staika | `STIK` | ALT | [Link](https://cryptoquant.com/asset/stik/summary) | | Numeraire | `NMR` | ERC20 | [Link](https://cryptoquant.com/asset/nmr/summary) | | ISLM | `ISLM` | ALT | [Link](https://cryptoquant.com/asset/islm/summary) | | RedStone | `RED` | ERC20 | [Link](https://cryptoquant.com/asset/red/summary) | | Celo | `CELO` | ALT | [Link](https://cryptoquant.com/asset/celo/summary) | | Non-Playable Coin | `NPC` | ERC20 | [Link](https://cryptoquant.com/asset/npc/summary) | | Grass | `GRASS` | ALT | [Link](https://cryptoquant.com/asset/grass/summary) | | Loopring | `LRC` | ERC20 | [Link](https://cryptoquant.com/asset/lrc/summary) | | Centrifuge | `CFG` | ALT | [Link](https://cryptoquant.com/asset/cfg/summary) | | Memecoin | `MEME` | ERC20 | [Link](https://cryptoquant.com/asset/meme/summary) | | ssv.network | `SSV` | ERC20 | [Link](https://cryptoquant.com/asset/ssv/summary) | | Status | `SNT` | ERC20 | [Link](https://cryptoquant.com/asset/snt/summary) | | GEODNET | `GEOD` | ALT | [Link](https://cryptoquant.com/asset/geod/summary) | | SKALE Network | `SKL` | ERC20 | [Link](https://cryptoquant.com/asset/skl/summary) | | Vana | `VANA` | ERC20 | [Link](https://cryptoquant.com/asset/vana/summary) | | Ankr | `ANKR` | ERC20 | [Link](https://cryptoquant.com/asset/ankr/summary) | | ZIGChain | `ZIG` | ERC20 | [Link](https://cryptoquant.com/asset/zig/summary) | | Orca | `ORCA` | ALT | [Link](https://cryptoquant.com/asset/orca/summary) | | UMA | `UMA` | ERC20 | [Link](https://cryptoquant.com/asset/uma/summary) | | Casper | `CSPR` | ALT | [Link](https://cryptoquant.com/asset/cspr/summary) | | Secret | `SCRT` | ALT | [Link](https://cryptoquant.com/asset/scrt/summary) | | Chia | `XCH` | ALT | [Link](https://cryptoquant.com/asset/xch/summary) | | Mask Network | `MASK` | ERC20 | [Link](https://cryptoquant.com/asset/mask/summary) | | AI Rig Complex | `ARC` | ALT | [Link](https://cryptoquant.com/asset/arc/summary) | | Enjin Coin | `ENJ` | ERC20 | [Link](https://cryptoquant.com/asset/enj/summary) | | Chintai | `CHEX` | ERC20 | [Link](https://cryptoquant.com/asset/chex/summary) | | Altlayer | `ALT` | ERC20 | [Link](https://cryptoquant.com/asset/alt/summary) | | ICON | `ICX` | ALT | [Link](https://cryptoquant.com/asset/icx/summary) | | Polymesh | `POLYX` | ALT | [Link](https://cryptoquant.com/asset/polyx/summary) | | Ardor | `ARDR` | ALT | [Link](https://cryptoquant.com/asset/ardr/summary) | | Pundi X (New) | `PUNDIX` | ERC20 | [Link](https://cryptoquant.com/asset/pundix/summary) | | Decentralized Social | `DESO` | ALT | [Link](https://cryptoquant.com/asset/deso/summary) | | Terra | `LUNA` | ALT | [Link](https://cryptoquant.com/asset/luna/summary) | | GOHOME | `GOHOME` | ALT | [Link](https://cryptoquant.com/asset/gohome/summary) | | UPCX | `UPC` | ERC20 | [Link](https://cryptoquant.com/asset/upc/summary) | | Tellor | `TRB` | ERC20 | [Link](https://cryptoquant.com/asset/trb/summary) | | Snek | `SNEK` | ALT | [Link](https://cryptoquant.com/asset/snek/summary) | | Ontology | `ONT` | ALT | [Link](https://cryptoquant.com/asset/ont/summary) | | HashKey Platform Token | `HSK` | ERC20 | [Link](https://cryptoquant.com/asset/hsk/summary) | | Notcoin | `NOT` | ALT | [Link](https://cryptoquant.com/asset/not/summary) | | Harmony | `ONE` | ALT | [Link](https://cryptoquant.com/asset/one/summary) | | Storj | `STORJ` | ERC20 | [Link](https://cryptoquant.com/asset/storj/summary) | | EthereumPoW | `ETHW` | ALT | [Link](https://cryptoquant.com/asset/ethw/summary) | | BORA | `BORA` | ALT | [Link](https://cryptoquant.com/asset/bora/summary) | | iExec RLC | `RLC` | ERC20 | [Link](https://cryptoquant.com/asset/rlc/summary) | | BounceBit | `BB` | ALT | [Link](https://cryptoquant.com/asset/bb/summary) | | AI Companions | `AIC` | ALT | [Link](https://cryptoquant.com/asset/aic/summary) | | Band Protocol | `BAND` | ERC20 | [Link](https://cryptoquant.com/asset/band/summary) | | GMT | `GMT` | ERC20 | [Link](https://cryptoquant.com/asset/gmt/summary) | | World Mobile Token | `WMTX` | ERC20 | [Link](https://cryptoquant.com/asset/wmtx/summary) | | Neiro (First Neiro On Ethereum) | `NEIRO` | ERC20 | [Link](https://cryptoquant.com/asset/neiro/summary) | | Tokenlon Network Token | `LON` | ERC20 | [Link](https://cryptoquant.com/asset/lon/summary) | | LCX | `LCX` | ERC20 | [Link](https://cryptoquant.com/asset/lcx/summary) | | COTI | `COTI` | ALT | [Link](https://cryptoquant.com/asset/coti/summary) | | Ark | `ARK` | ALT | [Link](https://cryptoquant.com/asset/ark/summary) | | Powerledger | `POWR` | ERC20 | [Link](https://cryptoquant.com/asset/powr/summary) | | Babylon | `BABY` | ALT | [Link](https://cryptoquant.com/asset/baby/summary) | | Hive | `HIVE` | ALT | [Link](https://cryptoquant.com/asset/hive/summary) | | ConstitutionDAO | `PEOPLE` | ERC20 | [Link](https://cryptoquant.com/asset/people/summary) | | WOO | `WOO` | ERC20 | [Link](https://cryptoquant.com/asset/woo/summary) | | MVL | `MVL` | ERC20 | [Link](https://cryptoquant.com/asset/mvl/summary) | | IOST | `IOST` | ALT | [Link](https://cryptoquant.com/asset/iost/summary) | | Usual | `USUAL` | ERC20 | [Link](https://cryptoquant.com/asset/usual/summary) | | peaq | `PEAQ` | ALT | [Link](https://cryptoquant.com/asset/peaq/summary) | | Yield Guild Games | `YGG` | ERC20 | [Link](https://cryptoquant.com/asset/ygg/summary) | | Big Time | `BIGTIME` | ERC20 | [Link](https://cryptoquant.com/asset/bigtime/summary) | | CARV | `CARV` | ERC20 | [Link](https://cryptoquant.com/asset/carv/summary) | | SwftCoin | `SWFTC` | ERC20 | [Link](https://cryptoquant.com/asset/swftc/summary) | | Radix | `XRD` | ALT | [Link](https://cryptoquant.com/asset/xrd/summary) | | Gravity | `G` | ALT | [Link](https://cryptoquant.com/asset/g/summary) | | AI Analysis Token | `AIAT` | ERC20 | [Link](https://cryptoquant.com/asset/aiat/summary) | | io.net | `IO` | ALT | [Link](https://cryptoquant.com/asset/io/summary) | | Solayer | `LAYER` | ALT | [Link](https://cryptoquant.com/asset/layer/summary) | | Rocket Pool | `RPL` | ERC20 | [Link](https://cryptoquant.com/asset/rpl/summary) | | ECOMI | `OMI` | ERC20 | [Link](https://cryptoquant.com/asset/omi/summary) | | Euler | `EUL` | ERC20 | [Link](https://cryptoquant.com/asset/eul/summary) | | Bancor | `BNT` | ERC20 | [Link](https://cryptoquant.com/asset/bnt/summary) | | Civic | `CVC` | ERC20 | [Link](https://cryptoquant.com/asset/cvc/summary) | | Orbs | `ORBS` | ERC20 | [Link](https://cryptoquant.com/asset/orbs/summary) | | Banana For Scale | `BANANAS31` | ALT | [Link](https://cryptoquant.com/asset/bananas31/summary) | | Dogelon Mars | `ELON` | ERC20 | [Link](https://cryptoquant.com/asset/elon/summary) | | Spell Token | `SPELL` | ERC20 | [Link](https://cryptoquant.com/asset/spell/summary) | | Stratis \[New] | `STRAX` | ALT | [Link](https://cryptoquant.com/asset/strax/summary) | | Solar | `SXP` | ALT | [Link](https://cryptoquant.com/asset/sxp/summary) | | Orbler | `ORBR` | ERC20 | [Link](https://cryptoquant.com/asset/orbr/summary) | | BOOK OF MEME | `BOME` | ALT | [Link](https://cryptoquant.com/asset/bome/summary) | | Prometeus | `PROM` | ERC20 | [Link](https://cryptoquant.com/asset/prom/summary) | | MiL.k | `MLK` | ALT | [Link](https://cryptoquant.com/asset/mlk/summary) | | Flux | `FLUX` | ALT | [Link](https://cryptoquant.com/asset/flux/summary) | | Arkham | `ARKM` | ERC20 | [Link](https://cryptoquant.com/asset/arkm/summary) | | Kyber Network | `KNC` | ERC20 | [Link](https://cryptoquant.com/asset/knc/summary) | | Osmosis | `OSMO` | ALT | [Link](https://cryptoquant.com/asset/osmo/summary) | | Lisk | `LSK` | ALT | [Link](https://cryptoquant.com/asset/lsk/summary) | | Biconomy | `BICO` | ERC20 | [Link](https://cryptoquant.com/asset/bico/summary) | | Audius | `AUDIO` | ERC20 | [Link](https://cryptoquant.com/asset/audio/summary) | | Illuvium | `ILV` | ERC20 | [Link](https://cryptoquant.com/asset/ilv/summary) | | WAX | `WAXP` | ALT | [Link](https://cryptoquant.com/asset/waxp/summary) | | Blast | `BLAST` | ALT | [Link](https://cryptoquant.com/asset/blast/summary) | | Shentu | `CTK` | ALT | [Link](https://cryptoquant.com/asset/ctk/summary) | | Smooth Love Potion | `SLP` | ERC20 | [Link](https://cryptoquant.com/asset/slp/summary) | | IQ | `IQ` | ERC20 | [Link](https://cryptoquant.com/asset/iq/summary) | | Venom | `VENOM` | ALT | [Link](https://cryptoquant.com/asset/venom/summary) | | Animecoin | `ANIME` | ERC20 | [Link](https://cryptoquant.com/asset/anime/summary) | | Propy | `PRO` | ERC20 | [Link](https://cryptoquant.com/asset/pro/summary) | | TerraClassicUSD | `USTC` | ALT | [Link](https://cryptoquant.com/asset/ustc/summary) | | Ontology Gas | `ONG` | ALT | [Link](https://cryptoquant.com/asset/ong/summary) | | Ergo | `ERG` | ALT | [Link](https://cryptoquant.com/asset/erg/summary) | | Manta Network | `MANTA` | ALT | [Link](https://cryptoquant.com/asset/manta/summary) | | Chromia | `CHR` | ERC20 | [Link](https://cryptoquant.com/asset/chr/summary) | | Steem | `STEEM` | ALT | [Link](https://cryptoquant.com/asset/steem/summary) | | API3 | `API3` | ERC20 | [Link](https://cryptoquant.com/asset/api3/summary) | | Aevo | `AEVO` | ERC20 | [Link](https://cryptoquant.com/asset/aevo/summary) | | Metis | `METIS` | ERC20 | [Link](https://cryptoquant.com/asset/metis/summary) | | Gigachad | `GIGA` | ALT | [Link](https://cryptoquant.com/asset/giga/summary) | | Hivemapper | `HONEY` | ALT | [Link](https://cryptoquant.com/asset/honey/summary) | | SATS (Ordinals) | `SATS` | ALT | [Link](https://cryptoquant.com/asset/sats/summary) | | Phala Network | `PHA` | ALT | [Link](https://cryptoquant.com/asset/pha/summary) | | Balancer | `BAL` | ERC20 | [Link](https://cryptoquant.com/asset/bal/summary) | | Zentry | `ZENT` | ERC20 | [Link](https://cryptoquant.com/asset/zent/summary) | | PAAL AI | `PAAL` | ERC20 | [Link](https://cryptoquant.com/asset/paal/summary) | | Metal DAO | `MTL` | ALT | [Link](https://cryptoquant.com/asset/mtl/summary) | | Liquity | `LQTY` | ERC20 | [Link](https://cryptoquant.com/asset/lqty/summary) | | Bounce Token | `AUCTION` | ERC20 | [Link](https://cryptoquant.com/asset/auction/summary) | | Goatseus Maximus | `GOAT` | ALT | [Link](https://cryptoquant.com/asset/goat/summary) | | dKargo | `DKA` | ERC20 | [Link](https://cryptoquant.com/asset/dka/summary) | | Taiko | `TAIKO` | ALT | [Link](https://cryptoquant.com/asset/taiko/summary) | | Constellation | `DAG` | ALT | [Link](https://cryptoquant.com/asset/dag/summary) | | GameBuild | `GAME` | ERC20 | [Link](https://cryptoquant.com/asset/game/summary) | | Across Protocol | `ACX` | ERC20 | [Link](https://cryptoquant.com/asset/acx/summary) | | MediBloc | `MED` | ALT | [Link](https://cryptoquant.com/asset/med/summary) | | Aergo | `AERGO` | ALT | [Link](https://cryptoquant.com/asset/aergo/summary) | | Aurora | `AURORA` | ERC20 | [Link](https://cryptoquant.com/asset/aurora/summary) | | Tokamak Network | `TOKAMAK` | ERC20 | [Link](https://cryptoquant.com/asset/tokamak/summary) | | Cartesi | `CTSI` | ERC20 | [Link](https://cryptoquant.com/asset/ctsi/summary) | | Destra Network | `DSYNC` | ERC20 | [Link](https://cryptoquant.com/asset/dsync/summary) | | aixbt | `AIXBT` | ALT | [Link](https://cryptoquant.com/asset/aixbt/summary) | | Xai | `XAI` | ALT | [Link](https://cryptoquant.com/asset/xai/summary) | | Treasure | `MAGIC` | ERC20 | [Link](https://cryptoquant.com/asset/magic/summary) | | Cheelee | `CHEEL` | ALT | [Link](https://cryptoquant.com/asset/cheel/summary) | | Marlin | `POND` | ERC20 | [Link](https://cryptoquant.com/asset/pond/summary) | | QuarkChain | `QKC` | ERC20 | [Link](https://cryptoquant.com/asset/qkc/summary) | | Tensor | `TNSR` | ALT | [Link](https://cryptoquant.com/asset/tnsr/summary) | | Celer Network | `CELR` | ERC20 | [Link](https://cryptoquant.com/asset/celr/summary) | | ChainGPT | `CGPT` | ERC20 | [Link](https://cryptoquant.com/asset/cgpt/summary) | | Osaka Protocol | `OSAK` | ERC20 | [Link](https://cryptoquant.com/asset/osak/summary) | | tokenbot | `CLANKER` | ALT | [Link](https://cryptoquant.com/asset/clanker/summary) | | Dymension | `DYM` | ALT | [Link](https://cryptoquant.com/asset/dym/summary) | | Solana Name Service | `FIDA` | ALT | [Link](https://cryptoquant.com/asset/fida/summary) | | Pixels | `PIXEL` | ERC20 | [Link](https://cryptoquant.com/asset/pixel/summary) | | B3 (Base) | `B3` | ALT | [Link](https://cryptoquant.com/asset/b3/summary) | | Delysium | `AGI` | ERC20 | [Link](https://cryptoquant.com/asset/agi/summary) | | Wilder World | `WILD` | ERC20 | [Link](https://cryptoquant.com/asset/wild/summary) | | Echelon Prime | `PRIME` | ERC20 | [Link](https://cryptoquant.com/asset/prime/summary) | | WINkLink | `WIN` | ALT | [Link](https://cryptoquant.com/asset/win/summary) | | Braintrust | `BTRST` | ERC20 | [Link](https://cryptoquant.com/asset/btrst/summary) | | Clearpool | `CPOOL` | ERC20 | [Link](https://cryptoquant.com/asset/cpool/summary) | | IAGON | `IAG` | ALT | [Link](https://cryptoquant.com/asset/iag/summary) | | Adventure Gold | `AGLD` | ERC20 | [Link](https://cryptoquant.com/asset/agld/summary) | | Moonriver | `MOVR` | ALT | [Link](https://cryptoquant.com/asset/movr/summary) | | Symbol | `XYM` | ALT | [Link](https://cryptoquant.com/asset/xym/summary) | | Banana Gun | `BANANA` | ERC20 | [Link](https://cryptoquant.com/asset/banana/summary) | | WalletConnect Token | `WCT` | ERC20 | [Link](https://cryptoquant.com/asset/wct/summary) | | Ponke | `PONKE` | ALT | [Link](https://cryptoquant.com/asset/ponke/summary) | | JOE | `JOE` | ALT | [Link](https://cryptoquant.com/asset/joe/summary) | | Avail | `AVAIL` | ERC20 | [Link](https://cryptoquant.com/asset/avail/summary) | | Moonbeam | `GLMR` | ALT | [Link](https://cryptoquant.com/asset/glmr/summary) | | Gods Unchained | `GODS` | ERC20 | [Link](https://cryptoquant.com/asset/gods/summary) | | Coin98 | `C98` | ERC20 | [Link](https://cryptoquant.com/asset/c98/summary) | | Arcblock | `ABT` | ERC20 | [Link](https://cryptoquant.com/asset/abt/summary) | | BENQI | `QI` | ALT | [Link](https://cryptoquant.com/asset/qi/summary) | | Orchid | `OXT` | ERC20 | [Link](https://cryptoquant.com/asset/oxt/summary) | | Cetus Protocol | `CETUS` | ALT | [Link](https://cryptoquant.com/asset/cetus/summary) | | Polyhedra Network | `ZKJ` | ERC20 | [Link](https://cryptoquant.com/asset/zkj/summary) | | Nillion | `NIL` | ALT | [Link](https://cryptoquant.com/asset/nil/summary) | | Metaplex | `MPLX` | ALT | [Link](https://cryptoquant.com/asset/mplx/summary) | | DOGS | `DOGS` | ALT | [Link](https://cryptoquant.com/asset/dogs/summary) | | Vulcan Forged (PYR) | `PYR` | ERC20 | [Link](https://cryptoquant.com/asset/pyr/summary) | | Origin Protocol | `OGN` | ERC20 | [Link](https://cryptoquant.com/asset/ogn/summary) | | Dent | `DENT` | ERC20 | [Link](https://cryptoquant.com/asset/dent/summary) | | Cookie DAO | `COOKIE` | ALT | [Link](https://cryptoquant.com/asset/cookie/summary) | | Vanar Chain | `VANRY` | ERC20 | [Link](https://cryptoquant.com/asset/vanry/summary) | | Saga | `SAGA` | ALT | [Link](https://cryptoquant.com/asset/saga/summary) | | Bone ShibaSwap | `BONE` | ERC20 | [Link](https://cryptoquant.com/asset/bone/summary) | | Alchemix | `ALCX` | ERC20 | [Link](https://cryptoquant.com/asset/alcx/summary) | | MyNeighborAlice | `ALICE` | ERC20 | [Link](https://cryptoquant.com/asset/alice/summary) | | Apu Apustaja | `APU` | ERC20 | [Link](https://cryptoquant.com/asset/apu/summary) | | SUPRA | `SUPRA` | ALT | [Link](https://cryptoquant.com/asset/supra/summary) | | Highstreet | `HIGH` | ERC20 | [Link](https://cryptoquant.com/asset/high/summary) | | FUNToken | `FUN` | ERC20 | [Link](https://cryptoquant.com/asset/fun/summary) | | Popsicle Finance | `ICE` | ERC20 | [Link](https://cryptoquant.com/asset/ice/summary) | | Freysa | `FAI` | ALT | [Link](https://cryptoquant.com/asset/fai/summary) | | GRIFFAIN | `GRIFFAIN` | ALT | [Link](https://cryptoquant.com/asset/griffain/summary) | | Goldfinch | `GFI` | ERC20 | [Link](https://cryptoquant.com/asset/gfi/summary) | | Neutron | `NTRN` | ALT | [Link](https://cryptoquant.com/asset/ntrn/summary) | | MetFi | `METFI` | ALT | [Link](https://cryptoquant.com/asset/metfi/summary) | | Hamster Kombat | `HMSTR` | ALT | [Link](https://cryptoquant.com/asset/hmstr/summary) | | Scroll | `SCR` | ALT | [Link](https://cryptoquant.com/asset/scr/summary) | | Test | `TST` | ALT | [Link](https://cryptoquant.com/asset/tst/summary) | | Devve | `DEVVE` | ERC20 | [Link](https://cryptoquant.com/asset/devve/summary) | | PepeCoin | `PEPECOIN` | ERC20 | [Link](https://cryptoquant.com/asset/pepecoin/summary) | | Access Protocol | `ACS` | ALT | [Link](https://cryptoquant.com/asset/acs/summary) | | DODO | `DODO` | ERC20 | [Link](https://cryptoquant.com/asset/dodo/summary) | | Humans.ai | `HEART` | ERC20 | [Link](https://cryptoquant.com/asset/heart/summary) | | X Empire | `X` | ALT | [Link](https://cryptoquant.com/asset/x/summary) | | Gitcoin | `GTC` | ERC20 | [Link](https://cryptoquant.com/asset/gtc/summary) | | Zerebro | `ZEREBRO` | ALT | [Link](https://cryptoquant.com/asset/zerebro/summary) | | PinLink | `PIN` | ERC20 | [Link](https://cryptoquant.com/asset/pin/summary) | | Acet | `ACT` | ALT | [Link](https://cryptoquant.com/asset/act/summary) | | Roam | `ROAM` | ALT | [Link](https://cryptoquant.com/asset/roam/summary) | | Oasys | `OAS` | ALT | [Link](https://cryptoquant.com/asset/oas/summary) | | OmiseGO | `OMG` | ERC20 | [Link](https://cryptoquant.com/asset/omg/summary) | | dForce | `DF` | ERC20 | [Link](https://cryptoquant.com/asset/df/summary) | | Aavegotchi | `GHST` | ERC20 | [Link](https://cryptoquant.com/asset/ghst/summary) | | Ski Mask Dog | `SKI` | ALT | [Link](https://cryptoquant.com/asset/ski/summary) | | SUNDOG | `SUNDOG` | ALT | [Link](https://cryptoquant.com/asset/sundog/summary) | | UXLINK | `UXLINK` | ALT | [Link](https://cryptoquant.com/asset/uxlink/summary) | | Dego Finance | `DEGO` | ERC20 | [Link](https://cryptoquant.com/asset/dego/summary) | | dHedge DAO | `DHT` | ERC20 | [Link](https://cryptoquant.com/asset/dht/summary) | | ArchLoot | `AL` | ERC20 | [Link](https://cryptoquant.com/asset/al/summary) | | Radio Caca | `RACA` | ERC20 | [Link](https://cryptoquant.com/asset/raca/summary) | | Bluzelle | `BLZ` | ERC20 | [Link](https://cryptoquant.com/asset/blz/summary) | | MESSIER | `M87` | ERC20 | [Link](https://cryptoquant.com/asset/m87/summary) | | NEM | `XEM` | ALT | [Link](https://cryptoquant.com/asset/xem/summary) | | Mythos | `MYTH` | ERC20 | [Link](https://cryptoquant.com/asset/myth/summary) | | BugsCoin | `BGSC` | ALT | [Link](https://cryptoquant.com/asset/bgsc/summary) | | Broccoli (firstbroccoli.com) | `BROCCOLI` | ALT | [Link](https://cryptoquant.com/asset/broccoli/summary) | | Saros | `SAROS` | ALT | [Link](https://cryptoquant.com/asset/saros/summary) | | Ribbon Finance | `RBN` | ERC20 | [Link](https://cryptoquant.com/asset/rbn/summary) | | Kadena | `KDA` | ALT | [Link](https://cryptoquant.com/asset/kda/summary) | | Efinity Token | `EFI` | ERC20 | [Link](https://cryptoquant.com/asset/efi/summary) | | ParaSwap | `PSP` | ERC20 | [Link](https://cryptoquant.com/asset/psp/summary) | | mStable Governance Token : META | `MTA` | ERC20 | [Link](https://cryptoquant.com/asset/mta/summary) | | Cream Finance | `CREAM` | ERC20 | [Link](https://cryptoquant.com/asset/cream/summary) | | Voyager Token | `VGX` | ERC20 | [Link](https://cryptoquant.com/asset/vgx/summary) | | Auto | `AUTO` | ALT | [Link](https://cryptoquant.com/asset/auto/summary) | | ARMOR | `ARMOR` | ERC20 | [Link](https://cryptoquant.com/asset/armor/summary) | | BLOCKv | `VEE` | ERC20 | [Link](https://cryptoquant.com/asset/vee/summary) | | Covalent | `CQT` | ERC20 | [Link](https://cryptoquant.com/asset/cqt/summary) | | EOS | `EOS` | ALT | [Link](https://cryptoquant.com/asset/eos/summary) | | Ethernity Chain | `ERN` | ERC20 | [Link](https://cryptoquant.com/asset/ern/summary) | | H2O DAO | `H2O` | ALT | [Link](https://cryptoquant.com/asset/h2o/summary) | | Human | `HMT` | ERC20 | [Link](https://cryptoquant.com/asset/hmt/summary) | | Huobi Token | `HT` | ERC20 | [Link](https://cryptoquant.com/asset/ht/summary) | | Maker | `MKR` | ERC20 | [Link](https://cryptoquant.com/asset/mkr/summary) | | Maple | `MPL` | ERC20 | [Link](https://cryptoquant.com/asset/mpl/summary) | | Mines of Dalarnia | `DAR` | ERC20 | [Link](https://cryptoquant.com/asset/dar/summary) | | Nexusmind | `NMD` | ALT | [Link](https://cryptoquant.com/asset/nmd/summary) | | Ocean Protocol | `OCEAN` | ERC20 | [Link](https://cryptoquant.com/asset/ocean/summary) | | PlayDapp | `PLA` | ERC20 | [Link](https://cryptoquant.com/asset/pla/summary) | | Polygon | `MATIC` | ERC20 | [Link](https://cryptoquant.com/asset/matic/summary) | | Polymath | `POLY` | ERC20 | [Link](https://cryptoquant.com/asset/poly/summary) | | Temple DAO | `TEMPLE` | ERC20 | [Link](https://cryptoquant.com/asset/temple/summary) | | ai16z | `AI16Z` | ALT | [Lin](https://cryptoquant.com/asset/ai16z/summary) | # Supported ERC20 List Source: https://docs.cryptoquant.com/catalog/supported-erc20-tokens Tokens supported by the CryptoQuant API. | Name | Token | Supported Categories | Contract Created Datetime (Block, Datetime) | | - | - | - | - | | Chainlink | `link` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 4281611, 2017-09-16 21:26:29 | | Uniswap | `uni` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10861674, 2020-09-14 18:11:26 | | Sushiswap | `sushi` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10736094, 2020-08-26 12:28:07 | | Aave | `aave` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10926829, 2020-09-24 18:06:28 | | Maker | `mkr` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 4620855, 2017-11-25 18:24:17 | | OmiseGO | `omg` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 3978297, 2017-07-05 02:18:58 | | Uma | `uma` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 9247089, 2020-01-09 14:44:21 | | Compound | `comp` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 9601359, 2020-03-04 00:08:55 | | Basic Attention Token | `bat` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 3788558, 2017-05-29 18:45:10 | | Synthetix | `snx` | - Entity Status - Exchange Flow - Market Data | 5750875, 2018-06-08 02:14:23 | | Yearn.finance | `yfi` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10475744, 2020-07-17 08:01:25 | | Decentraland | `mana` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 4162059, 2017-08-15 19:18:09 | | The Sandbox | `sand` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 8835135, 2019-10-29 16:48:43 | | Axie Infinity | `axs` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 12314534, 2021-04-26 07:16:09 | | Smooth Love Potion | `slp` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 12314545, 2021-04-26 07:18:32 | | Gala | `gala` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10828939, 2020-09-09 17:32:51 | | Enjin Coin | `enj` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 4329040, 2017-10-02 01:02:07 | | Yield Guild Games | `ygg` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 12901564, 2021-07-26 11:30:17 | | Illuvium | `ilv` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 12084124, 2021-03-21 19:43:46 | | Adventure Gold | `agld` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 13142655, 2021-09-01 23:09:32 | | Chiliz | `chz` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 6585593, 2021-10-26 07:00:45 | | Mines of Dalarnia | `dar` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 13454131, 2021-10-20 10:38:06 | | Aavegotchi | `ghst` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10852634, 2020-09-13 08:48:20 | | MyNeighborAlice | `alice` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 11958870, 2021-03-02 12:43:37 | | Ethereum Name Service | `ens` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 13533418, 2021-11-01 20:55:17 | | Dego Finance | `dego` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10835762, 2020-09-10 18:51:00 | | Origin Protocol | `ogn` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 6436154, 2018-10-01 23:06:11 | | Ethernity Chain | `ern` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 11749003, 2021-01-29 05:48:45 | | SHIBA INU | `shib` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10569013, 2020-07-31 18:32:43 | | Storj | `storj` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 3898942, 2017-06-19 16:16:35 | | Bluzelle | `blz` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 4911588, 2018-01-15 08:19:33 | | Holo | `hot` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 5008746, 2018-02-01 01:21:09 | | Alchemix | `alcx` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 11937199, 2021-02-27 04:28:02 | | FTX Token | `ftt` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 7611221, 2019-04-21 13:21:27 | | Curve DAO Token | `crv` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10647806, 2020-08-12 22:17:28 | | Bancor | `bnt` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 3851136, 2017-06-10 16:02:40 | | 0x | `zrx` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 4145415, 2017-08-11 18:39:16 | | 1inch Network | `1inch` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 11511393, 2020-12-23 18:13:31 | | Kyber Network Crystal v2 | `knc` | - Entity Status - Exchange Flow - Network Data - Market Data | 12224343, 2021-04-12 09:04:54 | | dYdX | `dydx` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 12809555, 2021-07-12 01:37:12 | | DODO | `dodo` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10956992, 2020-09-29 10:58:50 | | LoopringCoin V2 | `lrc` | - Network Data - Market Data | 7544036, 2019-04-11 02:10:37 | | Ankr | `ankr` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 7246755, 2019-02-21 00:57:45 | | Polygon | `matic` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 7605604, 2019-04-20 16:34:12 | | Amp | `amp` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10635417, 2020-08-11 00:27:19 | | SKALE Network | `skl` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10363171, 2020-06-29 21:44:26 | | Balancer | `bal` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 10299683, 2020-06-20 01:32:59 | | Polymath | `poly` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 4994844, 2018-01-29 16:34:21 | | Fetch.ai | `fet` | - Entity Status - Exchange Flow - Market Data | 10998076, 2020-10-05 21:06:18 | | The Graph | `grt` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 11446769, 2020-12-13 20:17:13 | | Ocean Protocol | `ocean` | - Entity Status - Exchange Flow - Network Data - Market Data | 10945544, 2020-09-27 15:54:07 | | Numeraire | `nmr` | - Entity Status - Exchange Flow - Market Data | 3902326, 2017-06-20 08:10:37 | | Mask Network | `mask` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 11886238, 2021-02-19 08:26:41 | | JasmyCoin | `jasmy` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 9164378, 2019-12-26 05:59:52 | | Gitcoin | `gtc` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 12422079, 2021-05-12 21:48:02 | | Keep Network | `keep` | - Entity Status - Network Data - Market Data | 9958363, 2020-04-28 02:52:46 | | Quant | `qnt` | - Entity Status - Exchange Flow - Market Data | 5392950, 2018-04-06 19:52:41 | | Voyager Token | `vgx` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 12916697, 2021-07-28 21:11:47 | | ParaSwap | `psp` | - Network Data | 13619386, 2021-11-15 08:58:18 | | Immutable X | `imx` | - Network Data | 13415141, 2021-10-14 07:59:20 | | Highstreet Token | `high` | - Network Data | 13395328, 2021-10-11 05:00:48 | | Radio Caca V2 | `raca` | - Network Data | 13369114, 2021-10-07 02:16:48 | | Temple DAO | `temple` | - Network Data | 13321581, 2021-09-29 15:52:47 | | Gods Unchained | `gods` | - Network Data | 12955434, 2021-08-04 12:08:03 | | Ribbon Finance | `rbn` | - Network Data | 12497174, 2021-05-24 13:12:02 | | dHedge DAO Token | `dht` | - Network Data | 10833180, 2020-09-10 09:35:31 | | Cream Finance | `cream` | - Network Data | 10594024, 2020-08-04 15:06:57 | | Meta | `mta` | - Network Data | 10450640, 2020-07-13 10:23:56 | | Alchemy | `ach` | - Network Data | 8482162, 2019-09-04 07:00:52 | | PlayDapp Token | `pla` | - Network Data | 9921528, 2020-04-22 09:40:15 | | Efinity Token | `efi` | - Network Data | 12349290, 2021-05-01 04:06:34 | | Prometeus Network | `prom` | - Network Data | 7789253, 2019-05-19 07:49:05 | | Armor | `armor` | - Network Data | 11707709, 2021-07-22 21:23:49 | | Popsicle Finance | `ice` | - Network Data | 12121350, 2021-03-27 13:30:15 | | Liquity: LQTY Token | `lqty` | - Network Data | 12178618, 2021-04-05 08:33:10 | | Human Token | `hmt` | - Network Data | 12184475, 2021-04-06 06:22:26 | | Wrapped BTC | `wbtc` | - Network Data | 6766284, 2018-11-24 21:45:52 | | GateChain Token | `gt` | - Network Data | 7726894, 2019-05-09 14:20:19 | | Crypto.com Coin | `cro` | - Network Data | 6702068, 2018-11-14 09:11:48 | | OKB Token | `okb` | - Network Data | 7641712, 2019-04-26 07:47:59 | | 0x (ZRX) | `zrx` | - Network Data | 4145415, 2017-08-11 18:39:16 | | Gnosis | `gno` | - Network Data | 3557596, 2017-04-18 13:45:16 | | Covalent Query Token | `cqt` | - Network Data | 12474448, 2021-05-21 12:15:53 | | Request | `req` | - Network Data | 4345153, 2017-10-07 15:47:37 | | Kucoin Token | `kcs` | - Network Data | 11638804, 2021-01-12 07:29:47 | | Olympus | `ohm` | - Network Data | 12084967, 2021-03-21 22:48:40 | | HTX Token | `ht` | - Network Data | 5005233, 2018-01-31 10:50:02 | # Supported Stablecoin List Source: https://docs.cryptoquant.com/catalog/supported-stablecoins Tokens supported by the CryptoQuant API. | Name | Token | Supported Categories | Contract Created Datetime (Block, Datetime) | Deprecated | | - | - | - | - | - | | All Tokens | `all_token` | - Entity Status - Exchange Flow - Flow Indicator - Network Data | The earliest time in the tokens below. | | | Tether USD(Eth) | `usdt_eth` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 4638757, 2017-11-28 16:24:26 | | | Tether USD(Trx) | `usdt_trx` | - Entity Status - Exchange Flow - Network Data - Market Data | 4638757, 2017-11-28 16:24:26 | | | Paxos Dollar | `usdp` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 6306166, 2018-09-10 13:03:56 | | | USD Coin | `usdc` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 6307510, 2018-09-10 18:26:41 | | | True USD | `tusd` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 5198636, 2018-03-05 03:30:14 | | | Dai | `dai` | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 8928674, 2019-11-13 21:22:33 | | | Binance USD | `busd` | - Entity Status - Exchange Flow - Market Data | 8493105, 2019-09-05 23:56:17 | | | Gemini dollar | `gusd` | - Entity Status - Exchange Flow | 6301780, 2018-09-09 19:36:14 | | | sUSD | `susd` | - Entity Status - Exchange Flow | 5751012, 2018-06-08 02:48:10 | | | ~~Tether USD(Omni)~~ | ~~`usdt_omni`~~ | - Network Data - Market Data | 325157, 2014-10-13 14:27:52 | [2025-08-28](https://tether.io/news/tether-provides-an-update-on-prioritizing-community-preferences-for-blockchain-support-in-strategic-shift) | | ~~Sai (Old Dai)~~ | ~~`sai`~~ | - Entity Status - Exchange Flow - Flow Indicator - Network Data - Market Data | 4755950, 2017-12-18 19:22:10 | 2025-08-28 | | ~~HTX USD~~ | ~~`husd`~~ | - Entity Status - Exchange Flow | 8174400, 2019-07-18 11:30:44 | 2025-08-28 | | ~~USDK~~ | ~~`usdk`~~ | - Entity Status - Exchange Flow | 7769943, 2019-06-16 07:21:40 | 2025-08-28 | | ~~TerraUSD~~ | ~~`ust`~~ | - Market Data | | 2025-08-28 | Until now, `all_token` is available in Exchange Flow, Network Data, Flow Indicator.\ Supported tokens for `all_token` varies with categories.\ Exchange Flow: `usdt_eth`, `usdt_trx`, `usdp`, `usdc`, `tusd`, `dai`, `busd`, `gusd`, `susd`\ Network Data: `usdt_eth`, `usdt_trx`, `usdp`, `usdc`, `tusd`, `dai`\ Deprecated: `usdt_omni`, `sai`, `husd`, `usdk`, `ust` # TRON (TRX) Source: https://docs.cryptoquant.com/catalog/trx All TRX metrics available in the CryptoQuant API — endpoints, parameters, response fields, and data latency. > Machine-readable version of this catalog: [catalog.json](/catalog/catalog.json) Each section lists its metrics; open **Data latency** under a section to see the block and process delay per resolution — see [how latency works](/guides/data-latency). ## Market Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Price OHLCV](/api-reference/trx-market-data/price-ohlcv) | `/trx/market-data/price-ohlcv` | — | `date` `open` `high` `low` `close` `volume` | | [Capitalization](/api-reference/trx-market-data/capitalization) | `/trx/market-data/capitalization` | — | `date` `market_cap` | > [accordion] Data latency > > [Price OHLCV](/api-reference/trx-market-data/price-ohlcv)`/trx/market-data/price-ohlcv` > > > [tab] Day > > > > Windowblock?process?7day—283.61s30day—287.99s > > > [tab] Hour > > > > Windowblock?process?24hour—305.75s168hour—275.88s > > > [tab] Minute > > > > Windowblock?process?10min—262.35s60min—250.43s > > Mutable: no · measured 2026-11-10 > > [Capitalization](/api-reference/trx-market-data/capitalization)`/trx/market-data/capitalization` > > > [tab] Day > > > > Windowblock?process?7day11.00s214,109.39s30day11.40s218,362.99s > > Mutable: no · measured 2026-11-10 ## Network Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Supply](/api-reference/trx-network-data/supply) | `/trx/network-data/supply` | — | `date` `supply_total` `supply_circulating` `supply_minted` `supply_burned` `supply_staked` | | [Transactions Count](/api-reference/trx-network-data/transactions-count) | `/trx/network-data/transactions-count` | — | `date` `transactions_count_total` `transactions_count_mean` | | [Addresses Count](/api-reference/trx-network-data/addresses-count) | `/trx/network-data/addresses-count` | — | `date` `addresses_count_active` `addresses_count_sender` `addresses_count_receiver` | | [Tokens Transferred](/api-reference/trx-network-data/tokens-transferred) | `/trx/network-data/tokens-transferred` | — | `date` `tokens_transferred_total` `tokens_transferred_mean` `tokens_transferred_median` | | [Block Count](/api-reference/trx-network-data/block-count) | `/trx/network-data/block-count` | — | `date` `block_count` | | [Fees](/api-reference/trx-network-data/fees) | `/trx/network-data/fees` | — | `date` `fees_total` `fees_total_usd` `fees_block_mean` `fees_block_mean_usd` | | [TPS](/api-reference/trx-network-data/tps) | `/trx/network-data/tps` | — | `date` `tps` | | [Total Value Staked](/api-reference/trx-network-data/total-value-staked) | `/trx/network-data/total-value-staked` | — | `date` `v1_staking_amount` `v2_staking_amount` | | [Staking Rate](/api-reference/trx-network-data/staking-rate) | `/trx/network-data/staking-rate` | — | `date` `staking_rate` | | [Energy Stake](/api-reference/trx-network-data/energy-stake) | `/trx/network-data/energy-stake` | — | `date` `total_energy_weight` `energy_rate` | > [accordion] Data latency > > [Supply](/api-reference/trx-network-data/supply)`/trx/network-data/supply` > > > [tab] Day > > > > Windowblock?process?7day11.00s201,781.59s30day11.40s224,093.26s > > Mutable: no · measured 2026-10-15 > > [Transactions Count](/api-reference/trx-network-data/transactions-count)`/trx/network-data/transactions-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s103,021.76s30day11.40s102,850.13s > > Mutable: no · measured 2026-10-15 > > [Addresses Count](/api-reference/trx-network-data/addresses-count)`/trx/network-data/addresses-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s103,021.76s30day11.40s102,850.13s > > Mutable: no · measured 2026-10-15 > > [Tokens Transferred](/api-reference/trx-network-data/tokens-transferred)`/trx/network-data/tokens-transferred` > > > [tab] Day > > > > Windowblock?process?7day11.00s176,851.34s30day11.40s186,345.99s > > Mutable: no · measured 2026-10-15 > > [Block Count](/api-reference/trx-network-data/block-count)`/trx/network-data/block-count` > > > [tab] Day > > > > Windowblock?process?7day11.00s103,021.76s30day11.40s102,850.13s > > Mutable: no · measured 2026-10-15 > > [Fees](/api-reference/trx-network-data/fees)`/trx/network-data/fees` > > > [tab] Day > > > > Windowblock?process?7day11.00s176,703.87s30day11.40s186,279.81s > > Mutable: no · measured 2026-10-15 > > [TPS](/api-reference/trx-network-data/tps)`/trx/network-data/tps` > > > [tab] Day > > > > Windowblock?process?7day11.00s103,021.76s30day11.40s102,850.13s > > Mutable: no · measured 2026-10-15 > > [Total Value Staked](/api-reference/trx-network-data/total-value-staked)`/trx/network-data/total-value-staked` > > > [tab] Day > > > > Windowblock?process?7day11.00s201,781.59s30day11.40s224,093.26s > > Mutable: no · measured 2026-10-15 > > [Staking Rate](/api-reference/trx-network-data/staking-rate)`/trx/network-data/staking-rate` > > > [tab] Day > > > > Windowblock?process?7day11.00s201,781.59s30day11.40s224,093.26s > > Mutable: no · measured 2026-10-15 ## DEFI | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Sunpump Tokens](/api-reference/trx-defi/sunpump-tokens) | `/trx/defi/sunpump-tokens` | — | `date` `token_create_event_count` `cumulative_count_create_events` | | [Sunswap Activity](/api-reference/trx-defi/sunswap-activity) | `/trx/defi/sunswap-activity` | — | `date` `total_transaction_count` `wtrx_transaction_count` `other_transaction_count` `wtrx_dominance` `wtrx_amount` `wtrx_amount_usd` | > [accordion] Data latency > > [Sunpump Tokens](/api-reference/trx-defi/sunpump-tokens)`/trx/defi/sunpump-tokens` > > > [tab] Day > > > > Windowblock?process?7day11.00s362,726.99s30day11.40s624,275.39s > > Mutable: no · measured 2026-10-15 > > [Sunswap Activity](/api-reference/trx-defi/sunswap-activity)`/trx/defi/sunswap-activity` > > > [tab] Day > > > > Windowblock?process?7day11.00s177,089.11s30day11.40s186,589.35s > > Mutable: no · measured 2026-10-15 # XRP Ledger (XRP) Source: https://docs.cryptoquant.com/catalog/xrp All XRP metrics available in the CryptoQuant API — endpoints, parameters, response fields, and data latency. > Machine-readable version of this catalog: [catalog.json](/catalog/catalog.json) Each section lists its metrics; open **Data latency** under a section to see the block and process delay per resolution — see [how latency works](/guides/data-latency). ## Market Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Price OHLCV](/api-reference/xrp-market-data/price-ohlcv) | `/xrp/market-data/price-ohlcv` | — | `date` `blockheight` `datetime` `open` `high` `low` `close` `volume` | | [Open Interest](/api-reference/xrp-market-data/open-interest) | `/xrp/market-data/open-interest` | `exchange` | `date` `datetime` `open_interest` | | [Funding Rates](/api-reference/xrp-market-data/funding-rates) | `/xrp/market-data/funding-rates` | `exchange` | `date` `datetime` `funding_rates` | | [Taker Buy Sell Stats](/api-reference/xrp-market-data/taker-buy-sell-stats) | `/xrp/market-data/taker-buy-sell-stats` | `exchange` | `date` `datetime` `taker_buy_volume` `taker_sell_volume` `taker_buy_ratio` `taker_sell_ratio` `taker_buy_sell_ratio` | | [Liquidations](/api-reference/xrp-market-data/liquidations) | `/xrp/market-data/liquidations` | `exchange` | `date` `datetime` `long_liquidations` `short_liquidations` `long_liquidations_usd` `short_liquidations_usd` | | [Capitalization](/api-reference/xrp-market-data/capitalization) | `/xrp/market-data/capitalization` | — | `blockheight` `date` `datetime` `market_cap` | | [Estimated Leverage Ratio](/api-reference/xrp-market-data/estimated-leverage-ratio) | `/xrp/market-data/estimated-leverage-ratio` | `exchange` | `date` `datetime` `estimated_leverage_ratio` | > [accordion] Data latency > > [Price OHLCV](/api-reference/xrp-market-data/price-ohlcv)`/xrp/market-data/price-ohlcv` > > > [tab] Day > > > > Windowblock?process?7day—66.12s30day—82.69s > > > [tab] Hour > > > > Windowblock?process?24hour—91.20s168hour—93.02s > > > [tab] Minute > > > > Windowblock?process?10min—5.62s60min—4.63s > > Mutable: no · measured 2026-11-10 > > [Open Interest](/api-reference/xrp-market-data/open-interest)`/xrp/market-data/open-interest` > > > [tab] Day > > > > Windowblock?process?7day—21.93s30day—21.86s > > > [tab] Hour > > > > Windowblock?process?24hour—16.04s168hour—16.05s > > > [tab] Minute > > > > Windowblock?process?10min—10.12s60min—10.11s > > Mutable: no · measured 2026-11-10 > > [Funding Rates](/api-reference/xrp-market-data/funding-rates)`/xrp/market-data/funding-rates` > > > [tab] Day > > > > Windowblock?process?7day—10.57s30day—10.56s > > > [tab] Hour > > > > Windowblock?process?24hour—5.56s168hour—5.93s > > > [tab] Minute > > > > Windowblock?process?10min—2.78s60min—2.74s > > Mutable: no · measured 2026-11-10 > > [Taker Buy Sell Stats](/api-reference/xrp-market-data/taker-buy-sell-stats)`/xrp/market-data/taker-buy-sell-stats` > > > [tab] Day > > > > Windowblock?process?7day—10.57s30day—10.57s > > > [tab] Hour > > > > Windowblock?process?24hour—5.57s168hour—5.57s > > > [tab] Minute > > > > Windowblock?process?10min—1.27s60min—1.28s > > Mutable: no · measured 2026-11-10 > > [Liquidations](/api-reference/xrp-market-data/liquidations)`/xrp/market-data/liquidations` > > > [tab] Day > > > > Windowblock?process?7day—21.93s30day—21.86s > > > [tab] Hour > > > > Windowblock?process?24hour—16.07s168hour—16.06s > > > [tab] Minute > > > > Windowblock?process?10min—10.35s60min—10.34s > > Mutable: no · measured 2026-11-10 > > [Capitalization](/api-reference/xrp-market-data/capitalization)`/xrp/market-data/capitalization` > > > [tab] Day > > > > Windowblock?process?7day1.00s93,736.77s30day1.00s92,655.78s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s23,015.22s168hour1.00s24,223.08s > > Mutable: no · measured 2026-11-10 > > [Estimated Leverage Ratio](/api-reference/xrp-market-data/estimated-leverage-ratio)`/xrp/market-data/estimated-leverage-ratio` > > > [tab] Day > > > > Windowblock?process?7day1.00s7,128.86s30day1.00s6,250.91s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s16,852.61s168hour1.00s17,205.19s > > Mutable: no · measured 2026-11-10 ## Entity Flows | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Reserve](/api-reference/xrp-entity-flows/reserve) | `/xrp/entity-flows/reserve` | — | `date` `datetime` `reserve` `reserve_usd` | | [Share](/api-reference/xrp-entity-flows/share) | `/xrp/entity-flows/share` | — | `date` `datetime` `share` | | [Transactions Count](/api-reference/xrp-entity-flows/transactions-count) | `/xrp/entity-flows/transactions-count` | — | `blockheight` `date` `datetime` `transactions_count_deposit` `transactions_count_withdraw` | | [Inflow](/api-reference/xrp-entity-flows/inflow) | `/xrp/entity-flows/inflow` | — | `blockheight` `date` `datetime` `inflow` `inflow_usd` | | [Outflow](/api-reference/xrp-entity-flows/outflow) | `/xrp/entity-flows/outflow` | — | `blockheight` `date` `datetime` `outflow` `outflow_usd` | | [Addresses Count](/api-reference/xrp-entity-flows/addresses-count) | `/xrp/entity-flows/addresses-count` | — | `blockheight` `date` `datetime` `addresses_count_deposit` `addresses_count_withdraw` | | [Whale Movements](/api-reference/xrp-entity-flows/whale-movements) | `/xrp/entity-flows/whale-movements` | — | `blockheight` `date` `datetime` `transaction_counts` `volume` | > [accordion] Data latency > > [Reserve](/api-reference/xrp-entity-flows/reserve)`/xrp/entity-flows/reserve` > > > [tab] Day > > > > Windowblock?process?7day1.00s5,903.58s30day10.97s5,908.69s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s5,792.88s168hour1.00s5,834.67s > > > [tab] Block > > > > Windowblock?process?10min4.10s1,576.40s60min3.92s3,098.39s > > Mutable: no · measured 2026-10-15 > > [Share](/api-reference/xrp-entity-flows/share)`/xrp/entity-flows/share` > > > [tab] Day > > > > Windowblock?process?7day1.00s5,903.58s30day10.97s5,908.69s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s5,792.88s168hour1.00s5,834.67s > > Mutable: no · measured 2026-10-15 > > [Transactions Count](/api-reference/xrp-entity-flows/transactions-count)`/xrp/entity-flows/transactions-count` > > > [tab] Day > > > > Windowblock?process?7day1.00s—30day10.97s592.34s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s1,902.68s168hour1.00s1,930.15s > > > [tab] Block > > > > Windowblock?process?10min3.85s4,306.62s60min3.85s5,785.59s > > Mutable: no · measured 2026-10-15 > > [Inflow](/api-reference/xrp-entity-flows/inflow)`/xrp/entity-flows/inflow` > > > [tab] Day > > > > Windowblock?process?7day1.00s—30day10.97s585.51s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s1,820.35s168hour1.00s1,959.97s > > > [tab] Block > > > > Windowblock?process?10min3.65s4,266.45s60min3.91s5,727.45s > > Mutable: no · measured 2026-10-15 > > [Outflow](/api-reference/xrp-entity-flows/outflow)`/xrp/entity-flows/outflow` > > > [tab] Day > > > > Windowblock?process?7day1.00s—30day10.97s583.64s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s1,821.59s168hour1.00s1,961.10s > > > [tab] Block > > > > Windowblock?process?10min3.68s4,256.38s60min3.83s5,757.00s > > Mutable: no · measured 2026-10-15 > > [Addresses Count](/api-reference/xrp-entity-flows/addresses-count)`/xrp/entity-flows/addresses-count` > > > [tab] Day > > > > Windowblock?process?7day1.00s—30day10.97s592.34s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s1,902.68s168hour1.00s1,930.15s > > > [tab] Block > > > > Windowblock?process?10min3.85s4,306.62s60min3.85s5,785.59s > > Mutable: no · measured 2026-10-15 > > [Whale Movements](/api-reference/xrp-entity-flows/whale-movements)`/xrp/entity-flows/whale-movements` > > > [tab] Day > > > > Windowblock?process?7day1.00s—30day10.97s591.15s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s2,204.31s168hour1.00s2,273.67s > > > [tab] Block > > > > Windowblock?process?10min3.34s4,507.77s60min3.75s6,241.18s > > Mutable: no · measured 2026-10-15 ## Flow Indicator | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Exchange Inflow Value Distribution](/api-reference/xrp-flow-indicator/exchange-inflow-value-distribution) | `/xrp/flow-indicator/exchange-inflow-value-distribution` | `exchange` | `blockheight` `date` `datetime` `range_1000_below` `range_1001_to_10000` `range_10001_to_100000` `range_100001_to_1000000` `range_1000000_over` | | [Exchange Outflow Value Distribution](/api-reference/xrp-flow-indicator/exchange-outflow-value-distribution) | `/xrp/flow-indicator/exchange-outflow-value-distribution` | `exchange` | `blockheight` `date` `datetime` `range_1000_below` `range_1001_to_10000` `range_10001_to_100000` `range_100001_to_1000000` `range_1000000_over` | | [Exchange Inflow Count Value Distribution](/api-reference/xrp-flow-indicator/exchange-inflow-count-value-distribution) | `/xrp/flow-indicator/exchange-inflow-count-value-distribution` | `exchange` | `blockheight` `date` `datetime` `range_1000_below` `range_1001_to_10000` `range_10001_to_100000` `range_100001_to_1000000` `range_1000000_over` | | [Exchange Outflow Count Value Distribution](/api-reference/xrp-flow-indicator/exchange-outflow-count-value-distribution) | `/xrp/flow-indicator/exchange-outflow-count-value-distribution` | `exchange` | `blockheight` `date` `datetime` `range_1000_below` `range_1001_to_10000` `range_10001_to_100000` `range_100001_to_1000000` `range_1000000_over` | | [Exchange Supply Ratio](/api-reference/xrp-flow-indicator/exchange-supply-ratio) | `/xrp/flow-indicator/exchange-supply-ratio` | `exchange` | `date` `datetime` `exchange_supply_ratio` | > [accordion] Data latency > > [Exchange Inflow Value Distribution](/api-reference/xrp-flow-indicator/exchange-inflow-value-distribution)`/xrp/flow-indicator/exchange-inflow-value-distribution` > > > [tab] Day > > > > Windowblock?process?7day1.00s—30day10.97s590.21s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s1,954.02s168hour1.00s1,972.53s > > > [tab] Block > > > > Windowblock?process?10min3.65s4,277.51s60min3.91s5,738.51s > > Mutable: no · measured 2026-10-15 > > [Exchange Outflow Value Distribution](/api-reference/xrp-flow-indicator/exchange-outflow-value-distribution)`/xrp/flow-indicator/exchange-outflow-value-distribution` > > > [tab] Day > > > > Windowblock?process?7day1.00s—30day10.97s585.43s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s2,084.40s168hour1.00s2,128.99s > > > [tab] Block > > > > Windowblock?process?10min3.68s4,375.41s60min3.83s5,876.03s > > Mutable: no · measured 2026-10-15 > > [Exchange Inflow Count Value Distribution](/api-reference/xrp-flow-indicator/exchange-inflow-count-value-distribution)`/xrp/flow-indicator/exchange-inflow-count-value-distribution` > > > [tab] Day > > > > Windowblock?process?7day1.00s—30day10.97s590.21s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s1,954.02s168hour1.00s1,972.53s > > > [tab] Block > > > > Windowblock?process?10min3.65s4,277.51s60min3.91s5,738.51s > > Mutable: no · measured 2026-10-15 > > [Exchange Outflow Count Value Distribution](/api-reference/xrp-flow-indicator/exchange-outflow-count-value-distribution)`/xrp/flow-indicator/exchange-outflow-count-value-distribution` > > > [tab] Day > > > > Windowblock?process?7day1.00s—30day10.97s585.43s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s2,084.40s168hour1.00s2,128.99s > > > [tab] Block > > > > Windowblock?process?10min3.68s4,375.41s60min3.83s5,876.03s > > Mutable: no · measured 2026-10-15 > > [Exchange Supply Ratio](/api-reference/xrp-flow-indicator/exchange-supply-ratio)`/xrp/flow-indicator/exchange-supply-ratio` > > > [tab] Day > > > > Windowblock?process?7day1.00s5,971.97s30day10.97s14,572.63s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s15,897.40s168hour1.00s16,394.23s > > Mutable: no · measured 2026-10-15 ## Network Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Addresses Count](/api-reference/xrp-network-data/addresses-count) | `/xrp/network-data/addresses-count` | — | `date` `active_account` `total_account` `sending_account` `recieving_account` | | [Velocity](/api-reference/xrp-network-data/velocity) | `/xrp/network-data/velocity` | — | `date` `velocity` | | [Block Interval](/api-reference/xrp-network-data/block-interval) | `/xrp/network-data/block-interval` | — | `date` `datetime` `average_block_interval` | | [XRP Burnt](/api-reference/xrp-network-data/xrp-burnt) | `/xrp/network-data/xrp-burnt` | — | `date` `datetime` `xrp_burnt` | | [Ledger Count](/api-reference/xrp-network-data/ledger-count) | `/xrp/network-data/ledger-count` | — | `blockheight` `date` `datetime` `total_ledgers` | | [Fees](/api-reference/xrp-network-data/fees) | `/xrp/network-data/fees` | — | `blockheight` `date` `datetime` `total_fees` | | [Transactions Count](/api-reference/xrp-network-data/transactions-count) | `/xrp/network-data/transactions-count` | — | `blockheight` `date` `datetime` `total_transactions_count` | | [Tokens Transferred](/api-reference/xrp-network-data/tokens-transferred) | `/xrp/network-data/tokens-transferred` | — | `blockheight` `date` `datetime` `tokens_transferred_total` | | [Supply](/api-reference/xrp-network-data/supply) | `/xrp/network-data/supply` | — | `date` `supply_total` | > [accordion] Data latency > > [Addresses Count](/api-reference/xrp-network-data/addresses-count)`/xrp/network-data/addresses-count` > > > [tab] Day > > > > Windowblock?process?7day1.00s92,446.98s30day10.97s98,160.30s > > Mutable: no · measured 2026-10-15 > > [Velocity](/api-reference/xrp-network-data/velocity)`/xrp/network-data/velocity` > > > [tab] Day > > > > Windowblock?process?7day1.00s5,909.69s30day10.97s11,666.85s > > Mutable: no · measured 2026-10-15 > > [Block Interval](/api-reference/xrp-network-data/block-interval)`/xrp/network-data/block-interval` > > > [tab] Day > > > > Windowblock?process?7day1.00s5,909.69s30day10.97s11,666.85s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s5,637.50s168hour1.00s5,539.53s > > Mutable: no · measured 2026-10-15 > > [XRP Burnt](/api-reference/xrp-network-data/xrp-burnt)`/xrp/network-data/xrp-burnt` > > > [tab] Day > > > > Windowblock?process?7day1.00s92,303.17s30day10.97s98,065.28s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s21,836.94s168hour1.00s23,221.34s > > Mutable: no · measured 2026-10-15 > > [Ledger Count](/api-reference/xrp-network-data/ledger-count)`/xrp/network-data/ledger-count` > > > [tab] Day > > > > Windowblock?process?7day1.00s5,909.69s30day10.97s11,666.85s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s5,637.50s168hour1.00s5,539.53s > > > [tab] Block > > > > Windowblock?process?10min3.84s2,937.25s60min3.86s4,442.25s > > Mutable: no · measured 2026-10-15 > > [Fees](/api-reference/xrp-network-data/fees)`/xrp/network-data/fees` > > > [tab] Day > > > > Windowblock?process?7day1.00s5,909.69s30day10.97s11,666.85s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s5,637.50s168hour1.00s5,539.53s > > > [tab] Block > > > > Windowblock?process?10min3.84s2,937.25s60min3.86s4,442.25s > > Mutable: no · measured 2026-10-15 > > [Transactions Count](/api-reference/xrp-network-data/transactions-count)`/xrp/network-data/transactions-count` > > > [tab] Day > > > > Windowblock?process?7day1.00s5,909.69s30day10.97s11,666.85s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s5,637.50s168hour1.00s5,539.53s > > > [tab] Block > > > > Windowblock?process?10min3.84s2,937.25s60min3.86s4,442.25s > > Mutable: no · measured 2026-10-15 > > [Tokens Transferred](/api-reference/xrp-network-data/tokens-transferred)`/xrp/network-data/tokens-transferred` > > > [tab] Day > > > > Windowblock?process?7day1.00s5,909.69s30day10.97s11,666.85s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s5,637.50s168hour1.00s5,539.53s > > > [tab] Block > > > > Windowblock?process?10min3.84s2,937.25s60min3.86s4,442.25s > > Mutable: no · measured 2026-10-15 > > [Supply](/api-reference/xrp-network-data/supply)`/xrp/network-data/supply` > > > [tab] Day > > > > Windowblock?process?7day1.00s92,303.17s30day10.97s98,065.28s > > Mutable: no · measured 2026-10-15 ## Network Indicator | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [NVT](/api-reference/xrp-network-indicator/nvt) | `/xrp/network-indicator/nvt` | — | `date` `nvt` | > [accordion] Data latency > > [NVT](/api-reference/xrp-network-indicator/nvt)`/xrp/network-indicator/nvt` > > > [tab] Day > > > > Windowblock?process?7day1.00s5,909.69s30day10.97s11,666.85s > > Mutable: no · measured 2026-10-15 ## Entity Status | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Entity List](/api-reference/xrp-entity-status/entity-list) | `/xrp/entity-status/entity-list` | — | `name` `symbol` `is_validated` `market_type` | ## Dex Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Volume](/api-reference/xrp-dex-data/volume) | `/xrp/dex-data/volume` | — | `date` `dex_volume` | | [Transaction count](/api-reference/xrp-dex-data/transaction-count) | `/xrp/dex-data/transactions-count` | — | `date` `transactions_count` | | [Liquidity](/api-reference/xrp-dex-data/liquidity) | `/xrp/dex-data/liquidity` | — | `date` `liquidity` | | [XRP DEX Price](/api-reference/xrp-dex-data/xrp-dex-price) | `/xrp/dex-data/dex-price` | — | `date` `dex_price_usd` | > [accordion] Data latency > > [Volume](/api-reference/xrp-dex-data/volume)`/xrp/dex-data/volume` > > > [tab] Day > > > > Windowblock?process?7day115,200.71s4,472.41s30day26,880.93s17,324.77s > > > [tab] Hour > > > > Windowblock?process?24hour300,600.00s—168hour127,693.51s7,049.13s > > Mutable: no · measured 2026-10-15 > > [Transaction count](/api-reference/xrp-dex-data/transaction-count)`/xrp/dex-data/transactions-count` > > > [tab] Day > > > > Windowblock?process?7day115,200.71s4,472.41s30day26,880.93s17,324.77s > > > [tab] Hour > > > > Windowblock?process?24hour300,600.00s—168hour127,693.51s7,049.13s > > Mutable: no · measured 2026-10-15 > > [Liquidity](/api-reference/xrp-dex-data/liquidity)`/xrp/dex-data/liquidity` > > > [tab] Day > > > > Windowblock?process?7day115,200.71s4,469.77s30day26,880.93s8,633.40s > > > [tab] Hour > > > > Windowblock?process?24hour297,000.00s—168hour129,214.93s4,487.19s > > Mutable: no · measured 2026-10-15 > > [XRP DEX Price](/api-reference/xrp-dex-data/xrp-dex-price)`/xrp/dex-data/dex-price` > > > [tab] Day > > > > Windowblock?process?7day115,200.71s4,482.18s30day26,880.93s8,632.47s > > > [tab] Hour > > > > Windowblock?process?24hour298,400.00s—168hour131,585.93s5,189.67s > > Mutable: no · measured 2026-10-15 ## AMM Data | Metric | Endpoint | Required params | Response fields | | - | - | - | - | | [Price](/api-reference/xrp-amm-data/price) | `/xrp/amm-data/price` | `amm` | `date` `price_xrp` `price_usd` | | [Liquidity](/api-reference/xrp-amm-data/liquidity) | `/xrp/amm-data/liquidity` | `amm` | `date` `liquidity_xrp` `liquidity_usd` | | [Fee](/api-reference/xrp-amm-data/fee) | `/xrp/amm-data/fee` | `amm` | `date` `fee_percent` | | [Swap Statistics](/api-reference/xrp-amm-data/swap-statistics) | `/xrp/amm-data/swap-stats` | `amm` | `date` `num_swaps` `num_traders` | > [accordion] Data latency > > [Price](/api-reference/xrp-amm-data/price)`/xrp/amm-data/price` > > > [tab] Day > > > > Windowblock?process?7day63,772.29s5,539.34s30day14,880.97s17,717.08s > > > [tab] Hour > > > > Windowblock?process?24hour300,600.00s—168hour127,693.51s21,111.37s > > Mutable: no · measured 2026-10-15 > > [Liquidity](/api-reference/xrp-amm-data/liquidity)`/xrp/amm-data/liquidity` > > > [tab] Day > > > > Windowblock?process?7day63,772.29s5,539.34s30day14,880.97s17,717.08s > > > [tab] Hour > > > > Windowblock?process?24hour300,600.00s—168hour127,693.51s21,111.37s > > Mutable: no · measured 2026-10-15 > > [Fee](/api-reference/xrp-amm-data/fee)`/xrp/amm-data/fee` > > > [tab] Day > > > > Windowblock?process?7day1.00s6,502.27s30day1.00s26,573.25s > > > [tab] Hour > > > > Windowblock?process?24hour1.00s5,616.67s168hour1.00s5,751.39s > > Mutable: no · measured 2026-10-15 > > [Swap Statistics](/api-reference/xrp-amm-data/swap-statistics)`/xrp/amm-data/swap-stats` > > > [tab] Day > > > > Windowblock?process?7day63,772.29s5,539.34s30day14,880.97s17,717.08s > > > [tab] Hour > > > > Windowblock?process?24hour300,600.00s—168hour127,693.51s21,111.37s > > Mutable: no · measured 2026-10-15 # Exchange Flows/Indicators Source: https://docs.cryptoquant.com/data-guide/exchange Entry into Exchange flow/indicator
Data/IndicatorDefinitionInterpretation
**Exchange**-An **exchange** is where the actual trading events occur, which reflects the **demand** side-The basic information and why it matters-Find out more on [What are Entities?](https://userguide.cryptoquant.com/what-is-cryptoquant/background-knowledge/why-entity-matters)-Place where the price is mostly determined-In relation to fiat
[Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow)Amount of coin deposited/withdrawn into/from the exchange wallets
  • Increase of inflow -**Bearish** sign
  • Increase of outflow -**Bullish** sign
  • Increasing Trend Possible volatility Helps predict the Market Trend
[Exchange Reserve](/data-guide/exchange/exchange-reserve)The total amount of coins held in the exchange addresses
  • High High selling pressure -**Bearish** sign
  • Low Low selling pressure -**Bullish** sign
[Exchange Addresses Count](/data-guide/exchange/exchange-addresses-count)The number of unique addresses making inflow/outflow transactions of exchanges
  • High Large number of investors engagement
  • Low Small number of investors engagement
  • Increasing trendExpanding Interest and Activeness
  • Decreasing TrendDiminishing Interest and Activeness
[Exchange Transactions Count](/data-guide/exchange/exchange-transactions-count)The total number of deposits/withdrawals transactions of the exchange
  • High Large number of transactions
  • Low Small number of transactions
  • Increasing TrendExpanding Interest and Activeness
  • Decreasing TrendDiminishing Interest and Activeness
## How to look at indicators This section identifies the lookout point for individual indicators. These indicators could be divided by their identity and the usefulness in trading. Each data tracks each feature of exchanges and put together they cover multiple aspects and capture movements in exchange relatively precisely. #### If you want to make use of exchange data by figuring out ### 1) How many coins came out from or into the exchange Checking the flow into the exchange is a great way to keep track of coins that could be sold or to be held in long-term purpose [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) ### 2) How many coins are in the exchange Checking the total reserve in the exchange is a great way to figure out how scarce the coin is in the market (exchange) [Exchange Reserve](/data-guide/exchange/exchange-reserve) ### 3) How many addresses or transactions are active or being made through the exchanges Checking the active address count or transactions is a great way to figure out how many addresses are participated in the movement in the price and find out the sentiment behind it [Exchange Addresses Count](/data-guide/exchange/exchange-addresses-count) [Exchange Transactions Count](/data-guide/exchange/exchange-transactions-count) It is wise to take a look at each indicator according to the number stated above. ## Points to be aware CryptoQuant always try to be precise and take immediate actions but addresses that are newly created or not labeled need some time to be corrected. For example, large amount of bitcoin could be seen to get its way out of the exchange but it could be just an internal wallet change. It gives an impression of an outflow but instead it is just the same bitcoin staying in the same exchange. However, the accuracy of labeling and tracking exchange addresses continues to increase making the flow and indicators in the same way. Also, the heuristic running to label the exchange addresses continues to evolve around time. # Exchange Addresses Count Source: https://docs.cryptoquant.com/data-guide/exchange/exchange-addresses-count The number of unique addresses making inflow/outflow transactions of exchanges. ## What is Exchange Addresses Count? The number of unique addresses making inflow/outflow transactions of exchanges. | Metrics | Description | | - | - | | Addresses Count Inflow | The number of the token addresses making inflow transactions to the exchange. | | Addresses Count Outflow | The number of the token addresses making outflow transactions from the exchange. | ## How to interpret Exchange Addresses Count Considering that it costs fees to send from wallets to different number of wallets, active exchange address count indicates the **closest meaning to the number of investors** that are involved in exchange related transactions. This naturally leads to possible interpretation of correlating exchange address count to the level of attention of trading investors. ### By value itself [#interpretation](#interpretation) It shows whether **few or large numbers of investors** are involved in transaction. * **High** : **Large number of investors** are accountable for [Exchange In/Outflow & Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) * **Low** : **Small number of investors** are accountable for [Exchange In/Outflow & Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) ### By examining trend [#use-case](#use-case) It shows the **level of Exchange Activeness & Volatility** * **Increasing trend** : **expanding interest and activeness** More people are participating in exchange flows indicating expanding interest and activeness of exchange trading leading to possible volatility * **Decreasing trend** : **diminishing interest and activeness** Less people are participating in exchange flows indicating diminishing interest and activeness of exchange trading leading to possible decreasing volatility ## Link to Our Data * [BTC: Exchange Addresses Count in CryptoQuant Live Chart ](https://cryptoquant.com/asset/btc/chart/addresses) * [ETH: Exchange Addresses Count in CryptoQuant Live Chart ](https://cryptoquant.com/asset/eth/chart/addresses) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Addresses Count](/api-reference/btc-exchange-flows/addresses-count) * **ETH** — [Addresses Count](/api-reference/eth-exchange-flows/addresses-count) * **ERC-20** — [Addresses Count](/api-reference/erc20-exchange-flows/addresses-count) # Exchange In/Outflow and Netflow Source: https://docs.cryptoquant.com/data-guide/exchange/exchange-in-outflow-and-netflow Exchange inflow is defined as the amount of coins deposited into exchange wallets. Exchange outflow is the amount withdrawn from exchange wallets. Exchange Inflow - Outflow = Netflow. ## What is Exchange In/Outflow and Netflow? **Exchange Inflow** is defined as the amount of coins deposited into the crypto exchange wallets. | Inflow Total | The total amount of BTC transferred to the exchange. | | - | - | | Inflow Mean | The mean amount of BTC per transaction sent to the exchange. | | Inflow Mean(MA7) | The 7 days moving average of mean BTC inflow to the exchange. | **Exchange Outflow** is defined as an amount of coin withdrawal from the exchange wallets. | Metrics | Description | | - | - | | Outflow Total | The total amount of BTC transferred from the exchange. | | Outflow Mean | The mean amount of BTC per transaction sent from the exchange. | | Outflow Mean(MA7) | The 7 days moving average of mean BTC outflow from the exchange. | **Exchange Netflow** is the difference between BTC flowing into and out of the exchange. (Inflow - Outflow = Netflow). $$ \text{Inflow} - \text{Outflow} = \text{Netflow} $$ The mean value is the In/Outflow Total divided by the Transactions Count In/Outflow. $$ \text{Inflow Mean} = \frac{\text{Inflow Total}}{\text{Transactions Count Inflow}} \qquad \text{Outflow Mean} = \frac{\text{Outflow Total}}{\text{Transactions Count Outflow}} $$ ## How to interpret Exchange In/Outflow and Netflow ![CryptoQuant Exchange In/Outflow and Netflow Section](https://images.surferseo.art/890249e5-461d-4a0a-80c2-084263cc185f.png) ### By Value Itself * **The increase in inflows** to exchanges is mostly a **Bearish** sign. * **The increase in outflows** from exchanges is mostly a **Bullish** sign. ### By Examining Trend * **Increasing inflow/outflow** indicates **possible volatility** and **helps predict market trends.** ## How does Exchange In/Outflow and Netflow work? ### About Inflows Considering the fact that moving coins costs fees, wallets from outside exchanges send their coins to crypto exchanges for three possible reasons. #### **1) To Sell their Coins - Bearish** In the case of inflow to spot exchange, investors are likely sending Bitcoin (BTC) for selling. This action includes retail buyers' coins moving into the exchange but also the result of custody services provided by institutional buyers. Instead of storing them in cold storage, they move them into other services, such as exchange wallets. This indicates the urge to turn coins into fiat assets or stablecoins. This reason of action mostly leads to the price drop which indicates a bearish sign. #### **2) To Trade in the Derivative Market - Volatility Risk** The purpose for sending coins to derivative market wallets indicates that more trades will be happening on the derivative market. This could possibly lead to increased volatility risk as a result of increased trading activity, investors looking to take profits, and/or to rebalance to de-risk their investment portfolios. This type of action has difficulty in deciding the effect on price since coins in the derivative market could be used to open both long/short positions. Instead, it should be interpreted as increased volatility risk. #### **3) To Use services in Crypto Exchanges - Neutral** Sometimes, investors send their coins to exchange for the purposes of staking, airdrop, and to fit the requirement for IEO. In this case, there is no indication to infer on both price or volatility. However, please note that in the case of an airdrop, indicators such as funding rate and open interest should be considered due to price hedge motivation. This reason of action should be interpreted as neutral. ### About Outflow Considering the fact that moving coins cost fees, Bitcoin wallets outside from exchanges send their coins from the exchanges for two possible scenarios. #### **1) Moving coins after the purchase- Bullish** In the case of outflow from the spot exchange, these metrics show that investors are likely sending BTC outside for storage. Instead of letting their coins sit in the exchange wallets, investors are pulling out their coins from exchange to hold their coins for security and long-term hold. This action includes retail buyers and holders' coins moving out of the exchange but also the result of custody services provided by institutional buyers. This reason of action mostly leads to the price rise which indicates a bullish sign. #### **2) Moving coins that are no longer needed for derivative trades** The purpose for sending coins from derivative market wallets indicates that fewer trades will be happening on the derivative market. This could be the result of trading activity where investors take profits or rebalance to de-risk their investment portfolios. ### Inflow vs. Outflow When Bitcoin/liquidity inflows into exchanges, these metrics often signal an intent to sell or engage in dynamic trading activities. Conversely, when coins make their way out of exchange wallets, it signifies a more optimistic outlook. Investors withdrawing coins are essentially expressing confidence in Bitcoin's long-term potential, akin to holding onto prized assets. This nuanced understanding of inflows and outflows provides a valuable compass for interpreting investor sentiment. ## By Examining Trend in Values ### Indicating the Level of Exchange Activity A positive trend of inflows or outflow to centralized exchanges can indicate an increase in overall exchange activity, meaning more and more users actively use the exchange for trading. This possibly means that the sentiment of traders is in the **bullish moment**. According to this interpretation, the other way around means **bearish sentiment**. ### Predicting Volatility Bitcoin In/Outflow Mean(MA7) explain the strength of previous **volatility** in price, which possibly means the current position might be local tops or bottoms. This is because a portion of large inflows is based on transactions among exchanges, where the analysis is done by the CryptoQuant research team, and this phenomenon can be explained by the results of arbitrage strategies. ### Predicting Market Trend (Bullish or Bearish) Based on the "Exchange Activity" interpretation, we can see the trend of inflow to all exchanges and outflow of liquidity from all exchanges by applying a moving average to data, which is one of the well-known technical indicators for having data's historical trend. We also apply multiple moving averages to see exact inflection points, called [moving average ribbon](https://www.investopedia.com/terms/m/movingaverageribbon.asp). As you can see below, both inflow and outflow trends roughly well-explain bullish or bearish sentiments for the past 3 years where a stable and meaningful number of exchanges have been activated, which supports the "Exchange Activity" interpretation. ![Chart – Inflow to all Exchanges – Source: CryptoQuant](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MCvk0XNID7vEejLW3Gv.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=8c2df827e1da4c457ba55b7ab2414d59) ![Chart – Outflow to all Exchanges – Source: CryptoQuant](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MCvk6FHiRMdzVWUyr1J.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=a2ac8e82c367d25289dc56fc314c29f3) ### ## Predicting Volatility with Bticoin (BTC) Inflow/Outflow Mean(MA7) By looking at Bitcoin (BTC) Inflow Mean (MA7)'s degree of where local tops are located, we can estimate how much the current location is a local top (in red circle) or bottom (in green circle). If your BTC Inflow Mean (MA7) value is in a similar position, you need to check other complementary indicators telling you selling or buying pressure to determine the current price position is in the local top or bottom. ![](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MCvg3it-a6BDk_eU4bJ.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=a1ec79148010191c2692cce46f34d94b) By looking at Bitcoin Outflow Mean's (MA7's) degree of where local tops are located, we can estimate how much the current location is a local top (in red circle) or bottom (in green circle). If your BTC Outflow Mean (MA7) value is in a similar position, you need to check other complementary indicators telling you selling or buying pressure to determine the current price position is in the local top or bottom. ![Chart – Outflow MA7 – Source: CryptoQuant](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MCvgBwegatV3J8l2rWv.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=294af52c74e385a1e87e98ed59a1acab) ## Link to Our Data * [BTC: Exchange In/Outflow & Netflow in CryptoQuant Live Chart](https://cryptoquant.com/overview/btc-exchange-flows) * [ETH: Exchange In/Outflow & Netflow in CryptoQuant Live Chart](https://cryptoquant.com/asset/eth/chart/exchange-flows) * [Altcoins: Exchange In/Outflow & Netflow in CryptoQuant Live Chart](https://cryptoquant.com/asset/link/chart/exchange-flows) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Netflow](/api-reference/btc-exchange-flows/netflow) · [Inflow](/api-reference/btc-exchange-flows/inflow) · [Outflow](/api-reference/btc-exchange-flows/outflow) * **ETH** — [Netflow](/api-reference/eth-exchange-flows/netflow) · [Inflow](/api-reference/eth-exchange-flows/inflow) · [Outflow](/api-reference/eth-exchange-flows/outflow) * **ERC-20** — [Netflow](/api-reference/erc20-exchange-flows/netflow) · [Inflow](/api-reference/erc20-exchange-flows/inflow) · [Outflow](/api-reference/erc20-exchange-flows/outflow) # Exchange Inflow CDD Source: https://docs.cryptoquant.com/data-guide/exchange/exchange-inflow-cdd This indicator is a noise-removed version of CDD with respect to exchange dumping signal ## What is Exchange Inflow CDD? [Coin Days Destroyed (CDD)](https://cryptoquant.com/asset/btc/chart/network-indicator/coin-days-destroyed-cdd) of coins destroyed by flowing into exchanges. High values indicate that more long-term holders moved their coins for the purpose of possible selling. This indicator is a noise-removed version of CDD with respect to exchange dumping signal. $$ \text{Exchange Inflow CDD}=\sum\_{o \in \text{spent outputs to the exchange}}\text{lifespan}\_o\*\text{value}\_o $$ ## How to interpret Exchange Inflow CDD Exchange Inflow CDD is a subset of Coin Days Destroyed (CDD) where coins are destroyed by flowing into exchanges. This indicator is noise-removed version of CDD with respect to exchange dumping signal. Also, note that exchange to exchange inter flow's value was excluded to clear the noise. Exchange Inflow CDD specifically screens transaction that involved inflow to exchanges' wallets and represent its value as CDD. CDD gives more weight to 1\) longer-lived UTXO 2\) Amount of UTXO is holding BTC. Weighting more on these makes the indicator sensitive to long-term holders’ movement and show sentiment & behavior. ### By value itself [#interpretation](#interpretation) * **High**: Long-held coins or great amount of coins or both are moving into the exchange \ -**Volatility Risk or Possible Trend Reversal** A large number of alive days are destroyed which indicates that long-term holders' coins are exposed to selling. It is especially notable that coins that held large alive days or in quantity are moving into exchange, indicating possible sell pressure or trend reversal. * **Low**: Long-held coins are moving in less amount ## Link to Our Data * [Exchange Inflow CDD Live Chart](https://cryptoquant.com/asset/btc/chart/flow-indicator/exchange-inflow-cdd?exchange=all_exchange\&window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=line) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Exchange Inflow CDD (Coin Days Destroyed)](/api-reference/btc-flow-indicator/exchange-inflow-cdd-coin-days-destroyed) # Exchange Inflow - Spent Output Age Bands Source: https://docs.cryptoquant.com/data-guide/exchange/exchange-inflow-spent-output-age-bands Exchange Inflow - Spent Output Age Bands is a set of all spent outputs that were created within a specified age band which flowed into exchange wallets. ## What is Exchange Inflow - Spent Output Age Bands? Exchange Inflow - Spent Output Age Bands is a set of all spent outputs that were created within a specified age band which flowed into exchange wallets. Each colored band represents the total value of spent outputs that flowed into exchanges, which were last created within the denoted time period. This indicator summarizes the flow of capital into exchanges from long-term and short-term holders in a bundle along with the price actions. $$ \text{Exchange Inflow - Spent Output Age Bands}=\sum\_{u \in \text{inflow-utxos}\_t} \text{value}\_u \* \mathbb{I}(a\_i \leq \text{lifespan}\_u < b\_i) $$ $$ \text{Exchange Inflow - Spent Output Age Bands(%)}\frac{\sum\_{u \in \text{inflow-utxos}\_t} \text{value}\_u \* \mathbb{I}(a\_i \leq \text{lifespan}*u < b\_i)}{\sum*{u \in \text{inflow-utxos}*t} \text{value}*{u}} \* 100 $$ $$ \[a\_i, bi) \in \[\[0, 1d), \[1d, 1w), \[1w, 1m), \[1m, 3m), \[3m, 6m), \[6m, 12m), \[12m, 18m), \[18m, 24m)\ \[2y, 3y), \[3y, 5y), \[5y, 7y), \[7y, 10y), \[10y, \inf) $$ | Metric | Definition | | - | - | | Exchange Inflow - Spent Output Age Bands | Each colored band represents the **total value** of spent outputs that flowed into exchanges, which were last created within the denoted time period. | | Exchange Inflow - Spent Output Age Bands (%) | Each colored band represents **the ratio of** the total value of spent outputs that flowed into exchanges, which were last created within the denoted time period. | ## How to interpret Exchange Inflow - Spent Output Age Bands ![Bitcoin: Exchange Inflow - Spent Output Age Bands - All Exchanges. CryptoQuant](https://images.surferseo.art/08fced55-9c90-41ae-8794-0c935700d81b.png) This indicator summarizes the behavior of long-term and short-term holders along with the price actions. As price rises/falls, it is advised to watch out for values in the Spent Output Age Bands to further gain insights on the market through analyzing its participants. Unlike UTXO Age Bands, Spent Output Age Bands focus on the UTXOs that were destroyed within the set metric window. With the help of Spent Output Age Bands, it is possible to pinpoint which aged UTXOs were destroyed in what amount. Using this knowledge, investors can correlate any price movement or changes in the network with the action of long-term/short-term holders' action. Different from regular Spent Output Age Band, Exchange Inflow - Spent Output Age Bands specifically screens spent output that relates to exchanges' wallets and thus provides powerful insights like below ### 1) Targeting Specific Exchange Inflow's coins' feature (Long-term / Short-term / Cohort's Coins) If a large inflow happened to Binance's Wallet, taking interpretation from Exchange Inflow - Spent Output Age Bands (Binance) could indicate whether long-term/short-term holders' coins were accountable for most of the inflow. If drastic price movement was made after the inflow, it is reasonable to infer that **" Inflow that happened in the Binance are Long-term/Short-term investors that drove the price to drop/rise."** ### 2) Keep track of only the short-term/long-term coins' exchange inflow If certain age band's coins were flowed into the exchange, CryptoQuant users can infer their past behavior pattern and take market situation into consideration and act correspondingly. ## By value itself * **High value (Native Value) & Dominance (%)** in certain Spent Output Age Bands\ \- **Mostly accountable for changes in the network** ### Example For instance, when examining the UTXO Age Band spanning from 3 years to 5 years, if this specific band exhibits the highest value or dominance within the SOABs, the line represents a crucial insight. It signifies that investors holding assets for a duration of 3 years to 5 years predominantly influence any price movements or changes observed in the market within the specified metric window. This analysis underscores the significance of this particular band, as the line represents the substantial impact of investors within this time frame on market dynamics. Understanding such patterns becomes pivotal in comprehending market trends and potential shifts. ## Link to Our Data * [Exchange Inflow - Spent Output Age Bands Live Chart](https://cryptoquant.com/asset/btc/chart/flow-indicator/exchange-inflow-spent-output-age-bands?exchange=all_exchange\&window=DAY\&priceScale=linear\&metricScale=linear) * [Exchange Inflow - Spent Output Age Bands (%) Live Chart](https://cryptoquant.com/asset/btc/chart/flow-indicator/exchange-inflow-spent-output-age-bands-percent?exchange=all_exchange\&window=DAY\&priceScale=linear\&metricScale=linear) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Exchange Inflow Age Distribution](/api-reference/btc-flow-indicator/exchange-inflow-age-distribution) # Exchange Inflow - Spent Output Value Bands Source: https://docs.cryptoquant.com/data-guide/exchange/exchange-inflow-spent-output-value-bands Exchange Inflow - Spent Output Value Bands shows the distribution of all spent outputs flowed into exchange wallets according to its value. ## What is Exchange Inflow - Spent Output Value Bands? Exchange Inflow - Spent Output Value Bands show the distribution of all spent outputs flowed into exchange wallets according to their value. Each colored band represents the total value of spent outputs that flowed into exchanges that have a value within the denoted range. This indicator can be used to estimate the flow of capital, or how coins moved into exchanges from whale and retail holders. $$ \text{Exchange Inflow - Spent Output Value Bands}=\sum\_{u \in \text{inflow-utxos}\_t} \text{value}\_u \* \mathbb{I}(a\_i \leq \text{value}\_u < b\_i) $$ $$ \text{Exchange Inflow - Spent Output Value Bands(%)}=\frac{\sum\_{u \in \text{inflow-utxos}\_t} \text{value}\_u \* \mathbb{I}(a\_i \leq \text{value}*u < b\_i)}{\sum*{u \in \text{inflow-utxos}*t} \text{value}*{u}} \* 100 $$ $$ \[a\_i, bi) \in \[0, 0.01), \[0.01, 0.1), \[0.1, 1), \[1, 10), \[10, 100), \[100, 1k), \[1k, 10k), \[10k, inf) $$ | Metric | Definition | | - | - | | Exchange Inflow - Spent Output Value Bands | Each colored band represents **the total value of** spent outputs that flowed into exchanges, that have a value within the denoted range. | | Exchange Inflow - Spent Output Value Bands (%) | Each colored band represents **the ratio of** the total value of spent outputs that flowed into exchanges, that have a value within the denoted range. | ## How to interpret Exchange Inflow - Spent Output Value Bands ![Bitcoin: Exchange Inflow - Spent Output Value Bands - All Exchanges. CryptoQuant](https://images.surferseo.art/b81642d2-6441-4f0e-b2f1-8aa66b7bee50.png) This indicator can be used to estimate the number of coins moved by whales and retail holders. As price rises/falls, it is advised to watch out for values in the Spent Output Value Bands to further gain insights on the market through analyzing its participants. Exchange Inflow - Spent Output Value Bands can provide information that is not notified by our alert telegram channel and provide details such as Multiple Whale Possibilities and Aggregated Retail Inflow. Unlike UTXO Value Bands, Spent Output Value Bands focus on the UTXOs that were destroyed within the set metric window. With the help of Spent Output Value Bands, it is possible to pinpoint which sized UTXOs were destroyed in what amount. Using this knowledge, investors can correlate any price movement or changes in the network with the action of whales/retails' action precisely. Different from regular Spent Output Value Band, Exchange Inflow - Spent Output Value Bands specifically screen spent output that relates to exchanges' wallets and thus provides powerful insights like those below ### **1) Targeting Specific Exchange Inflow's coins' feature (Whale/Retail)** For example, if a large inflow happened to Binance's Wallet, taking an interpretation from Exchange Inflow - Spent Output Value Bands (Binance) could indicate whether Whales/Retails' coins were accountable for most of the inflow. If drastic price movement was made after the inflow, it is reasonable to infer that **" Whales/Retails deposited most of the inflow to the Binance and caused the price to drop/rise."** ### **2) Keep track of only the whale/retails' coins' exchange inflow** One notable application of Exchange Inflow - Spent Output Value Bands lies in its ability to precisely track the movement of whale and retail-held coins specifically within exchange inflows. By focusing solely on the influx of coins associated with whales and retail investors, investors can gain a targeted understanding of market dynamics. This tailored insight is particularly valuable for discerning whether significant price fluctuations following an inflow can be attributed to the strategic actions of whales or retail participants. In essence, this feature enables users to keep a vigilant eye on the exchange inflow of coins held by these key players, offering a nuanced perspective on market behavior. ## By Value Itself * **High value (Native Value) & Dominance (%)** in certain Spent Output Value Bands - **Mostly accountable for changes in the network** For example, if the UTXO Value Band of 1k to 10k has the greatest Spent Output Value Bands in terms of value or dominance, it could be interpreted that investors holding at least 1k to 10k are primarily accountable for any price movement or changes that occur in the exchange within a set metric window. ### **Bitcoin: Spent Output Value Bands USD Value Range** ![Bitcoin: Spent Output Value Bands USD](https://images.surferseo.art/108642d7-1d42-4dac-acfb-76efa78c5423.png) The Spent Output Value Bands reveal the distribution of all spent outputs based on their respective values. Each distinct band visually encapsulates the cumulative value of spent outputs falling within the specified USD value range. This metric serves as a valuable tool for gauging the volume of coins in motion, offering insights into the activity of both prominent whales and individual retail holders. ### Links to Our Data * [Exchange Inflow - Spent Output Value Bands Live Chart](https://cryptoquant.com/asset/btc/chart/flow-indicator/exchange-inflow-spent-output-value-bands?exchange=all_exchange\&window=DAY\&priceScale=linear\&metricScale=linear) * [Exchange Inflow - Spent Output Value Bands (%) Live Chart](https://cryptoquant.com/asset/btc/chart/flow-indicator/exchange-inflow-spent-output-value-bands-percent?exchange=all_exchange\&window=DAY\&priceScale=linear\&metricScale=linear) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Exchange Inflow Supply Distribution](/api-reference/btc-flow-indicator/exchange-inflow-supply-distribution) # Exchange Reserve Source: https://docs.cryptoquant.com/data-guide/exchange/exchange-reserve The total amount of coins held in the exchange addresses. ## What is Exchange Reserve? Exchange Reserve refers to the overall quantity of coins or cryptocurrencies, like Bitcoin, stored in the wallets or addresses controlled by a particular exchange. It represents the total holdings that the exchange has available for various purposes, such as facilitating trades, withdrawals, and managing user balances. ## How to interpret Exchange Reserve Understanding the dynamics of exchange reserves involves recognizing its role as a key metric in determining the availability of coins for potential sale within the market. The exchange reserves serve as an aggregated measure, reflecting the total quantity of coins held by the exchange and poised for potential transactions. Exchange Reserve is the accumulated result of [Exchange In/Outflow & Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) which naturally follows the indications that in/outflow has. Similar to Exchange NetFlow's interpretation, an increasing trend in netflow indicates the selling pressure and the decreasing trend indicates the buying pressure. Much like the interpretation of Exchange NetFlow, which tracks the net movement of assets into or out of an exchange, Exchange Reserves provides insights into market dynamics. An upward trend in the exchange reserves typically suggests an increasing selling pressure, indicating that more coins from the exchange's holdings are potentially entering the market for sale. Conversely, a downward trend in the exchange reserves points towards decreasing selling pressure, implying that fewer coins are available for sale. In essence, the interpretation of the exchange reserves, coupled with insights from related metrics like Exchange NetFlow, aids analysts and market participants in gauging the overall sentiment and potential market direction of currencies based on the exchange's coin holdings and their movement patterns. However, instead of Exchange In/Outflow & Netflow indicating the specific moment or period, Exchange Reserves makes it **easy to track the result of the entire period's movements.** ## By Value Itself The exchange reserve is a valuable metric that provides **insights into the** **level of accumulated selling pressure within an exchange**. By analyzing exchange reserves, market participants can gain a clearer understanding of the dynamics influencing the supply of coins available for trading. ### **High Selling Pressure** ![Bitcoin Exchange Reserves – Higher Selling Pressure](https://images.surferseo.art/7d82b2b3-cbb6-4ab7-9637-7434d8d62011.png) In scenarios where the exchange reserves are high, it signifies an elevated level of selling pressure in the market. This occurs when a substantial number of coins are held within the exchange's addresses, awaiting potential trades. Essentially, market participants are opting to keep a large portion of their holdings within the exchange, suggesting a readiness to sell. The **increased exchange reserve serves as an indicator that a significant volume of coins is available for trading**, potentially leading to a higher supply in the market. #### **Example** If a cryptocurrency exchange reports a substantial increase in its reserve, such as a spike from 10,000 to 50,000 Bitcoin over a short period, it implies to the markets that a considerable number of users have deposited coins into the exchange, signaling a heightened selling sentiment among traders. ### **Low Selling Pressure** ![Bitcoin Exchange Reserves – Low Selling Pressure](https://images.surferseo.art/74c77750-ed96-49a4-be03-b406548b873e.png) Conversely, a low exchange reserve indicates diminished selling pressure. In such instances, a smaller number of coins are held within centralized exchanges, awaiting potential trade transactions. This suggests that **market participants are more inclined to withdraw their coins from the exchange for purposes other than immediate selling**, leading to a reduced supply available for trading. #### **Example** Suppose a cryptocurrency exchange experiences a decline in its reserve, dropping from 30,000 to 5,000 Bitcoin. This decline in reserve currency signifies to the markets that a smaller number of users are keeping their coins within the exchange, implying a lower selling sentiment and a potential shift towards other activities like becoming long-term holders or making external transfers. ## By Examining Trend Examining the trend of centralized exchanges and even decentralized exchange reserves is a pivotal aspect of financial analysis, providing insights into the dynamics of deposits, asset availability, and strategic practices of companies within the market. This examination is essential for risk management, assessing liabilities, and gauging potential profit in response to fluctuations in supply and demand. ### **Changing Status in Scarcity** Delving deeper into the changing status of scarcity, the trend in exchange reserves is a critical indicator for financial analysts. It involves the careful evaluation of deposits, the supply of assets, and the financial companies' practices to navigate through different economic regimes and countries. ### **Increasing Trend: Decreasing Scarcity - Bearish** Witnessing an increasing trend in exchange reserves often suggests a decrease in currency scarcity, a phenomenon that aligns with bearish market sentiment. In this scenario, financial companies may be opting to deposit more coins into the exchange, responding to a perceived decrease in risk and potentially lowering overall market power. #### **Example** A surge in exchange reserves from 20,000 to 50,000 Bitcoin during, for example, March, due to the spot Bitcoin ETF getting rejected, may be indicative of a strategic response to a decrease in perceived risk, a practice observed by many financial companies. ### **Decreasing Trend: Increasing Scarcity - Bullish** Conversely, a decreasing trend in exchange reserves signals an increasing scarcity of coins, an occurrence typically associated with bullish market movements. This trend signifies a preference for asset accumulation among market participants, reflecting a shift in supply-demand dynamics and a potential increase in market power. #### **Example** If exchange reserves decrease from 30,000 to 10,000 Bitcoin due to the spot Bitcoin ETF approval, it may suggest a bullish sentiment as financial companies and traders seek to accumulate assets, and become long-term holders amid decreasing Bitcoin scarcity. ## Final Notes In conclusion, the role of Bitcoin exchange reserves extends far beyond numerical values on a balance sheet. It serves as a compass, guiding investors through the ever-shifting landscape of cryptocurrency markets. By interpreting trends, understanding selling pressure, and analyzing changing scarcity dynamics, market participants can navigate strategic decisions with confidence. The insights drawn from exchange reserves not only shape investment strategies but also offer a glimpse into the collective sentiment of market participants. In a landscape marked by constant evolution, the scrutiny of exchange reserves emerges as a key practice for those seeking to master the art of strategic cryptocurrency investment. ## Links to Our Data * [BTC: Exchange Reserve in CryptoQuant Live Chart](https://cryptoquant.com/asset/btc/chart/exchange-flows/exchange-reserve?exchange=all_exchange\&window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=line) * [ETH: Exchange Reserve in CryptoQuant Live Chart](https://cryptoquant.com/asset/eth/chart/exchange-flows/exchange-reserve?exchange=all_exchange\&window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=line) * [Altcoins: Exchange Reserve in CryptoQuant Live Chart](https://cryptoquant.com/asset/link/chart/exchange-flows) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Reserve](/api-reference/btc-exchange-flows/reserve) * **ETH** — [Reserve](/api-reference/eth-exchange-flows/reserve) * **ERC-20** — [Reserve](/api-reference/erc20-exchange-flows/reserve) # Exchange Supply Ratio Source: https://docs.cryptoquant.com/data-guide/exchange/exchange-supply-ratio Exchange Supply Ratio is calculated as the exchange reserve divided by the total supply. ## What is Exchange Supply Ratio? Exchange Supply Ratio is calculated as the exchange reserve divided by the total supply. The metric measures the ratio of tokens reserved in exchange wallets relative to the total supply of the token. $$ \text{Exchange Supply Ratio} = \frac{\text{Exchange Reserve}}{\text{Total Supply}} $$ ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Exchange Supply Ratio](/api-reference/btc-flow-indicator/exchange-supply-ratio) * **ETH** — [Exchange Supply Ratio](/api-reference/eth-flow-indicator/exchange-supply-ratio) * **XRP** — [Exchange Supply Ratio](/api-reference/xrp-flow-indicator/exchange-supply-ratio) * **Stablecoin** — [Exchange Supply Ratio](/api-reference/stablecoin-flow-indicator/exchange-supply-ratio) * **ERC-20** — [Exchange Supply Ratio](/api-reference/erc20-flow-indicator/exchange-supply-ratio) # Exchange to Exchange Source: https://docs.cryptoquant.com/data-guide/exchange/exchange-to-exchange The total amount of coins transferred from exchange to other exchange wallets. ## What is Exchange to Exchange? The total amount of coins transferred from one cryptocurrency exchange to another exchange's digital wallet represents the cumulative volume of digital assets moved between different trading platforms. This metric provides insights into liquidity patterns, asset distribution, and capital movements within the cryptocurrency market, aiding in informed decision-making based on market trends. | Metrics | Description | | - | - | | Flow Total | The total amount of BTC transferred from the exchange to other exchange wallets. | | Flow Mean | The mean amount of BTC transferred from the exchange to other exchange wallets. | | Transactions Count Flow | The number of transactions from exchange to other exchange wallets. | The mean value is the Flow Total divided by the Transactions Count Flow. Data entries were collected from the first transaction between two entities. ## **Significance of Crypto Exchange-to-Exchange Transfers** ![Inter Entity Flows: CryptoQuant Platform](https://images.surferseo.art/1d225844-a06e-4e12-aa01-9ad2c378f9cc.png) In the dynamic crypto market, the movement of digital assets between various exchanges holds paramount significance. As cryptocurrencies gain widespread acceptance, understanding the seamless transfer of assets across cryptocurrency exchanges becomes crucial for comprehending market dynamics. Whether through centralized exchanges known for convenience or decentralized exchanges offering enhanced security and low fees, the significance of exchange-to-exchange transfers lies in their contribution to overall liquidity, market volume, and participant interactions. ### **Analyzing Flow Total** ![Bitcoin Exchange to Exchange Flow (Total) - All Exchanges, Spot Exchanges. CryptoQuant](https://images.surferseo.art/b6790c79-5144-4094-b107-cd93bd2f299e.png) The "Flow Total" metric plays a pivotal role in unraveling the intricacies of the crypto market. It encapsulates the total amount of digital currencies transferred between crypto exchanges, providing a bird's-eye view of transactional activities. By delving into the Flow Total, market participants gain valuable insights into liquidity trends, transactional volume patterns, and potential market shifts, empowering them to make informed decisions regarding the buying and selling of cryptocurrencies. ### **Understanding Flow Mean** ![Bitcoin: Exchange to Exchange Flow (Mean) - All Exchanges, Spot Exchanges. CryptoQyant](https://images.surferseo.art/669359e7-7d1e-4dec-8cb8-163a4dbbaabd.png) Comprehending the "Flow Mean" adds an additional layer of insight to the analysis of crypto exchange-to-exchange transfers. This metric, representing the mean amount of cryptocurrencies moved between exchanges, unveils patterns and anomalies in trading behavior. Investors and traders can leverage this understanding to discern market trends, adapt strategies, and capitalize on opportunities, contributing to a more nuanced approach in navigating the crypto market. ### **Transactions Count Flow and Its Role in Crypto Exchanges** ![Bitcoin: Exchange to Exchange Transactions - All Exchanges, Spot Exchanges. CryptoQuant.](https://images.surferseo.art/f6bffcbe-3a69-41f6-ae4b-32b905dac8a7.png) The "Transactions Count Flow" metric holds a key role in supplementing the analysis of cryptocurrency exchange-to-exchange transfers. Beyond just amounts, this metric provides essential information on the frequency of transactions between crypto exchanges. This nuanced view enhances the overall comprehension of market dynamics, aiding market participants in gauging the intensity and frequency of exchange interactions. Whether engaging with decentralized or centralized exchange, investors can utilize this metric for strategic decision-making, adding a valuable layer to their market analysis toolkit. ## Link to Our Data * [Exchange to Exchange in CryptoQuant Live Chart](https://cryptoquant.com/asset/btc/chart/inter-entity-flows) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Exchange to Exchange](/api-reference/btc-inter-entity-flows/exchange-to-exchange) # Exchange Transactions Count Source: https://docs.cryptoquant.com/data-guide/exchange/exchange-transactions-count The total number of deposits/withdrawals transactions of the exchange. ## What is Exchange Transactions Count? The total number of deposits/withdrawals transactions of the exchange. | Metrics | Description | | - | - | | Transactions Count Inflow | The total number of deposits to the exchange. | | Transactions Count Outflow | The total number of withdrawals from the exchange. | ## How to interpret Exchange Transactions Count Considering that it costs fees to make multiple transactions, the active exchange transaction count indicates the **closest meaning to the number of investors** that are involved in a network transaction. This naturally leads to possible interpretation of correlating exchange transactions count to the level of attention of trading investors. ### By value itself [#interpretation](#interpretation) It shows whether **few or large numbers of transactions** are involved in netflows. * **High** : **Large** number of transactions are accountable for [Exchange In/Outflow & Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) * **Low** : **Small** number of transactions are accountable for [Exchange In/Outflow & Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) ### By examining trend [#use-case](#use-case) It shows the **level of Exchange Activeness & Volatility** * **Increasing trend** : **Expanding interest and activeness** More people are participating in exchange flows indicating expanding interest and activeness of exchange trading leading to possible volatility * **Decreasing** **trend** : **Diminishing interest and activeness** Less people are participating in exchange flows indicating diminishing interest and activeness of exchange trading leading to possible decreasing volatility ## Link to Our Data * [BTC: Exchange Transactions Count in CryptoQuant Live Chart](https://cryptoquant.com/asset/btc/chart/transactions) * [ETH: Exchange Transactions Count in CryptoQuant Live Chart](https://cryptoquant.com/asset/eth/chart/transactions) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Transactions Count](/api-reference/btc-exchange-flows/transactions-count) * **ETH** — [Transactions Count](/api-reference/eth-exchange-flows/transactions-count) * **ERC-20** — [Transactions Count](/api-reference/erc20-exchange-flows/transactions-count) # Fund Flow Ratio Source: https://docs.cryptoquant.com/data-guide/exchange/fund-flow-ratio The total BTC amount flowing into or out of exchange divided by the total BTC amount transferred on the whole Bitcoin network. ## What is Fund Flow Ratio? The Fund Flow Ratio is a crucial metric in crypto, calculated by dividing the total amount of Bitcoin (BTC) flowing into or out of exchanges by the overall BTC amount transferred across the entire Bitcoin network. This ratio serves as a comprehensive indicator, providing insights into the relative movement of BTC between exchanges and the broader network, helping analysts assess the dynamics of funds in and out of trading platforms in relation to the overall Bitcoin ecosystem. $$ \text{Fund Flow Ratio} = \frac{\text{Total Exchange Inflows + Outflows in BTC}}{\text{Total Transferred BTC (whole network)}} $$ ## How to interpret Fund Flow Ratio ![Bitcoin: Fund Flow Ratio - All Exchanges](https://images.surferseo.art/b41503c4-d094-403b-8603-63f361605d3e.png) The Fund Flow Ratio serves as a quantitative measure, shedding light on the proportion of bitcoins held by exchanges in comparison to the total bitcoins circulating within the broader Bitcoin network. * High Values: Investors are **actively using the exchanges** * Low Values: Investing **activities in exchanges at low rates** When the Fund Flow Ratio registers high values, it indicates a scenario where investors are actively utilizing exchanges, suggesting heightened engagement and trading activities within these platforms. Conversely, low values in the Fund Flow Ratio signify that investors are employing exchanges at lower rates, possibly indicating subdued trading activity or a preference for alternative avenues for managing their bitcoins. This metric not only reflects the fund flow data dynamics within exchanges but also provides valuable insights into investor sentiment and behavior. By examining the Fund Flow Ratio alongside other fundamental indicators such as net fund flow, flow statement, positive and negative fund flow, analysts can gain a comprehensive understanding of investor preferences and activities in the cryptocurrency market. This nuanced analysis allows for a more informed assessment of the underlying assets, helping discern trends in investor behavior and market dynamics. ### Increase in Fund Flow An upswing in the Fund Flow Ratio holds significant implications for the cryptocurrency market, offering key insights into the heightened activity and dynamics within exchanges. This increase, indicative of a surge in transactions involving Bitcoins, can be interpreted through two distinct perspectives: #### **Surging Interest and Activity in Bitcoin Trading** A notable rise in the Fund Flow Ratio suggests an increased enthusiasm and engagement among market participants in Bitcoin trading activities. Traders and investors are actively involved in buying or selling Bitcoins, signifying a heightened interest in capitalizing on market opportunities. This surge in activity may be driven by positive market sentiments, favorable price trends, or emerging opportunities within the cryptocurrency landscape. #### **Escalation in Selling Pressure or Profit-Taking** Alternatively, an uptick in the Fund Flow Ratio could indicate a surge in selling pressure, particularly when accompanied by profit-taking strategies. In this scenario, traders and investors may be capitalizing on favorable price movements to realize profits, contributing to the increased flow of Bitcoins within exchanges. The heightened selling pressure might suggest a cautious approach from market participants who are leveraging favorable market conditions to secure gains. ### Decrease in Fund Flow ![Decrease in Fund Flow Ratio](https://images.surferseo.art/5f1ce29f-158a-42db-b0b5-b2bd93a01e8a.png) A decline in the Fund Flow Ratio is a pivotal indicator that sheds light on the transactional activity within cryptocurrency exchanges, specifically the buying or selling of Bitcoins. This reduction in the Fund Flow Ratio holds dual implications, providing valuable insights into market dynamics: #### **Lower Interest in Bitcoin Trading** A diminishing Fund Flow Ratio might signify a decline in overall interest and participation in Bitcoin trading. Traders, anticipating a potential drop or stagnant price movement, may opt to reduce their activity on exchanges. This scenario suggests a cautious sentiment prevailing among market participants who may be adopting a wait-and-watch approach, expecting market conditions to evolve before resuming significant trading activities. #### **Decrease in Selling Pressure by Whales** Conversely, the decrease in the Fund Flow Ratio could stem from a reduction in selling pressure, particularly influenced by large-scale cryptocurrency holders, such as institutions, often referred to as whales. In this context, a declining Fund Flow Ratio may indicate that whales are choosing to retain their Bitcoin holdings rather than initiating substantial sell-offs. This strategic behavior from whales can be interpreted as a potential bullish signal, suggesting confidence in the market's upward trajectory. The reluctance of significant holders to sell their Bitcoin positions may signify an anticipation of future price appreciation, influencing market sentiment positively. ## By Examining Trend ### **Negative Fund Flow and Investor Sentiment** The Fund Flow Ratio is a crucial metric that goes beyond a simple net movement analysis, offering insights into investor sentiment and preferences within the financial markets. Negative fund flow, as revealed by fund flow statements, can be indicative of a scenario where investors are withdrawing their assets from exchanges. This outflow might signal a shift in investor sentiment, influencing the cash flows of cryptocurrency exchanges and impacting their financial health. ### **Analyzing Fund Flow Statement: Cryptocurrency Market** Understanding cash flows is paramount for evaluating the financial health of exchanges. Fund flow refers to the net movement of funds, and examining cash flow statements can unveil the dynamics of how an exchange generates and utilizes its financial assets. The Fund Flow Ratio provides a comprehensive overview, assisting investors in gauging the balance sheet of exchanges and making informed decisions based on these financial indicators. ### **Equity Funds and the Fund Flow Ratio** Equity funds play a crucial role in influencing the fund flow ratio within cryptocurrency exchanges. By delving into the net fund flow and its correlation with equity funds, investors can better grasp the interplay between financial assets and investor behavior. This analysis can unveil trends in investor sentiment, guiding market participants to navigate the ever-evolving landscape of the cryptocurrency market. ## Links to Our Data * [Fund Flow Ratio in CryptoQuant Live Chart](https://cryptoquant.com/asset/btc/chart/flow-indicator/fund-flow-ratio?exchange=all_exchange\&window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=line) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Fund Flow Ratio](/api-reference/btc-flow-indicator/fund-flow-ratio) # Fund Data & Premium Source: https://docs.cryptoquant.com/data-guide/fund-premium Fund and premium indicators — Grayscale GBTC/ETHE holdings and premiums, Coinbase Premium, Korea Premium Index, and Bank Supply Ratio — that gauge institutional and regional demand. * [Grayscale Bitcoin Trust (GBTC)](/data-guide/fund-premium/grayscale-bitcoin-trust-gbtc) * [GBTC Digital Asset Holdings](/data-guide/fund-premium/grayscale-bitcoin-trust-gbtc/gbtc-digital-asset-holdings): Grayscale BTC Holdings represents how much BTC Grayscale is holding for its investment. It is calculated by multiplying GBTC's shares outstanding and assets per share. * [GBTC Premium or Discount](/data-guide/fund-premium/grayscale-bitcoin-trust-gbtc/gbtc-premium-or-discount): The percent difference between the market price (GBTC) and native asset value (BTC). Higher the premium indicates the U.S. bull market. * [Grayscale Ethereum Trust (ETHE)](/data-guide/fund-premium/grayscale-ethereum-trust-ethe) * [ETHE Digital Asset Holdings](/data-guide/fund-premium/grayscale-ethereum-trust-ethe/ethe-digital-asset-holdings) * [ETHE Premium or Discount](/data-guide/fund-premium/grayscale-ethereum-trust-ethe/ethe-premium-or-discount) * [Coinbase Premium](/data-guide/fund-premium/coinbase-premium): Coinbase Premium is the gap between Coinbase Pro price (USD pair) and Binance price(USDT pair) * [Korea Premium Index](/data-guide/fund-premium/korea-premium-index): Korea Premium Index is the percent difference between the market price of Korean exchanges and other exchanges * [Bank Supply Ratio](/data-guide/fund-premium/bank-supply-ratio): Bank Supply Ratio is calculated as the bank reserve divided by the total supply. # Bank Supply Ratio Source: https://docs.cryptoquant.com/data-guide/fund-premium/bank-supply-ratio Bank Supply Ratio is calculated as the bank reserve divided by the total supply. ## What is Bank Supply Ratio? Bank Supply Ratio is calculated as the bank reserve divided by the total supply. The metric measures the ratio of tokens reserved in bank wallets relative to the total supply of the token. ### **Calculation Method** The Bank Supply Ratio is derived through a straightforward calculation – the bank reserve is divided by the total supply of the token. This simple yet powerful formula unveils a percentage that reflects the proportion of tokens held in bank wallets compared to the overall supply available in the market. $$ \text{Bank Supply Ratio} = \frac{\text{Bank Reserve}}{\text{Total Supply}} $$ ### **Exploring Bank Supply Ratio in Cryptocurrency Analysis** ![Bitcoin: Bank Supply Ratio – CryptoQuant](https://images.surferseo.art/120500d4-1f02-44af-8cf8-a3d3f137a70b.png) The Bank Supply Ratio is a critical metric of cryptocurrency analysis, offering profound insights into the dynamics of token reserves and their relationship with the total token supply. Let's delve deeper into the intricacies of this metric to understand its significance and how it contributes to a comprehensive evaluation of the market. #### **Understanding Total Supply** Total supply refers to the overall quantity of tokens that exists in the cryptocurrency ecosystem. It includes tokens in circulation, those held by individual investors, and, importantly, the tokens reserved in bank wallets. This comprehensive approach ensures that the Bank Supply Ratio encapsulates the entire spectrum of token distribution. #### **Significance of the Ratio** The resulting ratio from this calculation is a key indicator of the token's liquidity and concentration. A higher Bank Supply Ratio suggests a larger portion of the total token supply is held in bank reserves, indicating potential concentration among major stakeholders. Conversely, a lower ratio implies a more dispersed distribution, with a significant portion of tokens in the hands of individual investors. #### **Implications for Market Analysis** Analysts and investors utilize the Bank Supply Ratio to draw insights into market dynamics and anticipate potential shifts. A rising ratio may signal increased concentration, potentially impacting market volatility. On the other hand, a decreasing ratio could indicate a more decentralized distribution, which might lead to a more stable market. #### **Risk Assessment and Decision-Making** For investors and traders, understanding the Bank Supply Ratio is instrumental in risk assessment and decision-making. High concentration in bank reserves might suggest vulnerability to market manipulation by large entities, whereas a balanced distribution may foster a healthier and more resilient market. #### **Incorporating Bank Supply Ratio in Strategies** Savvy market participants often incorporate the Bank Supply Ratio into their analytical strategies. By monitoring changes in this ratio over time, traders can adapt their strategies to align with evolving market conditions, potentially gaining a competitive edge in the fast-paced cryptocurrency landscape. ## Final Notes In conclusion, the Bank Supply Ratio stands as a valuable metric for those navigating the cryptocurrency market. Its capacity to reveal insights into token concentration, liquidity, and potential market shifts makes it an indispensable tool for comprehensive market analysis and strategic decision-making. As the cryptocurrency ecosystem continues to evolve, the Bank Supply Ratio remains a key metric for those seeking a nuanced understanding of market dynamics. # Coinbase Premium Source: https://docs.cryptoquant.com/data-guide/fund-premium/coinbase-premium Coinbase Premium is the gap between Coinbase Pro price (USD pair) and Binance price(USDT pair) ## What is Coinbase Premium? It's the price difference between Coinbase's BTCUSD pair and Binance's BTCUSDT pair. ## How to interpret Coinbase Premium Coinbase Premium is one of the indicators that shows a sign for "whale accumulation". Coinbase Pro is considered to be the gateway for institutional investors purchase to cryptocurrencies. Thus, Coinbase Premium is used to track institutional whale's movement. Also, 2020 bull run was driven by institutional investors and high net-worth individuals in the U.S. which makes investors check Coinbase Premium more than ever. For example. when the Bitcoin price continuously broke 20k, 30k, and 40k while the Coinbase premium was maintaining more than \$50 premium. It indicates that during these dips, institutions or other whales were accumulating. ### By value itself [#interpretation](#interpretation) It shows whether **investors who use Coinbases' purchase strength** * **High** : **Possible** **Strong buy from Coinbase** Coinbase whales might be accumulating Bitcoin despite the high price * **Low** : **Possible** **Strong sell or dormant status from Coinbase** Coinbase whales are not buying much as regular or possibly selling coins ### By examining trend [#use-case](#use-case) It shows the **Sentiment of Coinbase Whale or investors**. * **Increasing trend** : **Possible Whale Accumulation** It indicates that whales are strengthening their accumulation and continuously buying at a higher premium. In addition, it shows expanding interest and activeness of investors in Coinbase. * **Decreasing trend** : **Possible Whale Sell or dormant status of whales** It indicates that whales are continuously selling at a lower premium. In addition, it shows decreasing interest and activeness of investors in Coinbase. ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Coinbase Premium Index](/api-reference/btc-market-data/coinbase-premium-index) * **ETH** — [Coinbase Premium Index](/api-reference/eth-market-data/coinbase-premium-index) # Grayscale Bitcoin Trust (GBTC) Source: https://docs.cryptoquant.com/data-guide/fund-premium/grayscale-bitcoin-trust-gbtc Grayscale Bitcoin Trust (GBTC) holdings and premium data — a proxy for institutional U.S. demand for indirect Bitcoin exposure through a regulated security. ## What is Grayscale Bitcoin Trust (GBTC)? Grayscale Bitcoin Trust is solely and passively invested in Bitcoin, enabling investors to gain exposure to BTC in the form of a security while avoiding the challenges of buying, storing, and safekeeping BTC directly. ## Why look at Grayscale? ### Insight on demand for indirect investment As mentioned in the definition, Grayscale provides exposure to BTC while providing trading and security services and could be traded like any other securities. In addition, funds or trusts like Grayscale has limitation in fluent trading such as lock-up period. Utilizing this feature, keeping track of how much BTC Grayscale's BTC fund holds provides the closest meaning in finding out the degree of needs for especially certified institutional U.S. investors. [GBTC Digital Asset Holdings](/data-guide/fund-premium/grayscale-bitcoin-trust-gbtc/gbtc-digital-asset-holdings) ### Insight on a different degree of demand between direct & indirect investment GBTC premium or Discount shows the difference of need between indirect & direct investment through comparing respective prices. Difference between the price in exchange and trading GBTC stocks, it is natural to assume the premium or discount with its demand. [GBTC Premium or Discount](/data-guide/fund-premium/grayscale-bitcoin-trust-gbtc/gbtc-premium-or-discount) ## Link to Our Data * [Grayscale Bitcoin Trust (GBTC) in CryptoQuant Live Chart](https://cryptoquant.com/asset/btc/chart/fund-data/fund-holdings?symbol=gbtc\&window=DAY\&sma=0\&ema=0\&priceScale=log\&metricScale=linear\&chartStyle=line) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Market Price USD](/api-reference/btc-fund-data/market-price-usd) · [Market Volume](/api-reference/btc-fund-data/market-volume) # GBTC Digital Asset Holdings Source: https://docs.cryptoquant.com/data-guide/fund-premium/grayscale-bitcoin-trust-gbtc/gbtc-digital-asset-holdings Grayscale BTC Holdings represents how much BTC Grayscale is holding for its investment. It is calculated by multiplying GBTC's shares outstanding and assets per share. ## What is GBTC Digital Asset Holdings? $$ \text{Asset Holdings} = \text{Shares outstanding} \* \text{Asset per share} $$ ## How to interpret GBTC Digital Asset Holdings Grayscale BTC Holdings represents how much BTC Grayscale is holding for its investment. This metric indicates the stock market's sentiment where higher the value means bullish sentiment of investors in the stock market. This metric indicates the stock market's sentiment toward BTC * **Higher** the value means **bullish sentiment** of investors toward BTC in the stock market. ## Link to Our Data * [Grayscale Bitcoin Trust (GBTC) in CryptoQuant Live Chart](https://cryptoquant.com/overview?search=GBTC) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Digital Asset Holdings](/api-reference/btc-fund-data/digital-asset-holdings) # GBTC Premium or Discount Source: https://docs.cryptoquant.com/data-guide/fund-premium/grayscale-bitcoin-trust-gbtc/gbtc-premium-or-discount The percent difference between the market price (GBTC) and native asset value (BTC). Higher the premium indicates the U.S. bull market. ## What is GBTC Premium or Discount? The percent difference between the market price (GBTC) and native asset value (BTC). $$ \text{Premium} = \frac{\text{GBTC price} - \text{Bitcoin per share \* Bitcoin price}}{\text{Bitcoin per share \* Bitcoin price}} $$ ## Interpretation of Grayscale Bitcoin Trust (GBTC) Premium or Discount ### **High Premium** A high premium suggests a bullish market sentiment in the United States. This scenario indicates that investors are willing to pay more for GBTC shares than the actual net asset value of the Bitcoin it holds. Investors should be cautious as it signals a potential downside risk, and they might be paying a premium for exposure to Bitcoin. ### **Low Premium** Conversely, a low premium indicates a bearish market sentiment in the U.S. Investors in this situation may be hesitant to pay extra for GBTC shares compared to the net asset value of Bitcoin. This scenario suggests potential upside risk, as investors may be getting exposure to Bitcoin at a discount. ### **Net Asset Value (NAV)** The Net Asset Value represents the total value of Grayscale Bitcoin Trust's assets (in this case, Bitcoin) minus its liabilities. It is a crucial indicator of the trust's intrinsic value and provides a baseline for assessing the premium or discount. ## **Investment Objective** GBTC's investment objective is to track the BTC market price performance, and its structure allows investors to passively invest in Bitcoin. This passive investment approach can be appealing to those seeking asset exposure without directly holding or managing the assets themselves. ### **Enabling Investors to Gain Exposure** Grayscale Bitcoin Trust plays a crucial role in enabling investors to gain exposure to Bitcoin without directly dealing with the complexities of cryptocurrency ownership. This indirect investment avenue appeals to institutional and retail investors seeking a regulated and familiar investment environment. ### **Passively Invested with Less Fees** Investors in GBTC benefit from a passive investment strategy, mirroring the performance of Bitcoin. This approach offers convenience and simplicity, especially for those looking to gain exposure to these assets without actively managing their investments. Additionally, the fees associated with GBTC are typically lower than directly holding and securing Bitcoin. ### **Is GBTC an Exchange Traded Fund (ETF)?** While GBTC is not an ETF, it operates similarly as it enables investors to gain exposure to digital assets. Exchange Traded Funds, unlike GBTC, are a type of investment fund and exchange-traded product, with shares that can be traded on stock exchanges. ### **Grayscale Investments and Regulatory Compliance** Grayscale Investments, the entity behind GBTC, has played a pioneering role in offering regulated investment products tied to crypto assets. Regulatory compliance is a key aspect, ensuring that GBTC adheres to applicable securities laws, providing a level of assurance for investors. ### **First Securities Product for BTC** GBTC holds historical significance as the first securities product solely invested in Bitcoin. Its introduction marked a milestone in the financial industry by providing a traditional investment avenue for a digital asset. ### **Bitcoin Held by GBTC and Securities and Exchange Commission (SEC) Oversight** The Bitcoin held by GBTC is subject to oversight by the U.S. Securities and Exchange Commission (SEC). This regulatory scrutiny adds an additional layer of assurance for investors, contributing to the trust's credibility in the market. ## Final Notes In conclusion, monitoring the GBTC Premium or Discount provides investors with valuable insights into market sentiment regarding Bitcoin. Understanding the nuances of GBTC, its net asset value, and its role in enabling exposure to digital assets is crucial for making informed investment decisions in the rapidly evolving cryptocurrency landscape. ## Link to Our Data * [Grayscale Bitcoin Trust (GBTC) in CryptoQuant Live Chart](https://cryptoquant.com/overview?search=GBTC) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Market Premium](/api-reference/btc-fund-data/market-premium) # Grayscale Ethereum Trust (ETHE) Source: https://docs.cryptoquant.com/data-guide/fund-premium/grayscale-ethereum-trust-ethe Grayscale Ethereum Trust (ETHE) holdings and premium data — a proxy for institutional U.S. demand for indirect Ethereum exposure through a regulated security. ## What is Grayscale Ethereum Trust (ETHE)? Grayscale Ethereum Trust is solely and passively invested in Ethereum, enabling investors to gain exposure to ETH in the form of a security while avoiding the challenges of buying, storing, and safekeeping ETH directly. ## Why look at Grayscale? ### Insight on demand for indirect investment As mentioned in the definition, Grayscale provides exposure to ETH while providing trading and security services and could be traded like any other securities. In addition, funds or trusts like Grayscale has limitation in fluent trading such as a lock-up period. Utilizing this feature, keeping track of how much ETH Grayscale's ETH fund holds provides the closest meaning in finding out the degree of needs for especially certified institutional U.S. investors. [ETHE Digital Asset Holdings](/data-guide/fund-premium/grayscale-ethereum-trust-ethe/ethe-digital-asset-holdings) ### Insight on a different degree of demand between direct & indirect investment ETHE premium or Discount shows the difference of need between indirect & direct investment through comparing respective prices. Difference between the price in exchange and trading ETHE stocks, it is natural to assume the premium or discount with its demand. [ETHE Premium or Discount](/data-guide/fund-premium/grayscale-ethereum-trust-ethe/ethe-premium-or-discount) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **ETH** — [Market Price USD](/api-reference/eth-fund-data/market-price-usd) · [Market Volume](/api-reference/eth-fund-data/market-volume) # ETHE Digital Asset Holdings Source: https://docs.cryptoquant.com/data-guide/fund-premium/grayscale-ethereum-trust-ethe/ethe-digital-asset-holdings How much ETH the Grayscale Ethereum Trust holds, calculated as shares outstanding times assets per share — a gauge of stock-market sentiment toward ETH. ## What is ETHE Digital Asset Holdings? $$ \text{Asset Holdings} = \text{Shares outstanding} \* \text{Asset per share} $$ ## How to interpret ETHE Digital Asset Holdings Grayscale ETH Holdings represents how much ETH Grayscale is holding for its investment. This metric indicates the stock market's sentiment * **Higher** the value means bullish sentiment of investors are toward ETH in the stock market. ## Link to Our Data * [Grayscale Ethereum Trust (ETHE) in CryptoQuant Live Chart](https://cryptoquant.com/overview?search=ETHE) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **ETH** — [Digital Asset Holdings](/api-reference/eth-fund-data/digital-asset-holdings) # ETHE Premium or Discount Source: https://docs.cryptoquant.com/data-guide/fund-premium/grayscale-ethereum-trust-ethe/ethe-premium-or-discount The percent difference between the ETHE market price and the value of the ETH it represents — a high premium signals U.S. bullishness, a discount signals bearishness. ## What is ETHE Premium or Discount? The percent difference between the market price(ETHE) and native asset value(ETH). $$ \text{Premium} = \frac{\text{ETHE price} - \text{Ethereum per share \* Ethereum price}}{\text{Ethereum per share \* Ethereum price}} $$ ## How to interpret ETHE Premium or Discount **High** premium: It indicates the **U.S. bullish market** toward ETH, which also indicates downside risk. **Low** premium: It indicates the **U.S. bearish market** toward ETH**,** which also indicates the upside risk. ## Link to Our Data * [Grayscale Ethereum Trust (ETHE) in CryptoQuant Live Chart](https://cryptoquant.com/overview?search=ETHE) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **ETH** — [Market Premium](/api-reference/eth-fund-data/market-premium) # Korea Premium Index Source: https://docs.cryptoquant.com/data-guide/fund-premium/korea-premium-index Korea Premium Index is the percent difference between the market price of Korean exchanges and other exchanges ## What is Korea Premium Index? Korea Premium Index is the percent difference between the VWAP of Korean exchanges and other exchanges. ## How to interpret Korea Premium Index Korean crypto market is mostly made up of retail investors due to regulations against institutional investors and stable coins. Utilizing this unique market structure, Korean Premium Index indicates the **closest meaning to the retailers' sentiment and buying power** or particularly Korean market buying power. Historically, Korean premium over 16 percent gave an indication that the price could be a local top or an indication of FOMO in the market. ![](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/8KFuy6uBuamltDBhWdb0.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=86706ab4e3793906274c564362b6a5eb) ### By value itself [#interpretation](#interpretation) ![](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/2XWvPZUYghvQg5lUxNFW.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=2ab63c824ceb4b2879e5f9123a761a21) It shows how much premium retailers or Koreans are willing to pay for the purchase * **Above '0' (+)**: Retailers are willing to pay a **premium** for the purchase * **Below '0' (-)**: Retailers are only willing to purchase at a **discount** ### By examining trend [#use-case](#use-case) It shows the **level of retailers' Activeness & Volatility** * **Increasing trend** : **Expanding interest and activeness** Increasing values in the Korean Premium Index indicates that more retailers are continuously buying at a higher price than average market price. * **Decreasing** **trend** : **Diminishing interest and activeness** Decreasing values in the Korean Premium Index indicates that retailers are continuously selling at a lower price than average market price. ## Link to Our Data * [BTC: Korea Premium Index in CryptoQuant Live Chart](https://cryptoquant.com/overview/btc-market-data/465?window=day) * [ETH: Korea Premium Index in CryptoQuant Live Chart ](https://cryptoquant.com/overview/eth-market-data/466?window=day) # Market Data/Indicators Source: https://docs.cryptoquant.com/data-guide/market Entry into Market Data/Indicators | Data/Indicator | Definition | Implied | | - | - | - | | Liquidation | When investor close their position voluntarily or by forced liquidation which comes with bankruptcy procedure | Any form of liquidation could affect the price and call in for another action of forced liquidationEx. Short/Long Squeeze | | [Taker Buy Sell Volume/Ratio](/data-guide/market/taker-buy-sell-volume-ratio) | ​Defined as the ratio of Taker Buy Volume divided by the Taker Sell Volume |
  • Over values of '1' Dominant **Bullish** sentiment
  • Under values of '1'Dominant **Bearish** sentiment
| | [Open Interest](/data-guide/market/open-interest) | The number of open positions (including both long and short positions) currently on a derivative exchange's BTC/USD trading pairs. |
  • Increasing-Adding liquidity, volatility, and attention -Supporting ongoing price trend
  • DecreasingExiting liquidity, volatility, and attention
| | [Funding Rates](/data-guide/market/funding-rates) | Periodic payments to long or short traders based on the difference between the perpetual contract market and the spot price |
  • Rates over ‘0’Dominant Long Sentiment
  • Rates under ‘0’Dominant Short Sentiment
  • IncreasingLongs gaining dominance
  • Decreasing trendShorts gaining dominance
| | [Estimated Leverage Ratio](/data-guide/market/estimated-leverage-ratio) | Defined as the ratio of open interest divided by the reserve of an exchange |
  • High-Over Leveraged Market-Possible Volatility
  • LowLow Leveraged Market
  • Increasing Holding More Leverage
  • Decreasing trendTaking off Leverage
| | [Fund Flow Ratio](/data-guide/exchange/fund-flow-ratio) | The total BTC amount flowing into or out of exchange divided by the total BTC amount transferred on the whole Bitcoin network |
  • Increasing-Possible Volatility-Active Exchanges' Activity
  • DecreasingPossible OTC
| # Capitalization models Source: https://docs.cryptoquant.com/data-guide/market/capitalization-models Alternative capitalization models to market price. ### Alternative Capitalization Models The market price itself can be easily manipulated by forces, especially in cryptocurrency markets, which we call noise. In order not to be fooled by market price, traders need to see multiple **alternative capitalization models** to see how the market is going. #### Market Cap ![Bitcoin Market Cap. Source: CryptoQuant](https://images.surferseo.art/b4f984e0-d210-46de-8a48-8e0448e6e7c7.png) Market Cap is defined as the total market capitalization of the coin, calculated by multiplying the total supply with its USD price. $$ \text{Market Cap} = \text{Total Supply} \* \text{Price in USD} $$ #### Realized Cap ![Bitcoin Realized Cap. Source: CryptoQuant](https://images.surferseo.art/5f05aba7-a19d-4fd5-b72b-fdaf257090b5.png) Realized Cap is the sum of each UTXO \* last movement price. Since cryptocurrencies can be lost, unclaimed, or unreachable through various bugs, Realized Cap is introduced to discount those coins which have remained unmoved for a long period. It is one way to attempt to measure the value of the coin. This can be described as an on-chain version of the volume-weighted average price (VWAP). $$ \text{Realized Cap} = \sum\_i \text{UTXO}\_i \* \text{Price at creation} $$ #### Average Cap ![Bitcoin Average Cap. Source: CryptoQuant](https://images.surferseo.art/d91518a8-a005-4e29-9f48-948c35e2f944.png) Average Cap is a forever moving average, calculated by dividing the cumulated sum of daily market cap by the age of the market. Instead of using fixed time for calculating the moving average (e.g. 50 days, 100 days ...), this serves as the true mean. $$ \text{Average Cap} = \frac{\sum \text{Daily Market Cap}}{\text{Age in days}} $$ #### Delta Cap ![Bitcoin Delta Cap. Source: CryptoQuant](https://images.surferseo.art/75acc51e-0a46-4e81-a7b9-cfa466b38ce8.png) Delta Cap is calculated as the subtraction of Realized Cap to Average Cap. Delta Cap is often used to spot market bottoms. Moreover, by analyzing the movement of Delta Cap which oscillates between Realized Cap and Average Cap, we could notice that market tops are reached when Delta Cap is near Realized Cap (in a log scaled chart). $$ \text{Delta Cap} = \text{Realized Cap} - \text{Average Cap} $$ #### Thermo Cap (Inflows Cap) Thermo Cap is calculated as the weighted sum of mined coins by the creation price. This measures total capitalization flowed into the blockchain network, which in turn is to be called as Inflows Cap. As shown in the below figure, by comparing to Market Cap, Thermo Cap allows traders to spot market tops or bottoms. ![Thermo Cap vs. Market Cap. Source: CryptoQuant](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MELiV3i2_66QbXErNSE.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=70ae1b5fdfad024a346f7d884ad65d38)Smaller gap between market cap and thermo cap allows to see market bottoms as shown in red boxes. ## Final Note In conclusion, navigating the volatile terrain of cryptocurrency markets demands a nuanced understanding that goes beyond the simplicity of market prices. Alternative capitalization models serve as indispensable tools for the discerning investor, offering a more comprehensive perspective and mitigating the impact of market noise. The Market Cap, a fundamental metric and capitalization model, computes the total market capitalization by multiplying the coin's total supply with its USD price. Realized Cap, on the other hand, factors in the movement of coins over time, discounting those that have remained stagnant. This provides a more accurate reflection of a coin's value, akin to an on-chain version of the volume-weighted average price. The Average Cap introduces a dynamic element, eschewing fixed time frames and offering a moving average calculated by dividing the cumulative sum of daily market cap by the age of the market. Delta Cap, the subtraction of Realized Cap from Average Cap, becomes a valuable tool for identifying market bottoms and tops. Analyzing the oscillation of Delta Cap between Realized Cap and Average Cap unveils potential market trends, particularly when Delta Cap nears Realized Cap in a log-scaled chart. Thermo Cap, or Inflows Cap, serves as a weighted sum of mined coins by creation price, unveiling the total capitalization flowing into the blockchain network. Comparing Thermo Cap to Market Cap enables traders to identify market tops or bottoms, with a smaller gap indicating potential market bottoms. In this dynamic landscape, where words like "volatility" and "uncertainty" are divided by the innovative spirit of blockchain, these alternative capitalization models represent a forward-looking method for traders looking to make an investment. By incorporating these measures into their analyses, traders can present a more nuanced understanding of market dynamics, better equipped to navigate the present and future of cryptocurrency markets. ## Links to our Data * [Market Cap in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/471?window=day) * [Realized Cap in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/194?window=day) * [Average Cap in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/195?window=day) * [Delta Cap in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/196?window=day) * [Thermo Cap in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/472?window=day) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Capitalization](/api-reference/btc-market-data/capitalization) * **ETH** — [Capitalization](/api-reference/eth-market-data/capitalization) * **XRP** — [Capitalization](/api-reference/xrp-market-data/capitalization) * **TRX** — [Capitalization](/api-reference/trx-market-data/capitalization) * **Stablecoin** — [Capitalization](/api-reference/stablecoin-market-data/capitalization) # Estimated Leverage Ratio Source: https://docs.cryptoquant.com/data-guide/market/estimated-leverage-ratio Estimated Leverage Ratio (ELR) is defined as the ratio of open interest divided by the reserve of an exchange ## What is Estimated Leverage Ratio? Estimated Leverage Ratio (ELR) is defined as the ratio of open interest divided by the reserve of an exchange. $$ \text{Estimated Leverage Ratio} = \frac{\text{Open Interest}}{\text{Amount of Reserve}} $$ ## How to interpret Estimated Leverage Ratio Estimated Leverage Ratio indicates how much leverage is used by users on average. ELR for a derivative exchange tells us how much leverage is used by users on average. This information measures traders' sentiment whether they take a high risk or low risk. ### By value itself [#interpretation](#interpretation) It could be interpreted as the degree of leverage of the market * **High**: **Over Leveraged Market+ Possible Volatility** * **Low**: **Low Leveraged Market** ### By examining trend [#indicating-selling-or-buying-pressure](#indicating-selling-or-buying-pressure) It shows the sentiment or tendency of total investors' urge to use leverage. * **Increasing trend: Holding More Leverage** Increasing in values indicates more investors are taking high leverage risk in the derivatives trade. Also, if ELR value is high compared to the last couple of days, it indicates traders are quite confident in their positions. * **Decreasing trend**: **Taking off Leverage** Decreasing in values indicates more investors are taking off leverage risk in the derivatives trade. Also, if ELR value is low compared to the last couple of days, it indicates traders are changing their views or finishing their positions. ## Link to Our Data * [Estimated Leverage Ratio in CryptoQuant Live Chart](https://cryptoquant.com/asset/btc/chart/market-indicator/estimated-leverage-ratio?exchange=all_exchange\&window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=line) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Estimated Leverage Ratio](/api-reference/btc-market-indicator/estimated-leverage-ratio) * **ETH** — [Estimated Leverage Ratio](/api-reference/eth-market-indicator/estimated-leverage-ratio) * **XRP** — [Estimated Leverage Ratio](/api-reference/xrp-market-data/estimated-leverage-ratio) # Exchange Whale Ratio Source: https://docs.cryptoquant.com/data-guide/market/exchange-whale-ratio The total BTC amount of top 10 transactions (in terms of total BTC sent) divided by the total BTC amount flowing into exchange. ## What is Exchange Whale Ratio? The total BTC amount of the top 10 transactions (in terms of total BTC sent) divided by the total BTC amount flowing into exchanges.\ $$ \text{Exchange Whale Ratio} = \frac{\text{Sum of Top 10 Exchange Inflow TXs(BTC)}}{\text{Total Exchange Inflows in BTC}} $$ ## How to interpret Exchange Whale Ratio Find Whale Focused Exchanges with Top 10 Inflows. Looking at the relative size of the top 10 inflows to total inflows, it is possible to discover which exchanges whales use. For example, as Gemini has mostly whale users, it is possible for the price to rise or fall dramatically. This has potential risks, but also the possibility of arbitrage. ## Link to Our Data * [Exchange Whale Ratio in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/595?window=day) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Exchange Whale Ratio](/api-reference/btc-flow-indicator/exchange-whale-ratio) # Funding Rates Source: https://docs.cryptoquant.com/data-guide/market/funding-rates Funding rates are periodic payments between traders to make the perpetual futures contract price close to the index price. ## Funding Rate: Definition Funding rates make the perpetual futures contracts price close to the index price. It is made to be closer to the spot prices and covers some of the gap generated by the perpetual period of time. All cryptocurrency derivatives exchanges use funding rates for perpetual contracts and the standard unit is a percentage. Funding Rate is a result of market behaviors and could be used to maker some interpretation in the derivative market which also is a dominant price maker in the market. However, correlating high funding rates with inevitable price drop could be a wrong interpretation. In the bull market, it has a tendency to naturally bring higher funding rates with price rises. \*CryptoQuant provides **minute-based funding rates** compared to exchange deciding every 8 hours ## How to interpret Funding Rates The funding rate represents traders' sentiments in the perpetual swaps market and the amount is proportional to the number of contracts. ### By Value Itself [#interpretation](#interpretation) ![BTC Funding Rates: All Exchanges, Long and Short Sentiment. Source: CryptoQuant](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/jkvbXOfgDf8ztwjsdIZL.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=10c03dbaf7a9e7055b5ee3c0a0732cc5) #### **Dominant Long Sentiment (Rates over '0')** ![Positive Funding Rate - All Exchanges. Source CryptoQuant](https://images.surferseo.art/565bb639-a033-4f7f-b91b-7c2f963b289c.webp) A positive funding rate — above 0 — reflects bullish sentiment, as long traders dominate and pay shorts to keep positions open. While it signals confidence in upward price movement, it mainly shows market positioning, not a guarantee of continued price gains. The optimism embedded in positive funding rates suggests a collective belief among traders in the potential for upward price movement. *Example:* During a Bitcoin bull market, positive funding rates might persist as traders express confidence in the coin's upward trajectory. This situation could be seen as an endorsement of the prevailing positive market sentiment. #### **Dominant Short Sentiment (Rates under '0')** ![Negative Funding Rate from BitMEX Exchange. Source: CrypotQuant](https://images.surferseo.art/5895484e-0224-4e9e-9136-db21e2b9270d.webp) On the flip side, negative funding rates (rates under '0') suggest a dominant bearish sentiment. In this scenario, short position traders are in control and are willing to pay long traders. Negative funding rates indicate a belief among traders that the market is more likely to experience a downward movement. *Example:* In periods of uncertainty or amid negative news about the cryptocurrency market, negative funding rates might emerge as traders bet on a potential decline in prices. This could be interpreted as a cautious or bearish stance. ## By Examining Trend ![Bitcoin Funding Rate - All Exchanges. Source: CryptoQuant](https://images.surferseo.art/1f698a58-0369-4b2e-9506-960741b0ac3d.png) ### **Increasing Trend: Longs Gaining Dominance** When crypto funding rates show an increasing trend, it suggests that long positions are gaining dominance. Traders holding long positions are willing to pay short traders, indicating a prevailing bullish sentiment in the market. Example: If Bitcoin's price has been on a week-long rise, an increasing trend in the funding rate could be anticipated, reflecting heightened expectations and confidence among traders in the cryptocurrency's upward trajectory. This period may also witness a surge in leveraged positions as traders based on recent euphoria might enter the market. However, caution is advised, as cumulative liquidations could occur in the event of a steep price move, resulting in partial or total loss for those holding leveraged positions. Crypto exchanges might forcefully close such positions, especially if funding levels indicate unusually high fees. ### **Decreasing Trend: Shorts Gaining Dominance** Conversely, a decreasing trend in funding rates implies that short positions are gaining dominance. Short traders are willing to pay long traders, suggesting a bearish sentiment in the market. Example: During a period of heightened uncertainty in the crypto markets, a decreasing trend in funding rates may coincide with traders adopting a cautious approach, leading to an increase in short positions. Traders might be borrowing funds to take leveraged short positions, anticipating a negative funding rate due to the prevailing bearish sentiment. ### Perpetual Contracts A Perpetual contract in the cryptocurrency market is intricately tied to funding rates, which are periodic payments exchanged between traders to bring the perpetual futures contract price in alignment with the index price. These rates are crucial in narrowing the gap created during the perpetual period, aiming to maintain proximity to spot prices. Funding rates reflect market behavior and data shows traders insights into derivative market dynamics. However, it's essential to avoid simplistic correlations, as high funding rates don't necessarily predict an inevitable price drop. Understanding the sentiment conveyed by funding rates—whether bullish with positive rates or bearish with negative rates—provides traders with valuable information to navigate the complex landscape of perpetual contracts in cryptocurrency markets. This includes gauging price rise expectations, assessing a funding fee for traders' leveraged positions, and indicating highly leveraged bets in the market. Traders hoping to capitalize on bullish bets need to monitor funding rates closely, considering their impact on spot markets led by bitcoin traders. Balancing a leveraged position with an understanding of the trader's initial margin is key to navigating the dynamics of highly leveraged bets and making informed decisions in this dynamic market environment. ## End Notes In such scenarios, it is crucial for traders to assess the market carefully, ensuring they have sufficient funds to cover potential losses, especially in leveraged positions. The negative funding rate could indicate a pessimistic outlook for the underlying asset, and traders should be mindful of the risks associated with leveraged trading in volatile crypto markets. Delving deeper into the space of cryptocurrency derivatives, understanding the dynamics of crypto futures funding rates becomes paramount for traders and market watchers alike. Examining trends in these rates unveils the ebb and flow of market dynamics, providing traders with valuable insights into the ever-shifting landscape of crypto futures and spot markets. As market participants navigate this intricate interplay between futures trading and spot markets, the significance of funding rates becomes increasingly apparent, offering a nuanced perspective for strategic decision-making. ## Link to Our Data * [Funding Rates in CryptoQuant Live Chart](https://cryptoquant.com/asset/btc/chart/derivatives/funding-rates?exchange=all_exchange\&window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=column) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Funding Rates](/api-reference/btc-market-data/funding-rates) * **ETH** — [Funding Rates](/api-reference/eth-market-data/funding-rates) * **XRP** — [Funding Rates](/api-reference/xrp-market-data/funding-rates) # MVRV (Market Value to Realized Value) Ratio Source: https://docs.cryptoquant.com/data-guide/market/mvrv-ratio MVRV (Market Value to Realized Value) ratio is defined as an asset's market capitalization divided by realized capitalization. ## What is MVRV (Market Value to Realized Value) Ratio? MVRV (Market Value to Realized Value) ratio is defined as an asset's market capitalization divided by [realized capitalization](/api-reference/btc-market-data/capitalization). $$ \text{MVRV Ratio} = \frac{\text{Market Cap}}{\text{Realized Cap}} $$ ### Market Value to Realized Value (MVRV) Overview The Market Value to Realized Value (MVRV) ratio serves as a crucial metric in the world of cryptocurrency, offering valuable insights into market dynamics and investor behavior. Understanding how MVRV is measured and its implications can provide a nuanced perspective on the valuation of a cryptocurrency. Here's a comprehensive overview of the MVRV ratio: #### **Measuring MVRV** MVRV is calculated by comparing two key metrics: market capitalization and realized capitalization. Market capitalization is determined by multiplying the current market price of a cryptocurrency by its circulating supply. On the other hand, realized capitalization considers the aggregate value of all coins based on the price at which they were last transacted. ## How to interpret MVRV (Market Value to Realized Value) Ratio By comparing two valuation methods, the MVRV ratio can tell us to get a sense of whether the price is fair or not, which means it is useful to get market tops and bottoms. It is important to note that historically, it has been an outstanding indicator to spot market top/bottom or local top/bottom that occurred through three halvings. ### By Value Itself [#interpretation](#interpretation) ![Bitcoin Market Value to Realized Value (MVRV) Ratio. Source: CryptoQuant](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/MbVqmGU2MoYT2N3RGReR.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=01c5ed47a1d1073112fadb14cc1117fa) MVRV accounts both realized cap and market cap into account making certain values critical in making an investment decision. * Values over **‘3.7’**: **Possible Market Top** If the values go above 3.7, it could be reasonable to sell the position off * Values under **‘1’**: **Possible Market Bottom** If the values go under 1**,** it signals an undervalued market (Market Cap below Realized Cap) and it is time to take a gradual long position. ### By Examining Trend [#indicating-selling-or-buying-pressure](#indicating-selling-or-buying-pressure) If Market cap growth outpaces that of the realized cap, MVRV values rise indicating possible motive for selling. * **Increasing trend**: **Increasing selling pressure** As MVRV increases, it indicates that the market cap is outpacing realized cap meaning there is increasing motive for selling in the market. * **Decreasing trend**: **Decreasing selling pressure** As MVRV decreases, it indicates that realized cap is outpacing the market cap meaning there is decreasing motive for selling in the market. ### **Implications of MVRV** #### **Overvaluation and Market Tops** ![Bitcoin MVRV Ratio - Overvaluation](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/iFl7BTwScAZwMhcLrgyQ.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=024e55958e844e96e0b866a64a3e7a26) **High MVRV:** When MVRV values are elevated, it may signal that the current market price of Bitcoin is significantly higher than the last transaction prices. This could indicate a state of overvaluation, potentially signaling a market top. Analyzing Bitcoin's fair value in the context of MVRV provides essential insights into whether the current price aligns with the aggregate market cost basis. #### **Undervaluation and Market Bottoms** ![Bitcoin MVRV Ratio - Undervaluation](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/oYFHVhuJMCVqsGsjKzql.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=35ec87f8490b05d98f87b6eb706b33c3) **Low MVRV:** Conversely, a low Market Value to Realized Value suggests that the current price of Bitcoin is relatively lower compared to the last transaction prices. This could point towards undervaluation, potentially signaling a market bottom. Investors keen on assessing the average price of Bitcoin in relation to its MVRV can use this metric to gauge potential buying opportunities. #### **Market Sentiment and Investor Behavior** **Fluctuations in MVRV:** Monitoring changes in the MVRV ratio over time provides insights into shifts in market sentiment and investor behavior, influencing Bitcoin's current market value. Sudden spikes or dips can indicate changing perceptions about the Bitcoin price, offering traders valuable information for strategic decision-making. #### **Long-Term vs. Short-Term Holder Behavior** **Divergence in MVRV:** Analyzing the MVRV for short-term holders versus long-term holders can reveal variations in behavior. A significant divergence might suggest different outlooks and strategies between these two groups of Bitcoin investors, shedding light on potential market trends. #### **Risk Management** **MVRV Trends:** Traders and investors can use Bitcoin MVRV trends to inform their risk management strategies. Understanding whether Bitcoin is currently trading at a premium or discount relative to its realized value can aid in making more informed decisions about the current Bitcoin price. This nuanced approach is crucial for navigating the dynamic and ever-evolving Bitcoin landscape. ### End Notes The MVRV ratio serves as a valuable tool for assessing the relative valuation of a cryptocurrency, offering a nuanced perspective on market conditions and investor sentiment. Traders and investors can leverage this metric to make more informed decisions in the dynamic and ever-evolving cryptocurrency landscape. ## Link to Our Data * [MVRV ratio in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/197?window=day) * [MVRV ratio in CryptoQuant Data API docs](https://cryptoquant.com/docs/#operation/getRiskIndicatorMVRV) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [MVRV](/api-reference/btc-market-indicator/mvrv) # Open Interest Source: https://docs.cryptoquant.com/data-guide/market/open-interest Open interest is defined as the amount of open positions (including both long and short positions) currently on a derivative exchange's BTC/USD trading pairs. ## What is Open Interest? Open interest is defined as the number of open positions (including both long and short positions) currently on a derivative exchange's BTC/USD trading pairs. ## How to interpret Open Interest ![Bitcoin: Open Interest - All Exchanges, All Symbol – Source: CryptoQaunt](https://images.surferseo.art/07cf81b9-6bdd-4e26-a1cc-fcd2ed506640.png) A large value of open interest can indicate increased **volatility** in the price of BTC. For this reason, an open interest chart could also be useful for determining the market tops and bottoms with additional indicators. * **Increasing**: **Adding liquidity, volatility, and attention + supporting ongoing price trend** As positions and contracts are continuously being opened, it indicates more liquidity, volatility, and attention are coming into the derivative market. Increasing trend in OI could support the current ongoing price trend. * **Decreasing**: **Exiting liquidity, volatility, and attention** As Open Interest (OI) decrease, it indicates futures contract/ positions are being closed. In turn, this might trigger the possibility of long/short squeeze caused by sudden price movement or vice versa. ### Understanding Open Interest ![Ethereum: Open Interest - All Exchanges, All Symbol – Source: CryptoQuant](https://images.surferseo.art/80932c9a-b7a0-4863-92b5-6a1618ef5018.png) Open interest plays a pivotal role in the world of cryptocurrency trading, and generally speaking especially on derivative exchanges. By exploring the concept in more detail, traders and investors can gain valuable insights into market trends and make informed decisions. ### **Why Open Interest Matters** While the definition of open interest is quite straightforward, its interpretation and real-world implications are more profound. Here's why open interest matters: **Volatility Indicator:** One of the primary reasons open interest matters is its role as a volatility indicator. When open interest is high, it signifies increased activity in the BTC/USD derivative market. This heightened activity often leads to greater price volatility. **Timing Market Tops and Bottoms:** In addition to measuring volatility, open interest can serve as a valuable tool for timing market tops and bottoms. Traders can use open interest charts alongside other indicators to enhance their market analysis and decision-making. ### **The Relationship Between Open Interest and Price Trends** Understanding the relationship between open interest and price trends is crucial. Here's how these two aspects are interconnected: #### **Increasing Open Interest** ![Increasing BTC Open Interest – Source: G a a h](https://images.surferseo.art/b212f200-46d5-4faa-9855-84837f1809d8.webp) When there is a high open interest amount, it signifies several important factors: **Adding Liquidity:** As open interest increases, more participants and new money entering the market means increased liquidity, making it easier to enter or exit positions. **Heightened Volatility:** A higher open interest often coincides with higher price volatility, providing trading opportunities. **Market Attention:** Higher open interest indicates more market participants are paying attention to the BTC/USD derivative market. As open interest increases this can lend support to the existing price trend, whether it's bullish or bearish. #### **Decreasing Open Interest** ![Decreasing Bitcoin Open Interest – Source: Maartunn](https://images.surferseo.art/e5830858-de94-434c-940d-417e90bddf35.webp) Conversely, when there is a low open interest indicates different dynamics in the market: **Exiting Liquidity:** As open interest decreases, participants are closing their positions, potentially signaling a decline in market sentiment and liquidity. **Reduced Volatility:** Lower open interest may lead to reduced price volatility, making the market less attractive for traders. **Shift in Attention:** A decrease in open interest might suggest a shift in market attention to other assets or trading opportunities. A low open interest can also trigger events like short squeezes or long squeezes, resulting from sudden price movements. ### **Practical Applications** The value of open interest extends beyond mere observation. It can be practically applied in various ways: **Timing Market Moves:** By closely monitoring open interest alongside other technical indicators, traders can better time their entries and exits, potentially maximizing their profitability. **Volatility Analysis:** Open interest's strong correlation with market volatility makes it a useful tool for traders looking to capitalize on price swings. **Statistical Correlation Analysis:** Statistical analysis reveals a positive correlation between open interest and volatility. This finding provides traders and investors with a data-driven approach to understanding market dynamics. ### **Insights from Trading Volume, Market Participants, and Futures Contracts** The interplay between trading volume, market participants, and futures contracts significantly influences open interest in the cryptocurrency market. Higher trading volumes boost liquidity and increase price volatility, attracting more market participants and subsequently elevating open interest. Various market players, including retail traders, institutions, "whales," and miners, influence both trading volume and open interest. Futures contracts, central to cryptocurrency derivatives, also shape open interest through leveraged positions and hedging strategies. These dynamics underpin the cryptocurrency market and are crucial for traders and investors. ## When to use Open Interest ### Statistical Correlation Analysis to Volatility We find that open interest (independent variable) and volatility (response variable) are statistically in **positive correlation** where p-values of F-statistic (for linear model) and the slope are less than 0.001. R-square of the model is estimated as 0.36 where the value is reasonably high considering financial raw data. ![](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MCBUg6ooEjgEGsdPI3O.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=ea3bc88257ff48748e84888fb5e683f4) The settings for this experiment are the followings: * We consider date range from '2018-11-05' to '2020-06-01'. * We resample the data in 15 days to compute volatility. * Volatility is computed as subtraction of max to min value of every resampled window. * Values in the above chart are in log form. ## Link to Our Data * [Open Interest in CryptoQuant Live Chart](https://cryptoquant.com/asset/btc/chart/derivatives/open-interest?exchange=all_exchange\&symbol=all_symbol\&window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=line) * [Open Interest in CryptoQuant Data API docs](https://cryptoquant.com/docs/#operation/getOpenInterest) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Open Interest](/api-reference/btc-market-data/open-interest) * **ETH** — [Open Interest](/api-reference/eth-market-data/open-interest) * **XRP** — [Open Interest](/api-reference/xrp-market-data/open-interest) # Realized Price Source: https://docs.cryptoquant.com/data-guide/market/realized-price Realized Price is calculated as Realized Cap divided by the total coin supply. ## What is Realized Price? Realized Price is calculated as Realized Cap divided by the total coin supply. It measures the average price weighted by the supply of what the entire market participants paid for their coins. It can be interpreted as the on-chain support or resistance price. $$ \text{Realized Price} = \frac{\text{Realized Cap}}{\text{Total Supply}} $$ ### Understanding Realized Price ![Full History of Bitcoin Realized Price – Source CryptoQuant](https://images.surferseo.art/d540298c-e1b0-418e-842d-29c88a819e3a.png) Understanding Realized Price is pivotal for anyone involved in on-chain analytics. At its core, Realized Price is a metric that provides insights into the actual market conditions and the average purchase price at which specific groups of cryptocurrency assets were acquired. Realized Price is derived from the aggregation of historical transaction data. It's a sophisticated metric that takes into account the varying prices at which each unit of a cryptocurrency was bought. This differs from the simpler Market Price, which only provides a snapshot of the current price based on the most recent trades. In essence, Realized Price digs deep into the entire history of sales of a cryptocurrency, offering a much broader perspective on its value. This metric reflects the average price at which investors have purchased a specific cryptocurrency, creating a more accurate representation of the market. In contrast, Market Price is influenced by current market trends and can sometimes be misleading, especially during periods of extreme volatility. Realized Price provides a historical view of the cryptocurrency's price movement, highlighting the levels at which investors have bought and sold, which can be instrumental in predicting market trends. It's a reflection of the "realized" value of the currency in circulation, as opposed to the "theoretical" value indicated by Market Price. ### Realized Price vs. Market Price Realized Price and Market Price are two distinct metrics, each offering unique insights into the crypto market. Understanding the differences between the two is vital for anyone looking to make informed decisions in the crypto space. Market Price is the most straightforward of the two. It represents the current price of a cryptocurrency based on the most recent trades. It's what you see on cryptocurrency exchanges and what the majority of investors reference. However, it's essential to remember that Market Price is heavily influenced by the current supply and demand dynamics and can fluctuate rapidly. Realized Price, on the other hand, provides a historical view of a cryptocurrency's average sale price. It considers the prices at which each unit of a cryptocurrency was acquired, leading to a more precise representation of the market. This history-based approach means that Realized Price is less susceptible to short-term price swings compared to Market Price. While Market Price can be affected by factors like market manipulation and speculative trading, Realized Price is more resistant to such influences. As a result, Realized Price is often considered a more reliable metric for understanding the "real" value of a cryptocurrency, which can be invaluable for investors and analysts seeking a deeper comprehension of the market. ### **Bitcoin Realized Price** ![Bitcoin: Realized Price Chart – Source: CryptoQuant](https://images.surferseo.art/f3d6bac7-d0ca-4b86-a0c1-377a2c83962b.png) Realized Price, an often-overlooked metric, is a critical tool for Bitcoin investors. During turbulent market periods, it acts as an early warning system. When the Market Price falls below the Realized Price, it's a sign that, on average, Bitcoin holders are facing paper losses. Value investors see this period as an opportunity to accumulate more Bitcoin. This accumulation phase often paves the way for a bull market as the Market Price rises above the Realized Price, as shown in the Bitcoin: Realized Price Chart. This pattern has held true throughout Bitcoin's adoption cycles to date, highlighting the enduring importance of the Realized Price metric for cryptocurrency investor ### Use Cases of Realized Price Realized Price has several noteworthy use cases in the world of cryptocurrency analytics. Here, in review, are a few key applications: #### Market Valuation Realized Price can provide a more accurate valuation of the cryptocurrency market, helping analysts assess whether the current market conditions are overvalued or undervalued. #### Investment Decisions Investors can use Realized Price to make more informed decisions. It can help identify potential buying or selling opportunities based on historical trends, enabling investors to time their moves more effectively. #### Market Cycles Realized Price can be a valuable tool for tracking market cycles. Understanding the phases of accumulation, distribution, and recovery can assist investors in adapting their strategies to prevailing market conditions. #### Risk Management Realized Price is instrumental in managing risk. By assessing the average price at which other investors entered the market, it's possible to gauge potential price levels where sell-offs or corrections may occur. #### Analyzing Network Health Realized Price can provide insights into the health of a cryptocurrency's network. Fluctuations in Realized Price can indicate changes in network dynamics, which can influence investor behavior and may impact overall market sentiment. ### End Notes By leveraging the Realized Price metric, investors and analysts can make more well-informed decisions, improve their risk management, and develop a deeper understanding of market dynamics in the ever-evolving world of cryptocurrency. ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Realized Price](/api-reference/btc-market-indicator/realized-price) # Taker Buy Sell Volume/Ratio Source: https://docs.cryptoquant.com/data-guide/market/taker-buy-sell-volume-ratio Understanding Taker Buy Sell Volume/Ratio involves discerning if the order taker is a buyer or seller based on ask or bid prices, distinguishing long volume from taker seller volume. ## Definition: Taker Buy Sell Ratio/Volume This concept is often confusing because every trade requires both a buyer and a seller of the given underlying asset. However, depending on whether the order taker is a buyer or seller (whether a transaction occurs at the ask price or the bid price), you can distinguish between long volume from taker seller volume. **Taker Buy Volume**: Volume of buy orders filled by takers in perpetual swaps (USD) **Taker Sell Volume**: Volume of sell orders filled by takers in perpetual swaps (USD) **Taker Buy Ratio**: Taker Buy Volume / Total volume in perpetual swaps (USD) **Taker Sell Ratio**: Taker Sell Volume / Total volume in perpetual swaps (USD) **Taker Buy Sell Ratio**: Taker Buy Volume / Taker Sell Volume *Note we unify the unit of return value to USD for each exchange where its contract specification may vary and covers perpetual swaps only.* ## How to interpret Taker Buy Sell Volume/Ratio A Taker buy or sell enables the transaction of a financial asset instantly at the current best available price. As takers are increasing it could be interpreted as they are willing to pay more to buy or sell at the highest level in an instant. Utilizing this feature, we can identify whether buying or selling pressure is great. ### By Value Itself * **Over values of 1**: Taker buy Volumes > Taker Sell Volume-Dominant It indicates to traders that more buyers are willing to buy coins at a higher price indicating that buying pressure is stronger than the selling pressure. It indicates a strong possibility of price rise and shows the bullish sentiment * **Under values of 1:** Taker Sell Volumes > Taker Buy Volume-Dominant It indicates that more sellers are willing to sell coins at a lower price indicating that sell pressure is stronger than the buying pressure. #### **Note** Even if the ratio is above 1 indicating that taker volume is dominant it does not necessarily mean that price is going up. It depends on the ratio and variance of volume that was traded on each bid/ask. ### Additional Explanation #### **Taker** In the context of trading, a taker is a market participant who places an order that is matched with an existing order on the order book. Takers "take" liquidity from the order book by executing trades at the current market price. #### **Maker** Maker trade refers to an order that goes on the order book (e.g. a limit order). These orders add volume to the order book, helping to 'make the market'. #### **Buy Volume** This represents the total volume and value of assets or securities bought by market participants during a specific time period. It indicates the total quantity of assets acquired in the market. #### **Sell Volume** Conversely, sell volume represents the total volume of assets or securities sold by market participants during a specific time period. It indicates the total quantity of assets disposed of in the market. #### **Taker Buy Sell Ratio** The ratio is a comparative measure that expresses the relationship between two quantities. In this context, the ratio provides insight into how buying volume compares to selling volume among market takers. #### **Bid and Ask Price** A maker who wants to buy an asset is willing to place limit orders in the order book at a lower price, and a maker who wants to sell is willing to place orders at a higher price. The bid price is the highest current price a buyer is willing to pay for an asset. The ask price is the lowest current price a seller is willing to sell a security for. There is always a bid price and an ask price in an actively traded asset which continuously fluctuates. When takers sell at the bid price set by makers, the amount of assets traded between the two contributes to the taker sell ratio and seller volume. This volume is selling volume because it has the potential to move the price down. When takers buy at the ask price, the amount of assets traded contributes to the taker buy volume–this volume pushes up the price. If the current market has more taker buy volume than taker sell volume, it means there is a tendency to increase the price as more trades occur at the ask price. When the current market has more taker sell volume than taker buy volume, it means there is a tendency to push the price down since there are more traders selling at the bid price. ### End Notes The Taker Buy Sell Volume/Ratio stands as one of the pivotal indicators for traders. It offers valuable insights into market sentiment and potential price movements. Despite its initial complexity, this metric provides a concise yet powerful tool for navigating dynamic market conditions. By evaluating the Taker Buy Sell Ratio and considering the interplay of volumes at bid and ask prices, traders can effectively gauge market dynamics. In doing so, this indicator becomes an indispensable asset for making informed decisions. ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Taker Buy Sell Stats](/api-reference/btc-market-data/taker-buy-sell-stats) * **ETH** — [Taker Buy Sell Stats](/api-reference/eth-market-data/taker-buy-sell-stats) * **XRP** — [Taker Buy Sell Stats](/api-reference/xrp-market-data/taker-buy-sell-stats) # Miner Flows/Indicators Source: https://docs.cryptoquant.com/data-guide/miner Entry into Miner flow/indicator | Data/Indicator | Definition | Interpretation | | - | - | - | | **Miner** | -A miner controls **supply** on the blockchain by mining blocks.If mining pools shut down their mining activities for some reason, the network cannot be maintained. -Find out more on [What are Entities?](https://userguide.cryptoquant.com/what-is-cryptoquant/background-knowledge/why-entity-matters) | -The place where additional newly coined amount is generated | | [Miner Outflow](/data-guide/miner/miner-outflow) | The outflow of BTC from mining pool wallets |
  • **High** A lot of miners' coins are exposed to selling -**Bearish**
  • **Low** Only a few of miners' coins are exposed to selling- **Bullish**
  • **Increasing** Miners' selling power is increasing- **Bearish**
  • **Decreasing** Miners' selling power is decreasing - **Bullish**
| | [Miner to Exchange](/data-guide/miner/miner-to-exchange) | The total amount of coins transferred from mining pool to exchange wallets |
  • **High** A lot of miners' coins are exposed to selling -**Bearish**
  • **Low** Only a few of miners' coins are exposed to selling- **Bullish**
  • **Increasing** Miners' selling power is increasing- **Bearish**
  • **Decreasing** Miners' selling power is decreasing - **Bullish**
| | [Miners' Position Index (MPI)](/data-guide/miner/miners-position-index) | Defined as the ratio of the number of all miners' outflows in USD divided by 365 days moving average of it. |
  • **High** Miners are sending their coins more than usual - **Bearish**
  • **Low** Miners are sending their coins less than usual - **Bullish**
  • **Increasing** **:** Miners are being more involved in selling and increasing their sell - **Bearish**
  • **Decreasing** : Miners are being less involved in selling and decreasing their sell - **Bullish**
| ## Reason to look for Miner flows/indicator ### Looking into Miner's cost-benefit model with BTC price [#miners-selling-capitulation](#miners-selling-capitulation) The time point for their selling or even buying provides valuable insights generated from miner's perspective. Miners spend their money in mining that comes with electricity or maintenance cost which makes them the only entity that follows a typical business model. They are forcibly required to sell some of their mined BTC to cover the costs. This business structure naturally exposes some of reasons behind miner's behavior. For example, 1\) If they sold their BTC regularly with unusually big amount, it could indicate that Miners are selling at over-valued BTC price. 2\) If they start to buy BTC instead of collecting fiats to pay for their costs, it could indicate that BTC is under-valued leading the miners to postpone their selling and trying to benefit from the under-valued BTC price. Thus, looking at the behavior pattern of miners could provide investors with market insight that took cost-benefit model of miners into account ## How to look at indicators This section identifies the look out point for individual indicators. These indicators could be divided by their identity and the usefulness in trading. Each data tracks each feature of miners and put together, they cover multiple aspects and capture movements in miners relatively precisely. If you want to make use of exchange data by figuring out ### 1) How many coins came out from miners Checking the outflow from miners [Miner Outflow](/data-guide/miner/miner-outflow) ### 2) How many coins are withdrawn from miners to the exchange Checking the flow into the exchange is a great way to keep track of coins that could be sold from miners [Miner to Exchange](/data-guide/miner/miner-to-exchange) ### 3) To look out if most of the miners are selling BTC Due to covering their cost, it is normal for miners to sell their BTC but if most of miners are selling, it could indicate a future price drop or provide top signal [Miners' Position Index (MPI)](/data-guide/miner/miners-position-index) It is wise to take a look at each indicator according to the number stated above. ## Points to be aware Just like any flow data, all the outflow from miners doesn't indicate immediate selling Firm belief in correlation to outflow from miner with price drop will not always be correct because there are several reasons miner send their BTC to other address. 1\) Just an internal wallet transfer 2\) Sending their BTC to sell in the future 3\) Possibility of re-sending BTC to their own wallet from exchange There is also a possibility where miners predicted or wrongfully valued BTC. Even though miners know the cost to generating BTC, their prediction of future BTC price could be wrong and inferring their movement with future BTC price might be misleading. For example, miner's selling does not necessarily mean a price top and their buys doesn't correlate to bottom price with BTC all the time. In addition, there are other factors to consider such as the market competitor relation with new-old miners affecting their unexpected cost and recovering cost time preference might differ from halving to halving or by different with miner pools. # Miner Outflow Source: https://docs.cryptoquant.com/data-guide/miner/miner-outflow The outflow of Bitcoin from mining pool wallets. We define mining pool wallets in our metrics as all participants in the mining pool including individual miners. ## What is Miner Outflow? Bitcoin miner outflows from mining pool wallets. We define mining pool wallets in our metrics as all participants in the mining pool including individual miners. | Metrics | Description | | - | - | | Outflow Total | The total amount of BTC transferred from the miner. | | Outflow Mean | The mean amount of BTC per transaction sent from the miner. | | Outflow Top10 | The total BTC amount of the top 10 transactions outflow from the miner | | Outflow Mean(MA7) | The 7 days moving average of mean BTC outflow from the miner. | The mean value is the Outflow Total divided by the Transactions Count Outflow. The outflow of BTC from mining pool wallets. We define mining pool wallets in our metrics as all participants in the mining pool including individual miners. Miner Outflow includes Miner sending their coins to the exchanges as well as internal transfers or to other entities. ## How to interpret Miner Outflow ### By value itself * **High**: A lot of miners' coins are exposed to selling, (**Bearish**) Bitcoin's price could go down. * **Low:** only a few of miners' coins are exposed to selling, (**Bullish**) Bitcoin's price could go up. #### By examining trend * **Increased Outflows:** Miners' selling power is increasing - **Bearish** * **Decreased Outflows**: Miners' selling power is decreasing - **Bullish** ![Bitcoin Miner Flows Data: CryptoQuant](https://images.surferseo.art/a3891a03-3c4f-483d-970c-065afe0122e7.png) ## About Bitcoin Miner Outflow As the [glossary](https://dataguide.cryptoquant.com/miner-flows-indicators/miner-outflow) says, bitcoin miners send their coins outside for various reasons. ![Bitcoin: Miner Outflow (Total) - All Miners. CryptoQuant](https://images.surferseo.art/fed59b94-c665-4080-b237-efac04143757.png) ### **Understanding Bitcoin Miner Outflows** Bitcoin miners play a pivotal role in the cryptocurrency ecosystem, but their activities often influence prices and market dynamics in ways that warrant closer examination. One such aspect is the movement of bitcoins from miners' wallets to external addresses, commonly known as miners' outflow. **Overview of Miner Outflows** Miners regularly transfer their coins to external addresses for various reasons, reflecting the dynamic nature of their operations. These outflows can provide valuable insights into market sentiment and crypto price trends. **Key Scenarios:** 1. **Moving to Exchanges for Possible Selling (Bearish Sign)**\ When miners transfer their coins to cryptocurrency exchanges, it is typically when indicating an intent to sell. This could be driven by the need to cover operational costs or to capitalize on price fluctuations. Such actions are often interpreted as bearish signals, as increased selling pressure may exert downward pressure on prices. 2. **Internal Wallet Movements (Neutral Sign)**\ Conversely, transfers between miners' internal wallets, excluding trading activities, carry a more neutral connotation. These movements may be conducted for reasons unrelated to market speculation, such as security enhancements or operational optimizations. While they do not directly impact market sentiment, they underscore the complexities of monitoring miners' activities. 3. **Strategic Hodling by Miners (Bullish Sign)** When miners opt to hold onto newly mined bitcoins instead of rushing to sell them, it's a bullish sign. This strategic decision reflects confidence in Bitcoin's long-term value and potential for growth. By reducing immediate selling pressure, miners contribute to a supply shortage, which can drive prices upward. Essentially, miners betting on Bitcoin's future success is a positive indicator for the market that prices may rise. **Implications and Analysis** Analyzing miners' outflows over the past few days can provide valuable insights into market dynamics. Large-scale movements, involving tens of thousands of bitcoins, may indicate shifts in the bitcoin miner outflow behavior that could influence less or more liquidity in the market and/or price stability. **Considering the Halving Effect** The halving event, which reduces the rate at which new blocks of bitcoins are generated, has historically influenced miner outflows behavior. As rewards diminish, miners may adjust their strategies to optimize profitability, potentially impacting the frequency and magnitude of outflows. ## **Final Words** In conclusion, monitoring Bitcoin miners' outflows offers a nuanced perspective on market dynamics, reflecting the interplay between mining operations, market sentiment, and price trends. By using miner outflows and understanding the motivations behind these movements and their potential implications, market participants can make more informed decisions in the ever-evolving crypto landscape. ### Links to Our Data * [Miner Outflow in CryptoQuant Live Chart](https://cryptoquant.com/asset/btc/chart/miner-flows) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Outflow](/api-reference/btc-miner-flows/outflow) # Miner Supply Ratio Source: https://docs.cryptoquant.com/data-guide/miner/miner-supply-ratio Miner Supply Ratio is calculated as the miner reserve divided by the total supply. ## What is Miner Supply Ratio? Miner Supply Ratio is calculated as the miner reserve divided by the total supply. The metric measures the ratio of tokens reserved in miner wallets relative to the total supply of the token. $$ \text{Miner Supply Ratio} = \frac{\text{Miner Reserve}}{\text{Total Supply}} $$ ### **The Miner's Role in the Ecosystem** ![Bitcoin: Miner Supply Ratio - All Miners. Source: CryptoQuant](https://images.surferseo.art/32723f9b-007f-4492-8741-fee9764e9300.png) To gain a comprehensive understanding of the Miner Supply Ratio, it is imperative to delve into the intricacies of the mining ecosystem. Miners serve as the cornerstone in validating blockchain transactions, ensuring security, and generating new tokens in the process. When miners are rewarded for their efforts, these tokens augment their reserves, invariably influencing the Miner Supply Ratio. The miner's perspective holds substantial significance, transcending the realms of solving intricate mathematical puzzles. It encapsulates the strategic choices regarding when to vend, retain, or accumulate the cryptocurrency they have earned. These determinations exert a direct impact on the Miner Supply Ratio and, in turn, the broader cryptocurrency market. ### **Historical Trends and Price Implications** Scrutinizing historical trends in the Miner Supply Ratio can be an enlightening experience. It can unveil patterns and correlations between fluctuations in the ratio and corresponding movements in cryptocurrency prices. For example, a conspicuous escalation in miner reserves often foreshadows an upswing in the cryptocurrency's price as miners anticipate and support its future appreciation. Conversely, a decline in the Miner Supply Ratio may serve as a bearish indicator. Miners may commence the liquidation of their reserves, triggering selling pressure and resultant price corrections. A profound comprehension of these historical price implications serves as an invaluable resource for traders and investors alike. ### **Comparative Analysis Across Cryptocurrencies** Conducting a comparative evaluation of Miner Supply Ratios across various cryptocurrencies can yield fascinating insights. Notably, Bitcoin may exhibit a considerably different Miner Supply Ratio in comparison to an alternative cryptocurrency. These disparities are shaped by diverse factors, including block rewards, total supply, and network adoption. Delving into these distinctions enables us to comprehend why specific cryptocurrencies are more susceptible to price volatility or stability than others. It also offers insights into the strategies of miners who endeavor to accumulate the cryptocurrencies they mine. ### **Wider Market Dynamics** The Miner Supply Ratio transcends the realms of a niche metric to exert a pivotal role in shaping the broader market dynamics. It imparts influence over liquidity, subsequently impacting price stability. When the Miner Supply Ratio trends upward, more coins are held in miner wallets and removed from active circulation, which tends to tighten the liquidity available to the market. Conversely, a declining Miner Supply Ratio means miners are releasing coins back into circulation, which can increase market liquidity—often coinciding with intensified price volatility as that supply reaches the market. Traders vigilantly monitor these trends, recognizing that they frequently present significant trading opportunities. ### **Real-World Implications of Miner Supply Ratio** In the dynamic world of cryptocurrency, metrics like Miner Supply Ratio transcend theory and exhibit substantial real-world and business implications. Here, we delve into some practical examples where this metric plays a pivotal role in understanding market dynamics and making informed decisions: #### **Bitcoin's Halving Events** Bitcoin's periodic halving events, which reduce the rate at which new bitcoins are issued, have a profound impact on its Miner Supply Ratio. As these events unfold, miners typically experience a substantial reduction in the value of their rewards. This leads to a decrease in their reserve of newly minted bitcoins, causing a shift in the Miner Supply Ratio. Observing this shift allows market participants to anticipate how miners may adjust their strategies, potentially influencing Bitcoin's price direction. #### **Bitcoin's Accumulation Phases** Historically, Bitcoin has experienced phases of accumulation by long-term investors, often coinciding with a declining Miner Supply Ratio. These accumulation phases suggest that miners and long-term investors are holding onto their BTC reserves, anticipating future price appreciation. As traders and investors identify these periods of reduced Miner Supply Ratios, they may consider them opportune times to accumulate Bitcoin before potential bullish trends. ### **Considerations for Investors** For investors within the cryptocurrency sphere, a comprehensive grasp of the Miner Supply Ratio is not only advantageous but imperative. This metric facilitates the identification of potential market trends, ranging from imminent price rallies to corrections. Additionally, it offers insights into the long-term health of a cryptocurrency by discerning whether miners are accumulating or divesting their holdings, thereby allowing investors to make well-informed decisions. ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Miner Supply Ratio](/api-reference/btc-flow-indicator/miner-supply-ratio) # Miner to Exchange Source: https://docs.cryptoquant.com/data-guide/miner/miner-to-exchange The total amount of coins transferred from mining pool to exchange wallets. ## What is Miner to Exchange? The total amount of coins transferred from the mining pool to exchange wallets. | Metrics | Description | | - | - | | Flow Total | The total amount of BTC transferred from a mining pool to exchange wallets. | | Flow Mean | The mean amount of BTC transferred from a mining pool to exchange wallets. | | Transactions Count Flow | The number of transactions from a mining pool to exchange wallets. | The mean value is the Flow Total divided by the Transactions Count Flow. Data entries were collected from the first transaction between two entities. ## How to interpret Miner to Exchange Identify if mining pool affiliated miners are preparing to sell coins. Unlike Miner Outflow, it only tracks the movement between Miner and Exchanges. ### By value itself [#interpretation](#interpretation) * **High** : A lot of miners' coins are exposed to selling - **Bearish** * **Low :** only a few of miners' coins are exposed to selling - **Bullish** ### By examining trend * **Increasing** **:** Miners' selling power is increasing - **Bearish** * **Decreasing** : Miners' selling power is decreasing - **Bullish** ## About Miners' Outflow to the exchange #### Moving to the exchanges for possible selling - Bearish Moving their coins to the exchanges includes the purposes of selling to cover the cost or to prepare for possible sell. Miner's selling actions include the immediate need to cover the cost or to gain excess gains by selling at the price they consider to be over-valued. Both cases are correlated to sell action which naturally lead to interpret this reason to the price drop which indicates a bearish sign. ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Miner to Exchange](/api-reference/btc-inter-entity-flows/miner-to-exchange) # Miners' Position Index (MPI) Source: https://docs.cryptoquant.com/data-guide/miner/miners-position-index Miners' Position Index (MPI) is defined as the ratio of the number of all miners' outflows in USD divided by 365 days moving average of it. ## What is Miners' Position Index (MPI)? The Miners' Position Index (MPI) metric is a valuable indicator that evaluates the relationship between the amount of Bitcoin (BTC) mined in the past year and its corresponding moving average over the same period. During bear markets, an increase in the MPI signals a notable trend – miners potentially capitulating and selling their mined Bitcoin at a loss. This phenomenon often occurs at market peaks, serving as a precursor to impending price corrections. Miners, recognizing the need to manage costs and optimize resources, may be prompted to move larger-than-usual amounts of their mined bitcoins during such market conditions. In bull markets, however, the MPI can reveal a different narrative. As market sentiment shifts, miners may choose to combine rewards from block transactions strategically, aligning with the prevailing bullish trend. This metric provides a nuanced perspective on miners' behavior, helping market participants gauge the ebb and flow of mined bitcoins against market dynamics, transactional costs, and the overall health of the network. This indicator is inspired by Puell Multiple. $$ \text{MPI} = \text{365 days moving z-score (Capitulation Index)} $$ $$ \text{Capitulation Index} = \frac{\text{Total Miner Outflows in USD}}{\text{365 days moving average (Total Miner Outflows in USD)}} $$ ## How to interpret Miners' Position Index (MPI) ### By value itself * **High**: Miners are sending their coins more than usual- **Bearish** * **Low:** Miners are sending their coins less than usual - **Bullish** ### By Examining Trend * **Increasing:** Miners are being more involved in selling and increasing their sell - **Bearish** * **Decreasing**: Miners are being less involved in selling and decreasing their sell - **Bullish** Unlike Miners outflow, Bitcoin Miners' Position Index (MPI) takes the average behavior of miners into account by using 365 days moving average. Also, MPI explains the relative miner's liquidation behavior compared to the historical average, assuming that most of the outflows from miners are heading to exchanges for selling. Assuming that miners are good at selling their positions at the right price and time as professional traders, MPI is a good indicator for **timing exit points (selling)** by duplicating their behaviors. This also helps to view miners' profitability along with **Puell Multiple**. [Puell Multiple](/data-guide/network/puell-multiple) ## When to use Miners' Position Index (MPI) ### Spotting Exit Points for Selling: Bitcoin Miners' Position Index (MPI) Given the interpretation that Bitcoin Miners' Position Index (MPI) helps us to spot selling points, we can benefit from the events where the large MPI values occur. In this use case, we utilize one of the well-known market technical indicators called [Bollinger-band](https://en.wikipedia.org/wiki/Bollinger_Bands) to detect abnormal MPI values. The below chart illustrates detected spots to exit from the market, selling. ![CryptoQuant: Miners' Position Index](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MCvXIaXsyQ9Y_KXE5Gd.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=cbaa378d7745fa8d2ad50e6ca37c51a7) ## Link to Our Data and Dashboard * [Miners' Position Index in CryptoQuant Live Chart](https://cryptoquant.com/asset/btc/chart/flow-indicator/miners-position-index-mpi?window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=line) * [Bitcoin Miner Dashboard](https://cryptoquant.com/analytics/dashboard/63064a8d77d099261f5ddfb8) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Miners' Position Index (MPI)](/api-reference/btc-flow-indicator/miners-position-index-mpi) # Network Indicators Source: https://docs.cryptoquant.com/data-guide/network Network valuation indicators — NVT Ratio, NVT Golden Cross, Puell Multiple, Stock-to-Flow, and NVM Ratio — that value a blockchain against its on-chain activity. * [NVT Ratio](/data-guide/network/nvt-ratio): Defined as the ratio of market capitalization divided by transacted volume in the specified window. * [NVT Golden Cross](/data-guide/network/nvt-golden-cross): NVT Golden Cross (NVT\_GC) is a Bollinger-band-like signaling indicator based on NVT, defined as the following equation * [Puell Multiple](/data-guide/network/puell-multiple): Puell Multiple is defined as the ratio of the daily value of the issued coin in USD divided by 365 days moving average of the daily value of issued coins in USD. * [Stock to Flow Ratio](/data-guide/network/stock-to-flow-ratio): Stock to Flow Ratio is defined as a ratio of currently circulating coins divided by newly supplied coins. * [Stock to Flow Reversion](/data-guide/network/stock-to-flow-reversion): Stock to Flow (SF) Reversion is defined as a ratio of the price of BTC divided by SF ratio. * [NVM Ratio](/data-guide/network/nvm-ratio): Network Value to Metcalfe Ratio (NVM Ratio) is defined as the ratio of the log of market capitalization divided by the log of the square of daily active addresses in the specified window. # NVM Ratio Source: https://docs.cryptoquant.com/data-guide/network/nvm-ratio Network Value to Metcalfe Ratio (NVM Ratio) is defined as the ratio of the log of market capitalization divided by the log of the square of daily active addresses in the specified window. ## What is NVM Ratio? Network Value to Metcalfe Ratio (NVM Ratio) is defined as the ratio of the log of market capitalization divided by the log of the square of daily active addresses in the specified window. $$ \text{NVM Ratio} = \frac{\ln (\text{Market Cap})}{\ln (\text{Daily Active Addresses}^2)} $$ ## How to interpret NVM Ratio NVM Ratio evaluates the fair value of the blockchain network by applying [Metcalfe's Law](https://en.wikipedia.org/wiki/Metcalfe%27s_law) where the law claims that the value of the network is proportional to the square of the number of active users. * **High values : Overvalued network**\ \ The network is **overvalued** by the interpretation where the price is too high compared to the low number of active addresses * **Low values** **: Undervalued network**\ \ The network is **undervalued** by the interpretation where the price is too low compared to the high number of active addresses ## When to use NVM Ratio ### RSI based market spotting [Relative Strength Index (RSI)](https://www.investopedia.com/terms/r/rsi.asp) is one of the famous technical indicators measuring the relative strength of an upward trend and downward trend. We apply RSI to NVM for spotting the market's local tops and bottoms by thresholding. As you can see in the figure below, RSI of NVM quite correctly spots local tops and bottoms in a robust way. ![](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MELypGFxV-bRKKXrf4a.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=c1491a229b14ae2fabf982c0789f9638) The settings for this analysis are the followings: * We use a 7-day window for NVM for smoothing. * We use a 14-day window for RSI formulation. * We use 70% and 30% thresholds for the upper and lower thresholding. ## Link to Our Data * [NVM in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/470?window=day) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [NVM](/api-reference/btc-network-indicator/nvm) # NVT Golden Cross Source: https://docs.cryptoquant.com/data-guide/network/nvt-golden-cross NVT Golden Cross (NVT GC) is a Bollinger-band-like signaling indicator based on NVT, defined as the following equation ## What is NVT Golden Cross? NVT Golden Cross (NVT\_GC) is a [Bollinger-band](https://en.wikipedia.org/wiki/Bollinger_Bands)-like signaling indicator based on NVT, defined as the following equation. $$ \text{NVT} = \frac{\text{Market Cap}}{\text{Transaction Volume}} \\ \text{NVT\_diff} = \text{NVT (10 days moving average)} - \text{NVT (30 days moving average)} \\ \text{NVT\_GC} = \frac{\text{NVT\_diff}}{\text{NVT\_diff (300 days moving standard deviation)}} $$ ## How to interpret NVT Golden Cross NVT Golden Cross targets to generate short or long signals by comparing the short-term trend of NVT and the long-term trend of NVT. This **leading indicator** predicts the appearances of local tops and bottoms, which helps traders to take their short or long positions. ### By value itself [#interpretation](#interpretation) **Predicting Local Tops and Bottoms** * **Values over ‘2.2’** : **Short Signal** If the short-term trend is way greater than the long-term trend is, the network can be interpreted as overpriced and will soon revert to mean value, meaning **short signal**. * **Values under ‘-1.6’** : **Long Signal** If the long-term trend is way greater than the short-term trend is, the network can be interpreted as under-priced and will soon revert to mean value, meaning **long signal**. ### By examining trend [#use-case](#use-case) It shows **the comparative trend difference between long-term and short-term.** * **Increasing trend** : Marketcap(Price) is **heating up** compared to transaction volume * **Decreasing** **trend** : Marketcap(Price) is **cooling down** compared to transaction volume ![](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MCvQBa12lvqtnkiFzlH.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=820d324d20e19f32d40db2fdb9f226b8) ## Link to Our Data * [NVT Golden Cross in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/201?window=day) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [NVT Golden Cross](/api-reference/btc-network-indicator/nvt-golden-cross) # NVT Ratio Source: https://docs.cryptoquant.com/data-guide/network/nvt-ratio Defined as the ratio of market capitalization divided by transacted volume in the specified window. ## What is NVT Ratio? There are numerous indicators that traders and investors use to make informed decisions. One such indicator is the Network Value to Transactions (NVT) Ratio. In this guide, we'll delve into the NVT Ratio, understand what it signifies, and explore its applications. $$ \text{NVT Ratio} = \frac{\text{Market Cap}}{\text{Transaction Volume in USD}} $$ ### **What is NVT Ratio?** ![Bitcoin: NVT Ratio – Source: CryptoQuant](https://images.surferseo.art/6eb00c90-1d34-4e17-9ea1-e052113407ba.png) Network Value to Transactions Ratio (NVT Ratio) is defined as the ratio of market capitalization divided by transacted volume in the specified window. ### **NVT Ratio: A Conceptual Overview** ![Bitcoin: NVT Ratio, 1D – Source: CryptoQuant](https://images.surferseo.art/1ca5d700-39c6-4f77-ac9d-c135ab6b5469.png) NVT can be seen as analogous to the PE Ratio (Price-Earnings Ratio) but applied in the crypto world. It is a measure of how investors perceive the cryptocurrency's value in relation to its utility, specifically in terms of transaction volume. The NVT Ratio helps us answer the fundamental question: Is the network's market cap justified by its transaction activity? If the value is too high, it means the network is overvalued compared to the low ability to transact coins in terms of volume, implying the possible removal of a coming price bubble. This interpretation is based on the effect of [mean reversion](https://en.wikipedia.org/wiki/Mean_reversion_\(finance\)).​ ### **Interpreting** Network Value to Transaction **Ratio** Understanding the interpretation of the NVT Ratio is crucial. This indicator measures whether the blockchain network is **overvalued or not**. Here's how to decipher this essential indicator: #### *High NVT Ratio* **High Overvalued** Network Worth = **Bearish.** A high NVT Ratio suggests that the cryptocurrency network is being priced at a premium. This often coincides with periods of market exuberance, where market cap growth outpaces transaction volume. Such periods have historically been associated with market tops and potential overvaluation. #### *Low NVT Ratio* **Low Undervalued** Network Worth = **Bullish.** ![Undervalued Representation of NVT Ratio – Source: CryptoQuant](https://images.surferseo.art/28d83bc5-b55f-4430-acd1-c4bf80556c35.png) Conversely, a low Network Value to Transactions Ratio indicates that the network is priced at a discount. This suggests that transaction volume and network utilization outpace market cap growth. Historically, this has been linked to accumulation opportunities and bullish trends. #### *Stable NVT Ratio* A consistent Network Value to Transactions Ratio signifies a balance between market cap growth and transaction volume. It often indicates that the market trend is sustainable and may persist. ### **Evolving Interpretation over Time** The interpretation of the NVT Ratio evolves as the cryptocurrency market matures and technology advances. Factors like the Lightning Network, shifting narratives, and rising coin prices can influence how we understand the Network Value to Transactions Ratio. Therefore, it's crucial to consider historical context and analyze trends rather than fixate on absolute values. ### **Enhancing NVT Ratio Analysis** To capture broader trends and respond to changing market dynamics, it is recommended to apply a moving average to the NVT Ratio. This offers a more comprehensive understanding of the indicator. ### **Variations of NVT Ratios** In addition to the standard Network Value to Transaction Ratio, there are variations that provide further insights: #### *NVT Signal (NVTS)* This version uses a 90-day moving average of daily transaction volume in the denominator instead of raw daily transaction volume, offering a more responsive indicator. #### *Velocity* Velocity measures how quickly units circulate in the network. It is calculated by dividing on-chain transaction volume by market cap, effectively being the inverse of the NVT Ratio. ## Link to Our Data * [NVT Ratio in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/198?window=day) * [NVT Ratio in CryptoQuant Data API docs](https://cryptoquant.com/docs/#operation/getRiskIndicatorNVT) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [NVT](/api-reference/btc-network-indicator/nvt) * **XRP** — [NVT](/api-reference/xrp-network-indicator/nvt) # Puell Multiple Source: https://docs.cryptoquant.com/data-guide/network/puell-multiple Puell Multiple is defined as the ratio of the daily value of the issued coin in USD divided by 365 days moving average of the daily value of issued coins in USD. ## What is Puell Multiple? Puell Multiple is defined as the ratio of the daily value of the issued coin in USD divided by 365 days moving average of the daily value of issued coins in USD. $$ \text{Puell Multiple} = \frac{\text{Mining Revenue in USD}}{\text{365 days moving average (Mining Revenue in USD)}} $$ ## How to interpret Puell Multiple Puell Multiple can be interpreted as "If all mined bitcoins were sold immediately in the market, how profitable mining pools are compared to last historical one year?" This metric explores market cycles from the global mining revenue perspective. Miners are the only entity that requires constant cost such as running electricity. Thus, miners' behaviors are always linked to price to certain degree. Puell Multiple compares 365 days average estimated revenue with short-term revenue of miners. ![Puell Multiple: CryptoQuant](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MCvR389AAq94fBXwq0z.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=3fd4c905f83e254beb39f1b874d5bcb7) ### By Value Itself [#interpretation](#interpretation) **Predicting Price Tops and Bottoms with the Puell Multiple** * **Values over ‘4’**: **Short Signal** If Puell multiple rises, it indicates that price=Miner's revenue is increasing significantly compared to the cost they put in. In this phase, bitcoin soared to point where Miner's revenue far exceeds the cost they put in. If we put regard bitcoin's true value with miners' cost (POW) and hashrate, this could indicate that bitcoin is overpriced. In other words, this could indicate that price is overvalued along with the increasing miner's motive to sell. ![Bitcoin Puell Multiple Short Signal](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/VeLGYZCEpE5WSKeIqocB.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=d53af66a71a4d7f6659f820450d00bc7) * **Values under ‘0.5’**: **Long Signal** If the Puell multiple decreases, it indicates that price=Miner's revenue is decreasing significantly compared to the cost they put in. In this phase, bitcoin can become extremely volatile, and prices plunge to the point where miners can't handle the fixed costs of electricity from their mining hardware, making some miners stop their mining action. In other words, this could indicate that the price is undervalued along with the increasing miner's motive to hold their bitcoin reserve. ![Bitcoin Puell Multiple Long Signal](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/fNGVkx2ie34QX2539SzA.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=d447663f8ed94fd5cee122d87b639128) ### By Examining Trend [#use-case](#use-case) It shows miners' short-term revenues relative to long-term profits. * **Increasing trend**: Marketcap (Price) is **heating up** compared to miners' cost * **Decreasing** **trend**: Marketcap (Price) is **cooling down** compared to miners' cost ### **Decoding Puell Multiple Framework: Market Cycles** Let's streamline its interpretation: #### **High Puell Multiple: Caution Flag** * **Indicator:** Potential market top. * **Implication:** May signal overvaluation as miners sell bitcoins at higher prices. #### **Low Puell Multiple: Buying Window** * **Indicator:** Potential market bottom. * **Implication:** Opportunity for accumulation as Bitcoin miners sell at relatively lower prices. #### **Halving Events: Puell Dynamics** * **Pre-Halving:** Expect highs as supply anticipation rises. * **Post-Halving:** Reflects shifts in miner behavior and market response. #### **Sentiment Gauge: Rapid Insights** * **Indicator:** Shifts in miner sentiment. * **Implication:** Early indicators of potential market trends. For the strategic Bitcoin investor, combining Puell Multiple insights with other indicators is key for a nuanced understanding of the dynamic cryptocurrency landscape. As you navigate Bitcoin's economy, Puell Multiple stands as a concise guide, unraveling hidden narratives within miner activities and market sentiments—a must for strategic Bitcoin investors. ## Link to Our Data * [Puell Multiple in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/393?window=day) * [Puell Multiple in CryptoQuant Data API Docs](https://cryptoquant.com/docs/#operation/getPuellIndex) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Puell Multiple](/api-reference/btc-network-indicator/puell-multiple) # Stock to Flow Ratio Source: https://docs.cryptoquant.com/data-guide/network/stock-to-flow-ratio Stock to Flow Ratio is defined as a ratio of currently circulating coins divided by newly supplied coins. ## What is Stock to Flow Ratio? Stock to Flow Ratio is defined as a ratio of currently circulating coins divided by newly supplied coins. $$ \text{SF Ratio} = \frac{\text{Currently circulating coins}}{\text{Newly supplied coins}} $$ ## How to interpret Stock to Flow Ratio Stock to Flow Ratio assumes that the scarcity of the coin drives the price of the coin. The Stock to Flow (S2F) Model, is a key metric introduced by the pseudonymous [Dutch institutional investor](https://100trillionusd.github.io/) who operates under the Twitter account “[PlanB](https://twitter.com/100trillionUSD)”. This ratio serves as a crucial tool for assessing market dynamics. When the supply of newly minted coins diminishes, the Stock to Flow Ratio experiences an increase. Similarly, if the number of circulating coins rises, the Stock to Flow Ratio also shows an upward trend. By analyzing the Stock to Flow Ratio chart, stakeholders can discern shifts in the market regime, providing valuable insights into potential Bitcoin price movements, economic factors and market conditions. Put simply: -If Newly supplied coins decrease, Stock to Flow Ratio rises. -If circulating coins rises, Stock to Flow Ratio rises. ## When to use Stock to Flow Ratio ### Statistical Analysis on Stock to Flow Ratio The original authors claim that the log of Stock to Flow Ratio is in a linear relationship with the log of the price. We reproduce the results of what they claim and as a result, shown in the figure below, Stock to Flow Ratio and price are in a linear relationship (not perfectly but in some sense) with significant statistics (p-value under 0.01, R-square over 90%). ![Stock to Flow Ratio Statistical Analysis](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MEMVn5EK4rV32yIe6pY.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=5ecf213ba4336fc90fc6b189f8447459) Following the above linear statistics (trend and intercept), we can plot how closely they are related in a time-series manner. With this graph, we can recognize that the current price is in what regime recently. ![Regression model of SF ratio to the price](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MEMRI4uyHpaECUtOyuD.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=cbaa91d2c4acedf3fe35a632b3fbe502) ## Why is the Bitcoin Stock to Flow Ratio Important? ![Bitcoin: Stock-to-Flow Ratio – Source CryptoQuant](https://images.surferseo.art/9fa70a79-a0e5-42b9-b7fc-62a5e1b81788.png) The Bitcoin Stock to Flow Ratio, often employed in the stock to flow model, stands as a crucial metric for evaluating the scarcity and potential future value of Bitcoin. Here's why it holds paramount importance in understanding Bitcoin's market dynamics: ### Bitcoin's Scarcity and Maximum Supply As a finite resource, Bitcoin's total supply is capped at 21 million coins, reinforcing its scarcity. The Stock to Flow model quantifies this scarcity by comparing the current stock (existing supply) to the flow (newly mined coins). A higher ratio underscores Bitcoin's rarity, aligning with its reputation as "digital gold." ### Predicting Bitcoin's Price The Stock to Flow Ratio has proven to be a reliable indicator for predicting Bitcoin's price movements. By historically correlating scarcity with value, this metric aids in generating BTC price predictions. Investors and analysts often use it as a tool to anticipate potential market trends and make informed decisions. Analysts and enthusiasts frequently leverage the Stock to Flow Ratio to formulate Bitcoin price predictions. The model suggests that the decreasing rate of new Bitcoin issuance over time will drive up its value, potentially leading to higher market prices. This predictive aspect enhances its significance for traders and investors seeking insights into future market trends. ### Comparative Analysis The Bitcoin Stock to Flow Ratio allows for comparative analysis not only within the cryptocurrency space but also against traditional assets. Its application extends beyond Bitcoin, serving as a yardstick to measure scarcity and value in various markets. This comparative approach offers a broader perspective on Bitcoin's unique position in the financial landscape. ## **Factors That Affect the Stock to Flow Model** Several factors influence the Stock to Flow (S/F) Ratio of Bitcoin, impacting its scarcity and, consequently, its potential market value. Here are key factors to consider: **Bitcoin Halving Events:** Bitcoin undergoes a halving event approximately every four years, this is an event where the reward for mining new blocks is halved, meaning miners receive 50% fewer bitcoins for verifying transactions. These events play a crucial role in diminishing the flow component of the S/F ratio, as Bitcoin's scarcity increases. **Market Demand:** The demand for Bitcoin is a significant driver. Increased demand, often fueled by growing institutional interest or macroeconomic uncertainties, can influence the price of bitcoin, and, consequently, the overall stock to flow dynamics. **Technological Developments:** Changes in the underlying technology of Bitcoin, such as upgrades or scalability solutions, can impact its supply dynamics. Technological advancements may influence how transactions are verified and how new bitcoins are issued. **Regulatory Landscape:** Regulatory developments and legal clarity around Bitcoin can affect market sentiment. Clear regulations may attract more institutional investors, affecting both demand and the perception of Bitcoin's relative scarcity. ## End Notes In essence, the Stock to Flow Ratio serves as a fundamental metric, encapsulating Bitcoin's intrinsic characteristics and influencing predictions about its future price movements. As a key element in the stock to flow model, it continues to play a pivotal role in shaping discussions around Bitcoin's economic model and its broader implications for the cryptocurrency market. * [Stock to Flow in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/467?window=day) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Stock to Flow](/api-reference/btc-network-indicator/stock-to-flow) # Stock to Flow Reversion Source: https://docs.cryptoquant.com/data-guide/network/stock-to-flow-reversion Stock to Flow (SF) Reversion is defined as a ratio of the price of BTC divided by SF ratio. ## What is Stock to Flow Reversion? Stock to Flow (SF) Reversion is defined as a ratio of the price of BTC divided by SF ratio. $$ \text{SF Reversion} = \frac{\text{Price of BTC}}{\text{SF Ratio}} $$ ## How to interpret Stock to Flow Reversion SF reversion is an indicator that measures the relative difference between the market price and SF ratio. SF ratio so far correctly estimates the price trend, which means the price deviation from SF ratio can be an opportunity to bet. If SF reversion is too high, the market price has deviated far above its SF-model value and would likely be corrected soon, meaning a bearish moment. ## When to use Stock to Flow Reversion ### Predicting market tops and bottoms We first build a linear regression model of SF reversion to the price to align two variables. After aligning both in a single graph shown below, we can clearly see the deviations of SF reversion to the price and those points clearly indicate bullish (green boxes) and bearish (red boxes) regimes respectively. ![](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MEMdl0bCFOw95sAzcYk.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=0a7007cca2cf6effbdfec30e45aa9ae7) ## Link to Our Data * [Stock to Flow Reversion in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/468?window=day) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Stock to Flow](/api-reference/btc-network-indicator/stock-to-flow) # Stablecoin Exchange Flows/Indicators Source: https://docs.cryptoquant.com/data-guide/stablecoin Entry into Stablecoin data/indicators | Data/Indicator | Definition | Interpretation | | - | - | - | | [Stablecoin Network Data](/data-guide/stablecoin/stablecoin-network-data) | -Type of cryptocurrency that is pegged to a fiat currency -How stablecoin is issued | -Stablecoin with treasury account-Stablecoin without treasury account | | [Stablecoin Exchange In/Outflow & Netflow](/data-guide/stablecoin/stablecoin-exchange-in-outflow-and-netflow) | Amount of Stablecoin deposited/withdrawn into/from the exchange wallets. |
  • Increase of inflow - Mostly a **Bullish** sign
  • Increase of outflow - Mostly a **Bearish** sign
| | [Stablecoin Exchange Reserve](/data-guide/stablecoin/stablecoins-exchange-reserve) | The amount of the stablecoins held in the exchange addresses |
  • HighHigh Buying pressure
  • LowLow selling pressure
  • Increasing trendIncreasing potential Buying power -**Bullish**
  • Decreasing trendDecreasing scarcity - **Bearish**
| | [Stablecoin Exchange Addresses Count](/data-guide/stablecoin/stablecoin-exchange-addresses-count) | The number of unique addresses making inflow/outflow transactions of exchanges |
  • HighLarge number of investors
  • LowSmall number of investors
  • Increasing trendExpanding interest and activeness
  • Decreasing trendDiminishing interest and activeness
| | [Stablecoin Exchange Transactions Count](/data-guide/stablecoin/stablecoin-exchange-transactions-count) | The total number of deposits/withdrawals transactions of the exchange |
  • HighLarge number of transactions
  • LowSmall number of transactions
  • Increasing trendExpanding interest and activeness
  • Decreasing trendDiminishing interest and activeness
| | [Stablecoin Supply Ratio (SSR)](/data-guide/stablecoin/stablecoin-supply-ratio) | Defined as a ratio of the Market Cap of BTC divided by the Market Cap of all Stablecoins |
  • **Increasing trend**Slowing down status of stablecoin's buying power - **Bearish or sideways sentiment**
  • **Decreasing** **trend**Rising status of stablecoin's buying power - **Bullish**
| ## How to look at indicators This section identifies the lookout point for individual indicators. These indicators could be divided by their identity and their usefulness in trading. Each indicator utilized each feature of stablecoin, and put together, they cover multiple aspects and capture movements in stablecoin relatively precisely. If you want to make use stablecoin feature by figuring out ### 1) How many stablecoins came out from or into the exchange Checking the flow into the exchange is a great way to keep track of stablecoins that could be a medium to buy cryptocurrencies or liquidity of the derivative market [Stablecoin Exchange In/Outflow & Netflow](/data-guide/stablecoin/stablecoin-exchange-in-outflow-and-netflow) ### 2) How many stablecoins are in the exchange Checking the Stablecoin Reserve in exchange helps to measure buying power in the exchange. [Stablecoin Exchange Reserve](/data-guide/stablecoin/stablecoins-exchange-reserve) ### 3) How many stablecoin addresses or transactions are active or being made through the exchanges Checking the active address count or transactions is a great way to determine how many addresses are participating in the movement in the price and find out the sentiment behind it. [Stablecoin Exchange Transactions Count](/data-guide/stablecoin/stablecoin-exchange-transactions-count) [Stablecoin Exchange Addresses Count](/data-guide/stablecoin/stablecoin-exchange-addresses-count) ### 4) Figuring out how buying power or liquidity in the market To figure out the power balance between the BTC and Stablecoin by market cap [Stablecoin Supply Ratio (SSR)](/data-guide/stablecoin/stablecoin-supply-ratio) #### It is wise to look at each indicator according to the abovementioned number. ### Note on Stablecoin Data Coverage CryptoQuant offers on-chain data for stablecoins on ERC20 for Charts, Pro-Charts, Alerts, and API. The market cap of the stablecoins in all chains is available in the dashboard. 👉 [Click to view the dashboard](https://cryptoquant.com/analytics/dashboard/636d36c908ec7d0bd8484912). # Stablecoin Exchange Addresses Count Source: https://docs.cryptoquant.com/data-guide/stablecoin/stablecoin-exchange-addresses-count The number of unique addresses making inflow/outflow transactions of exchanges. ## What is Stablecoin Exchange Addresses Count? The number of unique addresses making inflow/outflow transactions of exchanges. | Metrics | Description | | - | - | | Addresses Count Inflow | The number of the token addresses making inflow transactions to the exchange. | | Addresses Count Outflow | The number of the token addresses making outflow transactions from the exchange. | ## How to interpret Stablecoin Exchange Addresses Count Considering that it costs fees to send from wallets to different number of wallets, active Stablecoin Exchange Address Count indicates the **closest meaning to the number of investors** that are involved in exchange related transactions. This naturally leads to possible interpretation of correlating exchange address count to the level of attention of trading investors. ### By value itself [#interpretation](#interpretation) It shows whether **few or large numbers of investors** are involved in transaction. * **High** : **Large number of investors** are accountable for [Stablecoin Exchange Flows](/data-guide/stablecoin/stablecoin-exchange-in-outflow-and-netflow) * **Low** : **Small number of investors** are accountable for [Stablecoin Exchange Flows](/data-guide/stablecoin/stablecoin-exchange-in-outflow-and-netflow) ### By examining trend [#use-case](#use-case) It shows the **level of Exchange Activeness & Volatility** * **Increasing trend** : **expanding interest and activeness** More people are participating in stablecoin exchange flows indicating expanding interest and activeness of exchange trading leading to possible volatility * **Decreasing trend** : **diminishing interest and activeness** Less people are participating in stablecoin exchange flows indicating diminishing interest and activeness of exchange trading leading to possible decreasing volatility ## Link to Our Data * [Stablecoin Exchange Addresses Count in CryptoQuant Live Chart](https://cryptoquant.com/asset/stablecoin/chart/addresses) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **Stablecoin** — [Addresses Count](/api-reference/stablecoin-exchange-flows/addresses-count) # Stablecoin Exchange In/Outflow & Netflow Source: https://docs.cryptoquant.com/data-guide/stablecoin/stablecoin-exchange-in-outflow-and-netflow Stablecoin Exchange Inflow is defined as an amount of Stablecoin deposited into the exchange wallets. Exchange Outflow is defined as an amount of Stablecoin withdrawal from the exchange wallets. ## What is Stablecoin Exchange In/Outflow & Netflow? **Stablecoin Exchange Inflow** is defined as an amount of Stablecoin deposited into the exchange wallets. | Metrics | Description | | - | - | | Inflow Total | The total amount of Stablecoin transferred to the exchange. | | Inflow Mean | The mean amount of Stablecoin per transaction sent to the exchange. | | Inflow Top10 | The total Stablecoin amount of the top 10 transactions inflow to the exchange. | | Inflow Mean(MA7) | The 7 days moving average of mean Stablecoin inflow to the exchange. | **Stablecoin Exchange Outflow** is defined as an amount of Stablecoin withdrawal from the exchange wallets. | Metrics | Description | | - | - | | Outflow Total | The total amount of Stablecoin transferred from the exchange. | | Outflow Mean | The mean amount of Stablecoin per transaction sent from the exchange. | | Outflow Top10 | The total Stablecoin amount of the top 10 transactions outflow from the exchange. | | Outflow Mean(MA7) | The 7 days moving average of mean Stablecoin outflow from the exchange. | **Stablecoin Exchange Netflow** is the difference between Stablecoin flowing into and out of the exchange. (Inflow - Outflow = Netflow) The mean value is the In/Outflow Total divided by the Transactions Count In/Outflow. ## Interpretation [#interpretation](#interpretation) ### By value itself [#interpretation](#interpretation) * **Increase of inflow** to exchanges is mostly a **Bullish** sign * **Increase of outflow** from exchanges is mostly a **Bearish** sign Considering the fact that moving coins costs fees, wallets outside from exchange send their coins to the exchanges for two possible reasons. #### 1) To buy coins - Bullish In the case of inflow to spot exchange, it is highly likely that investors are sending Stablecoins for buying coins. This reason of action mostly leads to the price rise which indicates a bullish sign. #### 2) To trade in derivatives market - volatility risk The purpose for sending coins to derivative market wallets indicates that more trades will be happening on the derivative market. This could possibly lead to increased volatility risk as a result of increased trading activity, investors looking to take profits, and/or to rebalance to de-risk their investment portfolios. This type of action has difficulty in deciding the effect on price since coins in the derivative market could be used to open both long/short positions. Instead, it should be interpreted as increased volatility risk. ## Link to Our Data * [Stablecoin Exchange In/Outflow & Netflow in CryptoQuant Live Chart](https://cryptoquant.com/asset/stablecoin/chart/exchange-flows) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **Stablecoin** — [Netflow](/api-reference/stablecoin-exchange-flows/netflow) · [Inflow](/api-reference/stablecoin-exchange-flows/inflow) · [Outflow](/api-reference/stablecoin-exchange-flows/outflow) # Stablecoin Exchange Transactions Count Source: https://docs.cryptoquant.com/data-guide/stablecoin/stablecoin-exchange-transactions-count The total number of deposits/withdrawals transactions of the exchange. ## What is Stablecoin Exchange Transactions Count? The total number of deposits/withdrawals transactions of the exchange. | Metrics | Description | | - | - | | Transactions Count Inflow | The total number of deposits to the exchange. | | Transactions Count Outflow | The total number of withdrawals from the exchange. | ## How to interpret Stablecoin Exchange Transactions Count Considering that it costs fees make multiple transactions, active exchange transaction count indicates the **closest meaning to the number of investors** that are involved in network transaction. This naturally leads to possible interpretation of correlating exchange transactions count to the level of attention of trading investors. ### By value itself [#interpretation](#interpretation) It shows whether **few or large numbers of transactions** are involved in netflows. * **High** : **Large** number of transactions are accountable for [Stablecoin Exchange Flows](/data-guide/stablecoin/stablecoin-exchange-in-outflow-and-netflow) * **Low** : **Small** number of transactions are accountable for [Stablecoin Exchange Flows](/data-guide/stablecoin/stablecoin-exchange-in-outflow-and-netflow) ### By examining trend [#use-case](#use-case) It shows the **level of Exchange Activeness & Volatility** * **Increasing trend** : **Expanding interest and activeness** More people are participating in stablecoin exchange flows indicating expanding interest and activeness of exchange trading leading to possible volatility * **Decreasing** **trend** : **Diminishing interest and activeness** Less people are participating in stablecoin exchange flows indicating diminishing interest and activeness of exchange trading leading to possible decreasing volatility ## Link to Our Data * [Stablecoin Exchange Transactions Count in CryptoQuant Live Chart](https://cryptoquant.com/asset/stablecoin/chart/transactions) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **Stablecoin** — [Transactions Count](/api-reference/stablecoin-exchange-flows/transactions-count) # Stablecoin Network Data Source: https://docs.cryptoquant.com/data-guide/stablecoin/stablecoin-network-data Details about stablecoin issuing mechanism ## Stablecoin Issuing Mechanism Each individual Stablecoin is created by an issuing company and each of these companies operates with a different issue mechanism. There are many of these but the two most common are as follows. **Example 1** ![](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MZq88MSKnr8QLm0ezZJ.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=c4ccaeacfca75f2e84581e7cc745f883) Before providing clients with the granting address, the issuing company holds a treasury address. Through the contract, the tokens are minted and held in the treasury address. Once the client sends fiat currency, the clients' tokens are moved from the treasury address to the client address and the tokens are listed as being issued. Conversely, when redeeming tokens for fiat, the tokens are sent to the treasury address and redeemed. This won't be reflected in the supply unless these tokens are burned using a contract by the issuing company. The circulating supply is calculated as tokens that have been issued to clients, ignoring the supply held in the issuing company wallets. **Example 2** ![](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/-MZq8KYOvG3TDe_cco_0.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=c6b8ab0dc8bf44b5029d61a03fcbd22f) In this method, there is no separate treasury address. After confirming the deposit of fiat, tokens are minted from the contract address and delivered directly to the client's address. Minting and issuance occur simultaneously. When clients redeem tokens, the burn and redemption also are simultaneous. This means that with this method, total supply and circulating supply will be the same. There are various methods for Stablecoin issuance, and we calculated supply and locate significant transactions. based upon these types of factors. In the future, mint/issue/burn/redeem will be added to our available metrics and will be defined as listed below. | Term | Definition | | - | - | | Mint | Mint is a creation of new tokens that add to the supply. When tokens are minted, the total supply will increase. | | Issue | The Issue is when tokens are delivered to clients after the deposit of fiat has been confirmed. When tokens are issued, the circulating supply will increase. | | Burn | Burn is a revocation of currently existing tokens that results in a decreased supply. The opposite of Mint. | | Redeem | Redeem is an exchange of tokens for deposited fiat that results in a decrease in the circulating supply. The opposite of Issue. | ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **Stablecoin** — [Supply](/api-reference/stablecoin-network-data/supply) · [Events Count](/api-reference/stablecoin-network-data/events-count) · [Tokens Transferred](/api-reference/stablecoin-network-data/tokens-transferred) · [Addresses Count](/api-reference/stablecoin-network-data/addresses-count) # Stablecoin Supply Ratio (SSR) Source: https://docs.cryptoquant.com/data-guide/stablecoin/stablecoin-supply-ratio Stablecoin Supply Ratio (SSR) is defined as a ratio of the Market Cap of BTC divided by the Market Cap of all Stablecoins. ## What is Stablecoin Supply Ratio (SSR)? Stablecoin Supply Ratio (SSR) is defined as a ratio of the Market Cap of BTC divided by the Market Cap of all Stablecoins. In other words, the SSR is calculated as the ratio between the Bitcoin supply and the supply of stablecoins denoted in BTC. $$ \text{SSR}=\frac{\text{Market Cap of BTC }}{\text{Market Cap of stablecoins}} $$ ## How to interpret Stablecoin Supply Ratio (SSR) ![Bitcoin: Stablecoin Supply Ratio (SSR) Chart](https://images.surferseo.art/1bdef270-6f41-478d-a1cf-615680ae377c.png) In understanding Stablecoin Supply Ratio (SSR), understanding the function of a stablecoin and its assumption should be done. First, stablecoins play an important role in the cryptocurrency market as a fiat currency like USD in the regulated market. This is because fiat currencies like USD as a supplier of liquidity have a lot of regulation issues. Second, Stablecoin Supply Ratio (SSR) is easy to understand metric when there is an assumption that the market is a closed system containing only cryptocurrencies and stablecoins. The relationship between BTC and Stablecoins is like seasaw and provide valuable insight on who has more weight at the moment. ### By Value Itself This indicator shows the comparative power status between BTC and Stablecoins by comparing the market capitalization. #### **High: Low Potential Buying Pressure** High values mean Low Stablecoin supply compared to the market cap value of BTC indicating potential low buying pressure and possible price drop. #### **Low: High Potential Buying Pressure** Low values mean high Stablecoin supply compared to the market cap of BTC indicating potential buying pressure and support for possible price rise. ### By Examining Trend ![Buy and Sell Signals Dashboard for SSR. Source: CryptoQuant Verified Author - IT Tech](https://images.surferseo.art/8c1e0a28-069e-494e-8eb9-18bfe50d89e7.png) It shows the **level of Exchange Activeness and Volatility** * **Increasing trend**: Slowing down status of stablecoin's buying power - **Bearish or sideways sentiment** * **Decreasing** **trend**: Rising status of stablecoin's buying power - **Bullish** #### **Note** 1. Additional stablecoins could be minted anytime disrupting the assumption that crypto market is a closed system. However, as crypto market continues to expand, additional mint would gradually lose its impact on the model. 2. As time passes, the degree of values' meaning could differ on level. ### Practical Example Let's consider a hypothetical scenario to illustrate the Stablecoin Supply Ratio (SSR) in action: Suppose the market capitalization of Bitcoin (BTC) is $1 trillion, and the combined stablecoin market cap is $200 billion. In this case, the SSR would be calculated as follows: $$ SSR = \frac{ \text{Market Cap of BTC} }{ \text{Market Cap of Stablecoins} } = \frac{1,000,000,000,000}{200,000,000,000} =5 $$ #### Interpretation A Stablecoin Supply Ratio (SSR) of 5 indicates that the market cap of Bitcoin is five times larger than the combined market cap of all stablecoins. This scenario suggests a potential low buying pressure on stablecoins, indicating a possible price drop. Traders might interpret this as a time when Bitcoin holds a dominant position, and stablecoins are relatively less in demand. Conversely, if the SSR were, for instance, 0.2, it would signify a situation where the market capitalization of stablecoins is five times larger than that of Bitcoin. This could imply high potential buying pressure on stablecoins, supporting a possible value rise. Traders might view this as a period when stablecoins are gaining influence in the market compared to Bitcoin. By monitoring on-chain data and changes in SSR over time, traders can gain insights into the ebb and flow of buying pressures between Bitcoin and stablecoins, helping them make more informed decisions in the dynamic cryptocurrency market. ## Link to Our Data * [Stablecoin Supply Ratio in CryptoQuant Live Chart](https://cryptoquant.com/asset/btc/chart/market-indicator/stablecoin-supply-ratio-ssr?window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=line) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Stablecoin Supply Ratio](/api-reference/btc-market-indicator/stablecoin-supply-ratio) # Stablecoin Exchange Reserve Source: https://docs.cryptoquant.com/data-guide/stablecoin/stablecoins-exchange-reserve The amount of the stablecoins held in the exchange addresses. ## What is Stablecoin Exchange Reserve? The amount of stablecoin tokens held in exchange wallets for as far back as we track. Please note that the transfer generally occurs after a certain amount of time from the contract created time. ## How to interpret Stablecoin Exchange Reserve Stablecoin Exchange reserve is a collective measure of potential stablecoins that are ready to be used to buy cryptocurrencies in the market. Stablecoin Exchange Reserve is the accumulated result of [Stablecoin Exchange Flows](/data-guide/stablecoin/stablecoin-exchange-in-outflow-and-netflow) which naturally follows the indications that in/outflow has. Similar to Stablecoin Exchange NetFlow's interpretation, an increasing trend in netflow indicates the buying pressure and the decreasing trend indicates the selling pressure. However, instead of Exchange In/Outflow & Netflow indicating the specific moment or period, Stablecoin Exchange Reserve is **easy to track the result of the entire period's movements.** ### By value itself [#interpretation](#interpretation) It indicates the degree of **accumulated buying pressure** in the exchange * **High** : **High Buying Pressure** A large number of stablecoins are staying in the exchange to be traded indicating high buying pressure * **Low** : **Low Buying Pressure** A Small number of stablecoin are staying in the exchange to be traded indicating low buying pressure ### By examining trend [#indicating-selling-or-buying-pressure](#indicating-selling-or-buying-pressure) It shows the **changing buying power status** * **Increasing trend**: **Increasing potential Buying power -Bullish** More stablecoins are available in the exchange indicating the increasing buying power that are ready to be used to trade which supports bullish movement * **Decreasing trend**: **Decreasing Buying power - Bearish** Fewer stablecoins are available in the exchange indicating the decreasing buying power that is ready to be used to trade which supports bearish movement ## Link to Our Data * [Stablecoin Exchange Reserve in CryptoQuant Live Chart](https://cryptoquant.com/asset/stablecoin/chart/exchange-flows/exchange-reserve?exchange=all_exchange\&window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=line) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **Stablecoin** — [Reserve](/api-reference/stablecoin-exchange-flows/reserve) # Stablecoins Ratio Source: https://docs.cryptoquant.com/data-guide/stablecoin/stablecoins-ratio BTC reserve divided by all stablecoins reserve held by an exchange. This usually indicates potential sell pressure. ## What is Stablecoins Ratio? BTC reserve divided by the sum of all stablecoins reserve held by an exchange. $$ \text{Stablecoins Ratio} = \frac{\text{BTC Reserve}} {\text{All Stablecoins Reserve}}\\\ $$ $$ \text{Stablecoins Ratio(USD)} = \frac{\text{ BTC Reserve in USD}} {\text{All Stablecoins Reserve}} $$ ## How to interpret Stablecoins Ratio This usually indicates potential sell pressure. ## Link to Our Data * [Stablecoins Ratio in CryptoQuant Live Chart](https://cryptoquant.com/asset/btc/chart/flow-indicator/exchange-stablecoins-ratio?exchange=all_exchange\&window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=line) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Stablecoins Ratio](/api-reference/btc-flow-indicator/stablecoins-ratio) # UTxO Data/Indicators Source: https://docs.cryptoquant.com/data-guide/utxo Entry into UTxO data/indicators | Data/Indicator | Definition | Interpretation | | - | - | - | | [What is a UTxO?](https://userguide.cryptoquant.com/what-is-cryptoquant/background-knowledge/what-is-a-utxo) | It stands for unspent transaction output(UTxO) | -What is UTxO-How UTxOs are created and destroyed | | [Profit and Loss (UTxO)](/data-guide/utxo/profit-and-loss-utxo) | The amount/ratio of UTxOs being in profit or loss -AmountThe number of UTxOs being in profit/Loss-Profit/Loss PercentRatio of the number of UTxOs being in |
  • Numbers of UTxOs that are in Profit[Profit amount](https://cryptoquant.com/overview/btc-network-indicator/16432?window=day)
  • Numbers of UTxOs that are in Loss[Loss Amount](https://cryptoquant.com/overview/btc-network-indicator/16433?window=day)
  • Ratio of UTxOs that are in Profit[Profit percent](https://cryptoquant.com/overview/btc-network-indicator/16434?window=day)
  • Ratio of UTxOs that are in Loss[Loss percent ](https://cryptoquant.com/overview/btc-network-indicator/16435?window=day)
| | [Coin Days Destroyed (CDD)](/data-guide/utxo/coin-days-destroyed-cdd) | The sum of products of UTxO's alive days and its value |
  • HighLong-held coins are moving in great amounts - **Bearish**
  • LowLong-held coins are moving in less amount - **Bullish**
  • IncreasingIncreasing Selling pressure - **Bearish**
  • DecreasingDecreasing selling pressure - **Bullish**
| | [Mean Coin Age (MCA)](/data-guide/utxo/mean-coin-age-mca) | The mean value of products of coin unspent transaction output (UTxO) alive days and its value |
  • Continuous riseThe total days of coins alive accumulate - **Bullish**
  • Sudden decreaseCoins that were dormant moved in mass - **Bearish**
| | [Spent Output Profit Ratio (SOPR)](/data-guide/utxo/spent-output-profit-ratio-sopr) | Spent Output Profit Ratio (SOPR) evaluates the profit ratio of the whole market participants by comparing the value of outputs at the spent time to created time | [aSOPR (Adjusted SOPR)](/data-guide/utxo/spent-output-profit-ratio-sopr/asopr-adjusted-sopr)Modified SOPR that eliminated noises[STH-SOPR](/data-guide/utxo/spent-output-profit-ratio-sopr/sth-sopr)Modified SOPR that focuses on the behavior of short-term UTxOs.[LTH-SOPR](/data-guide/utxo/spent-output-profit-ratio-sopr/lth-sopr)Modified SOPR that focuses on the behavior of long-term UTxOs. | ## Reason to look for UTxO indicators ### Best for tracking down Long term holders It is reasonable to assume that long-term holders' bags are "Smart money" and it provides valuable insight for investors to notice their movements if they start to move in anyways. What makes these indicators better is that the longer the bitcoin holder had, the more sensitive indicator is to the movement of the long-lived UTxOs. The longer-lived UTxOs move, the more change in values for these indicators enabling people who use this metric to notice the difference easily. Thus, the best way to capture these "Smart money" movements is through utilizing UTxOs. Also because UTxOs are like traceable cash with the wallet's name on it, it is also possible to easily trace the record of how long those UTxOs are held. It is best at tracking long held coins but also easy to differentiate investors by age and draw behavior indications from tracking them. ## How to look at indicators This section identifies the lookout point for individual indicators. These indicators could be divided by their identity and their usefulness in trading. Each indicator utilized each feature of UTxOs and put together they cover multiple aspects and capture movements in UTxO relatively precisely. If you want to make use UTxO's feature of by figuring out ### 1) How many UTxOs itself is in profit or not Checking the absolute number of UTxO in Profit or loss [Profit and Loss (UTxO)](/data-guide/utxo/profit-and-loss-utxo) ### 2) Focusing on figuring out the days of UTxO lived or destroyed [Sum Coin Age (SCA)](/data-guide/utxo/sum-coin-age-sca) [Coin Days Destroyed (CDD)](/data-guide/utxo/coin-days-destroyed-cdd) ### 3) Closer look on whether or not certain kinds of UTxOs were moved in profit or not [Spent Output Profit Ratio (SOPR)](/data-guide/utxo/spent-output-profit-ratio-sopr) It is wise to take a look at each indicator according to the number stated above. ## Points to be aware When the UTxOs are moved, it doesn't necessarily mean that all of them are sold or bought. Relating any UTxO movement to trade-related actions and applying them to the indicators would not fit the purpose of the creation of these indicators. For instances of internal wallet movement, the UTxO does move, but it does not necessarily have to do with price issues. However, it is important to note that any kind of movement on the chain exposes the wallet to the security cost of sending to a wrongful address, getting into on-chain radar just by moving, and paying fees to have any kind of transaction. Thus, it is quite reasonable to assume that every transaction has to have a purpose behind it. ![](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/Wsr45WOCz0FqVKb0pvEJ.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=6e691fd4be285be80da8a6950ebca76a) # Binary CDD Source: https://docs.cryptoquant.com/data-guide/utxo/binary-cdd Binary CDD is binary value and if Supply Adjusted Coin Days Destroyed (Supply-Adjusted CDD) is larger than average Supply-Adjusted CDD, Binary Coin Days points to '1', and '0' if not ### Definition: Binary CDD & Supply Adjusted CDD ![Bitcoin: Binary CDD](https://images.surferseo.art/89dd2931-af3b-4353-9410-0a1d60f5600e.png) Binary Coin Days Destroyed is binary value and if Supply Adjusted Coin Days Destroyed is larger than average Supply Adjusted Coin Days Destroyed, Binary Coin Days points to ‘1' and points to ‘0' if not. Let's look into the Binary Coin Days Destroyed (CDD) values: * **shows 1:** If measured Supply-Adjusted CDD is larger than the average Supply Adjusted CDD * **shows 0:** If measured Supply-Adjusted CDD is less than the average Supply Adjusted CDD ### Interpretation It shows whether long-term holders' movements are higher or lower than average CDD. * **High density** of value pointing ‘1': Long-term holders moved their coins for possible selling * **Low density** of value pointing '1' : Long-term holders are not moving their coins ### How is Binary CDD Measured? Binary Coin Days Destroyed (Binary CDD) provides a nuanced perspective by evaluating Supply Adjusted Coin Days Destroyed (Supply-Adjusted CDD) against the historical average. This measurement considers the spending behavior of long-term holders, particularly with older coins, and aims to accurately represent economic activity within a cryptocurrency network. By assessing the CDD indicator in relation to the long-term historical average, Binary CDD gives more weight to extended periods of coin holding, often associated with cold storage or long-term investment strategies. This approach helps identify significant relative movements in on-chain activity, offering insights into market strength and potential smart money actions. The binary assessment serves as a valuable tool for understanding long-term holder behavior, shedding light on shifts in market sentiment and providing a timely indication of potential trends based on historical data and moving averages. ### Straightforward User Guide Binary CDD serves as a valuable tool for understanding the patterns and long term holder spending behavior in the cryptocurrency market. Generally, when the market is bullish, LTHs tend to spend their older coins, taking advantage of the market strength and positive trend and resulting in higher-than-average destruction of coin days. Conversely, during bearish trends, on-chain activity decreases, and off-chain exchange volumes become more dominant. In such periods, long-term investors with old coins, and savvy holders often accumulate inexpensive coins, withdrawing them to cold storage. This results in a reduction of coin days being destroyed compared to the average. Evaluating Binary CDD is most effective when considering the prevailing market trend. In bullish markets, Binary CDD often remains consistently at 1, reflecting higher on-chain volumes and the spending of older coins. In contrast, bearish markets exhibit a 'bar-code' style pattern in Binary CDD, with alternating 0 and 1 values, showcasing variable on-chain volumes and coin day lifespans, but with a higher proportion of below-average coin day destruction. ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Coin Days Destroyed](/api-reference/btc-network-indicator/coin-days-destroyed) # Coin Days Destroyed (CDD) Source: https://docs.cryptoquant.com/data-guide/utxo/coin-days-destroyed-cdd When UTxO is destroyed, Coin Days Destroyed (CDD) is calculated as the sum value of the number of days between created and spent multiplied by the UTxO amount. ## What is Coin Days Destroyed (CDD)? Coin Days evaluates the number of coins that are not being spent, which gives more weight to estimate long-term-holder (LTH) position. When that coin is spent, the coin is considered "destroyed," and is being updated on Coin Days Destroyed (CDD) metric. CDD is the sum of products of spent transaction output alive days and its value. $$ CDD=\sum\_{o \in \text{spent outputs}}\text{lifespan}\_o\*\text{value}\_o $$ ## How to interpret Coin Days Destroyed (CDD) ### By value itself [#interpretation](#interpretation) * **High**: Long-held coins are moving in great amounts - **Volatility Risk or Possible Trend Reversal** A large number of alive days are destroyed which indicates that long-term holders' coins are exposed to selling. Since coins held long have a huge impact on the market. * **Low**: Long-held coins are moving in less amount ### By Examining Trend [#indicating-selling-or-buying-pressure](#indicating-selling-or-buying-pressure) * **Increasing** trend: **Increasing selling pressure** Long term holders' coins are continuously being sold * **Decreasing** trend: **Decreasing selling pressure** Long term holders' coins are slowing down in movement ### Note on Coin Days Destroyed CDD gives more weight to: 1\) Longer-lived UTXO 2\) Amount of UTXO is holding BTC. Weighting more on these makes the indicator sensitive to long-term holders' movement and shows sentiment & behavior. ### Explanation on creation and destruction of UTxO(s) For every coin that has not been spent on that day, it accumulates one "Coin Day." To understand the concept of "Coin Day" better, check the examples below. * A UTxO for 1 BTC that has not been spent for 10-days has accumulated 10 coin days. * A UTxO for 0.5 BTC that has not been spent for 100-days has accumulated 50 coin days. * A UTxO for 8 BTC that has not been spent for 6-hours (1/4 day) has accumulated 2 coin days. When that coin is spent, the coin is considered "destroyed," and is being updated on CDD metric. #### **Coin Days Destroyed** ![Bitcoin: Coin Days Destroyed (CDD)](https://images.surferseo.art/ce02d527-88ff-4098-821f-b99e72476997.png) An indicator, Coin Days Destroyed (CDD), offers insights into market participants who have held Bitcoin on-chain for an extended period. *What it measures:* CDD metric is a measure of the cumulative number of days that a coin has not been moved before it is spent or transferred. *Why it matters:* Indicates the "age" of a coin before it is used, helping to identify periods of significant coin movement. #### **Supply Adjusted CDD** ![Bitcoin: Supply-Adjusted CDD](https://images.surferseo.art/77563ab6-9d5d-442a-a281-c745fb50ea64.png) Normalized CDD by supply total. *What it measures:* The amount of cryptocurrency (coins) moved or spent, adjusted based on the total supply. *Why it matters:* Helps assess the significance of coin movements relative to the overall available supply. #### **Average Supply Adjusted Coin Days Destroyed** ![Bitcoin: Average Supply-Adjusted CDD](https://images.surferseo.art/1373bb65-58a4-4cbe-bcd8-48e9f46c1eec.png) Average value of Supply-Adjusted CDD since genesis block. *What it measures:* The average age of coins destroyed in a transaction, adjusted for the total supply. *Why it matters:* Gives insight into the average time coins are held before being spent or moved, considering the entire supply. #### **Binary CDD** ![Bitcoin: Binary CDD](https://images.surferseo.art/5698d36c-1faa-4aea-a80e-46eff2860190.png) Signal whether the current Supply-Adjusted CDD is larger than its average or not. *What it measures:* Simplifies Coin Days Destroyed into a binary (yes/no) format, adjusted based on the total supply, indicating whether a significant amount of old coins has moved. *How it works:* Describes whether Supply-Adjusted CDD on any given day was above or below the historical average, offering insights into the activity of long-held coins in the market. *Why it matters:* Provides a binary indication of whether there are notable long-held coins moving, considering the total supply and historical averages, aiding in understanding market trends. ### **Example Application: Deciphering CDD in Market Trends** Understanding Coin Days Destroyed (CDD) is like having a magnifying glass for crypto market trends. Let's consider its practical application: ***Context Matters**:* Absolute CDD values need context. Lower values under 5 million days might indicate routine daily traffic. Values above 10 million days could signal bullish markets or turning points, impacting bitcoin days destroyed and investor decisions. ***Volatility Indicator**:* Spikes in CDD, especially exceeding 20 million days, are rare and often align with high volatility. It suggests significant movements of older coins, possibly indicating profit realization or losses and affecting CDD values. ***Market Confidence**:* CDD tends to rise in bullish markets and drop during corrections. A return to lower levels after an elevation might suggest increased confidence among long-period holders, favoring coin dormancy and impacting circulating supply. ***Smart Money Moves**:* CDD gives extra weight to long-held coins, often considered the 'smart money.' Tracking large movements in CDD provides valuable insights into market dynamics, especially during critical price action and considerations of circulating supply. ***Data Smoothness**:* To make sense of the raw blockchain data, using moving averages is common. It helps filter out noise, allowing strategic investors to spot trends more clearly, impacting long-term investors' decisions, and CDD values. ***Strategic Timing**:* Critical spikes in CDD often align with key moments in Bitcoin's price action. Large investors, holding bitcoin for extended periods, tend to make significant moves during these crucial times, influencing bitcoin days destroyed and CDD values. ## Link to Our Data * [BTC: Coin Days Destroyed Live Chart](https://cryptoquant.com/overview/full/16423?window=day) * [BTC: Binary Coin Days Destroyed Live Chart](https://cryptoquant.com/overview/full/16426?window=day) * [BTC: Supply-Adjusted Coin Days Destroyed Live Chart](https://cryptoquant.com/overview/full/16424?window=day) * [BTC: Average Supply-Adjusted Coin Days Destroyed Live Chart](https://cryptoquant.com/overview/full/16425?window=day) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Coin Days Destroyed](/api-reference/btc-network-indicator/coin-days-destroyed) # Mean Coin Age (MCA) Source: https://docs.cryptoquant.com/data-guide/utxo/mean-coin-age-mca Mean Coin Age is the mean value of products of coins unspent transaction output alive days and its value. ## What is Mean Coin Age (MCA)? Mean Coin Age(MCA) is the mean value of products of coin unspent transaction output (UTxO) alive days and its value. $$ MCA=\frac{\sum\_{u \in \text{unspent outputs}}\text{lifespan}\_u\*\text{value}*u}{\sum*{u \in \text{unspent outputs}}\text{value}\_u} $$ ## How to interpret Mean Coin Age (MCA) MCA is similar to CDD but focuses more on unspent transaction output. Mean Coin Dollar Age is the sum value of products of coin unspent transaction output alive days, value, and the price at the created time. This indicator enables estimating the Long-Term Holders' portion. * Mean Coin Age(MCA): MCA is the average age of UTxO. MCA drop implies the massive move of Bitcoin UTxOs that haven't moved for a long time. * Mean Coin Dollar Age(MCDA): MCDA is an indicator weighted by UTxO created price(USD) to the MCA. ## Link to Our Data * [BTC: Mean Coin Age Live Chart](https://cryptoquant.com/overview/full/16573?window=day) * [BTC: Mean Coin Dollar Age Live Chart](https://cryptoquant.com/overview/full/16574?window=day) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Mean Coin Age](/api-reference/btc-network-indicator/mean-coin-age) # Net Unrealized Profit/Loss (NUPL) Source: https://docs.cryptoquant.com/data-guide/utxo/net-unrealized-profit-and-loss-nupl Net Unrealized Profit and Loss (NUPL) is the difference between market cap and realized cap divided by market cap. ## What is Net Unrealized Profit/Loss (NUPL)? Net Unrealized Profit and Loss (NUPL) is the difference between market cap and realized cap divided by market cap. $$ NUPL = \frac{\text{Market Cap - Realized Cap}}{\text{Market Cap}} $$ ## How to interpret Net Unrealized Profit/Loss (NUPL) ### By Value Itself ![Net Unrealized Profit and Loss NUPL – Source: CryptoQuant](https://4184086776-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwY9jt5nY3DeH5c1WCCsW%2Fuploads%2FZCvO47aGKjHcmcJ4YLwG%2Fimage.png?alt=media\&token=bf3dd743-1a14-4e33-8ce3-c8d59466a18a) Assuming that the latest coin movement is the result of a purchase, NUPL (Net Unrealized Profit and Loss) indicates the total amount of profit/loss in all the coins represented as a ratio. * **Values over ‘0' (+)**: Coins or investors who are in profit are more than investors that are in loss In order for NUPL to be over 0 (+), the Market Cap has to be larger than the Realized Cap. As Market Cap rises above the Realized Cap, it indicates that the value that is being traded on market is greater than the on-chain expected value. For example, if the NUPL value hits 0.75, it means that Market Cap is four times the Realized Cap. It is reasonable to assume that most coins that were moved are on profit and the wide gap between the Realized Cap and Market Cap could act as selling pressure. * **Values under ‘0' (-)**: Coins or investors who are in loss are more than investors that are in profit In order for NUPL to be under 0 (-), the Market Cap has to be less than the Realized Cap. As Realized Cap exceeds the Market Cap, it indicates that the value that is being traded on market is less than the on-chain expected value. For example, if the Net Unrealized Profit/Loss value hits -0.5, it means that Market Cap is two-thirds of the Realized Cap. It is reasonable to assume that most coins that were moved are on loss and the wide gap between the Realized Cap and Market Cap could act as a buying motive. ### By Examining Trend ![Decreasing and Increasing Selling Pressure – Source: CryptoQuant](https://4184086776-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwY9jt5nY3DeH5c1WCCsW%2Fuploads%2FQ6RxxPsvlWjFDhCXxiUu%2Fimage.png?alt=media\&token=a28f0ff9-07b9-41b0-b91f-452f8714ee74) It shows the **changing profit geography of investors** * **Increasing trend: Increasing selling pressure** More coins or investors are beginning to be in profit and this phase naturally indicates the increasing motive to take profit which leads to an increase in sell pressure. Also, it indicates that Market Cap is exceeding Realized Cap making coins profitable to be sold through the market. * **Decreasing trend**: **Decreasing selling pressure** More coins or investors are beginning to be in loss and this phase naturally indicates the decreasing motive to realize loss which leads to a decrease in sell pressure. Also, it indicates that Realized Cap is exceeding Market Cap making coins less profitable to be sold through the market. ### Investing Applied Scenario Net Unrealized Profit/Loss (NUPL) stands as a pivotal metric, offering profound insights into the intricate dynamics of Bitcoin investments, reflecting investor sentiment, profit-taking strategies, and strategic decision-making by investors. When Net Unrealized Profit/Loss (NUPL) surpasses 0.7, a key principle comes into play, signifying proximity to the market top. This principle serves as a guiding force for cautious investors, prompting considerations for Bitcoin investors taking profit. The NUPL value, indicative of a substantial market cap exceeding realized cap, highlights a scenario where investors may strategically take profit, influencing average prices and contributing to increased selling pressure. Conversely, in a market with a Net Unrealized Profit/Loss (NUPL) of -0.2 or lower, a distinct key principle unfolds, signaling an opportune moment closer to the market bottom. This presents a potential buying opportunity for investors looking to accumulate at perceived undervalued levels. The NUPL value in this scenario suggests that realized cap exceeds market cap, indicating that coins are less profitable to be sold in the market. Strategic investors, recognizing this advantageous condition, may engage in accumulation strategies, influencing average prices with a potential dip. The interconnectedness of Net Unrealized Profit/Loss with investor sentiment, profit-taking motives, and strategic accumulation underscores the importance of monitoring these factors. In this dynamic strategic investor landscape, the influence of realized value, market value, market trends, Bitcoin price, relative unrealized profit, and relative unrealized loss becomes evident, impacting profit-taking decisions, average prices, and guiding strategic investors as they track Bitcoin price movements. ### **Related Data** #### **Net Unrealized Profit (NUP)** Sum of UTxO being in profit with the price difference between created and destroyed. #### **Net Unrealized Loss (NUL)** Sum of UTxO being in loss with the price difference between created and destroyed. #### **Net Unrealized Profit and Loss (NUPL)** The difference between market value and realized value ## Link to Our Data * [BTC: Net Unrealized Profit and Loss Live Chart](https://cryptoquant.com/overview/full/16429?window=day) * [BTC: Net Unrealized Loss Live Chart](https://cryptoquant.com/overview/full/16431?window=day) * [BTC: Net Unrealized Profit Live Chart](https://cryptoquant.com/overview/full/16430?window=day) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Net Unrealized Profit and Loss](/api-reference/btc-network-indicator/net-unrealized-profit-and-loss) # Profit and Loss (Supply) Source: https://docs.cryptoquant.com/data-guide/utxo/profit-and-loss-supply Profit and Loss (Supply) evaluates the sum of UTxOs being in profit or not by comparing the price between created and destroyed ## What is Profit and Loss (Supply)? Profit and Loss (Supply) evaluates the sum of UTxOs being in profit or not by comparing the price between created and destroyed. $$ \text{Supply in Profit} = \sum\_{u \in utxos} \text{value}\_u \* \mathbb{I}(\text{price}*u > \text{price}*{created, u}) $$ $$ \text{Supply in Loss} = \sum\_{u \in utxos} \text{value}\_u \* \mathbb{I}(\text{price}*u < \text{price}*{created, u}) $$ $$ \text{Percent Supply in Profit} = 100 \* \frac{\text{Supply in Profit}}{\text{Total Supply}} $$ $$ \text{Percent Supply in Loss} = 100 \* \frac{\text{Supply in Loss}}{\text{Total Supply}} $$ ## How to interpret Profit and Loss (Supply) These metrics are similar to the ones in Profit and Loss (UTxO) but put more weight on each UTxO with its value. It enables measuring the exact alive bitcoin transaction output value in profit. Profit and Loss (Supply) is calculated as the sum of UTxO value. * Profit Amount: The sum of UTxO value being in profit by comparing the price between created and destroyed. * Loss Amount: The sum of UTxO value being in loss by comparing the price between created and destroyed. * Profit Percent: Ratio of the sum of UTxO value being in profit among the total sum of UTxO value. * Loss Percent: Ratio of the sum of UTxO value being in loss among total UTxO value. ## Link to Our Data * [BTC: Profit Amount (Supply) Live Chart](https://cryptoquant.com/overview/full/16436?window=day) * [BTC: Loss Amount (Supply) Live Chart](https://cryptoquant.com/overview/full/16437?window=day) * [BTC: Profit Percent (Supply) Live Chart](https://cryptoquant.com/overview/full/16438?window=day) * [BTC: Loss Percent (Supply) Live Chart](https://cryptoquant.com/overview/full/16439?window=day) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Profit and Loss (Supply)](/api-reference/btc-network-indicator/profit-and-loss-supply) # Profit and Loss (UTxO) Source: https://docs.cryptoquant.com/data-guide/utxo/profit-and-loss-utxo The number of UTxOs being in profit or loss by comparing the price between created and destroyed ## What is Profit and Loss (UTxO)? Profit and Loss (UTxO) evaluates the number of UTxOs being in profit or loss by comparing the price between created and destroyed. When the price at destroyed time is higher than created, this transaction is in profit. $$ \text{UTxOs in Profit} = \text{Number of UTxOs being in profit} $$ $$ \text{UTxOs in Loss} = \text{Number of UTxOs being in loss} $$ $$ \text{Percent UTxOs in Profit} = 100 \* \frac{\text{UTxOs in Profit}}{\text{Number of UTxOs}} $$ $$ \text{Percent UTxOs in Loss} = 100 \* \frac{\text{UTxOs in Loss}}{\text{Number of UTxOs}} $$ ## How to interpret Profit and Loss (UTxO) Assuming that UTxO's movement is the result of trading transaction, Profit and Loss (UTxO) is the basic data that shows how many UTxOs are in profit or loss. ### By Examining Absolute Numbers [#interpretation](#interpretation) If you want to look for how **many** UTxOs are in profit/Loss * **Numbers** of UTxOs that are in **Profit**: [Profit amount](https://cryptoquant.com/overview/btc-network-indicator/16432?window=day) Profit amount naturally shows a correlation to the price * **Numbers** of UTxOs that are in **Loss**: [Loss Amount](https://cryptoquant.com/overview/btc-network-indicator/16433?window=day) Loss amount naturally shows an inverse correlation to the price ### By Examining Ratio [#indicating-selling-or-buying-pressure](#indicating-selling-or-buying-pressure) If you want to look for ratio of UTxOs are in profit/Loss comparative to all UTxOs * **Ratio** of UTxOs that are in **Profit:** [Profit percent](https://cryptoquant.com/overview/btc-network-indicator/16434?window=day) Profit percent naturally shows a correlation to the price * **Ratio** of UTxOs that are in **Loss:** [Loss percent ](https://cryptoquant.com/overview/btc-network-indicator/16435?window=day) Loss percent naturally shows an inverse correlation to the price ## Link to Our Data * [BTC: Profit Amount (UTxO) Live Chart](https://cryptoquant.com/overview/full/16432?window=day) * [BTC: Loss Amount (UTxO) Live Chart](https://cryptoquant.com/overview/full/16433?window=day) * [BTC: Profit Percent (UTxO) Live Chart](https://cryptoquant.com/overview/full/16434?window=day) * [BTC: Loss Percent (UTxO) Live Chart](https://cryptoquant.com/overview/full/16435?window=day) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Profit and Loss (UTxO)](/api-reference/btc-network-indicator/profit-and-loss-utxo) # Spent Output Profit Ratio (SOPR) Source: https://docs.cryptoquant.com/data-guide/utxo/spent-output-profit-ratio-sopr Spent Output Profit Ratio (SOPR) evaluates the profit ratio of the whole market participants by comparing the value of outputs at the spent time to created time. ## What is Spent Output Profit Ratio (SOPR)? Spent Output Profit Ratio (SOPR) evaluates the profit ratio of the whole market participants by comparing the value of outputs at the spent time to created time. In a simple way, you can estimate the distribution of spent transaction output is in profit or not. SOPR is calculated as the USD value of spent outputs at the spent time (realized value) divided by the USD value of spent outputs at the created time (value at creation). \ $$ SOPR=\frac{\sum\_{o \in \text{spent outputs}} \text{value}*o\*\text{price}*{spent, o}}{\sum\_{o \in \text{spent outputs}} \text{value}*o\*\text{price}*{created, o}} $$ ## Steps 1\. UTXO is transferred now 2\. CryptoQuant locates the USD Value of the spent period and divide them by the USD Value at the created time Simply put, SOPR = Now value/ Past value 3\. Categorize and put some figures separately by span time to conclude more specific meanings ## How to use SOPR for investment ### By Value itself ![Spent Output Profit Ratio. Source: CryptoQuant](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/LDoZd3nZxbtAmdLvJVwJ.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=49e517cf077a78a6bd7e301524386e98) * **SOPR value greater than 1 ( SOPR > 1 )** It implies that the coins moved in a certain timescale are, on average, selling at a profit. * **SOPR value of exactly 1** **( SOPR =1 )** It implies that the coins moved in a certain timescale are, on average, selling coins at break even. * **SOPR value less than 1 ( SOPR \< 1)** It implies that the coins moved in a certain timescale are, on average, selling at a loss. ![SOPR Values Below and Above 1](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/5hOtFnkbR7h7TyRcFyiK.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=ba96a920f2a67e3c39b1cbda20d470ac) ### By Examining Trend ![SOPR Trending Higher and Lower](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/JfwCkBb7FmSdudMubFEI.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=87c07f1b1a54cfdc3c99ed391ec873c6) * **SOPR Trending Higher** \ \ SOPR trending higher implies profits are being realized and coins that were in profit are being transferred to others.\ Also, it could be implied that investors who sell their coins in profit are increasing their sell or market condition for sellers are getting more profitable. * **SOPR Trending Lower** \  SOPR trending lower implies losses are being realized and coins that were in loss are being transferred to others. Also, it could be implied that investors who sell their coins in loss are increasing their sell or market condition for sellers are getting less profitable. ### **Real-World SOPR Dynamics:** Investing Applied Scenario As we delve into the practical applications of the Spent Output Profit Ratio (SOPR), We delve into its usefulness in handling diverse market scenarios, capturing the nuanced tale of market sentiment. #### **Bull Market** During a bull run, SOPR is a useful tool for profit realization. As prices rise, a larger coin supply turns profitable, enticing long-term holders to capitalize on gains. * **Resurgence After Correction:** Following a sentiment-driven correction, shrewd investors step in, creating demand that outpaces supply. A low SOPR (near or below 1) signals dormant profits from panic sellers. * **Strength in Profit Distribution:** When a rally intensifies the drive for profit realization, SOPR can peak successively as supply re-enters at higher profit margins. * **Local/Macro Top Achieved:** Freshly distributed supply can overwhelm demand, marking local tops or macro market tops. A high SOPR can signify substantial profit realization, considering both the absolute value and fiat value. #### **Bull Market Corrections** In bull market corrections, the SOPR indicator can showcase resilience as newer market participants may panic trade, while long-term holders can seize the opportunity to buy the dip. * **Market Summit Establishment:** Here, distributed supply can establish a market top. * **Navigating the Correction:** Profitable coins entering the correction can slow SOPR into a downtrend, leading to lower values. * **Reset:** Capitulation by new investors can result in a low SOPR (near or below 1), while profitable coins remain dormant, indicating conviction and the potential for panic selling. #### **Bull Market Reversals** As bull markets transition, SOPR provides insights into changing tides. * **Elevated Peaks:** This can indicate increasing profit realization, potentially necessitating more capital for coins sold at a higher fiat value. * **Persistent Profitability Signals:** Once this occurs, it suggests that spending on profitable coins continues during price dips, signaling a sentiment that coins are becoming expensive. * **Low Values in Correction:** When there is a price correction, it can indicate a broader market panic as investors realize substantial losses. #### **Bear Market** In bear markets, SOPR follows a reversal dance. * **Summit of Supply Over Demand:** Established when supply overwhelms demand, this can potentially lead to high SOPR values. * **Local Descent in Capitulation:** Investors selling at a loss during local lows can result in very low SOPR values (\<1), presenting opportunities for counter-trend traders. * **Profitable Return Phase:** Once this phase is reached, counter-trend traders or long-term holders can return to profitability, with SOPR potentially trending above 1. * **Sustained Capitulation Scenario:** As the bear market potentially reaches its final capitulation, SOPR may persist below 1, indicating a period where remaining profitable coins are dormant and potentially leading to a bullish supply squeeze. ## Why are Some Indicators Modified? ![Modified SOPR Indicators](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/fCe54kDXVYwybw6TFnlw.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=efa62a8baa2a78f526495aa34e044869) ### 1) Can Less Than an Hour-Long Aged UTXO Mean Significance? (aSOPR) aSOPR stands for adjusted SOPR( Spent Output Profit Ratio) . It derived from the standard SOPR by excluding UTXOs that has input-output span that are aged less than an hour long. If there are too many UTXO that are being generated recently, the indicator's value will be made equal to the number of 1 which would mean that many UTXO are at even. [aSOPR (Adjusted SOPR)](/data-guide/utxo/spent-output-profit-ratio-sopr/asopr-adjusted-sopr) ### 2) What if Long/Short Aged UTXO Specifically Suffer From Loss? (LTH-SOPR, STH-SOPR) LTH-SOPR stands for Long Term Holder - SOPR ( Spent Output Profit Ratio). It derived from the standard SOPR by leaving only the UTXO that are aged more than 155 days. [LTH-SOPR](/data-guide/utxo/spent-output-profit-ratio-sopr/lth-sopr) STH-SOPR stands for Short Term Holder - SOPR ( Spent Output Profit Ratio). It derived from the standard SOPR by leaving only the UTXO that are aged less than 155 days and more than an hour alive. [STH-SOPR](/data-guide/utxo/spent-output-profit-ratio-sopr/sth-sopr) ## Links to Our Data * [BTC: SOPR Live Chart](https://cryptoquant.com/overview/full/16440?window=day) * [BTC: Adjusted SOPR Live Chart](https://cryptoquant.com/overview/full/16441?window=day) * [BTC: Short Term Holder SOPR Live Chart](https://cryptoquant.com/overview/full/16443?window=day) * [BTC: Long Term Holder SOPR Live Chart](https://cryptoquant.com/overview/full/16442?window=day) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Spent Output Profit Ratio](/api-reference/btc-market-indicator/spent-output-profit-ratio) # aSOPR (Adjusted SOPR) Source: https://docs.cryptoquant.com/data-guide/utxo/spent-output-profit-ratio-sopr/asopr-adjusted-sopr Adjusted Spent Output Profit Ratio (aSOPR) is a ratio of spent outputs (lived more than an hour) in profit at the time of the window. ## What is aSOPR (Adjusted SOPR)? The adjusted Spent Output Profit Ratio (aSOPR) is a key metric in cryptocurrency analysis that provides insights into whether people are making a profit when they spend their coins. It takes into account factors like aggregate profit and adjusts for spent coins that may not re-enter circulation. By doing so, it offers a clearer understanding of market behavior. It's like a sophisticated tool that helps us see the cryptocurrency market with greater clarity and accuracy. ## How to interpret aSOPR (Adjusted SOPR) Adjustment was made to SOPR by not accounting for hour less lived coins' movements. This allows excluding noises that are only hour less lived UTXO which has minor implication compared to long lived UTXOs. As a result, the spectrum of UTXO coverage is **An Hour\ 1 )** It implies that the coins moved in a certain timescale are, on average, selling at a profit. ![Bitcoin aSOPR Market Top](https://images.surferseo.art/78eab551-9a08-42d5-9f5f-128dbf40d204.png) * **aSOPR value of exactly 1** **(SOPR =1 )** It implies that the coins moved in a certain timescale are, on average, selling coins at break even. * **aSOPR value less than 1 (SOPR \< 1)** It implies that the coins moved in a certain timescale are, on average, selling at a loss. ![Bitcoin aSOPR Market Bottom](https://images.surferseo.art/da364a48-2b10-4432-a6ca-af7dca9800cf.png) ### By Examining Trend * **aSOPR trending higher** implies profits are being realized with potential for previously illiquid supply being returned to liquid circulation * **aSOPR trending lower** implies losses are being realized and/or profitable coins are not being spent. ### **Adjusted Spent Output Profit Ratio: Investing Applied Scenario** ![Bitcoin: Adjusted SOPR (aSOPR)](https://images.surferseo.art/680c64e3-97c8-47b7-8e54-db8db4d2d276.png) 1. Historically, in the middle of bull sentiment, the market correction begins right before the bull run begins and makes aSOPR drop below '1'. This could be the right time to buy before the bull run starts. 2. Previously, in the middle of bear sentiment, the market correction begins right before the bear market starts making aSOPR rise above '1'. This could be the right time to sell before the bear market starts ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Spent Output Profit Ratio](/api-reference/btc-market-indicator/spent-output-profit-ratio) # LTH-SOPR Source: https://docs.cryptoquant.com/data-guide/utxo/spent-output-profit-ratio-sopr/lth-sopr Long Term Holder Spent Output Profit Ratio (LTH-SOPR) is a ratio of spent outputs (lived more than 155 days) in profit at the time of the window. ### Definition ![Long Term Holder Spent Output Profit Ratio ( LTH-SOPR)](https://images.surferseo.art/2767ac94-671e-4804-ae19-6919ee4a7e3a.png) The Long Term Holder Spent Output Profit Ratio (LTH-SOPR) is a crucial metric used in analyzing market trends and investor behavior, particularly among long-term investors. This ratio provides insights into the behavior of long-term holders by measuring the ratio of spent outputs, which are coins that have been held for more than 155 days, in profit at the time of spending. By focusing on spent outputs that have lived for an extended period (more than 155 days), the LTH-SOPR value offers valuable information about the profitability of coins held by long-term investors. It is calculated by dividing the USD value of spent outputs at the time of spending (realized value) by the USD value of spent outputs at the time of creation (value at creation). This calculation helps determine whether long-term holders are realizing profits or losses when they sell their coins. ### Interpretation The adjustment was made by not accounting for 155days less lived coins' movements to track long-term investors. This allows excluding short-term investors or coins and only focuses on long term held movements. **155 days\ 1)** ![Bitcoin: Long Term Holder SOPR. Greater than 1](https://images.surferseo.art/65378eb6-f18a-45e5-8924-c1289f3cdd17.png) When the LTH-SOPR value is greater than 1, it indicates that the realized value of spent outputs (profits) exceeds the value of those outputs at creation. This suggests that long-term holders are selling their coins at a profit, which could signify a bullish market sentiment and strong confidence among long-term investors. It may also indicate potential selling pressure from long-term holders looking to capitalize on their profits. #### **LTH-SOPR Value of Exactly 1 (LTH-SOPR = 1)** ![Bitcoin: Long Term Holder SOPR. Equal to 1](https://images.surferseo.art/5eb20ec5-71f0-432f-84a7-60085c91a1cf.png) When the LTH-SOPR value is exactly 1, it means that the realized value of spent outputs equals the value of those outputs at creation. In other words, long-term holders are neither realizing profits nor incurring losses when selling their coins. This could signal a period of stability in the market, with long-term investors holding onto their positions without actively buying or selling. #### **LTH-SOPR Value Less than 1 (LTH-SOPR \< 1)** ![Bitcoin: Long Term Holder SOPR. Less than 1](https://images.surferseo.art/19351999-a190-4681-9f98-aa1223c3f435.png) When the LTH-SOPR value is less than 1, it suggests that the realized value of spent outputs is lower than the value of those outputs at creation. This indicates that long-term holders are selling their coins at a loss, which may reflect a bearish market sentiment and a lack of confidence among long-term investors. It could also imply that long-term holders are taking losses to exit their positions or to rebalance their portfolios. ### By examining trend **LTH-SOPR Trending Higher**: When the LTH-SOPR is trending higher over time, it suggests an increasing proportion of spent outputs are realizing profits compared to their creation value. This upward trend may indicate growing bullish sentiment among long-term holders, with more investors selling their coins at a profit. It could signal a strengthening market and potential upward price movement. **LTH-SOPR Trending Lower**: Conversely, when the LTH-SOPR is trending lower, it implies a decreasing proportion of spent outputs are realizing profits compared to their creation value. This downward trend may suggest mounting selling pressure from long-term holders selling at a loss or a lack of confidence in the market. It could indicate a weakening market and potential downward price movement. By analyzing the LTH-SOPR both by value itself and by examining trends, investors can gain valuable insights into the sentiment and behavior of long-term holders, helping them make more informed decisions in the cryptocurrency market. ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Spent Output Profit Ratio](/api-reference/btc-market-indicator/spent-output-profit-ratio) # SOPR Ratio (LTH-SOPR/STH-SOPR) Source: https://docs.cryptoquant.com/data-guide/utxo/spent-output-profit-ratio-sopr/sopr-ratio-lth-sopr-sth-sopr SOPR Ratio is calculated as long-term holders' SOPR divided by short-term holders' SOPR. ## What is SOPR Ratio (LTH-SOPR/STH-SOPR)? LTH/STH SOPR calculates the ratio between the Long-Term Holder Spent Output Profit Ratio and the Short-Term Holder Spent Output Profit Ratio. A higher value of the ratio means a higher spent profit of LTH over STH, which is usually useful for spotting market tops. $$ \text{SOPR Ratio}=\frac{\text{LTH-SOPR}}{\text{STH-SOPR}} $$ ## How to interpret SOPR Ratio (LTH-SOPR/STH-SOPR) During bull markets or periods of rapid price appreciation in Bitcoin’s price, this ratio trends higher, which historically is a good time for market participants to realize a profit. During bear markets or periods of extended weakness, this ratio trends lower as the amount of profit from LTHs relative to STHs declines. Historically, investors have been rewarded when dollar cost averaging into BTC and holding long term when this ratio has been below 1.0 for extended periods of time during bear markets. Firmly reclaiming 1.0 with follow-through higher has led to strong recoveries, and in some cases the start of a new bull market. ### By Value itself * **SOPR Ratio value greater than 1** It implies that more long-term holders are making profits than short-term holders. * **SOPR Ratio value exactly at 1** **( LTH-SOPR =1 )** It implies that short-term holders and long-term holders are making the same profits. * **SOPR Ratio value less than 1 ( LTH-SOPR \< 1)** It implies that more short-term holders are making profits than long-term holders. ### By examining trend * **SOPR Ratio trending higher** implies profits are being realized with potential for previously illiquid supply being returned to liquid circulation * **SOPR Ratio trending lower** implies losses are being realized and/or profitable coins are not being spent. *This metric has been proposed by* [*Daniel Joe*](https://twitter.com/DanBTC916?s=20\&t=gVve4aC5BpsecALFs6p88w)*, CQ Verified Author.* ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [SOPR Ratio](/api-reference/btc-market-indicator/sopr-ratio) # STH-SOPR Source: https://docs.cryptoquant.com/data-guide/utxo/spent-output-profit-ratio-sopr/sth-sopr Short Term Output Profit Ratio (STH-SOPR) is a ratio of spent outputs (alive more than 1 hour and less than 155 days) in profit at the time of the window. ### Definition Short Term Holder Spent Output Profit Ratio (STH-SOPR) is a ratio of spent outputs (alive more than 1 hour and less than 155 days) in profit at the time of the window. It is calculated as the USD value of spent outputs at the spent time(realized value) divided by the USD value of spent outputs at the created time(value at creation). ### Interpretation The adjustment was made by not accounting for an hour less lived and 155 days more lived coins' movements to track short-term investors. This allows excluding long-term investors or coins and only focuses on short-term held movements. As a result, the spectrum of UTXO coverage is **an hour\ 1 )** It implies that the coins moved in a certain timescale are, on average, **selling at a profit**. * **STH-SOPR value of exactly 1** **(STH-SOPR =1 )** It implies that the coins moved in a certain timescale are, on average, **selling coins at break even**. * **STH-SOPR value less than 1 (STH-SOPR \< 1)** It implies that the coins moved in a certain timescale are, on average, **selling at a loss**. ### By examining trend * **Short-Term Holder SOPR trending higher** It implies that short term investors are realizing their coins where trading condition is getting more profitable. This equals a higher market sentiment. * **Short-Term Holder SOPR trending lower** It implies that short term investors are realizing their coins where trading condition is getting less profitable. This equals a lower sentiment in the market and one can see the potential of panic selling. ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Spent Output Profit Ratio](/api-reference/btc-market-indicator/spent-output-profit-ratio) # Sum Coin Age Distribution (SCA Distribution) Source: https://docs.cryptoquant.com/data-guide/utxo/sum-coin-age-distribution-sca-distribution Sum Coin Age Distribution(SCA Distribution) shows the distribution of Long-Term Holder and Short-Term Holder with UTxO data ## What is Sum Coin Age Distribution (SCA Distribution)? Sum Coin Age Distribution(SCA Distribution) shows the distribution of Long-Term Holder and Short-Term Holder with UTxO data. It is similar to UTxO age distribution but weighted by alive days(=age of each UTxO) to highlight long-term holder's distribution. Each field is calculated as the sum of the products of coin unspent transaction output alive days and its value in a given period, divided by their sum. $$ P(X=\[a\_i, bi))= \frac{\sum\_{u \in utxos} \text{lifespan}\_u \* \text{value}\_u \* \mathbb{I}(a\_i \leq \text{lifespan}*u < b\_i)}{\sum*{u \in utxos} \text{lifespan}*u \* \text{value}*{u}} $$ $$ \[a\_i, bi) \in \[\[0, 1d), \[1d, 1w), \[1w, 1m), \[1m, 3m), \[3m, 6m), \[6m, 12m), \[12m, 18m), \[18m, 24m)\ \[2y, 3y), \[3y, 5y), \[5y, 7y), \[7y, 10y), \[10y, \inf) $$ ## How to interpret Sum Coin Age Distribution (SCA Distribution) SCA Distribution is similar to UTxO age distribution but weighted by alive days to highlight long-term holder’s distribution in different ranges. If the long-term SCA Distribution ratio increases, then it could be interpreted as the coin's future value is greater than the current value. The range of SCA Distribution is as below * Less than 1 Day * 1 Day to 1 Week * 1 Week to 1 Month * 1 Month to 3 Month * 3 Month to 6 Month * 6 Month to 12 Month * 12 Month to 18 Month * 18 Month to 24 Month * 2 Year to 3 Year * 3 Year to 5 Year * 5 Year to 7 Year * 7 Year to 10 Year * 10 Year to Infinity ## Link to Our Data * [BTC: Sum Coin Age Distribution Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/sum-coin-age-distribution?window=DAY\&priceScale=linear\&metricScale=linear) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Sum Coin Age Distribution](/api-reference/btc-network-indicator/sum-coin-age-distribution) # Sum Coin Age (SCA) Source: https://docs.cryptoquant.com/data-guide/utxo/sum-coin-age-sca Sum Coin Age ( SCA ) is the sum value of products of coins unspent transaction output alive days and its value. ## What is Sum Coin Age (SCA)? Sum Coin Age ( SCA ) is the sum value of products of coins unspent transaction output alive days and its value. ## How to interpret Sum Coin Age (SCA) Sum Coin Age (SCA) is sum of ‘Alive days’ combining the days of all coins that was in a kept single wallet. SCA has a tendency to increase in value in principle because more BTC is being mined and not all BTC move all the time. * **Sudden decrease**: Coins that were dormant moved in mass- **Volatility Risk or Possible Trend Reversal** * **Continuous rise**: the total days of coins alive accumulates Continuous rise in SCA is normal in general but could turn to sell pressure when price begins to rise in sudden. ## Link to Our Data * [BTC: Sum Coin Age Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/sum-coin-age?window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=line) * [BTC: Sum Coin Dollar Age Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/sum-coin-dollar-age?window=DAY\&sma=0\&ema=0\&priceScale=linear\&metricScale=linear\&chartStyle=line) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Sum Coin Age](/api-reference/btc-network-indicator/sum-coin-age) # UTXO Bands (Age) Source: https://docs.cryptoquant.com/data-guide/utxo/utxo-bands-age UTXO Age Bands group all active supply by how long ago coins last moved, letting you separate long-term holder behavior from short-term traders. ![](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/R65LDQ0sLBDSHVDfjZwH.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=6729e75a9b3ff19097953d0b8955c3f1) 1. UTXO Age Bands is a set of all active supplies that were last moved within a specified age band. 2. Each colored band represents the standards stated below. 3. Because of their categorization by Age Bands, these metrics allow investors to infer market changes by investors' age span as broad as **'Long-term Investors'/'Short-term Investors'** or derive meanings set by **specific age cohort**. ## What are the differences between these metrics? Each colored band represents the standards that are stated below. ### 1) Finding out each age band's 'Total UTXO Amount' UTXO Age Bands' value that fit according to the age range represents the total value of UTXOs in existence, that was last moved within the denoted time period in native value. [UTXO Age Bands](/data-guide/utxo/utxo-bands-age/utxo-age-bands) ### 2)Finding out each age band's 'Realized Cap' Realized Cap - UTXO Age Bands shows the distribution of realized cap of a specified age band. Each colored band represents the Realized Cap of UTXOs in existence, that was last moved within the denoted time period in USD value [Realized Cap - UTXO Age Bands](/data-guide/utxo/utxo-bands-age/realized-cap-utxo-age-bands) ### 3)Finding out each age band's 'Number of UTXOs' UTXO Count - Age Bands shows the number of UTXOs that were last moved within a specified age band. Each colored band represents the number of UTXOs in existence, that were last moved within the denoted time period. [UTXO Count - Age Bands](/data-guide/utxo/utxo-bands-age/utxo-count-age-bands) ### 4)Finding out each which age band is responsible for the spent output Spent Output Age Bands is a set of all spent outputs that were created within a specified age band. Each colored band represents the total value of spent outputs, that were last created within the denoted time period. #### Steps 1\. CryptoQuant collects UTXOs that was destroyed in a certain window #### ⬇ 2\. CryptoQuant categorizes them to each band and shows the result by values or by percentage #### ⬇ 3\. Investors interpret categorized values and conclude which age band's UTXOs were mostly responsible for any changes in the market. [Spent Output Age Bands](/data-guide/utxo/utxo-bands-age/spent-output-age-bands) # Realized Cap - UTXO Age Bands Source: https://docs.cryptoquant.com/data-guide/utxo/utxo-bands-age/realized-cap-utxo-age-bands Realized Cap - UTXO Age Bands shows the distribution of realized cap of a specified age band ## What is Realized Cap - UTXO Age Bands? Realized Cap - UTXO Age Bands shows the distribution of realized cap of a specified age band. Each colored band represents the Realized Cap of UTXOs in existence, that were last moved within the denoted time period in USD value. Realized Cap is calculated by valuing each UTXO by the price when it was last moved. $$ \text{Realized Cap - UTXO Age Bands (USD)} ={\sum\_{u \in utxos} \text{value}\_u \* \mathbb{I}(a\_i \leq \text{lifespan}*u < b\_i) \* \text{Price}*{\text{u, at created}}} $$ $$ \text{Realized Cap - UTXO Age Bands (%)} =\frac{\sum\_{u \in utxos} \text{value}*u \* \mathbb{I}(a\_i \leq \text{lifespan}*u < b\_i) \* \text{Price}*{\text{u, at created}}}{\sum*{u \in utxos} \text{value}*{u} \* \text{Price}*{\text{u, at created}}}\*100 $$ $$ \[a\_i, bi) \in \[\[0, 1d), \[1d, 1w), \[1w, 1m), \[1m, 3m), \[3m, 6m), \[6m, 12m), \[12m, 18m), \[18m, 24m)\ \[2y, 3y), \[3y, 5y), \[5y, 7y), \[7y, 10y), \[10y, \inf) $$ #### **Modified Metrics** | Metric | Definition | | - | - | | Realized Cap - UTXO Age Bands USD | Each colored band represents the Realized Cap of UTXOs in existence, that were last moved within the denoted time period i**n USD value**. | | Realized Cap - UTXO Age Bands (%) | Each colored band represents **the ratio of** the Realized Cap of UTXOs in existence, that were last moved within the denoted time period. | ## How to interpret Realized Cap - UTXO Age Bands This indicator summarizes the capitalization held by long-term and short-term holders. As price rises/falls, it is advised to watch out for shifting distribution in the UTXO Age Bands to further gain insights on the market through analyzing its participants. Different from UTXO Age Bands indicating UTXO native values or USD value which applies the current same price standard to each band, Realized Cap - UTXO Age Bands (USD) applies each UTXO by the price when it was last moved to make the indicator some advantages overseeing the market. **1) Lost Old Coins' influence on the metric is minimized.** For example, UTXOs that locates at the Age Band of 10 years to infinity could be assumed lost since it hasn't moved for a long time. UTXOs like these could be represented as a substantial amount in the normal UTXO Age Bands but it's minimized at the Realized Cap- UTXO Age Bands because of the low price that bitcoin was at the time. Applying Realized price naturally accounts for long-held but lost coins. **2) Represents Stored Value as it counts for each economical circumstance at the time along with age band.** Bitcoin's price has been x10000 since its creation and equalling the same amount of purchase at the cost of a dollar with standards today might be misleading in evaluating stored value. Realized Cap - UTXO Age Bands accounts for the economic standard of the according to Band Age. ### By value itself [#interpretation](#interpretation) * **High value(Native Value) & Dominance(%) in certain UTXO Age Band**\ **-** Age Band's type of investor has more representative For example, if the UTXO Age Band of 3 years to 5 years have the greatest Realized Cap - UTXO Age Bands, 1\) It is possible to interpret it as investors that held 3 to 5 years have more potential of influencing the market both in terms of age and stored value. 2\) The average price range bought at the time could indicate an important price level in the market. * **Low value(Native Value) & Dominance(%) in certain UTXO Age Band** For example, if the UTXO Age Band of 3 years to 5 years has the least UTXO Age Band Value, 1\) It is possible to interpret it as investors that held 3 to 5 years have less potential of influencing the market than other UTXO Age Band in terms of economical stored value. 2\) The average price range bought at the time could indicate an important price level but could fall behind compared to other UTXO Age Bands. ### By examining trend [#indicating-selling-or-buying-pressure](#indicating-selling-or-buying-pressure) * **Longer UTXO Aged Bands Gaining Dominance or Larger in Depth**\ \- More UTXOs are being held for the Long term = **More HOLDing** As comparatively newer coins are being held or so to speak HODLed without any movement in the network, it moves on to the next UTXO Age Bands implying that more coins are being held in the long term and more values are being stored according to Age Band. * **Younger UTXO Aged Bands Gaining Dominance or Larger in Depth**\ **-** Old Coins Being Renewed to Younger Coins **= Old Coins Being Circulated** As older coins are being transferred in the network, they are destroyed and become new UTXO making the younger UTXO Age Bands increase in value which results in young UTXO Age Bands growing in size. ## Link to Our Data * [Realized Cap - UTXO Age Bands USD Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/realized-cap-utxo-age-bands-usd?window=DAY\&priceScale=linear\&metricScale=linear) * [Realized Cap - UTXO Age Bands (%) Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/realized-cap-utxo-age-bands-percent?window=DAY\&priceScale=linear\&metricScale=linear) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [UTxO Realized Age Distribution](/api-reference/btc-network-indicator/utxo-realized-age-distribution) # Realized Price - UTXO Age Bands Source: https://docs.cryptoquant.com/data-guide/utxo/utxo-bands-age/realized-price-utxo-age-bands UTxO Realized Price Age Distribution is a set of realized prices along with age bands. ## What is Realized Price - UTXO Age Bands? UTxO Realized Price Age Distribution is a set of realized prices along with age bands. The metrics help us to overview each cohort’s holding behavior by overlaying a set of different realized prices. Realized price is calculated as Realized Cap divided by the total supply. $$ \text{UTxO Realized Price Age Distribution} = \frac{\text{UTxO Realized Age Distribution for each band (USD)}}{\text{UTxO Age Distribution for each band (Native)}} $$ ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [UTxO Realized Price Age Distribution](/api-reference/btc-market-indicator/utxo-realized-price-age-distribution) # Spent Output Age Bands Source: https://docs.cryptoquant.com/data-guide/utxo/utxo-bands-age/spent-output-age-bands Spent Output Age Bands is a set of all spent outputs that were created within a specified age band. ## What is Spent Output Age Bands? Spent Output Age Bands is a set of all spent outputs that were created within a specified age band. Each colored band represents the total value of spent outputs, that were last created within the denoted time period. This indicator summarizes the behaviors of long-term and short-term holders along with the price actions. $$ \text{Spent Output Age Bands} ={\sum\_{o \in \text{spent outputs}} \text{value}\_o \* \mathbb{I}(a\_i \leq \text{lifespan}\_o < b\_i)} $$ $$ \text{Spent Output Age Bands(USD)} =\text{price}*{current}\*{\sum*{o \in \text{spent outputs}} \text{value}\_o \* \mathbb{I}(a\_i \leq \text{lifespan}\_o < b\_i)} $$ $$ \text{Spent Output Age Bands(%)} =\frac{\sum\_{o \in \text{spent outputs}} \text{value}*o \* \mathbb{I}(a\_i \leq \text{lifespan}*o < b\_i)}{\sum*{o \in \text{spent outputs}} \text{value}*{o}}\*100 $$ $$ \[a\_i, bi) \in \[\[0, 1d), \[1d, 1w), \[1w, 1m), \[1m, 3m), \[3m, 6m), \[6m, 12m), \[12m, 18m), \[18m, 24m)\ \[2y, 3y), \[3y, 5y), \[5y, 7y), \[7y, 10y), \[10y, \inf) $$ | Metric | Definition | | - | - | | Spent Output Age Bands | Each colored band represents the t**otal value of** spent outputs, that were last created within the denoted time period. | | Spent Output Age Bands USD | Each colored band represents the total value of spent outputs, that were last created within the denoted time period **in USD value**. | | Spent Output Age Bands (%) | Each colored band represents **the ratio of** the total value of spent outputs, that were last created within the denoted time period. | ## How to interpret Spent Output Age Bands This indicator summarizes the behavior of long-term and short-term holders along with the price actions. Beyond just long-term & short-term holders' behavior, it is possible to screen the specific Aged UTXOs (Cohort) behavior and their reaction to certain price range, market atmosphere. As price rises/falls, it is advised to watch out for values in the Spent Output Age Bands to further gain insights on the market through analyzing its participants. \ Unlike UTXO Age Bands, Spent Output Age Bands focus on the UTXOs that were destroyed within the set metric window. With the help of Spent Output Age Bands, it is possible to pinpoint which aged UTXOs (according to Age Bands timeline) were destroyed in what amount. Using this knowledge, investors can correlate any price movement or changes in the network with the action of long-term/short-term holders' action. ### By value itself * **High value(Native Value) & Dominance(%)** in certain Spent Output Age Bands\ \- **Mostly accountable for changes in the network** For example, if the UTXO Age Band of 3 years to 5 years have the greatest Spent Output Age Bands in terms of value or dominance, it could be interpreted that investors of 3 years to 5 years are mostly accountable for any price movement or changes that occur in the market within a set metric window. ## Link to Our Data * [Spent Output Age Bands Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/spent-output-age-bands?window=DAY\&priceScale=linear\&metricScale=linear) * [Spent Output Age Bands USD Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/spent-output-age-bands-usd?window=DAY\&priceScale=linear\&metricScale=linear) * [Spent Output Age Bands (%) Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/spent-output-age-bands-percent?window=DAY\&priceScale=linear\&metricScale=linear) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Spent Output Age Distribution](/api-reference/btc-network-indicator/spent-output-age-distribution) # UTXO Age Bands Source: https://docs.cryptoquant.com/data-guide/utxo/utxo-bands-age/utxo-age-bands UTXO Age Bands is a set of all active supply that were last moved within a specified age band. ## What is UTXO Age Bands? UTXO Age Bands is a set of all active supplies that were last moved within a specified age band. UTXO Age Bands' value that fit according to the age range represents the total value of UTXOs in existence, that were last moved within the denoted time period in native value. $$ \text{UTXO Age Bands} = {\sum\_{u \in utxos} \text{value}\_u \* \mathbb{I}(a\_i \leq \text{lifespan}\_u < b\_i)} $$ $$ \text{UTXO Age Bands (USD)} =\text{price}*{current}\*{\sum*{u \in utxos} \text{value}\_u \* \mathbb{I}(a\_i \leq \text{lifespan}\_u < b\_i)} $$ $$ \text{UTXO Age Bands (%)} =\frac{\sum\_{u \in utxos} \text{value}*u \* \mathbb{I}(a\_i \leq \text{lifespan}*u < b\_i)}{\sum*{u \in utxos} \text{value}*{u}}\*100 $$ $$ \[a\_i, bi) \in \[\[0, 1d), \[1d, 1w), \[1w, 1m), \[1m, 3m), \[3m, 6m), \[6m, 12m), \[12m, 18m), \[18m, 24m)\ \[2y, 3y), \[3y, 5y), \[5y, 7y), \[7y, 10y), \[10y, \inf) $$ #### **Modified Metrics** | Metric | Definition | | - | - | | UTXO Age Bands | Each colored band represents the total value of UTXOs in existence, that were last moved within the denoted time period in **native value**. | | UTXO Age Bands USD | Each colored band represents the total value of UTXOs in existence, that were last moved within the denoted time period in **USD value**. | | UTXO Age Bands (%) | Each colored band represents **the ratio of the total value of UTXOs in existence**, that were last moved within the denoted time period. | ## How to interpret UTXO Age Bands This indicator summarizes the behaviors of long-term and short-term holders along with the price actions. As price rises/falls, it is advised to watch out for shifting distribution in the UTXO Age Bands to further gain insights on the market through analyzing its participants. \ \ It also provides valuable tools for analyzing static macro views of holders' age distribution in the network and viewing the macro shift in influence difference between Long-held UTXOs and Short-held UTXOs. Keep in mind that each UTXO Age band is connected to each other. For example, UTXOs that were located in 6m\~12m UTXO Age band six months before shifts to 12m\~18m UTXO Age band now under the assumption that it has not moved. ### By value itself [#interpretation](#interpretation) * **High value(Native Value) & Dominance(%) in certain UTXO Age Band**\ **-** Age Band's type of investor has more representative For example, if the UTXO Age Band of 3 years to 5 years have the greatest UTXO Age Band Value, 1\) It is possible to interpret it as investors that held 3 to 5 years have more potential of influencing the market. 2\) The price range bought at the time could indicate an important price level in the market. * **Low value(Native Value) & Dominance(%) in certain UTXO Age Band**\ \- Less influence & type of investor has less representative For example, if the UTXO Age Band of 3 years to 5 years have the least UTXO Age Band Value, 1\) It is possible to interpret it as investors that held 3 to 5 years have less potential of influencing the market than other UTXO Age Band. 2\) The price range bought at the time could indicate an important price level but could fall behind compared to other UTXO Age Bands. ### By examining trend [#indicating-selling-or-buying-pressure](#indicating-selling-or-buying-pressure) * **Longer UTXO Aged Bands Gaining Dominance or Larger in Depth**\ \- More UTXOs are being held for the Long term = **More HODLing** As comparatively newer coins are being held or so to speak HODLed without any movement in the network, it moves on to the next UTXO Age Bands implying that more coins are being held in the long term. * **Younger UTXO Aged Bands Gaining Dominance or Larger in Depth**\ **-** Old Coins Being Renewed to Younger Coins **= Old Coins Being Circulated** As older coins are being transferred in the network, they are destroyed and become new UTXO making the younger UTXO Age Bands increase in value which results in young UTXO Age Bands growing in size. #### **Note** [#indicating-the-level-of-exchange-activity](#indicating-the-level-of-exchange-activity) 1. As the circulating supply continues, the total native value of UTXO Age Bands should increase. 2. Identifying the characteristics of UTXOs identical to the wallet/investors might be misleading.\ ex. One wallet might hold meaningful amounts of both old and young UTXOs in a single wallet. ## Link to Our Data * [UTXO Age Bands Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/utxo-age-bands?window=DAY\&priceScale=linear\&metricScale=linear) * [UTXO Age Bands USD Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/utxo-age-bands-usd?window=DAY\&priceScale=linear\&metricScale=linear) * [UTXO Age Bands (%) Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/utxo-age-bands-percent?window=DAY\&priceScale=linear\&metricScale=linear) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [UTxO Age Distribution](/api-reference/btc-network-indicator/utxo-age-distribution) # UTXO Count - Age Bands Source: https://docs.cryptoquant.com/data-guide/utxo/utxo-bands-age/utxo-count-age-bands UTXO Count - Age Bands shows the number of UTXOs that were last moved within a specified age band. ## What is UTXO Count - Age Bands? UTXO Count - Age Bands shows the number of UTXOs that were last moved within a specified age band. Each colored band represents the number of UTXOs in existence, that were last moved within the denoted time period. $$ \text{UTXO Count - Age Bands} = {\sum\_{u \in utxos} \mathbb{I}(a\_i \leq \text{lifespan}\_u < b\_i) } $$ $$ \text{UTXO Count - Age Bands (%)} =\frac{\sum\_{u \in utxos} \mathbb{I}(a\_i \leq \text{lifespan}*u < b\_i) }{\sum*{u \in utxos}1}\*100 $$ $$ \[a\_i, bi) \in \[\[0, 1d), \[1d, 1w), \[1w, 1m), \[1m, 3m), \[3m, 6m), \[6m, 12m), \[12m, 18m), \[18m, 24m)\ \[2y, 3y), \[3y, 5y), \[5y, 7y), \[7y, 10y), \[10y, \inf) $$ | Metric | Definition | | - | - | | UTXO Count - Age Bands | Each colored band represents the number of UTXOs in existence, that was last moved within the denoted time period | | UTXO Count - Age Bands (%) | Each colored band represents the **percent of the ratio** of UTXOs in existence that were last moved within the denoted time period. | ## How to interpret UTXO Count - Age Bands This indicator can be used to estimate the number of long-term and short-term holders that exist in each age band. UTXO Count- Age Bands could be interpreted as a 'proxy' to the actual holders that fit accordingly to the Age Band. ### By value itself * **High value(Native Value) & Dominance(%) in certain UTXO Age Band**\ **-** High Number of investors that fit the Age Band For example, if the UTXO Age Band of 3 years to 5 years have the greatest UTXO Count - Age Bands, 1\) It is possible to interpret it as investors that held 3 to 5 years take a large portion of the market in terms of the number of participants. 2\) The price range bought at the time could indicate an important price level in the market. * **Low value(Native Value) & Dominance(%) in certain UTXO Age Band**\ **-**Low Number of investors that fit the Age Band For example, if the UTXO Age Band of 3 years to 5 years has the least UTXO Count - Age Bands, 1\) It is possible to interpret it as investors that held 3 to 5 years take a small portion of the market in terms of the number of participants. 2\) The price range bought at the time could indicate an important price level but could fall behind compared to other UTXO Age bands. ### By examining trend [#indicating-selling-or-buying-pressure](#indicating-selling-or-buying-pressure) * **Longer UTXO Aged Bands Gaining Dominance or Larger in Depth**\ \- More UTXOs & holders are holding for the Long term = **More HOLDing Participants** As comparatively newer coins are being held or so to speak HODLed without any movement in the network, it moves on to the next UTXO Age Bands implying that more coins are being held in the long term and more investors are HODLing. * **Younger UTXO Aged Bands Gaining Dominance or Larger in Depth**\ **-** Old Coins Being Renewed to Younger Coins **= Old Coins Being Circulated** As older coins are being transferred in the network, they are destroyed and become new UTXO making the younger UTXO Age Bands increase in value which results in young UTXO Age Bands growing in size. ## Link to Our Data * [UTXO Count - Age Bands](https://cryptoquant.com/asset/btc/chart/network-indicator/utxo-count-age-bands?window=DAY\&priceScale=linear\&metricScale=linear) [Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/utxo-count-age-bands?window=DAY\&priceScale=linear\&metricScale=linear) * [UTXO Count - Age Bands(%)](https://cryptoquant.com/asset/btc/chart/network-indicator/utxo-count-age-bands-percent?window=DAY\&priceScale=linear\&metricScale=linear) [Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/utxo-count-age-bands-percent?window=DAY\&priceScale=linear\&metricScale=linear) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [UTxO Count Age Distribution](/api-reference/btc-network-indicator/utxo-count-age-distribution) # UTXO Bands (Value) Source: https://docs.cryptoquant.com/data-guide/utxo/utxo-bands-value UTXO Value Bands group all UTXOs by their value, letting you distinguish whale-sized holdings from retail-sized coins across the supply. ![](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/SYLOa9vonc7RxmRt1X7P.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=45c4521f133b98ce127d1978c0987343) 1. UTXO Value Bands shows the distribution of all UTXOs according to their value 2. Each colored band represents the standards stated below. 3. Because of their categorization by Value Bands, these metrics allow investors to infer market changes by investors' hold amount as broad as **'Whales/Retails'** or derive meanings set by **Specific Value Cohort**. ## What are the differences between these metrics? Each colored band represents the standards that are stated below. ### 1) Finding out each value band's 'Total UTXO Amount' UTXO Value Bands shows the distribution of all UTXOs according to their value. Each colored band represents the total value of all UTXOs, that has a value within the denoted range. [UTXO Value Bands](/data-guide/utxo/utxo-bands-value/utxo-value-bands) ### 2)Finding out each value band's 'Realized Cap' Realized Cap - UTXO Value Bands show the distribution of realized cap of a specified value band. Each colored band represents the Realized Cap of UTXOs in existence, which has a value within the denoted range in USD value. Realized Cap is calculated by valuing each UTXO by the price when it was last moved. [Realized Cap - UTXO Value Bands USD](/data-guide/utxo/utxo-bands-value/realized-cap-utxo-value-bands-usd) ### 3)Finding out each value band's 'Number of UTXOs' UTXO Count - Value Bands shows the distribution of the number of UTXOs according to their value. Each colored band represents the number of UTXOs in existence, that has a value within the denoted range. [UTXO Count - Value Bands](/data-guide/utxo/utxo-bands-value/utxo-count-value-bands) ### 4)Finding out each which value band is responsible for the spent output Spent Output Value Bands show the distribution of all spent outputs according to their value. Each colored band represents the total value of spent outputs, that has a value within the denoted range. #### Steps 1\. CryptoQuant collects UTXOs that was destroyed in a certain window #### ⬇ 2\. CryptoQuant categorizes them to each band and shows the result by values or by percentage #### ⬇ 3\. Investors interpret categorized values and conclude which value band's UTXOs were mostly responsible for any changes in the market. [Spent Output Value Bands](/data-guide/utxo/utxo-bands-value/spent-output-value-bands) # Realized Cap - UTXO Value Bands USD Source: https://docs.cryptoquant.com/data-guide/utxo/utxo-bands-value/realized-cap-utxo-value-bands-usd Realized Cap - UTXO Value Bands show the distribution of realized cap of a specified value band. ## What is Realized Cap - UTXO Value Bands USD? Realized Cap - UTXO Value Bands show the distribution of realized cap of a specified value band. Each colored band represents the Realized Cap of UTXOs in existence, which has a value within the denoted range in USD value. Realized Cap is calculated by valuing each UTXO by the price when it was last moved. This indicator summarizes the capitalization held by whales and retails. $$ \text{Realized Cap - UTXO Value Bands USD} =\sum\_{u \in utxos} \text{value}\_u \* \mathbb{I}(a\_i \leq \text{value}*u < b\_i) \* \text{Price}*{\text{u, at created}} $$ $$ \text{Realized Cap - UTXO Value Bands (%)} =\frac{\sum\_{u \in utxos} \text{value}*u \* \mathbb{I}(a\_i \leq \text{value}*u < b\_i) \* \text{Price}*{\text{u, at created}}}{\sum*{u \in utxos} \text{value}*{u} \* \text{Price}*{\text{u, at created}}} \* 100 $$ $$ \[a\_i, bi) \in \[0, 0.01), \[0.01, 0.1), \[0.1, 1), \[1, 10), \[10, 100), \[100, 1k), \[1k, 10k), \[10k, inf) $$ | Metric | Definition | | - | - | | Realized Cap - UTXO Value Bands USD | Each colored band represents the Realized Cap of UTXOs in existence, that have a value within the denoted range **in USD value**. | | Realized Cap - UTXO Value Bands (%) | Each colored band represents **the ratio of** Realized Cap of UTXOs in existence, that have a value within the denoted range. | ## How to interpret Realized Cap - UTXO Value Bands USD This indicator summarizes the behaviors of whales or retails separated by the amount of coins they hold along with price actions. As price rises/falls, it is advised to watch out for shifting distribution in the UTXO Value Bands to further gain insights on the market through analyzing its participants. \ \ It provides valuable tools for analyzing static macro views of holders' amount distribution (Whale/Retails) in the network and viewing the macro shift in influence difference between Whale and the retails. Different from UTXO Value Bands indicating UTXO native values or USD value which applies the current same price standard to each band, Realized Cap - UTXO Value Bands USD applies each UTXO by the price when it was last moved makes the indicator some advantages overseeing the market. **1) Lost Old Coins' influence on the metric is minimized.** Applying Realized price naturally accounts for long-held but lost coins. For example, UTXOs that located at the Value Band of 1k to 10k may be great in amount but if it is held over 10 years without any movement, it could be considered lost. UTXOs like these could be represented as a substantial amount in the normal UTXO Value Bands but it's minimized at the Realized Cap- UTXO Value Bands because of the low price that bitcoin was at the time. **2) Represents Stored Value as it counts for each economical circumstance at the time along with Value band.** Bitcoin's price has been x10000 since its creation and equalling the same amount of purchase at the cost of a dollar with standards today might be misleading in evaluating stored value. Realized Cap - UTXO Value Bands accounts for the economic standard according to the Value Band. ### By value itself [#interpretation](#interpretation) * **High value(Native Value) & Dominance(%) in certain Realized UTXO Value Band**\ **-** Value Band's type of investor has more representative For example, if the UTXO Value Band of 1k to 10k has the greatest UTXO Value Band Value, 1\) It is possible to interpret it as investors that hold 1k to 10k who are most likely to be whales have more potential of influencing the market in terms of both amount and the total amount it was paid to acquire. 2\) The average price range bought by the according to UTXO Value Bands(Whales/Retails) could indicate an important price level in the market. * **Low value(Native Value) & Dominance(%) in certain UTXO Value Band**\ \- Less influence & type of investor has less representative For example, if the UTXO Value Band of 1k to 10k has the lowest UTXO Value Band Value, It is possible to interpret it as investors that hold 1k to 10k who are most likely to be whales have less potential of influencing the market than other UTXO Value Band in terms of both amount and the total amount it was paid to acquire. ### By examining trend [#indicating-selling-or-buying-pressure](#indicating-selling-or-buying-pressure) * **Larger UTXO Value Bands Gaining Dominance or Larger in Depth**\ \- More UTXOs are being held in the hands of the possible whales and more capital (stored value) is being used to acquire them = **Increasing** **Whale Dominance** More UTXOs are being in large quantities that are mostly held by whales or in terms of capital it was required to acquire UTXOs. Unlike having mid-sized UTXOs in several numbers, increasing the number of big-sized UTXO (meaning in the amount) is strong evidence of whale presence. \ \ In addition, instead of UTXOs being in small amounts, it could indicate that the individual size of UTXO is starting to be managed in a big chunk. * **Smaller UTXO Value Bands Gaining Dominance or Larger in Depth**\ **-** More UTXOs are being held in the hands of the possible retail = **Possible** **Decrease of** **Whale Dominance** As more UTXOs are getting a smaller amount in size, it could indicate that retails are gaining more possession of the holdings, and retails are storing more value into the network. ## Link to Our Data * [Realized Cap - UTXO Value Bands USD](https://cryptoquant.com/asset/btc/chart/network-indicator/realized-cap-utxo-value-bands-usd?window=DAY\&priceScale=linear\&metricScale=linear) [Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/realized-cap-utxo-value-bands-usd?window=DAY\&priceScale=linear\&metricScale=linear) * [Realized Cap - UTXO Value Bands USD (%)](https://cryptoquant.com/asset/btc/chart/network-indicator/realized-cap-utxo-value-bands-percent?window=DAY\&priceScale=linear\&metricScale=linear) [Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/realized-cap-utxo-value-bands-percent?window=DAY\&priceScale=linear\&metricScale=linear) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [UTxO Realized Supply Distribution](/api-reference/btc-network-indicator/utxo-realized-supply-distribution) # Spent Output Value Bands Source: https://docs.cryptoquant.com/data-guide/utxo/utxo-bands-value/spent-output-value-bands Spent Output Value Bands show the distribution of all spent outputs according to its value. ## What is Spent Output Value Bands? Spent Output Value Bands show the distribution of all spent outputs according to its value. Each colored band represents the total value of spent outputs, that has a value within the denoted range. This indicator can be used to estimate the amount of coins moved by whale and retail holders $$ \text{Spent Output Value Bands} =\sum\_{o \in \text{spent outputs}} \text{value}\_o \* \mathbb{I}(a\_i \leq \text{value}\_o < b\_i) $$ $$ \text{Spent Output Value Bands (%)} =\frac{\sum\_{o \in \text{spent outputs}} \text{value}*o \* \mathbb{I}(a\_i \leq \text{value}*o < b\_i)}{\sum*{o \in \text{spent outputs}} \text{value}*{o}} \* 100 $$ $$ \[a\_i, bi) \in \[0, 0.01), \[0.01, 0.1), \[0.1, 1), \[1, 10), \[10, 100), \[100, 1k), \[1k, 10k), \[10k, inf) $$ | Metric | Definition | | - | - | | Spent Output Value Bands | Each colored band represents **the total value of spent outputs**, that have a value within the denoted range. | | Spent Output Value Bands USD | Each colored band represents the total value of spent outputs, that have a value within the denoted range **in USD Value**. | | Spent Output Value Bands (%) | Each colored band represents **the ratio of** the total value of spent outputs, that have a value within the denoted range. | ## How to interpret Spent Output Value Bands This indicator can be used to estimate the amount of coins moved by whale and retail holders. As price rises/falls, it is advised to watch out for values in the Spent Output Value Bands to further gain insights on the market through analyzing its participants. Unlike UTXO Value Bands, Spent Output Value Bands focus on the UTXOs that were destroyed within the set metric window. With the help of Spent Output Value Bands, it is possible to pinpoint which sized UTXOs were destroyed in what amount. Using this knowledge, investors can correlate any price movement or changes in the network with the action of whales/retails' action precisely. ### By value itself * **High value(Native Value) & Dominance(%)** in certain Spent Output Value Bands\ \- **Mostly accountable for changes in the network** For example, if the UTXO Value Band of 1k to 10k has the greatest Spent Output Value Bands in terms of value or dominance, it could be interpreted that investors holding at least 1k to 10k are mostly accountable for any price movement or changes that occur in the market within a set metric window. ## Link to Our Data * [Spent Output Value Bands Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/spent-output-value-bands?window=DAY\&priceScale=linear\&metricScale=linear) * [Spent Output Value Bands USD Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/spent-output-value-bands-usd?window=DAY\&priceScale=linear\&metricScale=linear) * [Spent Output Value Bands (%) Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/spent-output-value-bands-percent?window=DAY\&priceScale=linear\&metricScale=linear) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [Spent Output Supply Distribution](/api-reference/btc-network-indicator/spent-output-supply-distribution) # UTXO Count - Value Bands Source: https://docs.cryptoquant.com/data-guide/utxo/utxo-bands-value/utxo-count-value-bands UTXO Count - Value Bands shows the distribution of the number of UTXOs according to its value. ## What is UTXO Count - Value Bands? UTXO Count - Value Bands shows the distribution of the number of UTXOs according to its value. Each colored band represents the number of UTXOs in existence, that has a value within the denoted range. This indicator can be used to estimate the number of whale and retail holders by comparing each band. $$ \text{UTXO Count - Value Bands} =\sum\_{u \in utxos} \mathbb{I}(a\_i \leq \text{value}\_u < b\_i) $$ $$ \text{UTXO Count - Value Bands (%)} =\frac{\sum\_{u \in utxos} \mathbb{I}(a\_i \leq \text{value}*u < b\_i) }{\sum*{u \in utxos} 1} \* 100 $$ $$ \[a\_i, bi) \in \[0, 0.01), \[0.01, 0.1), \[0.1, 1), \[1, 10), \[10, 100), \[100, 1k), \[1k, 10k), \[10k, inf) $$ | Metric | Definition | | - | - | | UTXO Count - Value Bands | Each colored band represents **the number of UTXOs** in existence, that have a value within the denoted range. | | UTXO Count - Value Bands (%) | Each colored band represents **the ratio of** the number of UTXOs in existence, that have a value within the denoted range. | ## How to interpret UTXO Count - Value Bands This indicator can be used to estimate the number of whale and retail holders by comparing each band. UTXO Count- Value Bands could be interpreted as a 'proxy' to the actual holders count that fit according to the Value Band. ### By value itself * **High value(Native Value) & Dominance(%) in certain UTXO Value Band**\ **-** High Number of investors that fit the Value Band For example, if the UTXO Value Band of 1k to 10k has the greatest UTXO Count - Value Bands, 1\) It is possible to interpret it as investors that hold at least 1k to 10k (possible whales) take a large portion of the market in terms of the number of participants. 2\) The price range bought at the time could indicate an important price level in the market in terms of the number of holders. * **Low value(Native Value) & Dominance(%) in certain UTXO Value Band**\ **-**Low Number of investors that fit the Value Band For example, if the UTXO Value Band of 1k to 10k has the least UTXO Count - Value Bands, 1\) It is possible to interpret it as investors that hold at least 1k to 10k (possible whales) take a small portion of the market in terms of the number of participants. 2\) The price range bought at the time could indicate a less important price level in the market in terms of the number of holders. ### By examining trend [#indicating-selling-or-buying-pressure](#indicating-selling-or-buying-pressure) * **Greater UTXO Value Bands Gaining Dominance or Larger in Depth = Increasing** **Whale Dominance**\ \- Holders that have the possibility of being a whale is increasing in numbers * **Smaller UTXO Value Bands Gaining Dominance or Larger in Depth = Decreasing Whale Dominance**\ **-**Holders that have the possibility of being retail is increasing in numbers ## Link to Our Data * [UTXO Count - Value Bands Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/utxo-count-value-bands?window=DAY\&priceScale=linear\&metricScale=linear) * [UTXO Count - Value Bands (%) Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/utxo-count-value-bands-percent?window=DAY\&priceScale=linear\&metricScale=linear) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [UTxO Count Supply Distribution](/api-reference/btc-network-indicator/utxo-count-supply-distribution) # UTXO Value Bands Source: https://docs.cryptoquant.com/data-guide/utxo/utxo-bands-value/utxo-value-bands UTXO Value Bands shows the distribution of all UTXOs according to its value. ## What is UTXO Value Bands? UTXO Value Bands shows the distribution of all UTXOs according to its value. Each colored band represents the total value of all UTXOs, that have a value within the denoted range. This indicator summarizes the behaviors of whales or retails separated by amount of coins they hold along with price actions. $$ \text{UTXO Value Bands} =\sum\_{u \in utxos} \text{value}\_u \* \mathbb{I}(a\_i \leq \text{value}\_u < b\_i) $$ $$ \text{UTXO Value Bands(%)} =\frac{\sum\_{u \in utxos} \text{value}*u \* \mathbb{I}(a\_i \leq \text{value}*u < b\_i)}{\sum*{u \in utxos} \text{value}*{u}}\*100 $$ $$ \[a\_i, bi) \in \[0, 0.01), \[0.01, 0.1), \[0.1, 1), \[1, 10), \[10, 100), \[100, 1k), \[1k, 10k), \[10k, inf) $$ | Metric | Definition | | - | - | | UTXO Value Bands | Each colored band represents **the total value** of all UTXOs, that have a value within the denoted range | | UTXO Value Bands (%) | Each colored band represents **the ratio of** the total value of all UTXOs, that have a value within the denoted range. | ## How to interpret UTXO Value Bands This indicator summarizes the behaviors of whales or retails separated by the amount of coins they hold along with price actions. As price rises/falls, it is advised to watch out for shifting distribution in the UTXO Value Bands to further gain insights on the market through analyzing its participants. \ \ It provides valuable tools for analyzing static macro views of holders' amount distribution (Whale/Retails) in the network and viewing the macro shift in influence difference between Whale and the retails. ### By value itself [#interpretation](#interpretation) * **High value(Native Value) & Dominance(%) in certain UTXO Value Band**\ **-** Value Band's type of investor has more representative For example, if the UTXO Value Band of 1k to 10k has the greatest UTXO Value Band Value, It is possible to interpret it as investors that hold 1k to 10k who are most likely to be whales have more potential of influencing the market. * **Low value(Native Value) & Dominance(%) in certain UTXO Value Band**\ \- Less influence & type of investor has less representative For example, if the UTXO Value Band of 1k to 10k has the lowest UTXO Value Band Value, 1\) It is possible to interpret it as investors that hold 1k to 10k who are most likely to be whales have less potential of influencing the market than other UTXO Value Band. ### By examining trend [#indicating-selling-or-buying-pressure](#indicating-selling-or-buying-pressure) * **Larger UTXO Value Bands Gaining Dominance or Larger in Depth**\ \- More UTXOs are being held in the hands of the possible whales = **Increasing** **Whale Dominance** More UTXOs are being in large quantities that are mostly held by whales. Unlike having mid-sized UTXOs in several numbers, the increasing number of big-sized UTXO (meaning in the amount) is strong evidence of whale presence. \ \ In addition, instead of UTXOs being in small amounts, it could indicate that the individual size of UTXOs is starting to be managed in a big chunk. * **Smaller UTXO Value Bands Gaining Dominance or Larger in Depth**\ **-** More UTXOs are being held in the hands of the possible retail = **Possible** **Decrease of** **Whale Dominance** As more UTXOs are getting a smaller amount in size, it could indicate that retails are gaining more possession of the holdings. #### **Note** [#indicating-the-level-of-exchange-activity](#indicating-the-level-of-exchange-activity) * Identifying the characteristics of UTXOs identical to the wallet/investors might be misleading.\ ex. Whales could have multiple small-sized UTXOs and do not show up in the large value bands. ## Link to Our Data * [UTXO Value Bands Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/utxo-value-bands?window=DAY\&priceScale=linear\&metricScale=linear) * [UTXO Value Bands (%) Live Chart](https://cryptoquant.com/asset/btc/chart/network-indicator/utxo-value-bands-percent?window=DAY\&priceScale=linear\&metricScale=linear) ## Related API Endpoints Query this metric directly from the CryptoQuant Data API: * **BTC** — [UTxO Supply Distribution](/api-reference/btc-network-indicator/utxo-supply-distribution) # API Credits Source: https://docs.cryptoquant.com/guides/api-credits How API credits are granted each month, how much a call costs, and how top-up credits keep your calls running. Every plan is granted API credits each month. Each call deducts credits from that balance, and top-up credits let you keep calling the API without interruption after the monthly grant runs out. ## What are API credits? API credits are the unit consumed when you call the CryptoQuant data API. Every call deducts credits, and once your balance is fully depleted, further API calls fail with a `402 payment_required` response. There are two kinds of credits. | Type | How it's granted | Validity | | - | - | - | | **Plan credits** | Granted automatically every month on all plans, including Basic | Reset monthly, no rollover | | **Top-up credits** | Purchased on demand | 12 months from your last purchase, renewed on each purchase | > [!NOTE] > > You can check your credit balance in real time on the > [Settings > API](https://cryptoquant.com/settings/api) page. ## How much a call costs The credits deducted per API call are not a fixed amount — they depend on **how much and what kind of data** you receive. * **The more data you receive, the more credits are deducted.** The more data rows returned in the response, the higher the deduction. * **Different data types deduct different amounts.** Some data uses more credits than others. * **Failed calls are not charged.** Credits are deducted only when you successfully receive data. The exact credits deducted for each call appear in the usage history on the [Settings > API](https://cryptoquant.com/settings/api) page. ## How credits are used When you call the API, credits are deducted in this order: 1. **Plan credits are always used first.** 2. Once plan credits are fully used up, **top-up credits are used automatically** from the next call onward. No manual switch is needed. 3. When both are depleted, API calls fail with a `402 payment_required` response. Top up or wait for the monthly plan reset to continue. See [Status & Error Codes](/guides/status-codes). On the Premium plan you can call the API without any credit limit. ## Plan credits Plan credits are granted automatically every month. They are given on all plans, including the free Basic plan. * The amount granted depends on your subscribed plan. * Credits reset monthly on your billing date. (Basic plan credits reset based on your signup date.) * Unused credits are cleared at reset and do not roll over to the next month. | Plan | Monthly credits | | - | - | | Basic (Free) | 10,000 | | Advanced | 300,000 | | Professional | 500,000 | | Premium | Unlimited | See [CryptoQuant pricing plans](https://cryptoquant.com/pricing) for what else each plan includes. ## Top-up credits To keep using the API after your plan credits run out, purchase top-up credits. Top-up credits can only be purchased on the **Advanced and Professional** plans. The Basic plan cannot purchase them — upgrade to continue using the API — and the Premium plan has unlimited credits, so no purchase is needed. * Used automatically once plan credits are fully depleted. * **Valid for 12 months from your last purchase.** Each additional purchase renews the validity of your entire remaining top-up balance to 12 months from that point. * Retained regardless of plan credit resets. * Cumulative — each purchase is added to your existing balance. * If you downgrade your plan, your remaining top-up credits can still be used within their validity period. However, **additional purchases are only available on the higher plans** — you cannot purchase on the Basic plan. Each purchase unit is **100,000 credits (US\$5)**. ### How to buy **1. Open the API settings page** Go to [Settings > API](https://cryptoquant.com/settings/api). **2. Start the purchase** Click **Buy credits** to go to the payment page. **3. Complete payment** Once payment is complete, the credits are added to your existing balance. ## Auto-reload When your remaining credits fall below a value you set, top-up credits are purchased automatically. This is useful when you want to keep your balance topped up so API calls are never interrupted. * When your remaining credits (plan and top-up combined) fall below your trigger value, 100,000 credits (US\$5) are purchased automatically. * Purchased credits are added to your existing balance and charged to the card registered for your plan subscription. * Auto-purchases are limited to a maximum of 3 times per day. Once the cap is reached, no further auto-purchases occur that day, and API calls may fail if credits run out. You can turn Auto-reload on and off with the toggle on the [Settings > API](https://cryptoquant.com/settings/api) page. > [!WARNING] > > If you leave Auto-reload off, API calls may fail once your top-up credits are fully used up. ## Checking your credit balance The [Settings > API](https://cryptoquant.com/settings/api) page shows the following in real time: * Plan credits remaining this month * Top-up credit balance * Auto-reload setting status # Authentication Source: https://docs.cryptoquant.com/guides/authentication Authenticate requests with a Bearer token or an api_key query parameter. Each API request requires authentication to identify the member. Authentication is provided through an access token. The token is unique, issued for each client. You can authenticate in one of two ways. ## Access token (recommended) Include the `Authorization` HTTP header with `Bearer ` in every request. ```http theme={null} GET /v1/{PATH} HTTP/1.1 Host: api.cryptoquant.com Authorization: Bearer ``` ```python Python theme={null} import requests headers = {"Authorization": "Bearer " + API_KEY} response = requests.get(URL, headers=headers) ``` ```javascript JavaScript theme={null} const response = await fetch(URL, { headers: { Authorization: `Bearer ${API_KEY}` }, }); ``` ## Query parameter Alternatively, pass your key as the `api_key` query parameter. ```http theme={null} GET /v1/{PATH}?api_key={API_KEY} HTTP/1.1 Host: api.cryptoquant.com ``` ```python Python theme={null} import requests response = requests.get(URL, params={"api_key": API_KEY}) ``` ```javascript JavaScript theme={null} const response = await fetch(`${URL}?api_key=${API_KEY}`); ``` > [!WARNING] > > Prefer the `Authorization` header over the query parameter — URLs are often logged by > proxies and analytics, which can leak keys passed as query parameters. # API Changelog Source: https://docs.cryptoquant.com/guides/changelog Changes to the API itself — new endpoints and indicators, parameter and response changes, deprecations, and documentation updates. This page records changes to the **API itself**. Changes to the data behind it (address labeling rotations, data fixes, backfills) are on the [Data changelog](/guides/changelog-data). * **New** — a new endpoint, indicator, asset, or window is available. * **Improved** — an existing endpoint returns more, or better, without breaking existing clients. * **Changed** — a request or response shape changed; existing clients may need an update. * **Deprecation** — an endpoint or field is scheduled for removal, with the sunset date and the replacement to migrate to. * **Docs** — documentation-only change; no API behaviour changed. * **Beta** — the entry concerns API v2 On-chain Data, in beta since October 8, 2026. **November 9, 2026** **Bitunix is now available as an exchange on API v1.** Pass `exchange=bitunix` to the exchange flow endpoints of these assets: * **BTC** — `/v1/btc/exchange-flows/*` * **ETH** — `/v1/eth/exchange-flows/*` * **XRP** — `/v1/xrp/entity-flows/*` * **Stablecoins** — `/v1/stablecoin/exchange-flows/*` with `token=usdt_eth` or `token=usdc` (on Ethereum), and `token=usdt_trx` (USDT on TRON, `day` window only) Bitunix is also listed in the BTC, ETH, and XRP entity lists and in the `usdt_eth` and `usdc` stablecoin entity lists, classified as a derivatives exchange. **October 23, 2026** **API v2 Ethereum beta temporarily paused.** The Ethereum part of API v2 On-chain Data — native `eth`, ERC-20 tokens, and the stablecoins issued on Ethereum — is paused for performance optimization and will be re-enabled once the updates are complete. Until then: * Requests for an Ethereum asset on the shared `/v2/network/*`, `/v2/flows/exchange/*`, `/v2/indicator/*`, and `/v2/market/capitalization` endpoints return `400` (`Unsupported asset`). * The Ethereum-only endpoints (gas, fees, contract calls, staking, and the other `/v2/network/*` metrics that exist only for `eth`) are withdrawn from the catalog, [`/v2/discovery/endpoints`](/v2/discovery), and this documentation for the duration of the pause. * **Bitcoin on API v2 is unaffected** (`asset=btc` on the shared endpoints and all Bitcoin-only endpoints). * **API v1 is unaffected**: `/v1/eth/*`, `/v1/erc20/*`, and `/v1/stablecoin/*` keep serving as before. The October 8 and 9 entries below describe the Ethereum release as it shipped and are kept for reference. Re-enabling will be announced here. **October 9, 2026** **Stablecoins now have `10min` and `hour` windows on API v2.** [Supply](/v2/network/supply), [Addresses Count](/v2/network/addresses-count), Events Count (`/v2/network/events-count`), and [Tokens Transferred](/v2/network/tokens-transferred) accept `window=10min` and `window=hour` for the `stablecoin` class, alongside the existing `block` and `day`. History follows the v2 rule: `10min` keeps the last 3 months, `hour` the last 12 months. Values aggregate exactly to the `day` series (verified across every stablecoin and bucket before release). **October 14, 2026** **API v2 On-chain Data: shared endpoints now return one field set across assets.** Five shared endpoints carried asset-specific extras inherited from v1. Those are gone, so a client can handle `asset=btc`, `eth`, an ERC-20, or a stablecoin with one response model. The one remaining difference is noted below. * [`/v2/network/tokens-transferred`](/v2/network/tokens-transferred): `tokens_transferred_total_usd` and `tokens_transferred_mean_usd` are now returned for `btc` as well as `eth` (ERC-20 and stablecoin responses still have no USD fields). `tokens_transferred_median` and `tokens_transferred_median_usd` are no longer returned. * [`/v2/flows/exchange/in-house-flow`](/v2/flows/in-house-flow): `btc` now uses the Ethereum field names. `flow_total` is renamed `inhouse_total` and `transactions_count_flow` is renamed `inhouse_transactions_count`; `flow_mean` is dropped (divide `inhouse_total` by `inhouse_transactions_count` if you need it). For Ethereum assets, `inhouse_transfers_count` is no longer returned. * [`/v2/flows/exchange/inflow`](/v2/flows/inflow) and [`outflow`](/v2/flows/outflow): `inflow_mean_ma7` and `outflow_mean_ma7` are no longer returned. To reproduce them, take the `day` window and average `inflow_mean` / `outflow_mean` over a trailing 7-day window. * [`/v2/network/addresses-count`](/v2/network/addresses-count): `addresses_count_sender_percent` and `addresses_count_receiver_percent` are no longer returned for stablecoins. The ratios are `addresses_count_sender / addresses_count_active` and `addresses_count_receiver / addresses_count_active` (multiply by 100 for a percentage, and guard against `addresses_count_active` being 0). v2 is still in beta, which is why field changes like this can land without a version bump. The v1 responses are unchanged. **October 8, 2026** **API v2 On-chain Data now serves Bitcoin, in beta.** 33 Bitcoin-only endpoints join the section, and 22 of the Ethereum endpoints — network data, exchange flows, Exchange Supply Ratio, and Capitalization — now accept `asset=btc` (add `chain=bitcoin` if you want to be explicit). 95 endpoints in total. * **Mining pool flows** under [`/v2/flows/mining-pools/*`](/v2/flows/mining-pools/inflow) — inflow, outflow, netflow, reserve, transactions count, addresses count, and in-house flow, with the `miner` parameter (`all_miner` for the aggregate). * **Inter-entity flows** under [`/v2/flows/inter-entity/*`](/v2/flows/inter-entity/exchange-to-exchange) — exchange↔exchange, exchange↔miner, and miner↔miner, with `from_*`/`to_*` parameters. * **Indicators** regrouped by meaning under `/v2/indicator/*`: selling activity (CDD, Dormancy, Exchange Whale Ratio, Fund Flow Ratio, Exchange Shutdown Index, Mining Pool Supply Ratio, Stablecoin Supply Ratio), [valuation](/v2/indicator/nvt) (NVT, NVT Golden Cross, NVM, Puell Multiple, Stock to Flow), [profit & loss](/v2/indicator/mvrv) (MVRV, NUPL, PnL Index, NRPL, SOPR, SOPR Ratio), Realized Price, Mean Coin Age, and Estimated Leverage Ratio. [UTXO Count](/v2/network/utxo-count) joins network data. * **Capitalization** for `asset=btc` returns all five models — market, realized, average, delta, and thermo cap. * v1's `/v1/btc/*` groups map onto these paths as listed under [Coming from v1](/v2/onchain/overview#coming-from-v1) on the overview; metric definitions and metric field names are unchanged. The time key differs: v2 returns `datetime` for every window (v1 used `date` for daily rows). **Known issues at launch** * [Exchange Supply Ratio](/v2/indicator/exchange-supply-ratio) serves `block` only for `btc`, while the endpoint's default window is `day`. A request for `asset=btc` **must pass `window=block`**; omitting `window` returns `400`. * The Bitcoin exchange and mining pool indicators (Exchange Whale Ratio, Fund Flow Ratio, Exchange Shutdown Index, Mining Pool Supply Ratio, Exchange Supply Ratio) and Estimated Leverage Ratio serve `block` only; v1's `day` and `hour` windows for these will follow. * Bitcoin series are refreshed hourly, so `block` rows for `asset=btc` can trail the chain tip by up to about an hour. As with the Ethereum beta, endpoint shapes are final but historical values may still be corrected; changes will be listed here. **October 8, 2026** **API v2 On-chain Data is live in beta for Ethereum.** 62 endpoints under `/v2/network/`, `/v2/flows/`, `/v2/indicator/`, and `/v2/market/capitalization` serve network activity, exchange flows, and supply for native ETH, ERC-20 tokens, and the stablecoins issued on Ethereum. * **One path per metric, with the asset as a query parameter.** v1's `/v1/eth/network-data/supply`, `/v1/erc20/network-data/supply?token=aave`, and `/v1/stablecoin/network-data/supply?token=usdt_eth` become [`/v2/network/supply`](/v2/network/supply) with `?asset=eth`, `?asset=aave`, and `?asset=usdt`. The `asset` value drops the chain suffix — `usdt`, not `usdt_eth`. * **Available windows and response fields depend on the asset class.** `eth` and `erc20` supply is served at `block`, `10min`, `hour`, and `day`; `stablecoin` supply at `block` and `day`, with three extra fields for circulating supply. Every endpoint page carries the table for its own classes. * [**In-House Flow**](/v2/flows/in-house-flow) is new for Ethereum — movement between wallets of the same exchange, previously available only for Bitcoin. * Same `status`/`result` envelope, Bearer authentication, and `window`/`from`/`to` time convention as the rest of the API. See the [On-chain Data Overview](/v2/onchain/overview) for the full v1 → v2 path mapping. v1 remains fully supported. During the beta, endpoint shapes are final but we may still correct historical values; changes will be listed here. **Known issue at launch** * `exchange=all_exchange` on `/v2/flows/exchange/*` for some ERC-20 tokens (for example `busd`) is aggregated over a per-token exchange whitelist, the same rule the v1 `/erc20/exchange-flows/*` endpoints use. The total can therefore differ from the sum of the individual exchanges returned for the same token. Per-exchange values are exact. **October 7, 2026** **Sentiment Data documentation moved here.** The Analyst Consensus API reference — previously hosted at `consensus.cryptoquant.com/docs/api` — now lives in the new [Sentiment Data](/sentiment/overview) tab, so every CryptoQuant API is documented in one place. * Eight endpoints: the [Analyst Consensus Index](/sentiment/consensus-index), the [Consensus Breakdown](/sentiment/consensus-breakdown), [Analyst Stance](/sentiment/analyst-stance), [Analyst Views](/sentiment/analyst-views), [Recent Calls](/sentiment/calls), [Top Analysts](/sentiment/top-analysts), [Analyst Track Record](/sentiment/analyst-track-record) and the [asset registry](/sentiment/assets). * Its own [authentication](/sentiment/authentication) (`X-API-Key`), [plans](/sentiment/plans-and-access), [enums](/sentiment/enums), [error codes](/sentiment/errors) and [agent surfaces](/sentiment/for-agents) (OpenAPI, `llms.txt`, MCP). The API itself is unchanged — base URL `https://consensus.cryptoquant.com/api/v1/`. **August 19, 2026** **API v2 Market Data is live.** A new market data layer under the `/v2/market/` namespace serves raw market time-series — prices, volumes, and derivatives metrics — both per individual exchange and as CryptoQuant's cross-exchange aggregate. * Five metrics: [OHLCV](/v2/market/exchange-spot-ohlcv), [Trade](/v2/market/exchange-spot-trade), [Funding Rate](/v2/market/exchange-swap-funding-rate), [Open Interest](/v2/market/exchange-swap-open-interest), and [Liquidation](/v2/market/exchange-swap-liquidation), across `spot` and `swap` instruments. * Two discovery endpoints — [List Active Exchanges](/v2/market/info-exchanges) and [List Active Symbols](/v2/market/info-symbols) — to enumerate the exchanges and symbols that currently have data. * Same `status`/`result` envelope, Bearer authentication, and `window`/`from`/`to` time convention as the rest of the API. See the [Market Data Overview](/v2/market/overview). **June 12, 2026** **API v2 community-built indicators are live.** A new curated indicator layer built by the CryptoQuant **Vibe Quants** community is now available under the `/v2/community/` namespace. * 10 research-grade Bitcoin indicators released, including [Apparent Demand](/v2/community/bitcoin-apparent-demand), [MVRV Z-score](/v2/community/bitcoin-mvrv-z-score), [Metcalfe's Price](/v2/community/bitcoin-metcalfe-price), [PnL Index](/v2/community/bitcoin-pnl-index), and the [Bull-Bear Market Indicator](/v2/community/bitcoin-bull-bear-indicator). * Every metric ships with a built-in interpretation guide — what it measures, how to read it, key thresholds, and which signals to combine it with. * Same `status`/`result` envelope, Bearer authentication, and `window`/`from`/`to` time convention as v1. See the [API v2 Overview](/v2/overview) and [v2 Metric Catalog](/v2/catalog). **November 28, 2025** We have removed all Klaytn-related data from our platform. * All API endpoints under `/v1/klay/**` have been deprecated and will no longer return data. **October 14, 2025** The following change has been applied on October 14, 2025 (UTC). * A new API for **TRX (Tron)** has been added. This includes on-chain metrics such as market data, network data and DeFi. ([API Reference](/api-reference/trx-market-data/price-ohlcv)) * A new stablecoin **USDT(TRX)** (`usdt_trx`) has been added. ([Supported Stablecoin List](/catalog/supported-stablecoins)) **August 28, 2025** We decided to halt the updates of the below data on our platform. * Tether USD (Omni) `usdt_omni` — in accordance with the [official announcement by Tether](https://tether.io/news/tether-provides-an-update-on-prioritizing-community-preferences-for-blockchain-support-in-strategic-shift), data is not updated from September 1, 2025. * Sai (Old Dai) `sai` — migrated to DAI, deprecated. * HTX USD `husd` — unused after 2023, deprecated. * USDK `usdk` — unused after 2023, deprecated. * COCOS-BCX `cocos`, DeRace Token `derc`, Merit Circle `mc`, Tribe `tribe`, Serum `srm` ## Past changelog Entries written before 2025 are archived on Notion: * [Changelog archive (2022–2024)](https://cqlive.notion.site/CryptoQuant-Changelog-0ef73c0c86254b4b90100b76443f6074) # Data Changelog Source: https://docs.cryptoquant.com/guides/changelog-data Changes to the data itself — address labeling and entity re-clustering rotations, data fixes, and backfills that change served values. This page records changes to the **data itself**. API changes (new endpoints, parameters, deprecations) are on the [API changelog](/guides/changelog). * **Labeling** — our address labels for an exchange, miner, or other entity changed, and the affected datasets were re-computed and swapped into serving. One entry per swap; the date is the day the new data went live. Entity-level detail lives on the linked Notion page. * The **API v1 / API v2** badge on each entry says which API served the changed data. API v2 On-chain Data launched in beta on October 8, 2026, so earlier entries are v1 only. BTC v1 and v2 share one dataset, so BTC entries after the launch carry both badges. ETH v1 and v2 are computed separately; XRP and TRON data is served on v1 only. * **Data Fix** — a served value was wrong and has been corrected. * **Backfill** — history was extended or re-filled. **November 5, 2026** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Exchange flows and reserves for every served stablecoin and ERC-20 token were recomputed from each token's deployment with addresses labeled through 2026-10-28 and swapped into serving. New or updated address labels: OKX (about 21,000 addresses), Bybit, Coinbase Prime, Bitget, Coinbase Advanced, BitMEX, Binance, CoinEx and 7 more (MEXC, HTX Global, KuCoin, Deribit, Gate.io, Coinhako, Gemini). Entity set unchanged. Largest reserve revisions: OKX (about +$2.5B), MEXC (+$620M), Bybit (+\$320M), and CoinEx and HTX Global, whose ERC-20 holdings are now attributed for the first time; all-exchange reserve is about 6.5% higher, mostly USDT and USDC. **November 3, 2026** API v1 API v2 **BTC exchange and miner labels re-clustered.** Entity flows and reserves were recomputed and swapped into serving on both API v1 and API v2. Two label changes went in: about 91,000 exchange addresses registered between October 2025 and April 2026 that had never reached the serving label set are now counted (mostly Kraken deposit addresses, plus Coinbase, Binance, Bybit, Bithumb, KuCoin, OKX and Coinone wallets), and the weekly clustering pass propagated labels to roughly 420,000 more addresses in already-labeled clusters (largest: KuCoin, Coinbase, OKX, Antpool, Indodax, F2Pool, Huobi Pool, BTC.com). Entity set unchanged (73 entities). Largest reserve revisions: Coinbase, Binance, Bybit, Bithumb, KuCoin, OKX, Kraken — all-exchange reserve is up about 105K BTC; miner reserves are essentially unchanged. Kraken's historical inflow and outflow volumes rose materially because its deposit addresses are now attributed. **November 2, 2026** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH were recomputed from genesis with addresses labeled through 2026-10-28 and swapped into serving. New or updated address labels: OKX, Bybit, Coinbase, Bitget, Binance, CoinEx and 9 more (MEXC, BitMEX, HTX, Bithumb, Gemini, KuCoin, Deribit, Gate.io, Coinhako). Entity set unchanged. Largest reserve revisions: Coinhako (a newly labeled hot wallet adds about 50,000 ETH from September 2024 onward), Bybit, OKX, CoinEx, MEXC; all-exchange reserve is about 0.7% higher. **October 29, 2026** API v1 **TRON USDT exchange labels re-clustered.** `usdt_exchange_flow` for Tron was recomputed through 2026-10-28 and swapped into serving. Values changed for all-exchange. **October 22, 2026** API v1 API v2 **BTC exchange and miner labels re-clustered.** Entity flows and reserves were recomputed and swapped into serving on both API v1 and API v2 (first BTC rotation since the v2 beta launch). Two label changes went in: about 4,700 proof-of-reserve addresses registered since April for OKX, MEXC, Binance, Bybit, and CoinEx are now counted, and roughly 2.2 million addresses that sat in already-labeled clusters without an entity label now inherit the cluster's label (largest: Coinbase, F2Pool, BTC.com, Bybit, OKX, Kraken, Crypto.com, MEXC). Entity set unchanged (73 entities). Largest reserve revisions: OKX, Binance, MEXC, Bybit, Deribit, Bithumb among exchanges; Poolin, Foundry USA, BitMinter, BTC.com among miners. **October 2, 2026** API v1 **TRON USDT exchange labels re-clustered.** `usdt_exchange_flow` for Tron was recomputed through 2026-10-01 and swapped into serving. Row counts changed for all-exchange, Binance, Bitget, Bybit, HTX Global, and KuCoin. **September 15, 2026** API v1 **TRON USDT exchange labels re-clustered.** `usdt_exchange_flow` for Tron was recomputed through 2026-09-14 and swapped into serving. First rotation on the new pipeline. **July 10, 2026** API v1 **BTC exchange and miner labels re-clustered.** Entity flows and reserves were recomputed and swapped into serving. 68 inactive exchanges were removed from the entity set (e.g. AAX, AscendEX, CoinTiger, Crypto.com, Binance.US, CoinEx, CoinList Pro, DigiFinex). Largest reserve revisions: Poolin, Lubian, Bitfury, Coinbase Prime, P2PB2B, BTC.com, Huobi Pool. **June 29, 2026** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-12-31. New or updated address labels: Coinbase, Upbit, BitMEX. New exchanges added to the entity set: dYdX. Renamed: Gate.io. **June 29, 2026** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. Clustering refreshed only. **June 1, 2026** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: OKX, Bybit, BitMEX, Binance. **March 16, 2026** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: OKX, Bybit, BitMEX, Coinbase Prime, Binance, Bitget and 3 more. **March 9, 2026** API v1 **BTC exchange and miner labels re-clustered.** Entity flows and reserves recomputed and swapped into serving. New or updated address labels: OKX, Binance, BitMEX. **February 27, 2026** API v1 **BTC exchange and miner labels re-clustered.** Entity flows and reserves recomputed and swapped into serving. New or updated address labels: OKX, BitMEX, Bybit, Bithumb, HTX. **February 6, 2026** API v1 **BTC exchange and miner labels re-clustered.** Entity flows and reserves recomputed and swapped into serving. New or updated address labels: Coinbase, OKX, BitMEX, Binance. **January 22, 2026** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-12-03. New or updated address labels: Coinbase, KuCoin, BitMEX. New exchanges added to the entity set: Alpaca, ApeX, Arkham, BTCBOX, Backpack, Bequant, Bit2C, Bitbns and 19 more. **January 22, 2026** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Coinbase, Bybit, BitMEX. **January 12, 2026** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-11-05. New or updated address labels: Coinbase, Bithumb, BitMEX, MEXC, Kraken, SwissBorg and 3 more. **December 28, 2025** API v1 **BTC exchange and miner labels re-clustered.** Entity flows and reserves recomputed and swapped into serving. BTC entity clustering moved to the new pipeline; the cut-over rotations between December 15 and 28 are folded into this entry. New or updated address labels: OKX, Coinbase, BitMEX, Twenty One Capital (bank), Binance. **December 22, 2025** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-10-01. New or updated address labels: Coinbase, Kraken, BitMEX, SwissBorg, BlockFi (bank), FalconX. **December 22, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Coinbase, Upbit, BitMEX. **December 5, 2025** API v1 **BTC exchange and miner labels re-clustered.** Addresses labeled through 2025-11-10. New or updated address labels: Kraken, OKX, Korbit, Bithumb, BitMEX, KuCoin and 1 more. **November 26, 2025** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-09-10. New or updated address labels: Coinbase, Bybit, OKX, Binance, BitMEX, Upbit and 5 more. **November 26, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Coinbase. **November 11, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Coinbase, KuCoin, BitMEX, Bithumb, Kraken, MEXC and 4 more. **November 5, 2025** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-07-31. No new labels since the previous rotation; clustering refreshed only. **October 26, 2025** API v1 **BTC exchange and miner labels re-clustered.** Addresses labeled through 2025-10-07. New or updated address labels: Kraken, BitMEX, BingX. **October 20, 2025** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-07-31. No new labels since the previous rotation; clustering refreshed only. **October 1, 2025** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-07-31. No new labels since the previous rotation; clustering refreshed only. New exchanges added to the entity set: Bullish, FalconX. **September 29, 2025** API v1 **BTC exchange and miner labels re-clustered.** Addresses labeled through 2025-09-05. New or updated address labels: OKX, Crypto.com, BitMEX, Bybit, Binance, Kraken. **September 26, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Coinbase, Kraken, BitMEX, BlockFi (bank), Crypto.com. **September 8, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Coinbase, BitMEX, OKX, Bybit, Binance, Crypto.com. **September 5, 2025** API v1 **Stablecoin & ERC-20 entity flows moved to the v2 pipeline.** Labels re-clustered with addresses through 2025-07-31; the August roll-out rotations are folded into this entry. New or updated address labels: OKX, Coinbase, Upbit, Bithumb, Bybit, KuCoin and 16 more. **August 21, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Coinbase, Upbit, Binance, Bithumb, HTX. **August 12, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Coinbase, Bybit, Binance, Kraken, Deribit. **August 8, 2025** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-03-31. No new labels since the previous rotation; clustering refreshed only. **August 7, 2025** API v1 **BTC exchange and miner labels re-clustered.** Addresses labeled through 2025-07-15. New or updated address labels: Kraken, OKX, Bybit, Bitstamp, ViaBTC (miner), BitMEX and 31 more. **July 25, 2025** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-03-31. No new labels since the previous rotation; clustering refreshed only. **July 14, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Coinbase, Upbit, Bithumb, Bybit, Binance, BitMEX and 2 more. **July 4, 2025** API v1 **BTC exchange and miner labels re-clustered.** Addresses labeled through 2025-06-08. New or updated address labels: OKX, KuCoin, BitMEX, Robinhood, Binance. **July 1, 2025** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-03-31. No new labels since the previous rotation; clustering refreshed only. **June 23, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Bybit, Coinbase, Coinbase Prime, Bitget, Robinhood, BitMEX and 1 more. **June 10, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: BitMEX, Binance. **May 27, 2025** API v1 **BTC exchange and miner labels re-clustered.** Addresses labeled through 2025-05-05. New or updated address labels: OKX, BitMEX, KuCoin, Binance, HTX, Bitunix and 4 more. **May 21, 2025** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-03-31. New or updated address labels: Bybit. New exchanges added to the entity set: Bingx, Bitunix. **May 16, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: OKX, KuCoin. **April 28, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: OKX, Copper (custody), HTX, Kraken, Upbit, CoinEx and 7 more. **April 25, 2025** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2025-03-03. New or updated address labels: Phemex, Coinbase Prime, Coinbase, Binance, Bitvavo, Bitget and 22 more. **April 22, 2025** API v1 **BTC exchange and miner labels re-clustered.** Addresses labeled through 2025-04-05. New or updated address labels: Metaplanet (bank), Bybit, HashKey. **March 27, 2025** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2024-08-31. No new labels since the previous rotation; clustering refreshed only. **March 19, 2025** API v1 **BTC exchange and miner labels re-clustered.** Addresses labeled through 2025-02-24. New or updated address labels: BitMEX, Upbit, Binance, AntPool (miner), ZB.com, Coinone and 26 more. **March 14, 2025** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2024-08-31. No new labels since the previous rotation; clustering refreshed only. **March 10, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Bybit, Binance. **February 6, 2025** API v1 **BTC exchange and miner labels re-clustered.** Addresses labeled through 2024-11-27. New or updated address labels: BitMEX, Upbit, Bitget, Deribit, River, Bybit and 1 more. **January 2, 2025** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Binance, Bybit, Bithumb. **November 27, 2024** API v1 **Stablecoin & ERC-20 entity labels re-clustered.** Addresses labeled through 2024-08-31. New or updated address labels: Coinbase, Binance, BtcTurk, Coinbase Prime, Kraken, Nexo and 57 more. New exchanges added to the entity set: Lbank, River Financial. **November 27, 2024** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Deribit, Poloniex. **November 7, 2024** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Coinbase, Coinbase Prime, Bitget, Bitvavo, LBank, Uphold and 15 more. **October 17, 2024** API v1 **ETH exchange labels re-clustered.** Exchange flows and reserves for ETH recomputed and swapped into serving. New or updated address labels: Phemex, Coinbase Prime, Coinbase, Independent Reserve, Cobo (custody), Binance and 9 more. **October 14, 2024** API v1 **BTC exchange and miner labels re-clustered.** Entity flows and reserves recomputed and swapped into serving. ## Past changelog Entries before October 2024 predate API v2 and describe **API v1 data only**. They are archived on Notion: * [Changelog archive (2022–2024)](https://cqlive.notion.site/CryptoQuant-Changelog-0ef73c0c86254b4b90100b76443f6074) # Data Latency Source: https://docs.cryptoquant.com/guides/data-latency How fresh each metric is — append /latency to any v1 endpoint to see block and process delay. Every v1 data endpoint exposes a **`/latency`** sibling that reports how long after a block the metric's data becomes available. Append `/latency` to **any** v1 endpoint path — keep the `//` path you're already calling and add `/latency`: ```bash theme={null} # Pattern — works for every v1 data endpoint curl "https://api.cryptoquant.com/v1////latency" \ -H "Authorization: Bearer YOUR_API_KEY" # Example: /btc/exchange-flows/reserve → add /latency curl "https://api.cryptoquant.com/v1/btc/exchange-flows/reserve/latency" \ -H "Authorization: Bearer YOUR_API_KEY" ``` The [Data Catalog](/catalog/btc) shows these values under each section's **Data latency** panel — expand it and switch resolution tabs to see the block and process delay per window. [`catalog.json`](/catalog/catalog.json) carries the full breakdown for every metric. ## What the numbers mean The response reports two delays, per resolution (`day`, `hour`, `min`, and `block` where supported) and averaging window: | Field | Meaning | | - | - | | `block` | The delay within the blockchain network — consensus time, block creation time, and related factors. | | `process` | Delay from data processing within the platform. CryptoQuant avoids using the latest block to prevent block-data reorganization, ensuring data consistency over time. | | `mutable` | Whether values that were already served may still be revised later. | Each resolution reports the delay averaged over two windows (e.g. `7day` / `30day` for `day`, `10min` / `60min` for `block`). Durations are returned in ISO-8601 form, e.g. `P0DT0H16M23.5S` means 16 minutes 23.5 seconds. ## Try it live The playground below targets `reserve/latency` as an example — the response shape is identical for every endpoint, so swap in any path to check another metric. [**Reserve Latency** in the API Reference →](/api-reference/latency/reserve-latency) ## How to read the response ```json theme={null} { "status": { "code": 200, "message": "success" }, "result": { "data": [ { "all_parameters": true, "day": [ { "block": { "7day": "P0DT0H13M56.7S", "30day": "P0DT0H10M39.8S" }, "process": { "7day": "P0DT0H26M15.2S", "30day": "P0DT0H29M7.8S" }, "mutable": true } ] } ] } } ``` In this example, for the `day` resolution averaged over the last 7 days, the network (`block`) delay is about 14 minutes and the platform processing (`process`) delay about 26 minutes. # Frequently Asked Questions Source: https://docs.cryptoquant.com/guides/faq Answers to common questions about the CryptoQuant API — authentication, rate limits, credits, data freshness, supported assets, response format, pricing, and the MCP server. ## 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](/catalog/overview) for the full list. ### How do I get an API key? API access is available on [CryptoQuant pricing plans](https://cryptoquant.com/pricing). Once you subscribe, your access token appears in your [account settings](https://cryptoquant.com/settings/api). See the [Quickstart](/guides/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](/guides/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](/guides/status-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](/guides/mcp-server) gives you a dedicated rate limit instead of the shared keyless pool. Rate limits are separate from [API credits](/guides/api-credits), which meter how much data you consume. ### How are API credits consumed? Every call deducts credits from your monthly plan grant, and the amount depends on how many data rows the response returns and which data you requested. Failed calls are not charged. Once plan credits run out, top-up credits are used automatically — and on the Premium plan there is no credit limit at all. See [API Credits](/guides/api-credits). ### 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](/guides/status-codes). ## Data & response format ### What does an API response look like? Every response wraps data in a `status` / `result` envelope: ```json theme={null} { "status": { "code": 200, "message": "success" }, "result": { "window": "day", "data": [ { "date": "2026-06-11", "reserve": 540321.2, "reserve_usd": 58234567890.1 } ] } } ``` ### 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](/guides/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](/catalog/overview) or the machine-readable [`/catalog/catalog.json`](/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](/guides/mcp-server) and the [For AI Agents](/guides/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`](/catalog/catalog.json) plus the [OpenAPI specs](/openapi/v1.json) for endpoint definitions. Details on the [For AI Agents](/guides/for-ai-agents) page. ### What does each metric actually mean? See the [On-Chain Metrics Glossary](/guides/glossary) for quick definitions, or the [Data Guide](/data-guide/exchange) for full formulas and interpretation of every metric. # For AI Agents Source: https://docs.cryptoquant.com/guides/for-ai-agents Single entry point for AI agents: MCP server, machine-readable catalogs, OpenAPI specs, and raw Markdown access. This page is the map. If you are an AI agent (or building one), everything you need to discover and consume CryptoQuant data is listed here. ## Query data directly — MCP server ```text theme={null} https://mcp.cryptoquant.com/mcp ``` Connect via Claude.ai connectors, Claude Desktop, Claude Code, or Cursor — setup in the [MCP guide](/guides/mcp-server). Supports API-key auth (dedicated rate limit) or keyless (shared pool). 245+ metrics across BTC, ETH, TRX, XRP, Stablecoin, ERC20, ALT. Analyst sentiment (the Analyst Consensus Index, analyst views, calls and track records) has its own keyless MCP server at `https://consensus.cryptoquant.com/mcp` — see [Sentiment Data → For AI Agents](/sentiment/for-agents). ## Discover what exists — machine-readable catalogs | Resource | What it contains | | - | - | | [`/catalog/catalog.json`](/catalog/catalog.json) | Every v1 and v2 metric: category, endpoint path, parameters, response field names, and a `docs` path to the page documenting it | | [`/legacy-redirect-map.json`](/legacy-redirect-map.json) | Mapping from legacy `cryptoquant.com/docs#operation/...` anchors to pages on this site | | [`/openapi/v1.json`](/openapi/v1.json) | Full v1 OpenAPI 3.0 spec — 242 endpoints with schemas and examples | | [`/openapi/v2.json`](/openapi/v2.json) | v2 (beta) OpenAPI spec — curated research indicators | | `/llms.txt` · `/llms-full.txt` | Index and full content of this documentation | | [`/openapi/sentiment.json`](/openapi/sentiment.json) | Sentiment Data (Analyst Consensus API) OpenAPI 3.1 spec — snapshot of [consensus.cryptoquant.com/openapi.json](https://consensus.cryptoquant.com/openapi.json) | ## Read any page as Markdown Append `.md` to any page URL: ```text theme={null} GET /v2/community/bitcoin-mvrv-z-score.md ``` ## Understand what the numbers mean Raw data without context produces bad analysis. Use these alongside the endpoints: * **[v2 Metric Guides](/v2/catalog)** — per-metric interpretation: what it measures, key thresholds, and how to combine signals (e.g. MVRV Z-score below its 365-day MA = high-conviction bear signal). * **[Data Guide](/data-guide/exchange)** — definitions, formulas, and interpretation for every v1 metric family (exchange flows, SOPR, MVRV, CDD, ...). * **[Glossary](/guides/glossary)** — one-line, answer-first definitions of every key metric with formulas and links. * **[FAQ](/guides/faq)** — common questions on auth, rate limits, data freshness, response format, and MCP. * **[Time Convention](/guides/time-convention)** — how `window`, `from`, `to` behave, and when end-of-day data becomes final (UTC 01:00). ## Call the API * Base URLs: `https://api.cryptoquant.com/v1/` · `https://api.cryptoquant.com/v2/` (beta) * [Authentication](/guides/authentication): `Authorization: Bearer {access_token}` * Every response: `{ "status": { "code", "message" }, "result": { "window", "data": [...] } }` * [Status & error codes](/guides/status-codes) — `429` means back off; rate limits are per-plan. # On-Chain Metrics Glossary Source: https://docs.cryptoquant.com/guides/glossary Plain-language definitions of every key CryptoQuant metric — MVRV, SOPR, NVT, CDD, exchange reserve, netflow, funding rate, NUPL, and more — with formulas and links to full guides. A quick-reference glossary of the on-chain and market metrics available through the CryptoQuant API. Each entry gives a one-line definition, the formula where relevant, and a link to the full guide. For machine-readable definitions of every endpoint, see [`/catalog/catalog.json`](/catalog/catalog.json). ## Valuation metrics ### What is MVRV (Market Value to Realized Value)? MVRV is an asset's market capitalization divided by its realized capitalization. It shows whether the market price is above (MVRV > 1, aggregate profit) or below (MVRV \< 1, aggregate loss) the average price at which all coins last moved. → [MVRV Ratio guide](/data-guide/market/mvrv-ratio) ### What is the MVRV Z-Score? The MVRV Z-Score standardizes MVRV by how many standard deviations it sits from its historical mean. It is used to detect cycle tops (extreme high) and bottoms (extreme low). → [MVRV Z-Score](/v2/community/bitcoin-mvrv-z-score) ### What is Realized Price? Realized Price is realized capitalization divided by circulating supply — the average cost basis of the entire market. It often acts as support in bull markets and resistance in bear markets. → [Realized Price guide](/data-guide/market/realized-price) ### What is NUPL (Net Unrealized Profit/Loss)? NUPL measures the total paper profit or loss of all coins as a share of market cap: `(Market Cap − Realized Cap) / Market Cap`. Positive means the market is in net unrealized profit; negative means net unrealized loss. → [NUPL guide](/data-guide/utxo/net-unrealized-profit-and-loss-nupl) ## Spending behavior (UTXO) metrics ### What is SOPR (Spent Output Profit Ratio)? SOPR is the realized profit ratio of coins moved on-chain — the value of spent outputs at the time of spending divided by their value when created. SOPR > 1 means coins are moving in profit; SOPR \< 1 means in loss; SOPR = 1 is the break-even level that often acts as support/resistance. → [SOPR guide](/data-guide/utxo/spent-output-profit-ratio-sopr) ### What is CDD (Coin Days Destroyed)? CDD weights each transaction by how long the coins had been dormant (coins × days held), surfacing the activity of long-term holders. A spike signals that old, "strong" hands are moving. → [CDD guide](/data-guide/utxo/coin-days-destroyed-cdd) ### What is Mean Coin Age (MCA)? Mean Coin Age is the average dormancy of the circulating supply, weighted by coin-days. A rising MCA indicates accumulation/holding; a falling MCA indicates distribution/spending. → [Mean Coin Age guide](/data-guide/utxo/mean-coin-age-mca) ### What are UTXO Age Bands? UTXO Age Bands group all unspent outputs by how long ago they last moved, separating long-term-holder supply from short-term-trader supply. → [UTXO Bands (Age)](/data-guide/utxo/utxo-bands-age) ## Exchange flow metrics ### What is Exchange Reserve? Exchange Reserve is the total amount of a coin held in known exchange wallets. A falling reserve suggests coins moving to self-custody (typically accumulation); a rising reserve suggests potential selling pressure. → [Exchange Reserve guide](/data-guide/exchange/exchange-reserve) ### What are Exchange Inflow, Outflow, and Netflow? Inflow is coins sent *to* exchanges, outflow is coins sent *from* exchanges, and netflow is inflow minus outflow. Large inflows can signal sell intent; large outflows can signal accumulation. → [Inflow/Outflow/Netflow guide](/data-guide/exchange/exchange-in-outflow-and-netflow) ### What is the Exchange Whale Ratio? The Exchange Whale Ratio is the share of the top-10 largest inflow transactions in total exchange inflow. A high ratio indicates whales are dominating exchange deposits, often a sign of incoming volatility. → [Exchange Whale Ratio guide](/data-guide/market/exchange-whale-ratio) ### What is the Fund Flow Ratio? The Fund Flow Ratio is the share of on-chain transaction volume that involves exchanges, showing how much network activity is exchange-related. → [Fund Flow Ratio guide](/data-guide/exchange/fund-flow-ratio) ## Network valuation metrics ### What is the NVT Ratio? NVT (Network Value to Transactions) is market capitalization divided by on-chain transacted volume — a "price-to-earnings" analogue for blockchains. A high NVT can indicate overvaluation relative to network usage. → [NVT Ratio guide](/data-guide/network/nvt-ratio) ### What is the Puell Multiple? The Puell Multiple is daily coin issuance value (USD) divided by its 365-day moving average. It measures miner revenue relative to its yearly norm, marking cycle extremes. → [Puell Multiple guide](/data-guide/network/puell-multiple) ### What is the Stock-to-Flow (S2F) Ratio? Stock-to-Flow is circulating supply divided by newly issued supply, quantifying scarcity. A higher S2F means new supply is small relative to existing supply. → [Stock-to-Flow guide](/data-guide/network/stock-to-flow-ratio) ## Derivatives & market metrics ### What is Open Interest? Open Interest is the total value of outstanding derivatives contracts (futures/perpetuals) that have not been settled. Rising OI means new money/leverage entering the market. → [Open Interest guide](/data-guide/market/open-interest) ### What is the Funding Rate? The Funding Rate is the periodic payment exchanged between long and short perpetual-futures holders. Positive funding means longs pay shorts (bullish leaning); negative means shorts pay longs. → [Funding Rate guide](/data-guide/market/funding-rates) ### What is the Estimated Leverage Ratio (ELR)? ELR is exchange open interest divided by exchange reserve — an estimate of how much leverage traders are taking per unit of coin held on the exchange. → [Estimated Leverage Ratio guide](/data-guide/market/estimated-leverage-ratio) ### What is the Taker Buy/Sell Volume Ratio? This ratio compares aggressive market-buy volume to aggressive market-sell volume from takers, indicating short-term directional pressure. → [Taker Buy/Sell guide](/data-guide/market/taker-buy-sell-volume-ratio) ## Miner metrics ### What is the Miners' Position Index (MPI)? MPI is the USD value of total miner outflow divided by its 365-day moving average. A high MPI indicates miners are selling more than usual. → [MPI guide](/data-guide/miner/miners-position-index) ### What is Miner Outflow? Miner Outflow is the total amount of coins sent from miner wallets, used to track miner selling behavior. → [Miner Outflow guide](/data-guide/miner/miner-outflow) ## Fund & premium metrics ### What is the Coinbase Premium? The Coinbase Premium is the price gap between Coinbase Pro (USD pair) and Binance (USDT pair). A positive premium suggests stronger U.S. institutional buying. → [Coinbase Premium guide](/data-guide/fund-premium/coinbase-premium) ### What is the Korea Premium Index (Kimchi Premium)? The Korea Premium Index is the percent difference between prices on Korean exchanges and other exchanges, reflecting regional demand. → [Korea Premium guide](/data-guide/fund-premium/korea-premium-index) > [card] [Browse every metric with parameters and response fields](/catalog/overview) > > See the full Metric Catalog for endpoints, parameters, and response schemas. # Local MCP Installation Source: https://docs.cryptoquant.com/guides/mcp-local Install the CryptoQuant MCP server locally for Claude Desktop, Claude Code, or Cursor by editing your MCP config file — for developers integrating into their own workflows. ### Quick Start #### Connecting Claude / Cursor > ⚠️ **Prerequisites**: Node.js v18 or higher must be installed. You can download it [from nodejs.org](https://nodejs.org/en/download). **Step 1: Locate the MCP Configuration File** | App | Configuration File Path | | - | - | | **Claude Desktop (Mac)** | `~/Library/Application Support/Claude/claude_desktop_config.json` | | **Claude Desktop (Windows)** | `%APPDATA%\Claude\claude_desktop_config.json` | | **Claude Code** | `~/.claude.json` or project `.mcp.json` | | **Cursor** | Project `.cursor/mcp.json` | **Step 2: Add Settings** Add the following settings to your MCP configuration file: ```json theme={null} { "mcpServers": { "cryptoquant": { "command": "npx", "args": ["-y", "cryptoquant-mcp"] } } } ``` **Step 3: Restart the App** After saving the configuration file, completely close the app and restart it. **Step 4: Verify Connection** Call the `initialize()` tool to verify the connection. Done! *** ### Authentication Methods #### Method A: Set Environment Variables (Recommended) Add the API key to your environment variables in MCP settings: ```json theme={null} { "mcpServers": { "cryptoquant": { "command": "npx", "args": ["-y", "cryptoquant-mcp"], "env": { "CRYPTOQUANT_API_KEY": "your-api-key" } } } } ``` #### Method B: Direct Parameter You can also pass the API key directly when calling `initialize()`: ``` initialize(api_key="your-api-key") ``` The key is stored in `~/.cryptoquant/credentials` and reused in subsequent sessions. **API Key Issuance**: [https://cryptoquant.com/settings/api](https://cryptoquant.com/settings/api) #### Managing Credentials When account switching or re-authentication is required: ``` # reset session reset_session(clear_stored=true) # Re-authenticate with new key initialize(api_key="new-api-key") ``` Additionally, when managing API keys directly via LLM, session initialization occurs automatically. *** ### MCP Tool List CryptoQuant MCP Server provides the following tools: | Tool | Description | | - | - | | `initialize` | Start session with API key, return plan information | | `discover_endpoints` | Explore over 245 endpoints | | `get_endpoint_info` | Retrieve detailed endpoint parameter information | | `query_data` | Query API data | | `describe_metric` | Metric Description and Threshold Lookup | | `list_assets` | Retrieve list of supported assets | | `reset_session` | Reset Session (Logout) | *** ### Setting Up a Local Development Environment Setting up a local development environment for developers: ```bash theme={null} git clone https://github.com/CryptoQuantOfficial/cryptoquant-mcp.git cd cryptoquant-mcp npm install && npm run build ``` *** ### Requirements | Components | Requirements | | - | - | | Node.js | v18+ | | API Access | [CryptoQuant API Key](https://cryptoquant.com/settings/api) - You can obtain an API key by accessing the website! | *** ### Troubleshooting #### When Connection Fails 1. Verify Node.js v18 or higher is installed 2. Verify the configuration file path is correct 3. Check for JSON syntax errors 4. Ensure the app has been fully restarted #### API Key Issues 1. Verify the API key is valid [on the settings page](https://cryptoquant.com/settings/api) 2. Execute `initialize()` again after calling `reset_session(clear_stored=true)` 3. If using environment variables, verify they are set correctly *** ### Additional Resources * **Local MCP GitHub Repository**: [https://github.com/CryptoQuantOfficial/cryptoquant-mcp](https://github.com/CryptoQuantOfficial/cryptoquant-mcp) # Remote MCP (Recommended) Source: https://docs.cryptoquant.com/guides/mcp-remote The easiest way to connect to CryptoQuant's MCP server — add the hosted URL as a connector in Claude.ai, Claude Desktop, or your AI client, no install required. ## Quick Start Remote MCP is the easiest way to connect. CryptoQuant hosts the MCP server, and your AI client connects to it directly via URL. > **Which method should I use?** > > * **Connector** — Recommended for most users. Simply connect and start asking questions in Claude.ai or Claude Desktop. > * **Config Setting** — For developers who want to integrate CryptoQuant MCP into their own workflows or tools. ### Using Connector — [Claude.ai](http://Claude.ai) and Claude Desktop 1. In Claude, click **"Add connectors"** 2. Select **"Add custom connector"** ![Add custom connector](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/uCluVYI4HwrxNRhAyli1.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=3a74f3811964eef0cb4f83654d70960c) 3. Enter the following: * **Name**: `CryptoQuant` * **Remote MCP Server URL**: `https://mcp.cryptoquant.com/mcp` 4. Click **"Add"** 5. Click **"Connect"** ![Connect connector](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/o6af7YGt3LXI9A6u8UId.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=10ed9a245dbb0e142cddd422f69a4da8) 6. Choose either **API Key** or **Keyless** authentication ![Authentication options](https://mintcdn.com/cryptoquant/Hw2Gulyp0hXS0SGm/images/userguide/G70F6jxOucgdkVHMZieG.png?fit=max\&auto=format\&n=Hw2Gulyp0hXS0SGm\&q=85\&s=a54bfae87d5bce8629bbb993854c0477) > ⚠️ **Keyless mode uses a shared rate limit pool.** This means limits may be reached more quickly due to usage from other users. For a dedicated rate limit, use your [own API Key](https://cryptoquant.com/settings/api). 7. You're ready to go! ### Using Config Setting — Claude Desktop/Claude Code/Cursor > ⚠️ **Prerequisites**: Node.js v18 or higher must be installed. [Download from nodejs.org](https://nodejs.org/en/download) Add the following to your MCP configuration file: #### **Claude Desktop (claude\_desktop\_config.json)** path for Mac : `~/Library/Application Support/Claude/claude_desktop_config.json` path for Windows : `%APPDATA%\\Claude\\claude_desktop_config.json` ```json theme={null} { "mcpServers": { "CryptoQuant": { "command": "npx", "args": [ "mcp-remote", "https://mcp.cryptoquant.com/mcp" ] } } } ``` #### **Cursor (mcp.json)** path `.cursor/mcp.json` ```json theme={null} { "mcpServers": { "CryptoQuant": { "url": "https://mcp.cryptoquant.com/mcp" } } } ``` #### **Claude Code** ```bash theme={null} claude mcp add --transport http CryptoQuant https://mcp.cryptoquant.com/mcp ``` After saving, restart the app. #### Authentication Complete the authentication flow the same way as the Connector setup above. ## Troubleshooting #### Remote MCP Connection Issues 1. Verify the server URL is correct: `https://mcp.cryptoquant.com/mcp` 2. Check your internet connection 3. For desktop clients using config setting, verify Node.js v18+ is installed 4. Try refreshing the connector or removing and re-adding it #### API Key Issues 1. Verify the API key is valid [on the settings page](https://cryptoquant.com/settings/api) 2. If using environment variables, verify they are set correctly # MCP Server Source: https://docs.cryptoquant.com/guides/mcp-server Connect Claude, Cursor, or any MCP client to CryptoQuant's 245+ on-chain metrics through the Model Context Protocol — query MVRV, SOPR, exchange flows, and more in natural language. > Beta Notice: CryptoQuant MCP Server is currently in beta, and tools and features may change. Data is accurate but may be misinterpreted by the LLM in use. *** ### Overview CryptoQuant MCP Server enables AI agents to access CryptoQuant's on-chain analytics data via the Model Context Protocol (MCP). MCP (Model Context Protocol) is an open standard that enables large language models (LLMs) and AI agents to safely interact with external data sources and tools. #### Key Features * **Real-time on-chain data**: Over 245 metrics including MVRV, SOPR, Exchange Flow, Funding Rate, etc. * **Natural Language Query Support**: Ask questions in various languages including Korean and English * **Whale Tracking**: Monitor movements of large holders * **AI-Based Interpretation**: AI-powered interpretation and insights for on-chain data > [!TIP] > > **Research and QuickTakes** from CryptoQuant are available for free in the beta version of MCP. #### Supported Assets BTC, ETH, TRX, XRP, Stablecoin, ERC20, ALT * Full list of supported assets: [/catalog/supported-assets](/catalog/supported-assets) *** ### Natural Language Query Ask questions in various languages, and Claude will automatically route them to the appropriate indicator: | Question Examples | Intent | Mapping Metrics | | - | - | - | | How is the Bitcoin price? | VALUATION | MVRV | | Is BTC overvalued? | VALUATION | MVRV | | Show me the whales' movements | WHALE\_ACTIVITY | whale-ratio | | What's the funding rate? | LEVERAGE | funding-rates | | Current profit-taking / stop-loss situation? | PROFIT\_BEHAVIOR | SOPR | *** ### License MIT License - See [LICENSE](https://github.com/CryptoQuantOfficial/cryptoquant-mcp/blob/main/LICENSE) # Plans & Limits Source: https://docs.cryptoquant.com/guides/plans-and-limits Which endpoints each plan can call, at what resolution, and how far back. Every endpoint belongs to one of two data classes, and your plan decides which classes you can call and how granular the data is. The tables below list each endpoint with that answer. ## The two data classes > [card] Market data > > Prices, trades, and derivatives from exchanges — OHLCV, market cap, funding rates, open interest, liquidations, taker buy/sell, premiums, ETF flows, DEX/AMM. > > **60 endpoints.** Available on every plan; the resolution ladder opens up as you go higher. > [card] On-chain data > > Derived directly from the blockchain — exchange flows, miner flows, entity flows, network metrics, and on-chain valuation indicators such as MVRV and SOPR. > > **205 endpoints.** Professional and above only. > [!WARNING] > > **`market-indicator` is on-chain data, despite the name.** > > MVRV, SOPR, realized price and the other metrics under `market-indicator` are computed from on-chain realized value, so they are classified as on-chain and require **Professional or above** — even though the category name starts with `market`. ## What each plan gets | | Basic | Advanced | Professional | Premium | | - | - | - | - | - | | **Resolution** | | | | | | └ Market data | Day | Hour | Minute | All windows | | └ On-chain data | ✕ | ✕ | Day | All windows | | Historical lookback | 30 days | 1 year | 1 year | Full history | | Rate limit | 10/min | 60/min | 120/min | 800/min | | License | Personal | Personal | Personal | Commercial | > [!NOTE] > > A plan opens the ladder up to its maximum — it does not create resolutions that do not exist. If an endpoint only publishes daily data, every plan gets daily. `✕` means the plan cannot call that data class at all. ## API v1 endpoints Paths follow `/v1/{asset}/{category}/{metric}`. Each cell lists the **windows that plan can actually request**; `✕` means the plan cannot call that endpoint at all. Superscripts after an endpoint are **required query parameters** — omitting them returns `400`, not `403`. See the [Data Catalog](/catalog/overview) for full parameter details. > [accordion] Bitcoin (88 endpoints) > > | Endpoint | Class | Basic | Advanced | Professional | Premium | > | - | - | - | - | - | - | > | `fund-data/digital-asset-holdings` symbol | Market | day | day | day | day | > | `fund-data/market-premium` symbol | Market | day | day | day | day | > | `fund-data/market-price-usd` symbol | Market | day | day | day | day | > | `fund-data/market-volume` symbol | Market | day | day | day | day | > | `market-data/capitalization` | Market | day | day | day | day, block | > | `market-data/coinbase-premium-index` | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/funding-rates` exchange | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/liquidations` exchange | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/open-interest` exchange | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/price-ohlcv` | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/taker-buy-sell-stats` exchange | Market | day | day, hour | day, hour, min | day, hour, min | > | `miner-data/companies` miner | Market | day | day | day | day | > | `exchange-flows/addresses-count` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `exchange-flows/in-house-flow` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `exchange-flows/inflow` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `exchange-flows/netflow` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `exchange-flows/outflow` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `exchange-flows/reserve` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `exchange-flows/transactions-count` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/exchange-inflow-age-distribution` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/exchange-inflow-cdd` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/exchange-inflow-supply-distribution` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/exchange-shutdown-index` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/exchange-supply-ratio` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/exchange-whale-ratio` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/fund-flow-ratio` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/miner-supply-ratio` miner | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/mpi` | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/stablecoins-ratio` exchange | On-chain | ✕ | ✕ | day | day, hour | > | `inter-entity-flows/exchange-to-exchange` to\_exchange, from\_exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `inter-entity-flows/exchange-to-miner` to\_miner, from\_exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `inter-entity-flows/miner-to-exchange` from\_miner, to\_exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `inter-entity-flows/miner-to-miner` from\_miner, to\_miner | On-chain | ✕ | ✕ | day | day, hour, block | > | `lightning/stats-in-total` | On-chain | ✕ | ✕ | day | day, hour | > | `market-indicator/estimated-leverage-ratio` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `market-indicator/mvrv` | On-chain | ✕ | ✕ | day | day, block | > | `market-indicator/pnl-index` | On-chain | ✕ | ✕ | day | day | > | `market-indicator/realized-price` | On-chain | ✕ | ✕ | day | day, block | > | `market-indicator/sopr` | On-chain | ✕ | ✕ | day | day, block | > | `market-indicator/sopr-ratio` | On-chain | ✕ | ✕ | day | day, block | > | `market-indicator/stablecoin-supply-ratio` | On-chain | ✕ | ✕ | day | day | > | `market-indicator/utxo-realized-price-age-distribution` | On-chain | ✕ | ✕ | day | day, hour, block | > | `mempool/stats-by-relative-fee` metric\_type | On-chain | ✕ | ✕ | day | day, hour | > | `mempool/stats-in-total` metric\_type | On-chain | ✕ | ✕ | day | day, hour | > | `miner-flows/addresses-count` miner | On-chain | ✕ | ✕ | day | day, hour, block | > | `miner-flows/in-house-flow` miner | On-chain | ✕ | ✕ | day | day, hour, block | > | `miner-flows/inflow` miner | On-chain | ✕ | ✕ | day | day, hour, block | > | `miner-flows/netflow` miner | On-chain | ✕ | ✕ | day | day, hour, block | > | `miner-flows/outflow` miner | On-chain | ✕ | ✕ | day | day, hour, block | > | `miner-flows/reserve` miner | On-chain | ✕ | ✕ | day | day, hour, block | > | `miner-flows/transactions-count` miner | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/addresses-count` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/block-bytes` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/block-count` | On-chain | ✕ | ✕ | day | day, hour | > | `network-data/block-interval` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/blockreward` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/difficulty` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/fees` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/fees-transaction` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/hashrate` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/supply` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/tokens-transferred` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/transactions-count` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/utxo-count` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/velocity` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-indicator/cdd` | On-chain | ✕ | ✕ | day | day, block | > | `network-indicator/dormancy` | On-chain | ✕ | ✕ | day | day, block | > | `network-indicator/mca` | On-chain | ✕ | ✕ | day | day, block | > | `network-indicator/nrpl` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-indicator/nupl` | On-chain | ✕ | ✕ | day | day, block | > | `network-indicator/nvm` | On-chain | ✕ | ✕ | day | day | > | `network-indicator/nvt` | On-chain | ✕ | ✕ | day | day | > | `network-indicator/nvt-golden-cross` | On-chain | ✕ | ✕ | day | day | > | `network-indicator/pnl-supply` | On-chain | ✕ | ✕ | day | day, block | > | `network-indicator/pnl-utxo` | On-chain | ✕ | ✕ | day | day | > | `network-indicator/puell-multiple` | On-chain | ✕ | ✕ | day | day | > | `network-indicator/sca` | On-chain | ✕ | ✕ | day | day, block | > | `network-indicator/sca-distribution` | On-chain | ✕ | ✕ | day | day, block | > | `network-indicator/spent-output-age-distribution` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-indicator/spent-output-supply-distribution` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-indicator/stock-to-flow` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-indicator/utxo-age-distribution` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-indicator/utxo-count-age-distribution` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-indicator/utxo-count-supply-distribution` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-indicator/utxo-realized-age-distribution` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-indicator/utxo-realized-supply-distribution` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-indicator/utxo-supply-distribution` | On-chain | ✕ | ✕ | day | day, hour, block | > | `status/entity-list` type | Utility | — | — | — | — | > [accordion] Ethereum (72 endpoints) > > | Endpoint | Class | Basic | Advanced | Professional | Premium | > | - | - | - | - | - | - | > | `fund-data/digital-asset-holdings` symbol | Market | day | day | day | day | > | `fund-data/market-premium` symbol | Market | day | day | day | day | > | `fund-data/market-price-usd` symbol | Market | day | day | day | day | > | `fund-data/market-volume` symbol | Market | day | day | day | day | > | `market-data/capitalization` | Market | day | day, hour | day, hour | day, hour, block | > | `market-data/coinbase-premium-index` | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/funding-rates` exchange | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/liquidations` exchange | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/open-interest` exchange | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/price-ohlcv` | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `market-data/taker-buy-sell-stats` exchange | Market | day | day, hour | day, hour, min | day, hour, min | > | `eth2/depositor-count-new` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `eth2/depositor-count-total` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `eth2/phase0-success-rate` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `eth2/staking-inflow-total` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `eth2/staking-rate` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `eth2/staking-transaction-count` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `eth2/staking-validator-total` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `eth2/total-value-staked` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/addresses-count` exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/inflow` exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/netflow` exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/outflow` exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/reserve` exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/transactions-count` exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `flow-indicator/exchange-supply-ratio` exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `market-indicator/estimated-leverage-ratio` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/addresses-count` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/addresses-count-all` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/base-fee` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/block-bytes` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/block-count` | On-chain | ✕ | ✕ | day | day, hour, 10min | > | `network-data/block-interval` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/blockreward` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/blockreward-except-uncle` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/contract-calls-count` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/contract-calls-count-external` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/contract-calls-count-internal` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/contracts-count` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/difficulty` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/failed-tokens-transferred-count` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/failed-transactions-count` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/fees` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/fees-burnt` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/fees-burnt-transaction` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/fees-tips` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/fees-tips-transaction` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/fees-transaction` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/gas` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/hashrate` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/max-fee` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/max-priority-fee` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/supply` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred-all` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred-between-eoa` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred-by-contract-calls` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred-by-contract-calls-external` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred-by-contract-calls-internal` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred-count` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred-count-all` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred-count-between-eoa` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred-count-by-contract-calls` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred-count-by-contract-calls-external` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred-count-by-contract-calls-internal` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/transactions-count` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/transactions-count-all` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/transactions-count-between-eoa` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/uncle-block-count` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/uncle-blockreward` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/velocity` | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `status/entity-list` type | Utility | — | — | — | — | > [accordion] XRP (40 endpoints) > > | Endpoint | Class | Basic | Advanced | Professional | Premium | > | - | - | - | - | - | - | > | `amm-data/fee` amm | Market | day | day, hour | day, hour | day, hour | > | `amm-data/liquidity` amm | Market | day | day, hour | day, hour | day, hour | > | `amm-data/price` amm | Market | day | day, hour | day, hour | day, hour | > | `amm-data/swap-stats` amm | Market | day | day, hour | day, hour | day, hour | > | `dex-data/dex-price` | Market | day | day, hour | day, hour | day, hour | > | `dex-data/liquidity` | Market | day | day, hour | day, hour | day, hour | > | `dex-data/transactions-count` | Market | day | day, hour | day, hour | day, hour | > | `dex-data/volume` | Market | day | day, hour | day, hour | day, hour | > | `dex-indicator/buy-sell-ratio` | Market | day | day, hour | day, hour | day, hour | > | `dex-indicator/trade-share` | Market | day | day, hour | day, hour | day, hour | > | `market-data/capitalization` | Market | day | day, hour | day, hour | day, hour | > | `market-data/estimated-leverage-ratio` exchange | Market | day | day, hour | day, hour, 10min | day, hour, 10min | > | `market-data/funding-rates` exchange | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/liquidations` exchange | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/open-interest` exchange | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/price-ohlcv` | Market | day | day, hour | day, hour, min | day, hour, min | > | `market-data/taker-buy-sell-stats` exchange | Market | day | day, hour | day, hour, min | day, hour, min | > | `entity-flows/addresses-count` | On-chain | ✕ | ✕ | day | day, hour, block | > | `entity-flows/inflow` | On-chain | ✕ | ✕ | day | day, hour, block | > | `entity-flows/outflow` | On-chain | ✕ | ✕ | day | day, hour, block | > | `entity-flows/reserve` | On-chain | ✕ | ✕ | day | day, hour, block | > | `entity-flows/share` | On-chain | ✕ | ✕ | day | day, hour | > | `entity-flows/transactions-count` | On-chain | ✕ | ✕ | day | day, hour, block | > | `entity-flows/whale-movements` | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/exchange-inflow-count-value-distribution` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/exchange-inflow-value-distribution` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/exchange-outflow-count-value-distribution` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/exchange-outflow-value-distribution` exchange | On-chain | ✕ | ✕ | day | day, hour, block | > | `flow-indicator/exchange-supply-ratio` exchange | On-chain | ✕ | ✕ | day | day, hour | > | `network-data/addresses-count` | On-chain | ✕ | ✕ | day | day | > | `network-data/block-interval` | On-chain | ✕ | ✕ | day | day, hour | > | `network-data/fees` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/ledger-count` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/supply` | On-chain | ✕ | ✕ | day | day | > | `network-data/tokens-transferred` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/transactions-count` | On-chain | ✕ | ✕ | day | day, hour, block | > | `network-data/velocity` | On-chain | ✕ | ✕ | day | day | > | `network-data/xrp-burnt` | On-chain | ✕ | ✕ | day | day, hour | > | `network-indicator/nvt` | On-chain | ✕ | ✕ | day | day | > | `status/entity-list` | Utility | — | — | — | — | > [accordion] TRON (15 endpoints) > > | Endpoint | Class | Basic | Advanced | Professional | Premium | > | - | - | - | - | - | - | > | `market-data/capitalization` | Market | day | day | day | day | > | `market-data/price-ohlcv` | Market | day | day, hour | day, hour, min | day, hour, min | > | `defi/sunpump-tokens` | On-chain | ✕ | ✕ | day | day | > | `defi/sunswap-activity` | On-chain | ✕ | ✕ | day | day | > | `network-data/addresses-count` | On-chain | ✕ | ✕ | day | day | > | `network-data/bandwidth-consumption` | On-chain | ✕ | ✕ | day | day | > | `network-data/block-count` | On-chain | ✕ | ✕ | day | day | > | `network-data/energy-consumption` | On-chain | ✕ | ✕ | day | day | > | `network-data/fees` | On-chain | ✕ | ✕ | day | day | > | `network-data/staking-rate` | On-chain | ✕ | ✕ | day | day | > | `network-data/supply` | On-chain | ✕ | ✕ | day | day | > | `network-data/tokens-transferred` | On-chain | ✕ | ✕ | day | day | > | `network-data/total-value-staked` | On-chain | ✕ | ✕ | day | day | > | `network-data/tps` | On-chain | ✕ | ✕ | day | day | > | `network-data/transactions-count` | On-chain | ✕ | ✕ | day | day | > [accordion] ERC-20 (15 endpoints) > > | Endpoint | Class | Basic | Advanced | Professional | Premium | > | - | - | - | - | - | - | > | `market-data/price-ohlcv` token | Market | day | day, hour | day, hour, min | day, hour, min | > | `exchange-flows/addresses-count` exchange, token | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/inflow` token, exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/netflow` token, exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/outflow` token, exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/reserve` token, exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/transactions-count` token, exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `flow-indicator/exchange-supply-ratio` exchange, token | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/addresses-count` token | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/supply` token | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred` token | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/tokens-transferred-count` token | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/transactions-count` token | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/velocity` token | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `status/entity-list` type, token | Utility | — | — | — | — | > [accordion] Stablecoin (14 endpoints) > > | Endpoint | Class | Basic | Advanced | Professional | Premium | > | - | - | - | - | - | - | > | `market-data/capitalization` token | Market | day | day | day | day, block | > | `market-data/price-ohlcv` token | Market | day | day, hour | day, hour, min | day, hour, min | > | `exchange-flows/addresses-count` token, exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/inflow` token, exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/netflow` token, exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/outflow` token, exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/reserve` token, exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `exchange-flows/transactions-count` token, exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `flow-indicator/exchange-supply-ratio` token, exchange | On-chain | ✕ | ✕ | day | day, hour, 10min, block | > | `network-data/addresses-count` token | On-chain | ✕ | ✕ | day | day, block | > | `network-data/events-count` token | On-chain | ✕ | ✕ | day | day, block | > | `network-data/supply` token | On-chain | ✕ | ✕ | day | day, block | > | `network-data/tokens-transferred` token | On-chain | ✕ | ✕ | day | day, block | > | `status/entity-list` token, type | Utility | — | — | — | — | > [accordion] Altcoin (1 endpoints) > > | Endpoint | Class | Basic | Advanced | Professional | Premium | > | - | - | - | - | - | - | > | `market-data/price-ohlcv` token | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | ## API v2 endpoints v2 uses the same envelope, authentication and `window` parameter as v1. The difference is how paths are organized: v1 keys off the asset (`/v1/{asset}/{category}/{metric}`), v2 keys off the data source (`/v2/market/{origin}/{product}/{metric}`, `/v2/community/{metric}`). The same two data classes and the same plan rules apply. As in v1, superscripts are **required query parameters**, and each cell lists the windows that plan can request. > [accordion] Market data (16 endpoints) > > | Endpoint | Class | Basic | Advanced | Professional | Premium | > | - | - | - | - | - | - | > | `/v2/market/cq/spot/ohlcv` symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/cq/spot/trade` symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/cq/swap/funding-rate` symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/cq/swap/liquidation` symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/cq/swap/ohlcv` symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/cq/swap/open-interest` symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/cq/swap/trade` symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/exchange/spot/ohlcv` exchange, symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/exchange/spot/trade` exchange, symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/exchange/swap/funding-rate` exchange, symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/exchange/swap/liquidation` exchange, symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/exchange/swap/ohlcv` exchange, symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/exchange/swap/open-interest` exchange, symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/exchange/swap/trade` exchange, symbol | Market | day | day, hour | day, hour, 10min, min | day, hour, 10min, min | > | `/v2/market/info/exchanges` origin, instrument, metric | Utility | — | — | — | — | > | `/v2/market/info/symbols` origin, instrument, metric | Utility | — | — | — | — | > [accordion] Community indicators (11 endpoints) > > | Endpoint | Class | Basic | Advanced | Professional | Premium | > | - | - | - | - | - | - | > | `/v2/community/bitcoin-apparent-demand` | On-chain | ✕ | ✕ | day | day | > | `/v2/community/bitcoin-bull-bear-indicator` | On-chain | ✕ | ✕ | day | day | > | `/v2/community/bitcoin-etf-demand` | On-chain | ✕ | ✕ | day | day | > | `/v2/community/bitcoin-metcalfe-price` | On-chain | ✕ | ✕ | day | day | > | `/v2/community/bitcoin-mvrv-z-score` | On-chain | ✕ | ✕ | day | day | > | `/v2/community/bitcoin-op-return-count` | On-chain | ✕ | ✕ | day | day | > | `/v2/community/bitcoin-pnl-index` | On-chain | ✕ | ✕ | day | day | > | `/v2/community/bitcoin-realized-profit-loss` | On-chain | ✕ | ✕ | day | day | > | `/v2/community/bitcoin-satoshi-era-miner` | On-chain | ✕ | ✕ | day | day | > | `/v2/community/bitcoin-trader-realized-price` | On-chain | ✕ | ✕ | day | day | > | `/v2/community/bitcoin-trader-unrealized-profit-margin` | On-chain | ✕ | ✕ | day | day | ## Known issues > [!NOTE] > > **Estimated Leverage Ratio is classified differently per asset.** On BTC and ETH it sits under `market-indicator` (on-chain, Professional and above); on XRP it sits under `market-data` (market, available from Basic). We are aware of this and plan to align it in a future release. ## Related > [card] [Data Catalog](/catalog/overview) > > Full metric details — parameters, response fields, and interpretation guides. > [card] [Pricing](https://cryptoquant.com/pricing) > > Plan prices and how to upgrade. # Quickstart Source: https://docs.cryptoquant.com/guides/quickstart Make your first CryptoQuant API call. ## 1. Get an API key API access is available on [CryptoQuant pricing plans](https://cryptoquant.com/pricing). Once subscribed, find your access token in your account settings. ## 2. Make a request Request the full historical on-chain balance (reserve) of a Bitcoin exchange: ```bash cURL theme={null} curl "https://api.cryptoquant.com/v1/btc/exchange-flows/reserve?exchange=binance&window=day&limit=5" \ -H "Authorization: Bearer $ACCESS_TOKEN" ``` ```python Python theme={null} import requests headers = {"Authorization": "Bearer " + access_token} url = "https://api.cryptoquant.com/v1/btc/exchange-flows/reserve" params = {"exchange": "binance", "window": "day", "limit": 5} print(requests.get(url, headers=headers, params=params).json()) ``` ```javascript JavaScript theme={null} const res = await fetch( "https://api.cryptoquant.com/v1/btc/exchange-flows/reserve?exchange=binance&window=day&limit=5", { headers: { Authorization: `Bearer ${accessToken}` } } ); console.log(await res.json()); ``` ## 3. Read the response Every response wraps data in a `status` / `result` envelope: ```json theme={null} { "status": { "code": 200, "message": "success" }, "result": { "window": "day", "data": [ { "date": "2026-06-11", "reserve": 540321.2, "reserve_usd": 58234567890.1 } ] } } ``` ## Next steps > [card] [Browse the catalog](/catalog/overview) > > Find the metric you need across all supported assets. > [card] [Time convention](/guides/time-convention) > > Understand `window`, `from`, and `to` parameters. # Status & Error Codes Source: https://docs.cryptoquant.com/guides/status-codes Every response includes a status object indicating success or the cause of an error. ## Status object Every response includes the status object which indicates if the request was successful. If it is not successful, `message` specifies the cause of the error. ```json theme={null} { "status": { "code": 200, "message": "success" } } ``` ## Status and error codes The CryptoQuant API uses standard HTTP status codes to indicate success or failure. `200` represents success, `4xx` represents a user error (such as a problem with your key), and `5xx` represents a problem with our API. In the status object, the `code` field contains the status code and the `message` field contains the type of response. | Code | Type | Description | | - | - | - | | `200` | `success` | Request was successful. | | `200` | `deprecated` | A resource is deprecated and will be removed in the future. | | `400` | `bad_request` | Some required parameter is missing or has the wrong value. | | `401` | `unauthorized` | Internal authorization failed. It might mean missing or wrong credentials. | | `402` | `payment_required` | The account has run out of API credits. Top up or wait for the monthly plan reset to continue. | | `403` | `forbidden` | You don't have access to the requested endpoint. | | `404` | `not_found` | URI is not valid or the resource ID does not correspond to an existing resource. | | `405` | `not_allowed` | HTTP method not allowed, such as attempting to use a POST request with an endpoint that only accepts GET requests, or vice versa. | | `429` | `too_many_requests` | The user has sent too many requests in a given amount of time. | | `500` | `internal_server_error` | Unexpected error occurred. Please report this when you see it. | A `402 payment_required` means your credit balance is exhausted rather than anything being wrong with the request. See [API Credits](/guides/api-credits) for how much a call costs, how to top up, and when your plan credits reset. # Time Convention Source: https://docs.cryptoquant.com/guides/time-convention How the window, from, and to parameters control data aggregation intervals. For all metrics, the `window` parameter is used to specify the time intervals for which the data is aggregated. Windows are provided in `window=min`, `window=hour`, `window=day` and `window=block`, and each metric supports different windows. For on-chain data, the smallest period available is block. Daily units are provided for added versatility. We use two parameters `from` and `to` to specify the start and end time for which data will be gathered. Generally, it can be formatted as `YYYYMMDDTHHMMSS` (e.g. `from=20191003T220000`) for all windows, and additional formats are supported for each window type. | Window | Description | `from`, `to` parameter format | | - | - | - | | `block` | Data representing a specific block. | Datetime (`YYYYMMDDTHHMMSS`) or block height (e.g. `550000`). If datetime is used, data for blocks corresponding to that time period will be returned. | | `min` | Currently supported for market data only. For time 18:12:00, it represents data from 18:12:00 UTC to 18:12:59 UTC. | Datetime (`YYYYMMDDTHHMMSS`). | | `hour` | Data calculated for all blocks produced in an hour. An hourly data is from 12:00:00 UTC to 12:59:59 UTC. | Datetime (`YYYYMMDDTHHMMSS`). | | `day` | Data calculated for all blocks produced in a day. Each day begins at 00:00:00 UTC and ends at 23:59:59 UTC. | Datetime (`YYYYMMDDTHHMMSS`) or date (`YYYYMMDD`). | > [!NOTE] > > End-of-day data of exchange/miner/inter-entity flow will be ready to serve from UTC 00:00 AM > and may take up to an hour. Since block confirmation takes time due to the nature of the > blockchain, blocks created before 00:00 AM are reflected in the calculation sequentially. > The block confirmation time varies, so the safe time to query the endpoint for a full day > would be an hour after the day (i.e., UTC 1:00 AM). Top 10 data will return `null` until > block confirmation is complete. # Vibe Quants Source: https://docs.cryptoquant.com/guides/vibe-quants Join Vibe Quants — CryptoQuant's community of builders turning on-chain ideas into research-grade indicators that ship straight into the API. ![CryptoQuant Vibe Quants](https://mintcdn.com/cryptoquant/a3rcxNn1q0oVgDku/images/vibe-quants/banner.png?fit=max\&auto=format\&n=a3rcxNn1q0oVgDku\&q=85\&s=01217f24e2362812d518712632425f9b) ## What is Vibe Quants? **Vibe Quants** is CryptoQuant's community of on-chain builders. It's where a market hunch becomes a real, queryable signal: members design indicators from CryptoQuant's data, refine them with the community, and the best ones graduate into the API for everyone to use. If you've ever looked at a chart and thought *"there's a pattern here"* — Vibe Quants is where you turn that instinct into a metric other traders, researchers, and AI agents can build on. ## From community idea to API endpoint Indicators created by the community ship in **API v2** under the `/v2/community/` namespace — the same battle-tested signals CryptoQuant's research team uses to call market cycles, now documented and queryable. > [card] [API v2 Overview](/v2/overview) > > How the curated, community-built indicator layer works. > [card] [v2 Metric Catalog](/v2/catalog) > > Browse every community-built indicator — endpoints, fields, and guides. ## Why contribute * **Reach** — your indicator ships in the CryptoQuant API, reachable by traders, funds, and AI agents through both the REST API and the [MCP server](/guides/mcp-server). * **Credit** — community-built metrics live under their own `community` namespace, with a dedicated interpretation guide for each one. * **Built on real data** — design on top of CryptoQuant's full on-chain, market, and flow datasets across BTC, ETH, XRP, TRX, stablecoins, and more. ## Join the community > **You're a Pro. Now become a Vibe Quant.** > Join the community of builders shipping AI trading agents. The Vibe Quants Discord is open to **Professional** and **Premium** plan subscribers. [Upgrade your plan](https://cryptoquant.com/pricing) to unlock access and start shaping the next indicator. > [card] [Join Discord](https://discord.gg/jQfpsqraQr) > > Open to Professional and Premium subscribers — build alongside other Vibe Quants. > [!NOTE] > > Not on a Professional or Premium plan yet? Compare tiers on the > [CryptoQuant pricing page](https://cryptoquant.com/pricing). # CryptoQuant API Source: https://docs.cryptoquant.com/index Simple and powerful endpoints for on-chain data, market data, and aggregate blockchain statistics. The CryptoQuant Data API provides simple and powerful endpoints to get information on general transaction data and aggregate on-chain statistics straight from the blockchain. ```text theme={null} API root endpoint https://api.cryptoquant.com/v1/ ``` > [card] [Quickstart](/guides/quickstart) > > Make your first API call in under a minute. > [card] [Authentication](/guides/authentication) > > Authenticate with a Bearer access token or an `api_key` query parameter. > [card] [API Reference](/api-reference) > > Every endpoint with parameters, response schemas, and runnable examples. > [card] [Metric Catalog](/catalog/overview) > > Browse all metrics by asset — endpoints, parameters, and response fields at a glance. > [card] [Data Guide](/data-guide/exchange) > > Definitions, formulas, and interpretation for every metric — MVRV, SOPR, exchange flows, and more. > [card] [Glossary](/guides/glossary) > > Quick, answer-first definitions of every key metric — what MVRV, SOPR, NVT, and CDD mean. > [card] [MCP Server](/guides/mcp-server) > > Connect Claude, Cursor, or any MCP client to CryptoQuant data with one URL. > [card] [Sentiment Data](/sentiment/overview) > > The Analyst Consensus API — the daily Analyst Consensus Index, per-asset breakdowns, analyst views and accuracy track records for 1,700+ assets. ## Supported assets | Asset | Categories | | - | - | | **Bitcoin** | Status, Exchange Flows, Flow Indicator, Market Indicator, Network Indicator, Miner Flows, Inter Entity Flows, Fund Data, Market Data, Miner Data, Network Data, Mempool, Lightning Network | | **Ethereum** | Status, Exchange Flows, Flow Indicator, Market Indicator, ETH 2.0, Fund Data, Market Data, Network Data | | **XRP** | Status, Entity Flows, Flow Indicator, Market Data, Network Data, Network Indicator, DEX Data, AMM Data | | **TRX** | Market Data, Network Data, DeFi | | **Stablecoin** | Status, Exchange Flows, Flow Indicator, Market Data, Network Data | | **ERC20** | Status, Exchange Flows, Flow Indicator, Market Data, Network Data | | **Alt** | Market Data | ## Built for AI agents This documentation is designed to be consumed by AI agents as well as humans: * **MCP server** — point any MCP client at `https://mcp.cryptoquant.com/mcp` to query CryptoQuant data directly. See the [setup guide](/guides/mcp-server). * Append `.md` to any page URL to get raw Markdown. * `/llms.txt` and `/llms-full.txt` expose the full docs index and content. * The complete metric catalog is available as machine-readable JSON: [`/catalog/catalog.json`](/catalog/catalog.json). * The full OpenAPI specification: [`/openapi/v1.json`](/openapi/v1.json). # Authentication Source: https://docs.cryptoquant.com/indicator-api/authentication Use a CryptoQuant API key to access Indicator API series endpoints. Indicator API catalog endpoints are public, but endpoints that return indicator values require a CryptoQuant API key. > [!WARNING] > > Access to the equities series starts at the CryptoQuant **Pro plan**. The > [Analyst Consensus Index](/indicator-api/consensus) series requires the **Premium plan**. > Lower-plan keys and invalid keys are rejected. ## Header Pass the key in the `Authorization` header: ```http theme={null} GET /api/equities/KRX:005930/pbr-band?limit=1&order=desc HTTP/1.1 Host: alpha.cryptoquant.com Authorization: Bearer ``` ## cURL ```bash theme={null} curl -X GET "https://alpha.cryptoquant.com/api/equities/KRX:005930/pbr-band?limit=1&order=desc" \ -H "Authorization: Bearer " ``` ## JavaScript ```javascript theme={null} const response = await fetch( "https://alpha.cryptoquant.com/api/equities/KRX:005930/pbr-band?limit=1&order=desc", { headers: { Authorization: "Bearer ", }, } ); const json = await response.json(); ``` ## Python ```python theme={null} import requests url = "https://alpha.cryptoquant.com/api/equities/KRX:005930/pbr-band" headers = {"Authorization": "Bearer "} params = {"limit": 1, "order": "desc"} response = requests.get(url, headers=headers, params=params) data = response.json() ``` ## Public catalog endpoints These endpoints do not require authentication: ```text theme={null} GET https://alpha.cryptoquant.com/api GET https://alpha.cryptoquant.com/api/consensus GET https://alpha.cryptoquant.com/api/equities GET https://alpha.cryptoquant.com/api/indicators ``` # Analyst Consensus Index Source: https://docs.cryptoquant.com/indicator-api/consensus Daily net bullish-vs-bearish balance of tracked crypto analysts, served through the Alpha Indicator API for CryptoQuant Premium plan users. The Analyst Consensus Index is the daily net sentiment of tracked crypto analysts — one vote per analyst (their latest post), aggregated to a single reading from **−100 (all bearish)** to **+100 (all bullish)**. It is the sentiment row on the [alpha.cryptoquant.com](https://alpha.cryptoquant.com) Bitcoin heatmap. The series is available to **CryptoQuant Premium plan** users through the Alpha Indicator API, with the same API key used for the core Data API. > [!NOTE] > > This route serves the **daily index only** (BTC, ETH, SOL). The full Analyst Consensus API — the > per-asset breakdown, analyst views and calls, per-analyst stance and accuracy track records across > 1,700+ assets — is documented in the [Sentiment Data](/sentiment/overview) tab. It runs on > `consensus.cryptoquant.com` with its own `X-API-Key` credential. ## Base endpoint ```text theme={null} https://alpha.cryptoquant.com/api/consensus ``` ## Assets | Asset | `{asset}` | Accepted aliases | | - | - | - | | Bitcoin | `BTC` | `bitcoin` | | Ethereum | `ETH` | `ethereum` | | Solana | `SOL` | `solana` | ## Endpoints ### Catalog (public) Asset list, metric metadata, field definitions, and query parameters — no values, no key needed. ```bash theme={null} curl -X GET "https://alpha.cryptoquant.com/api/consensus" ``` ### Daily series (Premium) ```bash theme={null} curl -X GET "https://alpha.cryptoquant.com/api/consensus/BTC?limit=30&order=desc" \ -H "Authorization: Bearer " ``` ## Query parameters | Parameter | Type | Description | | - | - | - | | `from` | `YYYY-MM-DD` | Return points on or after this UTC day | | `to` | `YYYY-MM-DD` | Return points on or before this UTC day | | `limit` | integer | Maximum number of rows, clamped to `1..10000` (default `10000`) | | `order` | `asc` or `desc` | Sort order. Defaults to `asc` | > [!NOTE] > > The index is end-of-day. The current UTC day is still accumulating votes and is excluded — the > latest point is the previous UTC day. History starts 2021-06-01. ## Response shape ```json theme={null} { "status": { "code": 200, "message": "success" }, "result": { "asset": { "id": "BTC", "name": "Bitcoin", "slug": "bitcoin", "aliases": ["BTC", "bitcoin"], "assetClass": "crypto" }, "metric": { "id": "analyst-consensus-index", "name": "Analyst Consensus Index", "meaning": "Crypto analysts' bullish vs. bearish balance", "category": "sentiment", "direction": "sell_high", "source": "unbias", "frequency": "daily", "range": { "min": -100, "max": 100 }, "experimental": true }, "data": [ { "datetime": "2026-09-09", "value": 32.89, "value_30d_ma": 35.72, "bullish_analysts": 80, "bearish_analysts": 32, "total_analysts": 112 } ] } } ``` ## Fields | Field | Meaning | | - | - | | `datetime` | UTC day (`YYYY-MM-DD`) | | `value` | Analyst Consensus Index: `(bullish − bearish) ÷ total × 100`, from −100 to +100 | | `value_30d_ma` | 30-day moving average of `value` (`null` while the window is filling) | | `bullish_analysts` | Analysts counted bullish that day | | `bearish_analysts` | Analysts counted bearish that day | | `total_analysts` | Analysts with a directional view that day (bullish + bearish) | `metric.source: "unbias"` records provenance — the index is produced by the unbias.fyi analyst-tracking pipeline. Access is through your CryptoQuant API key; no separate key or billing. ## How to read it Read contrarian: crowded bullishness (high positive readings) marks top risk, while capitulation in sentiment (deeply negative readings) has marked opportunity. On the heatmap the row is colored `sell_high` — high = red, low = green. ## Errors Requests without a key return `401 authentication required`; keys below the Premium plan return `403 premium_plan_required`; an unsupported `{asset}` returns `404 unknown asset`. See [Errors](/indicator-api/errors) for the envelopes. # Crypto Indicators (Bitcoin) Source: https://docs.cryptoquant.com/indicator-api/crypto On-chain, technical, and consensus indicators behind the Alpha Library Bitcoin heatmap, each mapped to the API endpoint or formula that produces it. The Alpha Library Bitcoin heatmap is built from three kinds of indicators: * **On-chain valuation & demand** — served directly by the core CryptoQuant Data API. * **Technical** — computed in-app from the Bitcoin daily close series (no dedicated endpoint). * **Consensus** — the Analyst Consensus Index, served by the Alpha Indicator API (`alpha.cryptoquant.com`) for Premium plan users. Each row is z-scored over a trailing multi-year window before it is colored on the heatmap (green = bull/buy regime, red = bear/sell regime). The tables below map every indicator to the endpoint or formula that produces its raw input. ## Base URL & request shape On-chain rows are `GET` requests against the core CryptoQuant Data API: ```text theme={null} https://api.cryptoquant.com ``` ```bash theme={null} curl -X GET "https://api.cryptoquant.com/v2/community/bitcoin-mvrv-z-score?window=day&limit=10000" \ -H "Authorization: Bearer " ``` > [!NOTE] > > On-chain indicator values are paywalled and require a CryptoQuant API key. The Alpha Library > itself exposes metadata only — signal values are never returned without authentication. ## On-chain indicators Served by the core CryptoQuant Data API. The heatmap reads the listed response fields. | Indicator | Endpoint | Fields | What it measures | How to use | | - | - | - | - | - | | MVRV Z-Score | `GET /v2/community/bitcoin-mvrv-z-score` | `mvrv_ratio_zscore` | MVRV ratio (market cap ÷ realized cap) standardized as a Z-score from its historical mean. | Crossing below the 365-day MA = bearish; deep negative = undervaluation near bottoms; crossing above the mean = early bull confirmation. | | Trader Unrealized Profit (NUPL) | `GET /v2/community/bitcoin-trader-unrealized-profit-margin` | `nupl_1m_3m` | Percent gap between price and the 1–3 month holder cost basis (Trader Realized Price). | Contrarian at extremes: >40% = overheating / correction risk; deeply negative = capitulation may be near. | | PnL Index | `GET /v2/community/bitcoin-pnl-index` | `pnl_index`, `pnl_index_365day_ma` | Composite valuation index built from the MVRV ratio, NUPL, and LTH/STH SOPR. | >1 = overvalued, \< −1.38 = undervalued; the 365-day MA separates bull from bear regimes. | | Bull/Bear Indicator | `GET /v2/community/bitcoin-bull-bear-indicator` | `bull_bear_indicator` | Momentum metric: the difference between the PnL Index and its 365-day moving average. | Above 0 = bull cycle; below 0 and below its 365-day MA = bear cycle. | | Apparent Demand (1Y) | `GET /v2/community/bitcoin-apparent-demand` | `apparent_demand`, `apparent_demand_1y` | Net change in BTC inactive for 1+ year, adjusted for block rewards (1-year rolling sum). | Rising = structural accumulation (bullish); negative or below its 365-day MA = distribution / bear. | | NVM Ratio | `GET /v2/community/bitcoin-metcalfe-price` | `active_addresses_squared_price_365ma` | Market value vs Metcalfe fair value (active addresses²) — price relative to network activity. | Above fair value = overvalued vs usage; near or below the lower bands = fundamental support. | | Realized Net P\&L (1Y) | `GET /v2/community/bitcoin-realized-profit-loss` | `yearly_realized_net_profit_btc` | Net profit/loss realized by sellers, as a 1-year rolling sum in BTC. | High = late-cycle profit-taking (top risk); declining peaks = cycle top passed; negative = capitulation near bottoms. | | Adjusted SOPR | `GET /v1/btc/market-indicator/sopr` | `a_sopr` | Value of spent coins ÷ their value at acquisition, excluding coins \< 1h old. >1 = realized profit. | Sustained >1 = profit-taking / top risk; pullbacks to \~1 act as support in bull markets. | | SOPR Ratio (LTH/STH) | `GET /v1/btc/market-indicator/sopr-ratio` | `sopr_ratio` | Long-term holder SOPR ÷ short-term holder SOPR. | High = long-term holders selling into strength (late cycle); low = long-term holders holding. | | Thermocap Multiple | `GET /v1/btc/market-data/capitalization` | `market_cap`, `thermo_cap` | Market cap ÷ thermocap (cumulative miner revenue). | High = price stretched vs cumulative security spend → cycle tops; low = undervalued. | ## Technical indicators Computed in-app from the Bitcoin daily close (`close` of `GET /v1/btc/market-data/price-ohlcv`). They are **not** served as dedicated endpoints — the formula is shown in place of a path. | Indicator | Formula | What it measures | How to use | | - | - | - | - | | Mayer Multiple | `close ÷ SMA(close, 200d)` | Price relative to its 200-day moving average — the classic trend-stretch gauge. | >1 = price above the 200-day MA (bull regime); historically >2.4 = overheated, \< 0.8 = deep value. | | RSI (Weekly) | `RSI(weekly close, 14)` — Wilder smoothing | 14-period RSI on weekly (Sunday UTC) closes, forward-filled to days. | >50 = bullish momentum regime; sustained 70+ = overheated cycle legs; sub-40 prints near bear-market bottoms. | | Pi Cycle Top | `SMA(close, 111d) ÷ (2 × SMA(close, 350d))` | Ratio of the 111-day MA to twice the 350-day MA of price. | The ratio reaching 1 (the famous cross) has marked every cycle top within days; rising = late-cycle acceleration. | | Bollinger %B (1y) | `(close − lower) ÷ (upper − lower)`, bands = `SMA(close, 365d) ± 2σ` | Position of the close within its 1-year ±2σ Bollinger Bands. | High / >1 = strong bull regime; low / \< 0 = deep drawdown; 0.5 = mid-band. | ## Consensus indicator Served by the **Alpha Indicator API** on `alpha.cryptoquant.com` — available to CryptoQuant **Premium plan** users with their regular API key. | Indicator | Endpoint | Fields | What it measures | How to use | | - | - | - | - | - | | Analyst Consensus Index | `GET https://alpha.cryptoquant.com/api/consensus/BTC` | `value`, `value_30d_ma` | Net analyst sentiment (−100 bearish … +100 bullish) aggregated daily from tracked crypto analysts. | Read contrarian: crowded bullishness = top risk; capitulation in sentiment = opportunity. | ```bash theme={null} curl -X GET "https://alpha.cryptoquant.com/api/consensus/BTC?limit=30&order=desc" \ -H "Authorization: Bearer " ``` > [!NOTE] > > Full endpoint reference — assets (BTC, ETH, SOL), query parameters, response shape, and field > definitions — on the [Analyst Consensus Index](/indicator-api/consensus) page. Keys below the > Premium plan receive `403 premium_plan_required`. ## Metadata catalog The value-free metadata for every Alpha Library indicator (ids, names, meanings, categories) is public: ```bash theme={null} curl -X GET "https://alpha.cryptoquant.com/api/indicators" ``` This catalog never returns signal values — it is for discovery, indexing, and agent context only. # KRX Equities Source: https://docs.cryptoquant.com/indicator-api/equities Computed Korean equity indicators served through the Alpha Indicator API. KRX equity endpoints expose computed indicator series for supported Korean equities. ## Base endpoint ```text theme={null} https://alpha.cryptoquant.com/api/equities ``` ## Asset identifiers The canonical asset id is: ```text theme={null} KRX:{code} ``` The API also accepts the 6-digit KRX code, Yahoo-style ticker, and Alpha Library slug. | Company | Canonical id | Accepted aliases | | - | - | - | | Samsung Electronics | `KRX:005930` | `005930`, `005930.KS`, `samsung-electronics` | | SK hynix | `KRX:000660` | `000660`, `000660.KS`, `sk-hynix` | | Hyundai Motor | `KRX:005380` | `005380`, `005380.KS`, `hyundai-motor` | ## Endpoints ### Catalog ```bash theme={null} curl -X GET "https://alpha.cryptoquant.com/api/equities" ``` ### All metrics for an asset ```bash theme={null} curl -X GET "https://alpha.cryptoquant.com/api/equities/KRX:005930?limit=30&order=desc" \ -H "Authorization: Bearer " ``` ### One metric for an asset ```bash theme={null} curl -X GET "https://alpha.cryptoquant.com/api/equities/KRX:005930/pbr-band?limit=30&order=desc" \ -H "Authorization: Bearer " ``` ## Query parameters | Parameter | Type | Description | | - | - | - | | `from` | `YYYY-MM-DD` | Return points on or after this date | | `to` | `YYYY-MM-DD` | Return points on or before this date | | `limit` | integer | Maximum number of rows, clamped to `1..10000` | | `order` | `asc` or `desc` | Sort order. Defaults to `asc` | ## Response shape ```json theme={null} { "status": { "code": 200, "message": "success" }, "result": { "asset": { "id": "KRX:005930", "code": "005930", "canonicalId": "KRX:005930", "slug": "samsung-electronics", "name": "Samsung Electronics", "ticker": "005930.KS", "aliases": ["005930", "005930.KS", "KRX:005930", "samsung-electronics"], "assetClass": "equities", "market": "KRX", "currency": "KRW", "sourcePolicy": "dart-computed", "rawRedistribution": false }, "metric": { "id": "pbr-band", "name": "PBR (Price/Book)", "source": "dart-computed", "frequency": "daily" }, "data": [ { "datetime": "2026-06-17", "value": 4.3276516223258525 } ] } } ``` # Equity Metrics Source: https://docs.cryptoquant.com/indicator-api/equity-metrics Metric ids currently available for KRX equity series endpoints. Use the metric id as the `{metric}` path segment: ```text theme={null} GET /api/equities/{asset}/{metric} ``` Example: ```bash theme={null} curl -X GET "https://alpha.cryptoquant.com/api/equities/KRX:005930/fair-value-gap?limit=30&order=desc" \ -H "Authorization: Bearer " ``` ## Metric catalog | Metric id | Frequency | Direction | Meaning | | - | - | - | - | | `fair-value-gap` | daily | `sell_high` | Price premium/discount versus historical-multiple fair value | | `per-band` | daily | `sell_high` | Price relative to trailing-twelve-month earnings per share | | `pbr-band` | daily | `sell_high` | Price relative to per-share book value | | `psr-band` | daily | `sell_high` | Price relative to trailing-twelve-month revenue per share | | `dividend-yield` | daily | `buy_high` | Annual cash dividend per share as a percentage of price | | `roe-ttm` | filing | `buy_high` | Trailing-twelve-month net income as a percentage of equity | | `operating-margin-ttm` | filing | `buy_high` | Trailing-twelve-month operating income as a percentage of revenue | | `net-margin-ttm` | filing | `buy_high` | Trailing-twelve-month net income as a percentage of revenue | | `gross-margin-ttm` | filing | `buy_high` | Trailing-twelve-month gross profit as a percentage of revenue | | `revenue-growth-ttm` | filing | `buy_high` | Trailing-twelve-month revenue versus a year earlier | | `operating-profit-growth-ttm` | filing | `buy_high` | Trailing-twelve-month operating profit versus a year earlier | | `operating-profit-growth-q` | filing | `buy_high` | Single-quarter operating profit versus the same quarter a year earlier | | `debt-to-equity` | filing | `sell_high` | Total liabilities as a percentage of equity | | `interest-coverage` | filing | `buy_high` | Trailing-twelve-month operating profit divided by interest paid | | `payout-ratio` | filing | `buy_high` | Cash dividends as a percentage of net income | | `buyback-yield` | daily | `buy_high` | Net treasury buybacks over the last year as a percentage of market cap | | `insider-net-buying` | filing | `buy_high` | Cumulative officer and major-shareholder net share purchases | | `piotroski-f-score` | filing | `buy_high` | 9-point financial-strength score | ## Source policy All current KRX equity metrics use: ```json theme={null} { "source": "dart-computed" } ``` This means the returned value is a computed indicator. It is not a DART/OpenDART raw filing row. # Errors Source: https://docs.cryptoquant.com/indicator-api/errors Authentication and lookup errors returned by the Indicator API. The Indicator API uses the same top-level `status` envelope pattern as the core CryptoQuant APIs. ## Missing API key ```json theme={null} { "status": { "code": 401, "message": "authentication required", "description": "Pass a CryptoQuant API key with Authorization: Bearer . CryptoQuant Pro plan or higher is required." } } ``` ## Invalid API key ```json theme={null} { "status": { "code": 401, "message": "invalid_api_key", "description": "A valid CryptoQuant API key is required." } } ``` The `description` names the plan the endpoint requires — **Pro** for the equities series, **Premium** for the [Analyst Consensus Index](/indicator-api/consensus). ## Plan below Pro Equities series endpoints: ```json theme={null} { "status": { "code": 403, "message": "pro_plan_required", "description": "CryptoQuant Pro plan or higher is required." } } ``` ## Plan below Premium Analyst Consensus Index series endpoint. The description also names the plan the key is on: ```json theme={null} { "status": { "code": 403, "message": "premium_plan_required", "description": "CryptoQuant Premium plan or higher is required. This key is on the Advanced plan. Upgrade at https://cryptoquant.com/pricing." } } ``` ## Unknown asset Analyst Consensus Index endpoint — `{asset}` is not one of `BTC`, `ETH`, `SOL` (or their slugs): ```json theme={null} { "status": { "code": 404, "message": "unknown asset" } } ``` ## Invalid date parameter `from` / `to` must be `YYYY-MM-DD`: ```json theme={null} { "status": { "code": 400, "message": "invalid from" } } ``` ## Unknown equity ```json theme={null} { "status": { "code": 404, "message": "unknown equity" } } ``` ## Unknown metric ```json theme={null} { "status": { "code": 404, "message": "unknown metric" } } ``` # Indicator API Overview Source: https://docs.cryptoquant.com/indicator-api/overview The Alpha Library indicator set, organized by asset class — Bitcoin on-chain/technical signals and computed Korean equity fundamentals. The Indicator API documents the **Alpha Library** — the indicator set behind the [alpha.cryptoquant.com](https://alpha.cryptoquant.com) heatmap. Indicators are organized by asset class, and each one is sourced one of three ways depending on the asset. ## Indicators by asset class | Asset class | Indicators | Source | Reference | | - | - | - | - | | **Crypto (Bitcoin)** | On-chain valuation & demand, technical, and analyst consensus | Core CryptoQuant Data API (`api.cryptoquant.com`), in-app technical formulas, and the Alpha consensus API (`alpha.cryptoquant.com/api/consensus`) | [Crypto Indicators](/indicator-api/crypto) · [Analyst Consensus Index](/indicator-api/consensus) | | **Equities (KRX)** | Computed fundamentals from DART filings, prices, and market data | Alpha equities API (`alpha.cryptoquant.com/api/equities`) | [KRX Equities](/indicator-api/equities) | Every indicator is z-scored over a trailing multi-year window before it is colored on the heatmap (green = bull/buy regime, red = bear/sell regime). ## Alpha API surface The Alpha equities indicators and the Analyst Consensus Index are served from a dedicated host: ```text theme={null} https://alpha.cryptoquant.com/api ``` Unlike the core CryptoQuant Data API, these endpoints are productized indicators, not raw source-data feeds. ### Endpoint structure ```text theme={null} https://alpha.cryptoquant.com/api ├── /consensus │ └── /{asset} ├── /equities │ ├── /{asset} │ └── /{asset}/{metric} └── /indicators ``` | Endpoint | Access | Purpose | | - | - | - | | `GET /api` | Public | Top-level Alpha API catalog | | `GET /api/consensus` | Public | Analyst Consensus Index catalog: assets, metric metadata, field definitions | | `GET /api/consensus/{asset}` | Premium API key | Daily Analyst Consensus Index series for one asset (BTC, ETH, SOL) | | `GET /api/equities` | Public | Equity asset catalog, metric catalog, identifier policy, and data policy | | `GET /api/equities/{asset}` | Pro+ API key | All computed indicator series for one KRX equity | | `GET /api/equities/{asset}/{metric}` | Pro+ API key | One computed indicator series for one KRX equity | | `GET /api/indicators` | Public | Metadata-only Alpha Library indicator catalog (all asset classes) | > [!NOTE] > > Bitcoin on-chain indicators are served by the **core CryptoQuant Data API** > (`api.cryptoquant.com`), not the Alpha host. See [Crypto Indicators](/indicator-api/crypto) for the > endpoint behind each signal. The one crypto series on the Alpha host is the > [Analyst Consensus Index](/indicator-api/consensus), which requires the **Premium plan**. ## Data policy > [!NOTE] > > DART/OpenDART source filing rows are not redistributed. Equity endpoints expose only > computed indicators derived from filings, prices, and market data. Each equity metric is marked with: ```json theme={null} { "source": "dart-computed", "sourcePolicy": "dart-computed", "rawRedistribution": false } ``` ## Relationship to API v1 and API v2 | API surface | Host | Scope | | - | - | - | | Core API v1 | `api.cryptoquant.com/v1` | Raw on-chain, market, and flow data | | Core API v2 | `api.cryptoquant.com/v2` | Curated crypto research indicators | | Indicator API | `alpha.cryptoquant.com/api` | Alpha product indicators: KRX equity fundamentals and the Analyst Consensus Index | The response envelope intentionally follows the same `status` / `result` pattern used by the core CryptoQuant APIs. # Analyst Stance Source: https://docs.cryptoquant.com/sentiment/analyst-stance openapi/sentiment.json GET /sentiment One analyst's daily stance on one asset, oldest first — each sentiment_score from 0 (bearish) to 100 (bullish). Premium and Enterprise keys. ## What it returns One analyst's daily stance on one asset, oldest first. Each `sentiment_score` ranges from **0** (bearish) to **100** (bullish). ## Access Per-analyst data is available on the **Premium** and **Enterprise** plans; a Free key answers `401 PLAN_REQUIRED`. Valid handles come from [`/analysts/top`](/sentiment/top-analysts) or the [analysts page](https://consensus.cryptoquant.com/analysts). ## Parameters | Name | Default | Description | | - | - | - | | `handle` | — | Analyst handle (required unless `analyst_id` is given); case-insensitive. | | `analyst_id` | — | Analyst UUID (alternative to `handle`; wins when both are given). | | `asset` | `BTC` | Any registered asset (see [`/assets`](/sentiment/assets)). A pair with no rows answers `count: 0`. | | `days` | `30` | Days of history ending yesterday UTC; capped at 36,500. | ## Notes * `sentiment_score_key_calls` and `key_calls_count` describe the analyst's key calls that day; `sentiment_score_key_calls` is `null` when there are none. * No tracked analyst matching `handle` answers `404 ANALYST_NOT_FOUND`; an analyst excluded from the stance pipeline answers `404 ANALYST_NOT_ELIGIBLE`; no rows for the analyst × asset pair in the range answers `404 NO_DATA` — see [Errors](/sentiment/errors). # Analyst Track Record Source: https://docs.cryptoquant.com/sentiment/analyst-track-record openapi/sentiment.json GET /analysts/{handle} One analyst's accuracy record — scores and ranks, tier per asset class, call counts by source platform, recent bias, covered assets and where they publish. Public, no API key. ## What it returns One analyst's record: `accuracy_score`, `accuracy_sample_size`, bull / bear / short / long scores with their ranks, `overall_rank`, the tier per asset class, call counts split by source platform (`calls.by_source`) with the definition of a call, recent bias, covered assets, the profile URL and where they publish. `{handle}` is the X handle, the platform handle or the `/analyst/{slug}` page slug. ## Access Public — no API key, no session. Responses are CDN-cached for one hour and carry `score_notes` explaining every number. Scores are comparative 0–100 values, not win probabilities — see the [Methodology](https://consensus.cryptoquant.com/methodology). ## Notes * A **call** is one directional (bullish or bearish) item about one tracked asset, over the whole stored history: X posts, TradingView ideas, Seeking Alpha articles (title + summary), Substack posts and sell-side analyst ratings. An article on several tickers is one call per ticker on each asset page and counts once per article × ticker pair in its author's total. * `calls.by_source` keys are the [`source_platform`](/sentiment/enums) values; `sources[]` uses the `analyst_source` values (`twitter` = X). * `tier` / `tiers` carry the badge key (`top1` · `top5` · `top10` · `tracked`), the pool rank and size, and a `reason` when the tier is `null` — see [`tier_reason`](/sentiment/enums). * No tracked analyst matching `{handle}` answers `404 ANALYST_NOT_FOUND`. > [!TIP] > > Building an agent tool? The same call backs the CryptoQuant MCP tool `get_analyst_profile` — see > [For AI Agents](/sentiment/for-agents). # Analyst Views Source: https://docs.cryptoquant.com/sentiment/analyst-views openapi/sentiment.json GET /analyst-views What analysts are saying about an asset — narratives grouped by thesis and one quotable excerpt per analyst, with the bull / bear case and the post split. Public, no API key. ## What it returns `/analyst-views?asset=&window=7d|30d` — what analysts are saying: * **`narratives`** — viewpoints grouped by thesis with analyst counts. * **`analyst_views`** — one quotable excerpt per analyst (the first ≤ 200 characters of one post, original language) with `source_url` and `profile_url`. * The bull / bear case and the post split (`bullish_pct` / `bearish_pct` are post shares, neutral excluded). `analyst_views` lists analysts with ≥ 3 directional posts on the asset in the window and a ≥ 60 % consistent side. The Analyst Consensus Index itself is on [`/consensus`](/sentiment/consensus-index). ## Access Public — no API key. 60 requests / minute per IP, cached 5 minutes. ## Notes * Neither this endpoint nor [`/calls`](/sentiment/calls) carries the full post text — the original statement is provided under an Integration agreement only, per API key, on [`/consensus/breakdown`](/sentiment/consensus-breakdown) (contact [sales@cryptoquant.com](mailto:sales@cryptoquant.com)). * Both carry `page_url`, `cite_as` and `data_by` — show the attribution with the numbers; `via=` tags the links. # List Assets Source: https://docs.cryptoquant.com/sentiment/assets openapi/sentiment.json GET /assets The asset registry every asset parameter is resolved against — one row per registered ticker with its aliases, class, category, coverage and page URL, plus every enum. ## What it returns The registry every `asset` parameter is resolved against: one row per registered ticker with `symbol`, `key` (the `/consensus/{key}` page), `name`, `aliases`, `retired_symbols`, `asset_class`, `category`, `coverage` (`live` / `mapped` / `pending` = page but no analyst data yet) and `page_url`, plus every enum under `enums`. An alias ticker (`GLD`) points at its canonical asset (`XAU`) through `canonical`. ## Filters `asset_class`, `category`, `q` (substring of symbol / name / key). Filters combine with AND. ## Access Public — no API key. Responses are CDN-cached for one hour. > [!TIP] > > Pass any of `symbol`, `key`, `name`, an alias or a retired symbol as `asset` on the other > endpoints (case-insensitive); the response always reports the canonical symbol. > `coverage=pending` assets have a page but no analyst data yet. # Authentication Source: https://docs.cryptoquant.com/sentiment/authentication Keyed Sentiment Data endpoints read the API key from the X-API-Key header or the api_key query parameter. Keyed endpoints read the API key from one of these two places: > [tab] Header (Recommended) > > ```http theme={null} > GET /api/v1/consensus?asset=BTC&days=365 HTTP/1.1 > Host: consensus.cryptoquant.com > X-API-Key: > ``` > [tab] Query parameter > > ```text theme={null} > https://consensus.cryptoquant.com/api/v1/consensus?asset=BTC&days=365&api_key= > ``` > > Avoid this form in logged URLs. > [!WARNING] > > `Authorization: Bearer` is **not** read by this API. The CryptoQuant [Data API](/guides/authentication) > and the [Alpha Indicator API](/indicator-api/authentication) use a Bearer token; the Analyst > Consensus API uses the two forms above. Keys start with `unbias_live_`. ## Which endpoints need a key The public endpoints need no key at all: * [`/assets`](/sentiment/assets) * [`/consensus`](/sentiment/consensus-index) without `days` (the latest point) * [`/analyst-views`](/sentiment/analyst-views) and [`/calls`](/sentiment/calls) * [`/analysts/top`](/sentiment/top-analysts) and [`/analysts/{handle}`](/sentiment/analyst-track-record) A key unlocks the index history (`/consensus` with `days`), the per-asset breakdown (`/consensus/breakdown`) and — on the Premium and Enterprise plans — the per-analyst stance series (`/sentiment`). What each plan can read is on [Plans & Access](/sentiment/plans-and-access). ## Getting a key Keys are provisioned with the CryptoQuant **Premium** plan or an **Enterprise** agreement; there is no self-serve key endpoint on this host. * **Premium** — subscribe on the [CryptoQuant pricing page](https://cryptoquant.com/pricing) and use the API as part of your subscription. * **Enterprise** — [contact us](https://cryptoquant.com/contact-us) to discuss your use case. > [!NOTE] > > **Relationship to your CryptoQuant API key.** The Analyst Consensus API key is a separate > credential from the key you use on `api.cryptoquant.com` — it carries its own plan (separate from > your site login) and is sent as `X-API-Key`. The CryptoQuant API key is **not** accepted on > `consensus.cryptoquant.com` today. If you only need the daily Analyst Consensus Index for BTC, ETH > or SOL, your CryptoQuant Premium key can read it from the > [Indicator API](/indicator-api/consensus) with Bearer authentication. ## cURL ```bash theme={null} curl -X GET "https://consensus.cryptoquant.com/api/v1/consensus?asset=BTC&days=365" \ -H "X-API-Key: " ``` ## JavaScript ```javascript theme={null} const response = await fetch( "https://consensus.cryptoquant.com/api/v1/consensus?asset=BTC&days=365", { headers: { "X-API-Key": "" } } ); const json = await response.json(); ``` ## Python ```python theme={null} import requests headers = {"X-API-Key": ""} url = "https://consensus.cryptoquant.com/api/v1/consensus?asset=BTC&days=365" print(requests.get(url, headers=headers).json()) ``` A request without a key on a keyed endpoint answers `401 API_KEY_REQUIRED`; an unknown or inactive key answers `401 INVALID_API_KEY` — see [Errors](/sentiment/errors). # Recent Calls Source: https://docs.cryptoquant.com/sentiment/calls openapi/sentiment.json GET /calls The newest directional calls on an asset — analyst, stance, the post's ≤ 200-character excerpt, source link and analyst page, newest first. Public, no API key. ## What it returns `/calls?asset=&limit=` — the newest directional calls (analyst, stance, the post's ≤ 200-character excerpt, source link, analyst page), newest first, `limit` 1–50. A **call** = one directional (bullish / bearish) post about this asset by a tracked, eligible analyst; neutral posts are not calls. ## Access Public — no API key. 60 requests / minute per IP, cached 5 minutes. ## Notes * `excerpt` = the first ≤ 200 characters of the post (original language); quote it with its `source_url` and the analyst's `profile_url`. The full statement is provided under an Integration agreement only (contact [sales@cryptoquant.com](mailto:sales@cryptoquant.com)) — see [Raw source text](/sentiment/plans-and-access#raw-source-text). * Carries `page_url`, `cite_as` and `data_by` — show the attribution with the numbers; `via=` tags the links. # Consensus Breakdown Source: https://docs.cryptoquant.com/sentiment/consensus-breakdown openapi/sentiment.json GET /consensus/breakdown Structured per-asset analyst-consensus breakdown for a time window — summary stats, bull / bear case, viewpoints grouped by thesis with their analysts and source posts. ## What it returns Structured per-asset analyst-consensus breakdown for a time window. A single call returns everything needed to render a consensus view: * **Aggregated stats** → `summary` (opinion counts, bullish / bearish %, `consensus_index`, `z_score`) * **Bull / bear case summaries** → `overall.bull_case` / `overall.bear_case` * **Viewpoints grouped by thesis** → `analyst_consensus.bullish[]` / `bearish[]`, each with its analysts and the underlying source posts * **Source text per key** → `source_text` + `note`: a key cleared under an Integration agreement (per-key clearance, not a plan) receives `sources[].statement` (the original post); every other key — Free, Premium, Enterprise, admin — receives `sources[].excerpt` (first ≤ 200 characters) * `url`. Viewpoint titles, theses, the bull / bear case, the index and the labels are identical on every plan. See [Raw source text](/sentiment/plans-and-access#raw-source-text). ## Access API key, any plan. Raw source text on Integration keys only. ## Parameters | Name | Default | Description | | - | - | - | | `asset` | `BTC` | Any registered asset (see [`/assets`](/sentiment/assets)). | | `window` | `3d` | One of `1d`, `3d`, `7d`, `30d`. | | `lang` | `en` | Output language of the generated text (summaries, viewpoint titles): `en`, `ko`, `zh`, `ja`, `es`, `pt`, `ru`, `hi`, `de`, `fr`, `tr`, `vi`, `id`, `it`, `th`, `pl`, `nl`, `uk`. Source posts stay in their original language; a missing translation falls back to English. | | `source_text` | what the key may receive | `statement` or `excerpt`. `statement` on a key without Integration raw access → `403 RAW_ACCESS_REQUIRED` (contact [sales@cryptoquant.com](mailto:sales@cryptoquant.com)); `excerpt` is always allowed. | ## Field notes * `sources[].statement` (original post title / text) is provided under an Integration agreement only — a per-key clearance, never a plan: Premium, Enterprise and admin-owned keys without it get `sources[].excerpt` — the first ≤ 200 characters of the original, cut on a sentence / word boundary with an ellipsis, original language (never a translation). `source_text` names the field you received; `note` says the same in a sentence. Integration use that needs the original source text: contact [sales@cryptoquant.com](mailto:sales@cryptoquant.com). * `sources[].url` always links the underlying post; `source_type` is one of the [`source_type`](/sentiment/enums) values (`tweet` = X, `quicktake` = CryptoQuant, …). * An analyst's `x_url` and `profile_url` are each nullable — CryptoQuant-native authors have no X link, and some have no public profile page; `avatar_url` may be `null` or a generated placeholder. * `consensus_index` and `z_score` are the latest daily index of the asset (they do not vary by `window`); `null` for an asset that has no index series yet. * `updated_at` is the timestamp of the most recent source post in the response — use it to detect freshness for the selected window. ## Response on a key with Integration raw access `source_text: "statement"` — everything else identical to the excerpt form; only the `sources[]` items change shape: ```json theme={null} [ { "analyst_handle": "CryptoMichNL", "statement": "What to expect from #Bitcoin? Honestly, I don't think we're done with the run.", "url": "https://x.com/CryptoMichNL/status/2103900910501990879", "source_type": "tweet", "published_at": "2026-09-26T17:34:00+00:00" }, { "analyst_handle": "the_daily_digits", "statement": "$2.1B sits on $95K BTC calls for Oct 30, Deribit's biggest strike.", "url": "https://cryptoquant.com/insights/quicktake/6ac453b68fa8e62507c0bf1b", "source_type": "quicktake", "published_at": "2026-10-06T01:49:42+00:00" } ] ``` # Analyst Consensus Index Source: https://docs.cryptoquant.com/sentiment/consensus-index openapi/sentiment.json GET /consensus The daily Analyst Consensus Index — one analyst = one vote, from −100 (all bearish) to +100 (all bullish). Public for the latest point; API key for the daily history. ## What it measures The Analyst Consensus Index: one analyst = one vote (their latest directional post on the asset, weighted by recency and accuracy), **−100** (all bearish) to **+100** (all bullish), one daily series per asset. * **Without a key** it answers the latest point for any asset with the bull / bear case, the 30-day split and the links to cite. * **With a key** it answers the daily history (Premium / Enterprise: the whole range; Free: the latest point only). ## Response fields (series) | Field | Description | | - | - | | `consensus_index` | Raw daily index (−100 … +100); `null` on a day without enough calls. | | `consensus_index_30d_ma` | 30-day moving average of the index. | | `z_score` | 90-day rolling z-score of the 30-day MA. Colour rule used on the site: z ≥ +0.8 bullish (green), z ≤ −1.5 bearish (red). | | `bullish_analysts` / `bearish_analysts` / `total_analysts` | Voters by side that day. | | `bullish_opinions` / `bearish_opinions` / `total_opinions` | Directional posts counted that day. | ## Notes * `days` counts days of history ending yesterday UTC (keyed only). Positive integer, capped at the plan's limit (36,500 = everything on Premium / Enterprise). The full BTC history is ≈ 1,950 rows. * `granularity` — only `daily` is offered (there is no hourly series). * `via` — public form only: tags the payload's links with `utm_source` (`chatgpt`, `claude`, `mcp`, `gemini`, `perplexity`, `api`). * An unregistered `asset` answers `400 UNKNOWN_ASSET`; the list is [`GET /assets`](/sentiment/assets). * Public payloads carry `page_url`, `cite_as` and `data_by` ("Data by CryptoQuant Consensus") — show the attribution with the numbers. > [!NOTE] > > The same daily index for BTC, ETH and SOL is also served with a **CryptoQuant API key** through > the [Indicator API](/indicator-api/consensus) (`Authorization: Bearer`, `from`/`to`/`limit`/ > `order`) — the index only, without the breakdown, stance or track record. # Data Coverage & Freshness Source: https://docs.cryptoquant.com/sentiment/data-coverage Which assets the Analyst Consensus API covers, how far back the history goes, when values update, where the posts come from, and the conventions every endpoint follows. ## Assets **1,712 assets** — Crypto 61 · US Equities 1,618 · Indices & ETFs 22 · Commodities 8 · KR Equities 3. Every one is listed by [`GET /assets`](/sentiment/assets) and on the [coverage page](https://consensus.cryptoquant.com/coverage). The `asset` parameter of every endpoint accepts a ticker, the route key, the name, an alias or a retired ticker (case-insensitive), and the response names the canonical symbol. ## History Daily index since **2021-06-01** for BTC; other assets from their first tracked post (the public snapshot and the track record report `as_of`; a series starts at its first row). ## Freshness * **Index and stance series** are end-of-day (UTC). The latest point is the previous UTC day — the current day is excluded until it is complete, so values never change retroactively. * **The breakdown** is recomputed daily (English by 04:00 UTC, translations by 06:00 UTC) and its opinion counts every 4 hours. * **Caching.** Public payloads are CDN-cached 5 minutes (track record and assets: 1 hour); keyed responses are never cached. ## Sources Curated analysts on X (Twitter), CryptoQuant (QuickTake and research), Seeking Alpha, TradingView and Substack, plus licensed sell-side analyst ratings on equities. Each post is classified per asset into one of five labels — `bullish` · `bullish_nuance` · `neutral` · `bearish_nuance` · `bearish` — the four directional ones are calls and votes, `neutral` never is. Where an analyst publishes is `source_platform`, what kind of post a row is `source_type` — both closed lists under [Enums](/sentiment/enums). Browse the analysts at [consensus.cryptoquant.com/analysts](https://consensus.cryptoquant.com/analysts). ## Conventions | Convention | Rule | | - | - | | Dates | `date` = UTC calendar day `YYYY-MM-DD`; timestamps are RFC 3339 / ISO 8601 in UTC. The current UTC day is never in a series. | | Pagination | None. A series comes back whole (`days` capped by the plan); lists are capped by `limit` (1–50, clamped silently). There is no cursor, offset or page parameter. | | Filters | Combine with AND. Unknown parameters are ignored; an enum parameter outside its values is a `400 INVALID_PARAMETER` with the accepted list in `message`. | | Sorting | Fixed per endpoint: series oldest first by date; `/calls` newest first; `/analysts/top` by `accuracy_score` desc (ties: sample size, then handle); `/assets` in registry order. | | Enums | Every enum is closed and listed in full on [Enums](/sentiment/enums); `GET /assets` returns them at runtime under `enums`. | > [!NOTE] > > These conventions differ from the CryptoQuant Data API's `window`/`from`/`to` > [time convention](/guides/time-convention) and `status`/`result` envelope — Sentiment Data > responses are flat JSON objects, and series are selected with `days`. # Enums Source: https://docs.cryptoquant.com/sentiment/enums Every value set the Analyst Consensus API speaks, listed in full — asset classes, source platforms, sentiment labels, stances, tier badges, windows, languages and plan ids. Every value set the API speaks, listed in full. The same lists are in the [OpenAPI document](https://consensus.cryptoquant.com/openapi.json) and are returned at runtime by [`GET /assets`](/sentiment/assets) under `enums`. | Enum | Values | Used for | | - | - | - | | `asset_class` | `crypto` · `equities` · `indices` · `commodities` | `asset_class` of an asset / a tier row | | `asset_category` | `crypto` · `us-equities` · `indices` · `commodities` · `kr-equities` | `category` (market) of an asset — the coverage-page grouping | | `asset_source` | `alpha` · `sellside` · `unbias` · `legacy` | which registry an asset row comes from | | `source_platform` | `x` · `cryptoquant` · `seekingalpha` · `tradingview` · `substack` · `benzinga` | where a tracked analyst publishes (`sources[]`, `calls.by_source` keys; `x` = X / Twitter, `benzinga` = licensed sell-side ratings) | | `analyst_source` | `twitter` · `cryptoquant` · `seekingalpha` · `tradingview` · `substack` · `other` | stored provenance of an analyst row (`sources[]` on the track-record payloads; `twitter` = X) | | `source_type` | `tweet` · `quicktake` · `research` · `news` · `seekingalpha` · `tradingview` · `substack` · `youtube` · `telegram` · `bluesky` | `source_type` of a post (`tweet` = X, `quicktake` / `research` = CryptoQuant, `news` = a news article) | | `sentiment_label` | `bullish` · `bullish_nuance` · `neutral` · `bearish_nuance` · `bearish` | per-post classifier label, bullish → bearish (`*_nuance` = directional with caveats) | | `directional_label` | `bullish` · `bullish_nuance` · `bearish_nuance` · `bearish` | the labels that count as a call / vote (`neutral` never does) | | `stance` | `bullish` · `bearish` · `neutral` | side of an aggregate: narrative, analyst view, call | | `bias` | `bullish` · `bearish` · `balanced` | `bias` / `recent_bias` of an analyst | | `tier_badge` | `top1` · `top5` · `top10` · `tracked` | accuracy badge key (Top 1% / 5% / 10% / Tracked) | | `tier_reason` | `excluded` · `ineligible` · `news_feed` · `company` · `unscored` · `insufficient_calls` · `pool_too_small` | why a tier is `null` | | `breakdown_window` | `1d` · `3d` · `7d` · `30d` | [`/consensus/breakdown`](/sentiment/consensus-breakdown) `window` | | `views_window` | `7d` · `30d` | [`/analyst-views`](/sentiment/analyst-views) `window` | | `breakdown_lang` | `en` · `ko` · `zh` · `ja` · `es` · `pt` · `ru` · `hi` · `de` · `fr` · `tr` · `vi` · `id` · `it` · `th` · `pl` · `nl` · `uk` | [`/consensus/breakdown`](/sentiment/consensus-breakdown) `lang` (generated text only; source posts keep their language) | | `via` | `chatgpt` · `claude` · `mcp` · `gemini` · `perplexity` · `api` | `via=` on the public endpoints — tags the links in the payload with `utm_source` | | `plan` | `free` · `pro` · `premium` · `enterprise` | API-key plan ids (`pro` = the pre-October-2026 Enterprise row) — see [Plans & Access](/sentiment/plans-and-access) | # Errors & Rate Limits Source: https://docs.cryptoquant.com/sentiment/errors Every Analyst Consensus API error is one JSON object with a stable code — this page lists each code with its HTTP status and what to do, plus the rate-limit headers. Every error is one JSON object: `error` (short legacy wording), `code` (stable — branch on this), `message` (what happened and what to do), `docs_url`, and per code `param`, `required_plans` / `upgrade_url` / `contact_url`, `limit` / `used` or `retry_after`. ```json theme={null} { "error": "Premium or Enterprise plan required", "code": "PLAN_REQUIRED", "message": "This key (Free plan) has no access to per-analyst data. Per-analyst endpoints are available on the Premium and Enterprise plans: subscribe to CryptoQuant Premium (upgrade_url) or contact CryptoQuant for Enterprise / trial access (contact_url).", "docs_url": "https://docs.cryptoquant.com/sentiment/plans-and-access", "plan": "FREE", "required_plans": ["premium", "enterprise"], "upgrade_url": "https://cryptoquant.com/pricing", "contact_url": "https://cryptoquant.com/get-in-touch", "upgradeUrl": "https://cryptoquant.com/pricing" } ``` > [!NOTE] > > These codes are specific to the Analyst Consensus API. The CryptoQuant Data API uses the > `status`/`result` envelope described in [Status & Error Codes](/guides/status-codes). ## Error codes | `code` | HTTP | What to do | | - | - | - | | `API_KEY_REQUIRED` | 401 | Send the key in the `X-API-Key` header (or the `api_key` query parameter). The key-free endpoints (`/assets`, `/analysts/*`, `/analyst-views`, `/calls`, `/consensus` without `days`) need none. | | `INVALID_API_KEY` | 401 | The key is unknown, inactive, expired, or its subscription is not active. Do not retry with the same key; obtain a valid one. | | `PLAN_REQUIRED` | 401 | The key's plan cannot read this endpoint. `required_plans` names the plans that can: upgrade at `upgrade_url` or contact sales at `contact_url`. Do not retry on the same plan. | | `RAW_ACCESS_REQUIRED` | 403 | The original source statement (full post text) is provided under an Integration agreement only, per key (not a plan: premium, enterprise and admin-owned keys without it get the excerpt). Drop `source_text=statement` to receive the ≤ 200-character excerpt + source link, or contact [sales@cryptoquant.com](mailto:sales@cryptoquant.com) (`contact_email`) for Integration raw-text access. Do not retry unchanged. | | `DAILY_LIMIT_EXCEEDED` | 429 | Free plan daily quota used (`limit` / `used`). It resets at 00:00 UTC; wait, or upgrade. | | `RATE_LIMIT_EXCEEDED` | 429 | Per-minute (keyed: your plan's `rate_limit_per_minute`; key-free: per-IP) limit hit. Wait `retry_after` seconds (header `Retry-After`), then retry; spread calls over the minute. | | `INVALID_PARAMETER` | 400 | A query parameter is malformed or outside its accepted values: `param` names it and `message` lists what is accepted. Fix the request; never retry it unchanged. | | `UNKNOWN_ASSET` | 400 | The asset is not registered. Resolve the name or ticker through [`GET /assets`](/sentiment/assets) (`symbol`, `key`, `name`, `aliases`) and retry with that symbol. | | `ANALYST_NOT_FOUND` | 404 | No tracked analyst matches. Pick a handle from [`GET /analysts/top?asset=…`](/sentiment/top-analysts) (field `handle`) and retry. | | `ANALYST_NOT_ELIGIBLE` | 404 | The analyst exists but is excluded from the stance pipeline (feed, company account, stakeholder). Not retryable. | | `NO_DATA` | 404 | No rows for that analyst × asset pair in the queried range. Not retryable; try another asset the analyst covers (`covered_assets` on [`/analysts/{handle}`](/sentiment/analyst-track-record)). | | `SERVICE_UNAVAILABLE` | 503 | An upstream list was unavailable. Retry after a few seconds with the same request. | | `INTERNAL_ERROR` | 500 | Our fault. Retry once after a few seconds; if it persists, report the full URL to [support](https://cryptoquant.com/contact-us). | ## Rate limit headers Responses include headers to help you track your usage: | Header | Description | | - | - | | `X-RateLimit-Limit` | Requests allowed per minute (your plan's limit; per IP on the public endpoints) | | `X-RateLimit-Remaining` | Requests remaining this minute | | `Retry-After` | On a 429: seconds to wait before retrying (also `retry_after` in the body) | | `X-Daily-Limit` | Daily limit (Free plan only) | | `X-Daily-Used` | Requests used today (Free plan only) | The per-plan limits are on [Plans & Access](/sentiment/plans-and-access). # For AI Agents Source: https://docs.cryptoquant.com/sentiment/for-agents Machine-readable access to Sentiment Data — the OpenAPI document, the Markdown index, and the Analyst Consensus MCP server (Streamable HTTP, no auth). The Analyst Consensus API ships three machine-readable surfaces next to this documentation. They are served by the consensus service itself, so they always describe the API as currently deployed. ## OpenAPI document ```text theme={null} https://consensus.cryptoquant.com/openapi.json https://consensus.cryptoquant.com/openapi.yaml ``` OpenAPI 3.1, version 2.2.0 — every endpoint with parameters, response schemas, validated examples, the structured error body, every enum in full, and an `x-plan` block per operation saying who may call it. Import it as a ChatGPT GPT Action (Authentication: None for the public operations) or any OpenAPI tool loader. The same document is also served at `/.well-known/openapi.json`. The spec also carries these top-level extension blocks: | Block | Contents | | - | - | | `x-plans` | Every plan with its endpoints, rate and daily limits, history and raw-source-text rule | | `x-raw-source-text` | How the Integration clearance works and how to request it | | `x-errors` | Every error code with its HTTP status and recovery | | `x-conventions` | Dates, pagination, filters, sorting, enums, caching | | `x-mcp` | The MCP server URL, transport and tool list | | `x-alternatives` | The CryptoQuant [Indicator API](/indicator-api/consensus) route to the daily index, `llms.txt`, `openapi.yaml` | > [!NOTE] > > This documentation renders a snapshot of that document (`openapi/sentiment.json`). If the two ever > disagree, the live `/openapi.json` is the source of truth. ## Markdown index ```text theme={null} https://consensus.cryptoquant.com/llms.txt ``` The Markdown index for answer engines — the same field reference as these pages. Append `.md` to any page on this site as well (for example `/sentiment/consensus-index.md`). ## MCP server ```text theme={null} https://consensus.cryptoquant.com/mcp ``` The same data as a remote **MCP server** — Streamable HTTP, read-only, stateless, **no authentication**, per-IP rate limit. Point a Claude connector, ChatGPT or any MCP client at the URL above. Tools: | Tool | Backed by | | - | - | | `get_consensus` | [`GET /consensus`](/sentiment/consensus-index) — the Analyst Consensus Index for an asset | | `get_analyst_views` | [`GET /analyst-views`](/sentiment/analyst-views) — what analysts are saying about an asset | | `get_top_analysts` | [`GET /analysts/top`](/sentiment/top-analysts) — the most accurate analysts on an asset | | `get_analyst_profile` | [`GET /analysts/{handle}`](/sentiment/analyst-track-record) — one analyst's track record | | `get_recent_calls` | [`GET /calls`](/sentiment/calls) — the newest analyst calls on an asset | Tag your surface with `?via=chatgpt` or `?via=claude` — the links in every answer carry the matching `utm_source`. A plain `GET` on the URL (without an MCP `Accept: text/event-stream`) returns a text description of the server. > [!NOTE] > > This MCP server covers Sentiment Data only. The CryptoQuant on-chain and market data MCP server is > at `https://mcp.cryptoquant.com/mcp` — see the [MCP Server guide](/guides/mcp-server). ## Attribution Every public payload carries `page_url` (link it), `cite_as` and `data_by` ("Data by CryptoQuant Consensus") — show the attribution with the numbers. # Sentiment Data Overview Source: https://docs.cryptoquant.com/sentiment/overview The Analyst Consensus API — what curated analysts say about 1,700+ assets as numbers: the daily Analyst Consensus Index, per-asset breakdowns, analyst views and calls, and every analyst's accuracy track record. **Sentiment Data** is the Analyst Consensus API from [consensus.cryptoquant.com](https://consensus.cryptoquant.com): what curated analysts say about 1,712 assets — crypto, US and KR equities, index ETFs and commodities — as numbers. It serves the daily **Analyst Consensus Index**, per-asset consensus **breakdowns**, **analyst views and calls**, and every analyst's **accuracy track record**. ```text theme={null} API root endpoint https://consensus.cryptoquant.com/api/v1/ ``` > [!NOTE] > > This API is served by the Analyst Consensus service, not by `api.cryptoquant.com`. It has its own > base URL, its own API key (`X-API-Key`, not `Authorization: Bearer`) and its own plan rules — see > [Authentication](/sentiment/authentication) and [Plans & Access](/sentiment/plans-and-access). > The daily index alone is also available with a CryptoQuant API key through the > [Indicator API](/indicator-api/consensus). ## Who can use it The Analyst Consensus API is available on the **Premium** plan and the **Enterprise** plan. Choose the path that fits you: > [card] [Premium plan](https://cryptoquant.com/pricing) > > **Individuals and small teams.** Subscribe to CryptoQuant Premium and use the API as part of > your subscription. > [card] [Enterprise plan](https://cryptoquant.com/contact-us) > > **Institutions and research teams.** Full history, higher rate limits and dedicated > onboarding. Pricing is custom per institution. ## Quick start **1. Call a public endpoint — no key needed** The latest index point of any asset, what analysts are saying, the newest calls, the analyst track record and the asset registry need no API key: ```bash theme={null} curl -X GET "https://consensus.cryptoquant.com/api/v1/consensus?asset=NVDA" ``` **2. Get an API key for history and per-analyst data** For the index history, the per-asset breakdown and per-analyst data, get an API key — subscribe to the [Premium plan](https://cryptoquant.com/pricing), or [contact us](https://cryptoquant.com/contact-us) for Enterprise access — and send it with every request: ```bash theme={null} curl -X GET "https://consensus.cryptoquant.com/api/v1/consensus?asset=BTC&days=365" \ -H "X-API-Key: " ``` **3. Building a tool or an agent?** Import the machine-readable spec from [`/openapi.json`](https://consensus.cryptoquant.com/openapi.json) or [`/openapi.yaml`](https://consensus.cryptoquant.com/openapi.yaml) (OpenAPI 3.1, version 2.2.0 — every endpoint with parameters, response schemas, validated examples, the structured error body, every enum in full, and an `x-plan` block per operation saying who may call it). The same data is an MCP server at [`https://consensus.cryptoquant.com/mcp`](https://consensus.cryptoquant.com/mcp) (Streamable HTTP, no auth). See [For AI Agents](/sentiment/for-agents). ## Endpoints | Endpoint | Access | What it returns | | - | - | - | | [`GET /assets`](/sentiment/assets) | Public | The asset registry every `asset` parameter resolves against, plus every enum | | [`GET /consensus`](/sentiment/consensus-index) | Public (latest point) · API key (history) | The daily Analyst Consensus Index, −100 … +100 | | [`GET /consensus/breakdown`](/sentiment/consensus-breakdown) | API key, any plan | Bull / bear case, viewpoints grouped by thesis, source posts | | [`GET /sentiment`](/sentiment/analyst-stance) | Premium / Enterprise key | One analyst's daily stance on one asset | | [`GET /analyst-views`](/sentiment/analyst-views) | Public | Narratives and one quotable view per analyst | | [`GET /calls`](/sentiment/calls) | Public | The newest directional calls on an asset | | [`GET /analysts/top`](/sentiment/top-analysts) | Public | The asset's analysts ranked by accuracy | | [`GET /analysts/{handle}`](/sentiment/analyst-track-record) | Public | One analyst's accuracy record | ## Learn more > [card] [Authentication](/sentiment/authentication) > > `X-API-Key` header or `api_key` query parameter — and how it differs from the Data API. > [card] [Plans & Access](/sentiment/plans-and-access) > > What No key, Free, Premium and Enterprise can read; rate and daily limits; raw source text. > [card] [Data Coverage & Freshness](/sentiment/data-coverage) > > 1,712 assets, history since 2021-06-01, end-of-day UTC, sources and conventions. > [card] [Errors](/sentiment/errors) > > Every error code with its HTTP status and what to do; rate-limit headers. > [card] [Methodology](https://consensus.cryptoquant.com/methodology) > > How the consensus index, the accuracy scores and the tier badges are calculated. > [card] [Support](https://cryptoquant.com/contact-us) > > Questions or issues? Contact us. # Plans & Access Source: https://docs.cryptoquant.com/sentiment/plans-and-access What each Analyst Consensus API plan can read — endpoints, history, rate limits and daily limits — and how raw source text is cleared. An API key carries its own plan (separate from your site login). What each plan can read: | Plan | Endpoints | History | Rate limit | Daily limit | | - | - | - | - | - | | **No key** | The public endpoints — [`/assets`](/sentiment/assets), [`/consensus`](/sentiment/consensus-index) without `days`, [`/analyst-views`](/sentiment/analyst-views), [`/calls`](/sentiment/calls), [`/analysts/top`](/sentiment/top-analysts), [`/analysts/{handle}`](/sentiment/analyst-track-record) | Latest point | 60 / min per IP | None (CDN-cached) | | **Free** | Public + `/consensus` (latest point) + [`/consensus/breakdown`](/sentiment/consensus-breakdown) (source posts as short excerpts + links). No per-analyst data (`/sentiment` → `401 PLAN_REQUIRED`). | 7 days | 10 / min | 100 / UTC day | | **Premium** | Everything, including per-analyst data; source posts as short excerpts + links | Full | 1,000 / min | None | | **Enterprise** | Everything, including per-analyst data; source posts as short excerpts + links (the raw source text is a separate per-key Integration clearance, below); custom terms, dedicated onboarding and support | Full | 1,000 / min | None | * **Premium** — for individuals and small teams. Subscribe on the [CryptoQuant pricing page](https://cryptoquant.com/pricing) and use the API as part of your subscription. The daily index is also exposed through the CryptoQuant [Indicator API](/indicator-api/consensus). * **Enterprise** — for institutions and quantitative research teams; pricing is custom per institution. [Contact us](https://cryptoquant.com/contact-us) to discuss your use case. Keys issued on the earlier Enterprise agreement (plan id `pro`) keep the full Enterprise access, raw source text included. A request outside your plan answers `401` with `code: "PLAN_REQUIRED"`, `required_plans`, `upgrade_url` and `contact_url` — see [Errors](/sentiment/errors). ## Raw source text Raw source text is an **Integration agreement only**, granted per API key (not a plan): a cleared key receives `/consensus/breakdown` `sources[].statement` = the original post title / text. Every other key — Free, Premium, Enterprise and admin-owned keys without the clearance — gets the thesis, narratives, index and bullish / bearish labels + the source link + a short excerpt (`sources[].excerpt`, the first ≤ 200 characters, original language). Asking for it explicitly (`source_text=statement`) without the clearance answers `403 RAW_ACCESS_REQUIRED`. The key-free `/analyst-views` and `/calls` excerpts follow the same ≤ 200-character rule — the full text never leaves without a cleared key. > [!NOTE] > > Integration use that needs the original source text: contact > [sales@cryptoquant.com](mailto:sales@cryptoquant.com). ## Plan ids The `plan` field on error bodies and the `x-plan` block of every operation in the OpenAPI document use these ids: | id | Plan | | - | - | | `free` | Free | | `premium` | Premium | | `enterprise` | Enterprise | | `pro` | Enterprise (the pre-October-2026 Enterprise row — behaves as `enterprise`) | # Top Analysts Source: https://docs.cryptoquant.com/sentiment/top-analysts openapi/sentiment.json GET /analysts/top The asset's analysts ranked by accuracy_score among those active in the last three calendar months, each with its tier badge. Public, no API key. ## What it returns The asset's analysts ranked by `accuracy_score` among those active in the last three calendar months. `asset` = any registered asset (default `BTC`); `limit` 1–50 (default 20). Each row carries its tier badge (Top 1% / 5% / 10% / Tracked — quote the badge, not the score). > [!NOTE] > > Accuracy scoring covers **crypto** today: for stocks, ETFs and commodities the list is returned > with `scored: false` and `null` scores. ## Access Public — no API key, no session. Responses are CDN-cached for one hour and carry `score_notes` explaining every number. ## Reading the scores Scores are **comparative 0–100 values, not win probabilities** — see the [Methodology](https://consensus.cryptoquant.com/methodology). * `accuracy_score` — overall accuracy, 0–100: an Empirical-Bayes-adjusted hit rate of the analyst's directional calls against subsequent price moves, shrunk toward the pool mean when the sample is small. Rank analysts on the same asset by it. * `accuracy_sample_size` — number of evaluated calls behind `accuracy_score`. Treat scores with a sample below \~10 as weak evidence. > [!TIP] > > Building an agent tool? The same call backs the CryptoQuant MCP tool `get_top_analysts` — see > [For AI Agents](/sentiment/for-agents). # v2 Community Metric Catalog Source: https://docs.cryptoquant.com/v2/catalog Community-built indicator metrics available in API v2 — endpoints, response fields, and interpretation guides. Curated, research-grade indicators. For raw exchange & aggregated market time-series (OHLCV, trade, funding, open interest, liquidation), see [Market Data](/v2/market/overview). | Metric | Endpoint | Fields | Asset | | - | - | - | - | | [Apparent Demand Growth 30-days](/v2/community/bitcoin-apparent-demand) | `/v2/community/bitcoin-apparent-demand` | `apparent_demand` `apparent_demand_1y` | bitcoin | | [ETF Bitcoin Demand 30-days](/v2/community/bitcoin-etf-demand) | `/v2/community/bitcoin-etf-demand` | `etf_demand_30d` `etf_demand_1y` | bitcoin | | [MVRV Z-score](/v2/community/bitcoin-mvrv-z-score) | `/v2/community/bitcoin-mvrv-z-score` | `mvrv_ratio_zscore` | bitcoin | | [On-chain Trader Realized Price bands](/v2/community/bitcoin-trader-realized-price) | `/v2/community/bitcoin-trader-realized-price` | `realized_price_1m_3m` `realized_price_max_band` `realized_price_upper_band` `realized_price_lower_band` `realized_price_min_band` | bitcoin | | [Bitcoin Metcalfe's Price](/v2/community/bitcoin-metcalfe-price) | `/v2/community/bitcoin-metcalfe-price` | `active_addresses_squared_price_365ma` `active_addresses_squared_50_price_365ma` `active_addresses_squared_25_price_365ma` `active_addresses_squared_10_price_365ma` `active_addresses_squared_3x_price_365ma` `active_addresses_squared_2x_price_365ma` `active_addresses_squared_04_price_365ma` | bitcoin | | [On-chain Trader Unrealized Profit/Loss Margin](/v2/community/bitcoin-trader-unrealized-profit-margin) | `/v2/community/bitcoin-trader-unrealized-profit-margin` | `nupl_1m_3m` | bitcoin | | [Realized Net Profit and Loss](/v2/community/bitcoin-realized-profit-loss) | `/v2/community/bitcoin-realized-profit-loss` | `positive_net_realized_profit` `negative_net_realized_profit` `yearly_realized_net_profit_btc` `yearly_realized_net_profit_usd` `monthly_realized_net_profit_btc` `monthly_realized_net_profit_usd` `positive_monthly_realized_net_profit_btc` `negative_monthly_realized_net_profit_btc` `positive_net_realized_profit_btc` `negative_net_realized_profit_btc` | bitcoin | | [OP Return Count](/v2/community/bitcoin-op-return-count) | `/v2/community/bitcoin-op-return-count` | `amount_null_data` | bitcoin | | [Satoshi-era miner](/v2/community/bitcoin-satoshi-era-miner) | `/v2/community/bitcoin-satoshi-era-miner` | `netflow` `netflow_usd` `total_balance` `total_balance_usd` `active_addresses` | bitcoin | | [PnL Index](/v2/community/bitcoin-pnl-index) | `/v2/community/bitcoin-pnl-index` | `pnl_index` `pnl_index_365day_ma` `buy` `neutral` | bitcoin | | [Bull-Bear Market Indicator](/v2/community/bitcoin-bull-bear-indicator) | `/v2/community/bitcoin-bull-bear-indicator` | `bull_bear_indicator` `type` | bitcoin | # Apparent Demand Growth 30-days Source: https://docs.cryptoquant.com/v2/community/bitcoin-apparent-demand openapi/v2.json GET /community/bitcoin-apparent-demand The 30-day change in Bitcoin Spot Demand, The 1-year change in Bitcoin Spot Demand ## What it measures Net change in Bitcoin supply inactive for 1+ year, adjusted for daily block rewards, as a 30-day and 1-year rolling sum in BTC ## How to interpret it 30-day. Positive = market absorbing more BTC than being released (bullish). Negative = supply outpacing demand (bearish). Sharp reversals from deep negative territory have historically preceded price rallies. 1-year. Rising = institutional/long-term capital accumulating structurally (bull). Falling even alongside rising prices = bull cycle losing foundation. Both 30D and 1Y negative simultaneously = confirmed bear market. ## Key thresholds 30-day. 490K–550K BTC = peak demand cycle tops; 0 = critical demand/supply boundary; Below 0 = contraction; Below –200K BTC = extreme weakness. A 30-day moving average crossover (above/below) indicates bullish/bearish conditions forming. 1-year. Positive and rising = structural bull; Flat/slowing = mid-cycle warning; Negative or below its 365-day moving average = bear market (–857K BTC recorded in April 2026 bear phase) ## How to use it 30-day. Necessary condition for sustained ATH rallies. Slowing rate of decline before zero crossing = early reversal signal. Read alongside ETF demand and whale accumulation. 1-year. Compare against 30-day reading to assess momentum direction. 1-year still positive but 30-day negative = bull correction. Both negative = structural bear market confirmed. > [card] [Run this metric in CryptoQuant Analytics](https://cryptoquant.com/analytics/query/6678ab90a0017a125b273dc3) # Bull-Bear Market Indicator Source: https://docs.cryptoquant.com/v2/community/bitcoin-bull-bear-indicator openapi/v2.json GET /community/bitcoin-bull-bear-indicator The bull/bear market cycle indicator is a momentum metric. It measures the difference between the P&L Index and its 365-day moving average. ## What it measures The Bull/Bear Market Cycle Indicator is a momentum metric built on top of the [P\&L Index](/v2/community/bitcoin-pnl-index). It measures the difference between the P\&L Index and its 365-day moving average, isolating the direction and strength of the current market cycle rather than the absolute valuation level. ## How to interpret it Because it tracks the P\&L Index relative to its own long-term trend, the indicator reads as a cycle-phase signal: * **Above 0** — the P\&L Index is above its 365-day average, indicating bullish momentum and a bull cycle. * **Below 0** — the P\&L Index is below its 365-day average, indicating bearish momentum and a bear cycle. Crosses of the zero line mark transitions between cycle phases, making the indicator useful for confirming regime shifts. ## Key thresholds * **Bull cycle:** indicator above 0. * **Bear cycle:** indicator below 0 and below its 365-day moving average. > [card] [Run this metric in CryptoQuant Analytics](https://cryptoquant.com/analytics/query/64f0d29476be393d0708f5c6) # ETF Bitcoin Demand 30-days Source: https://docs.cryptoquant.com/v2/community/bitcoin-etf-demand openapi/v2.json GET /community/bitcoin-etf-demand The 30-day and 1-year net Bitcoin purchase by spot Bitcoin ETFs (US, Europe and Canada) ## What it measures Net cumulative BTC purchased or sold by spot Bitcoin ETFs (US, Europe and Canada) over a 30-day and 1-year rolling window. ## How to interpret it 30-day. Positive = ETFs are net buyers. Negative = net sellers. Accelerating = institutional conviction growing. Decelerating even while positive = fading conviction. 1-year. Reveals whether institutional adoption is genuinely growing structurally or temporarily. Allows direct year-over-year comparison of institutional participation. ## Key thresholds \~9K BTC/day avg (Q1 2024) = peak buying pace; 5–8K BTC/day = strong demand; Near 0 or negative = net selling mode; ETF demand = \~33% of total demand at Dec 2024 peak ## How to use it Monitor alongside broader apparent demand. ETF demand alone is insufficient to drive ATH rallies without expanding total market demand. > [card] [Run this metric in CryptoQuant Analytics](https://cryptoquant.com/analytics/query/686530f2d040215728725e4e) # Bitcoin Metcalfe's Price Source: https://docs.cryptoquant.com/v2/community/bitcoin-metcalfe-price openapi/v2.json GET /community/bitcoin-metcalfe-price Bitcoin price valuation based on Metcalfe's model following the formula A*Active addresses^ 2. Each band represents a different value of A (3, 2, 1, 0.5, 0.25, 0.1 and 0.04) ## What it measures Fair value modeled from Metcalfe's Law as A × active addresses², where the coefficient A is calibrated from the historical relationship between market cap and active addresses² (i.e. A ≈ market cap ÷ active addresses²). Different A-coefficients produce a family of upper/lower valuation bands. ## How to interpret it Central Metcalfe Price = network-activity-based fair value. Higher A bands (3x, 2x) = upper valuation limits historically acting as resistance in bull markets. Lower A bands (0.5, 0.25, 0.1, 0.04) = lower support/fair value range. Bands themselves move with network activity levels. ## Key thresholds Red band (higher A): price resistance in bull markets, short-term rally targets; A=2x band: key support/resistance (\~\$91K in Nov 2025); Blue band (lower A): lower fair value support; Price between red and blue bands since Feb 2024 = "fair value range" ## How to use it Assess whether price is fundamentally supported by user activity. Price above red band = overvalued vs. network usage. Price bouncing off blue band = fundamental support. Watch bands shift downward when network activity (e.g. OP\_RETURN, transactions) declines. > [card] [Run this metric in CryptoQuant Analytics](https://cryptoquant.com/analytics/query/645d2594b1620f2a58fc7594) # MVRV Z-score Source: https://docs.cryptoquant.com/v2/community/bitcoin-mvrv-z-score openapi/v2.json GET /community/bitcoin-mvrv-z-score The Z-score of Bitcoin's MVRV Ratio ## What it measures MVRV ratio standardized as a Z-score — how many standard deviations current MVRV is from its historical mean ## How to interpret it Detects cycle extremes. Rising far above mean = market cap unusually high vs. aggregate cost basis (top zone). Crossing below 365-day MA = upward trend losing momentum. ## Key thresholds Z-score crossing below 365D MA = key bearish signal (sharp correction or start of bear market); Deep negative Z-score = extreme undervaluation near bear bottoms; Crossing above mean from below = early bull confirmation ## How to use it Most powerful combined with other valuation metrics. Z-score below 1-year MA while Bull Score \< 40 = high-conviction bear signal. Z-score crossing above trend during Bull Score recovery above 40 = bull cycle confirmed. > [card] [Run this metric in CryptoQuant Analytics](https://cryptoquant.com/analytics/query/664f7108175b1a2956933a59) # OP Return Count Source: https://docs.cryptoquant.com/v2/community/bitcoin-op-return-count openapi/v2.json GET /community/bitcoin-op-return-count The total amount of OP Return codes in Bitcoin transactions ## What it measures Total daily count of OP\_RETURN codes embedded in Bitcoin transactions — used by protocols (RUNES, Ordinals, OMNI/Tether) to write data on-chain ## How to interpret it High OP\_RETURN activity = strong secondary protocol demand → more transaction competition → higher fees → more miner revenue. Sudden collapses drag down transaction count, block utilization, fees, and cause Metcalfe bands to shift downward. ## Key thresholds 802K/day (Apr 2024) = all-time high at RUNES launch; 508K (Nov 2024) = still elevated; \~10K (Feb 2025) = collapsed 98%+ causing network activity one-year low; 81M total in 2024 = record annual inscriptions ## How to use it Primary indicator for network demand and fee-pressure. Monitor for sustained collapses as an early warning of falling miner revenue, lower transaction fees, and downward pressure on Metcalfe valuation bands. > [card] [Run this metric in CryptoQuant Analytics](https://cryptoquant.com/analytics/query/66281e322bbda620d309d72c) # PnL Index Source: https://docs.cryptoquant.com/v2/community/bitcoin-pnl-index openapi/v2.json GET /community/bitcoin-pnl-index CryptoQuant's P&L Index uses the MVRV ratio, NUPL and LTH/STH SOPR to build a single bitcoin valuation indicator. ## What it measures The P\&L (Profit & Loss) Index combines several on-chain profitability metrics — the MVRV ratio, NUPL, and the LTH/STH SOPR ratio — into a single normalized bitcoin valuation indicator. By aggregating these signals, it captures the aggregate profit/loss state of the market in one value, smoothing out the noise of any individual metric. ## How to interpret it The index oscillates around a neutral zone, with extremes flagging stretched valuations: * **Values above 1 (red line)** indicate bitcoin price is overvalued — the market is broadly in heavy unrealized profit, which historically coincides with cycle tops and elevated selling pressure. * **Values below -1.38 (green line)** indicate bitcoin price is undervalued — the market is broadly in unrealized loss, historically marking accumulation zones and cycle bottoms. ## Key thresholds * **Overvalued:** above 1 (red line) * **Undervalued:** below -1.38 (green line) To determine whether bitcoin is in a bull or bear market, compare the P\&L Index against its 365-day moving average: trading above the moving average signals a bull regime, while trading below it signals a bear regime. > [card] [Run this metric in CryptoQuant Analytics](https://cryptoquant.com/analytics/query/646cfa3c63e4017215b7f3c7?v=646cfa3c63e4017215b7f3c9) # Realized Net Profit and Loss Source: https://docs.cryptoquant.com/v2/community/bitcoin-realized-profit-loss openapi/v2.json GET /community/bitcoin-realized-profit-loss The net realized profit or loss of Bitcoin sellers in USD and BTC in daily, monthly and yearly windows. ## What it measures Total USD or BTC value of profit or loss realized by all Bitcoin holders on a given day, 30-day and 365-day rolling window. ## How to interpret it Single large loss days are not automatic bottom signals. Watch for patterns: cumulative monthly losses vs. prior bear market levels is more reliable than single-day readings. Declining profit peaks forming lower highs = bull-to-bear transition. BTC-denominated = best for structural cycle analysis across time. USD-denominated = best for measuring real-world economic impact. Rising annual profits = bull market in full force. Declining annual profit peaks = cycle top has passed. Monthly data provides near-term confirmation of profit-taking or capitulation cycles. Compare monthly readings in BTC terms against prior bear market capitulation benchmarks, not just USD figures. ## Key thresholds $5.4B single-day loss (Feb 5, 2026) = largest since Mar 2023, but insufficient for structural bottom; $9B single-day profit (Jul 2025) = local peak; Monthly BTC losses >1.1M BTC = historical capitulation level; 0.3M BTC (Feb 2026) = far below capitulation level BTC terms: 4.4M BTC annual net profit (Oct 2025) = cycle peak at \$126K ATH; +2.5M BTC (Jan 2026) = –43% from peak in 3 months, comparable to Mar 2022 (start of prior bear); Declining annual profit peaks forming lower highs = definitive bull-to-bear signal. Monthly data: 0.53M BTC (Jul 2025) = near-ATH monthly profits; +0.26M BTC (Oct 2025) = 50% below July, early momentum warning; 0.3M BTC monthly losses (Feb 2026) = far below 1.1M BTC capitulation level of 2022 ## How to use it Watch for patterns over weeks. Rising daily losses with declining price = capitulation approaching. Rising daily profits with declining trend = distribution phase ending. Successive lower profit peaks = bear market transition signal. The annual trend is the most reliable cycle signal. When annual profits begin forming lower peaks and are below its 30-day moving average, even as prices remain near highs, the cycle top has likely passed. 30-day data: Use alongside daily and annual figures for multi-timeframe confirmation. Monthly BTC-denominated losses approaching 1.1M BTC = structural capitulation approaching. > [card] [Run this metric in CryptoQuant Analytics](https://cryptoquant.com/analytics/query/6686acd11fe1d9469fd74407) # Satoshi-era miner Source: https://docs.cryptoquant.com/v2/community/bitcoin-satoshi-era-miner openapi/v2.json GET /community/bitcoin-satoshi-era-miner The flow, reserves, and active addresses count of Satoshi-era miner addresses. Flow and reserve data in BTC and USD terms. ## What it measures Net daily movement of BTC into or out of wallets identified as belonging to Bitcoin's earliest miners (2009–2012), excluding Satoshi (Patoshi) wallets. ## How to interpret it Positive = receiving. Negative = sending outflows (potential selling). Sustained multi-day outflows = supply shock risk. Movement to exchange hot wallets = direct sell pressure. Movement to new addresses = ambiguous (could be OTC pre-sale staging or self-custody). ## Key thresholds Any movement of 10+ year dormant coins = significant event requiring transaction tracing; Outflows to exchange hot wallets = immediate sell pressure; Outflows to newly created addresses = monitor closely for next hop ## How to use it Early warning system for rare supply shocks. When outflow detected, trace transaction destination: exchange vs. OTC vs. new self-custody to assess whether immediate sell pressure will result. > [card] [Run this metric in CryptoQuant Analytics](https://cryptoquant.com/analytics/query/65db8518e67c207e939d368b) # On-chain Trader Realized Price bands Source: https://docs.cryptoquant.com/v2/community/bitcoin-trader-realized-price openapi/v2.json GET /community/bitcoin-trader-realized-price The on-chain realized price of Bitcoin between 1 to 3 months old, including the max, upper, lower and min price bands. ## What it measures Average acquisition price (cost basis) of medium-term "traders" specifically, calculated from coins of 1 to 3 months old. Max band: Outermost upper extreme of the Trader Realized Price channel — maximum historical profit margin level (70%). Upper band: Fixed positive profit (40%) margin applied to the Trader Realized Price — where traders would be realizing above-average profits. Low band: Approximately –12% margin applied to the Trader Realized Price — where traders realize moderate losses. min band: Outermost lower extreme — maximum historical loss margin applied to Trader Realized Price (-37%). ## How to interpret it Realized price: In bull markets (Bull Score ≥ 60), it acts as price support — traders at breakeven have little incentive to sell. In bear markets (Bull Score ≤ 40), it flips to resistance — underwater traders rush to exit at breakeven. Max band: Historically marks blow-off top conditions. Price at or above the max band = extreme profit-taking risk. Rare to reach. Upper band: Marks a zone of elevated profit-taking risk. Price at or above the upper band in a bull market = deep profits = increased probability of selling pressure and short-term correction. Lower band: In bull markets: first major support below the Trader Realized Price; traders capitulate by selling at a loss, creating a buy opportunity. Breaking below the lower band in a bull cycle is a serious warning. In bear markets it becomes a near-term rally target from below. Min band: The "ultimate support during deep price corrections." Marks bear market capitulation extremes — the level where even distressed selling finds a floor. ## Key thresholds Realized price: \~$63K (Apr 2024) = support; ~$65.8K (Jun 2024) = support; \~$81.2K (Mar 2026) = bear market resistance; ~$91–92K (Apr 2025) = resistance. Key rule: Support when Bull Score ≥ 60, Resistance when Bull Score ≤ 40. Price at max band = cycle top warning / sell alert. Price reaching upper band in bull market = local top / correction risk signal. Lower band: \~$100K (Nov 2025) = failed to hold, signaling bear market start; ~$75–78K (Mar 2025/2026) = key support/resistance; \~$71.5K (Apr 2026) = bear market rally target. Min band: ~$63K (Mar 2025) = ultimate downside target if higher supports failed; \~\$72K (Nov 2025) = absolute downside target cited ## How to use it Realized price: Primary dynamic support/resistance level. Regime-dependent interpretation is critical. Max band: Use as a cycle top signal. Combine with Bull Score and MVRV Z-score for confirmation. Upper band: Use as a profit-taking alert level. Combine with realized profit/loss metrics to confirm whether selling is materializing. Lower band: Monitor as the first major support test during corrections. Failure to hold = escalating bear market risk. Min band: Use as the bear market floor target. When price approaches the min band, monitor for capitulation signals (massive daily losses, extreme negative NUPL). > [card] [Run this metric in CryptoQuant Analytics](https://cryptoquant.com/analytics/query/657b35ef21681e353192def5) # On-chain Trader Unrealized Profit/Loss Margin Source: https://docs.cryptoquant.com/v2/community/bitcoin-trader-unrealized-profit-margin openapi/v2.json GET /community/bitcoin-trader-unrealized-profit-margin The unrealized profit/loss margin (%) of Bitcoin between 1 to 3 months old. ## What it measures Percentage difference between current price and the Trader Realized Price — the unrealized profit or loss of active traders expressed as a % ## How to interpret it Extremely high margins = traders likely to start selling (overheating). Deeply negative margins = traders underwater, capitulation may be near. Crossing above/below 30-day MA = confirms positive/negative price momentum. ## Key thresholds > 40% = elevated, correction risk; \~7–8% = STH local top signal; 0% = breakeven (strong support in bull); –5% to –18% = distressed; –17% to –18% = extreme (seen at Aug 2024 crash and July 2024 correction, both price bottoms) ## How to use it Best as a contrarian indicator at extremes. Deeply negative = capitulation approaching. Extremely positive = overheating. Also watch vs. 30-day MA — crossing below confirms negative momentum. > [card] [Run this metric in CryptoQuant Analytics](https://cryptoquant.com/analytics/query/657b35ef21681e353192def5) # API v2 Discovery Source: https://docs.cryptoquant.com/v2/discovery Discover API v2 endpoints, parameter values, asset classes, windows, and the exchanges that hold data for each asset. Use the discovery APIs to enumerate endpoint parameters and on-chain assets before building a request. Both endpoints use Bearer authentication and return JSON in the same `result.data` / `status` envelope. The lists reflect the assets and endpoints visible in the serving environment. > [!WARNING] > > **List values are candidates. The endpoint page's Assets and windows table defines the > guaranteed coverage.** Endpoint parameter lists do not guarantee every combination of > asset, chain, exchange, and window. Asset-level windows are a union across endpoints, > and validated exchanges do not imply support for every metric or window. For example, > [Exchange Supply Ratio](/v2/indicator/exchange-supply-ratio) serves `block` only for `btc`, and > when several asset classes share a path their windows can differ. ## Discover endpoint parameters ```text theme={null} GET /v2/discovery/endpoints ``` Returns `/v2/` endpoint paths with their accepted parameter values and required parameter names. Parameters vary by endpoint: on-chain entries can include `asset`, `chain`, `exchange`, and `window`; other entries expose their own parameters. Common request parameters `from`, `to`, `limit`, and `format` are omitted from the returned metadata. ### Query parameters | Parameter | Type | Required | Description | | - | - | - | - | | `asset` | string | No | Filter entries by CryptoQuant asset alias, e.g. `btc`, `eth`, or `usdt` (no chain suffix). Only endpoints whose `parameters.asset` list contains the alias are returned. This does not narrow the other parameter lists to that asset. An unmatched alias returns an empty `data` array. | | `category` | string | No | Filter by `community`, `market`, `sentiment`, `network`, `flows`, or `indicator`. Omit to list all v2 categories. An unsupported category returns `400`. | | `format` | string | No | `json` (default) or `csv`. An unsupported format returns `400`. | ### curl examples ```bash theme={null} # List every visible v2 endpoint curl --request GET \ --url 'https://api.cryptoquant.com/v2/discovery/endpoints' \ --header 'Authorization: Bearer YOUR_API_KEY' # Find endpoints that accept the btc alias curl --request GET \ --url 'https://api.cryptoquant.com/v2/discovery/endpoints?asset=btc' \ --header 'Authorization: Bearer YOUR_API_KEY' ``` ### Response fields | Field | Type | Description | | - | - | - | | `result.data` | array of objects | Matching endpoint entries. | | `result.data[].path` | string | Full endpoint path, starting with `/v2/`. | | `result.data[].parameters` | object of string arrays | Parameter name → candidate values for that endpoint. | | `result.data[].parameters.asset` | string array | Asset aliases, when the endpoint has an asset parameter. Registry-backed assets are restricted to those visible and servable in the current environment. | | `result.data[].parameters.chain` | string array | Chains, when applicable, e.g. `bitcoin` or `ethereum`. Registry-backed chains are restricted to those with a visible, servable asset. | | `result.data[].parameters.exchange` | string array | Exchange names and aggregate aliases, when applicable. Use chain-specific metadata below when present. | | `result.data[].parameters.window` | string array | Candidate windows across the endpoint's assets; consult its **Assets and windows** table for each asset class. | | `result.data[].required_parameters` | string array | Required parameter names, excluding the common parameters omitted above. | | `result.data[].parameters_by_chain` | object | Optional parameter name → chain → string array mapping, e.g. `parameters_by_chain.exchange.bitcoin`. Present when chain-specific values are available; includes only servable chains. | | `status.code` | integer | `200` for a successful response. | | `status.message` | string | `success` for a successful response. | Illustrative JSON excerpt; live lists can contain additional values and entries: ```json theme={null} { "result": { "data": [ { "path": "/v2/network/supply", "parameters": { "asset": ["btc", "eth", "usdt"], "chain": ["bitcoin", "ethereum"], "window": ["block", "10min", "hour", "day"] }, "required_parameters": ["asset"] } ] }, "status": {"code": 200, "message": "success"} } ``` For `format=csv`, the response is `text/csv` with columns `path,parameters,required_parameters`. Object and array cells use Python-style representations (single quotes). The CSV response does not include the JSON envelope or `parameters_by_chain`; use JSON for chain-specific values. ## Discover assets ```text theme={null} GET /v2/discovery/assets ``` Returns one entry per asset alias and chain for the on-chain classes `btc`, `eth`, `erc20`, and `stablecoin`. Entries are sorted by alias, then chain. Only assets visible in the serving environment are included. Optional query filters `asset`, `chain`, and `symbol_class` narrow the list (for example `?symbol_class=stablecoin`); the response is JSON. ### curl example ```bash theme={null} curl --request GET \ --url 'https://api.cryptoquant.com/v2/discovery/assets' \ --header 'Authorization: Bearer YOUR_API_KEY' ``` ### Response fields | Field | Type | Description | | - | - | - | | `result.data` | array of objects | Asset-and-chain entries. | | `result.data[].asset` | string | CryptoQuant asset alias to use in `asset=`, without a chain suffix. | | `result.data[].chain` | string | Chain for this registry entry, e.g. `bitcoin` or `ethereum`. | | `result.data[].symbol_class` | string | `btc` (native Bitcoin), `eth` (native Ethereum), `erc20` (ERC-20 token), or `stablecoin`. | | `result.data[].status` | string | Registry lifecycle status: `dev`, `stage`, or `prod`, filtered by the serving environment. A missing registry status is treated as `prod`. | | `result.data[].windows` | string array | Sorted union of the windows supported for this asset and chain across visible endpoints. May be empty; it is not a per-endpoint guarantee. | | `result.data[].exchanges` | string array | Exchanges you can pass as `exchange=` for this asset. Native assets (`btc`, `eth`) list every validated exchange in the chain's entity registry. ERC-20 tokens and stablecoins list only the validated exchanges that hold reserve data for that token in the last 3 days, plus the aggregates `all_exchange`, `spot_exchange`, and `derivative_exchange` when at least one such exchange exists. An empty array means CryptoQuant has no exchange data for that asset yet, not that calls are rejected. | | `status.code` | integer | `200` for a successful response. | | `status.message` | string | `success` for a successful response. | Illustrative JSON excerpt; live lists can contain additional values and entries: ```json theme={null} { "result": { "data": [ { "asset": "btc", "chain": "bitcoin", "symbol_class": "btc", "status": "prod", "windows": ["block", "day", "hour"], "exchanges": ["all_exchange", "binance"] } ] }, "status": {"code": 200, "message": "success"} } ``` Start with the asset list, find candidate endpoints with `/v2/discovery/endpoints?asset=`, then check the selected endpoint's **Assets and windows** table before choosing a window. For exchange requests, also check the asset's `exchanges` (only exchanges with data for that asset) and any `parameters_by_chain` values returned by endpoint discovery. `/v2/discovery/endpoints?asset=` returns `400` when the alias is not a visible asset. # Addresses Count Source: https://docs.cryptoquant.com/v2/flows/addresses-count openapi/v2-onchain.json GET /flows/exchange/addresses-count The number of distinct addresses involved in the inflow and outflow transactions of a given exchange. ## What it measures The number of distinct addresses involved in the inflow and outflow transactions of a given exchange. **📖 Data Guide:** [Exchange Addresses Count](/data-guide/exchange/exchange-addresses-count) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `addresses_count_inflow` | integer | The number of addresses that sent into the exchange in the window. | | `addresses_count_outflow` | integer | The number of addresses that received from the exchange in the window. | # In-House Flow Source: https://docs.cryptoquant.com/v2/flows/in-house-flow openapi/v2-onchain.json GET /flows/exchange/in-house-flow Movement between wallets that belong to the same exchange. ## What it measures Movement between wallets that belong to the same exchange. These transfers never leave the exchange, so they are excluded from inflow and outflow — this endpoint reports them separately. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `inhouse_total` | number | The total amount moved between wallets belonging to the same exchange. | | `inhouse_transactions_count` | integer | The number of transactions moving funds within the exchange. | # Inflow Source: https://docs.cryptoquant.com/v2/flows/inflow openapi/v2-onchain.json GET /flows/exchange/inflow The amount of the asset flowing into the wallets of a given exchange, with the mean per transaction and the summed ten largest transactions of the interval. ## What it measures The amount of the asset flowing into the wallets of a given exchange, with the mean per transaction and the summed ten largest transactions of the interval. **📖 Data Guide:** [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `inflow_total` | number | The total amount transferred into the exchange in the window. | | `inflow_top10` | number | The summed amount of the ten largest transactions flowing into the exchange in the window. | | `inflow_mean` | number | The mean amount per transaction transferred into the exchange. | # Exchange to Exchange Source: https://docs.cryptoquant.com/v2/flows/inter-entity/exchange-to-exchange openapi/v2-onchain.json GET /flows/inter-entity/exchange-to-exchange The amount of the asset moved from one exchange to another — the total, the mean per transaction, and the number of transactions. ## What it measures The amount of the asset moved from one exchange to another — the total, the mean per transaction, and the number of transactions. The two exchanges must differ. **📖 Data Guide:** [Exchange to Exchange](/data-guide/exchange/exchange-to-exchange) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `flow_total` | number | The total amount moved along this flow in the window — within the entity for in-house flow, from the source entity to the destination entity for inter-entity flows. | | `flow_mean` | number | The mean amount per transaction along this flow. | | `transactions_count_flow` | integer | The number of transactions along this flow in the window. | # Exchange to Miner Source: https://docs.cryptoquant.com/v2/flows/inter-entity/exchange-to-miner openapi/v2-onchain.json GET /flows/inter-entity/exchange-to-miner The amount of the asset moved from an exchange to a mining pool — the total, the mean per transaction, and the number of transactions. ## What it measures The amount of the asset moved from an exchange to a mining pool — the total, the mean per transaction, and the number of transactions. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `flow_total` | number | The total amount moved along this flow in the window — within the entity for in-house flow, from the source entity to the destination entity for inter-entity flows. | | `flow_mean` | number | The mean amount per transaction along this flow. | | `transactions_count_flow` | integer | The number of transactions along this flow in the window. | # Miner to Exchange Source: https://docs.cryptoquant.com/v2/flows/inter-entity/miner-to-exchange openapi/v2-onchain.json GET /flows/inter-entity/miner-to-exchange The amount of the asset moved from a mining pool to an exchange — the total, the mean per transaction, and the number of transactions. ## What it measures The amount of the asset moved from a mining pool to an exchange — the total, the mean per transaction, and the number of transactions. Miners sending coins to exchanges is the classic sign of miner selling. **📖 Data Guide:** [Miner to Exchange](/data-guide/miner/miner-to-exchange) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `flow_total` | number | The total amount moved along this flow in the window — within the entity for in-house flow, from the source entity to the destination entity for inter-entity flows. | | `flow_mean` | number | The mean amount per transaction along this flow. | | `transactions_count_flow` | integer | The number of transactions along this flow in the window. | # Miner to Miner Source: https://docs.cryptoquant.com/v2/flows/inter-entity/miner-to-miner openapi/v2-onchain.json GET /flows/inter-entity/miner-to-miner The amount of the asset moved from one mining pool to another — the total, the mean per transaction, and the number of transactions. ## What it measures The amount of the asset moved from one mining pool to another — the total, the mean per transaction, and the number of transactions. The two pools must differ. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `flow_total` | number | The total amount moved along this flow in the window — within the entity for in-house flow, from the source entity to the destination entity for inter-entity flows. | | `flow_mean` | number | The mean amount per transaction along this flow. | | `transactions_count_flow` | integer | The number of transactions along this flow in the window. | # Mining Pool Addresses Count Source: https://docs.cryptoquant.com/v2/flows/mining-pools/addresses-count openapi/v2-onchain.json GET /flows/mining-pools/addresses-count The number of distinct addresses involved in the inflow and outflow transactions of a given mining pool. ## What it measures The number of distinct addresses involved in the inflow and outflow transactions of a given mining pool. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `addresses_count_inflow` | integer | The number of addresses that sent into the exchange in the window. | | `addresses_count_outflow` | integer | The number of addresses that received from the exchange in the window. | # Mining Pool In-House Flow Source: https://docs.cryptoquant.com/v2/flows/mining-pools/in-house-flow openapi/v2-onchain.json GET /flows/mining-pools/in-house-flow Movement between wallets that belong to the same mining pool. ## What it measures Movement between wallets that belong to the same mining pool. These transfers never leave the pool, so they are excluded from inflow and outflow — this endpoint reports them separately. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `flow_total` | number | The total amount moved along this flow in the window — within the entity for in-house flow, from the source entity to the destination entity for inter-entity flows. | | `flow_mean` | number | The mean amount per transaction along this flow. | | `transactions_count_flow` | integer | The number of transactions along this flow in the window. | # Mining Pool Inflow Source: https://docs.cryptoquant.com/v2/flows/mining-pools/inflow openapi/v2-onchain.json GET /flows/mining-pools/inflow The amount of the asset flowing into the wallets of a given mining pool, with the mean per transaction and the summed ten largest transactions of the interval. ## What it measures The amount of the asset flowing into the wallets of a given mining pool, with the mean per transaction and the summed ten largest transactions of the interval. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `inflow_total` | number | The total amount transferred into the exchange in the window. | | `inflow_top10` | number | The summed amount of the ten largest transactions flowing into the exchange in the window. | | `inflow_mean` | number | The mean amount per transaction transferred into the exchange. | # Mining Pool Netflow Source: https://docs.cryptoquant.com/v2/flows/mining-pools/netflow openapi/v2-onchain.json GET /flows/mining-pools/netflow Inflow minus outflow for a given mining pool. ## What it measures Inflow minus outflow for a given mining pool. A positive netflow means the pool is accumulating coins; a negative one means it is distributing them — often to exchanges. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `netflow_total` | number | Inflow minus outflow. Positive means more flowed in than out. | # Mining Pool Outflow Source: https://docs.cryptoquant.com/v2/flows/mining-pools/outflow openapi/v2-onchain.json GET /flows/mining-pools/outflow The amount of the asset flowing out of the wallets of a given mining pool, with the mean per transaction and the summed ten largest transactions of the interval. ## What it measures The amount of the asset flowing out of the wallets of a given mining pool, with the mean per transaction and the summed ten largest transactions of the interval. **📖 Data Guide:** [Miner Outflow](/data-guide/miner/miner-outflow) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `outflow_total` | number | The total amount transferred out of the exchange in the window. | | `outflow_top10` | number | The summed amount of the ten largest transactions flowing out of the exchange in the window. | | `outflow_mean` | number | The mean amount per transaction transferred out of the exchange. | # Mining Pool Reserve Source: https://docs.cryptoquant.com/v2/flows/mining-pools/reserve openapi/v2-onchain.json GET /flows/mining-pools/reserve The full on-chain balance held by a given mining pool, in the asset and in USD. ## What it measures The full on-chain balance held by a given mining pool, in the asset and in USD. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `reserve` | number | The on-chain balance held by the exchange at the end of the interval. | | `reserve_usd` | number | The on-chain balance held by the exchange, valued in USD. | # Mining Pool Transactions Count Source: https://docs.cryptoquant.com/v2/flows/mining-pools/transactions-count openapi/v2-onchain.json GET /flows/mining-pools/transactions-count The number of transactions flowing in and out of a given mining pool. ## What it measures The number of transactions flowing in and out of a given mining pool. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `transactions_count_inflow` | integer | The number of transactions sent to the exchange. | | `transactions_count_outflow` | integer | The number of transactions sent from the exchange. | # Netflow Source: https://docs.cryptoquant.com/v2/flows/netflow openapi/v2-onchain.json GET /flows/exchange/netflow Inflow minus outflow for a given exchange. ## What it measures Inflow minus outflow for a given exchange. Netflow is the usual way to read whether coins are accumulating on an exchange — available to be sold — or leaving it. **📖 Data Guide:** [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `netflow_total` | number | Inflow minus outflow. Positive means more flowed in than out. | # Outflow Source: https://docs.cryptoquant.com/v2/flows/outflow openapi/v2-onchain.json GET /flows/exchange/outflow The amount of the asset flowing out of the wallets of a given exchange, with the mean per transaction and the summed ten largest transactions of the interval. ## What it measures The amount of the asset flowing out of the wallets of a given exchange, with the mean per transaction and the summed ten largest transactions of the interval. **📖 Data Guide:** [Exchange In/Outflow and Netflow](/data-guide/exchange/exchange-in-outflow-and-netflow) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `outflow_total` | number | The total amount transferred out of the exchange in the window. | | `outflow_top10` | number | The summed amount of the ten largest transactions flowing out of the exchange in the window. | | `outflow_mean` | number | The mean amount per transaction transferred out of the exchange. | # Reserve Source: https://docs.cryptoquant.com/v2/flows/reserve openapi/v2-onchain.json GET /flows/exchange/reserve The full on-chain balance held by a given exchange, in the asset and in USD. ## What it measures The full on-chain balance held by a given exchange, in the asset and in USD. **📖 Data Guide:** [Exchange Reserve](/data-guide/exchange/exchange-reserve) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `reserve` | number | The on-chain balance held by the exchange at the end of the interval. | | `reserve_usd` | number | The on-chain balance held by the exchange, valued in USD. | # Transactions Count Source: https://docs.cryptoquant.com/v2/flows/transactions-count openapi/v2-onchain.json GET /flows/exchange/transactions-count The number of transactions flowing in and out of a given exchange. ## What it measures The number of transactions flowing in and out of a given exchange. **📖 Data Guide:** [Exchange Transactions Count](/data-guide/exchange/exchange-transactions-count) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `transactions_count_inflow` | integer | The number of transactions sent to the exchange. | | `transactions_count_outflow` | integer | The number of transactions sent from the exchange. | # Coin Days Destroyed Source: https://docs.cryptoquant.com/v2/indicator/cdd openapi/v2-onchain.json GET /indicator/selling-activity/cdd Coin Days Destroyed weights spending by how long the coins sat idle, so it gives more weight to long-term holders moving coins. ## What it measures Coin Days Destroyed weights spending by how long the coins sat idle, so it gives more weight to long-term holders moving coins. `cdd` is the raw sum; `sa_cdd` normalises it by total supply; `average_sa_cdd` is its mean since genesis; and `binary_cdd` flags intervals where `sa_cdd` is above that mean. **📖 Data Guide:** [Coin Days Destroyed (CDD)](/data-guide/utxo/coin-days-destroyed-cdd) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `cdd` | number | Coin Days Destroyed — for every UTXO spent in the window, the number of days since it was created multiplied by its amount, summed. | | `sa_cdd` | number | Supply-adjusted Coin Days Destroyed — `cdd` divided by total supply, so the series is comparable across eras of different supply. | | `average_sa_cdd` | number | The historical mean of `sa_cdd` since the genesis block. | | `binary_cdd` | integer | `1` when `sa_cdd` is above `average_sa_cdd`, `0` otherwise. | # Dormancy Source: https://docs.cryptoquant.com/v2/indicator/dormancy openapi/v2-onchain.json GET /indicator/selling-activity/dormancy Average dormancy is the mean number of coin days destroyed per coin transacted — how old, on average, the coins moving in the window were. ## What it measures Average dormancy is the mean number of coin days destroyed per coin transacted — how old, on average, the coins moving in the window were. The supply-adjusted variant normalises it by total supply. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `average_dormancy` | number | Average dormancy — the mean number of coin days destroyed per coin transacted. | | `sa_average_dormancy` | number | Supply-adjusted average dormancy — `average_dormancy` normalised by total supply. | # Estimated Leverage Ratio Source: https://docs.cryptoquant.com/v2/indicator/estimated-leverage-ratio openapi/v2-onchain.json GET /indicator/leverage-risk/estimated-leverage-ratio Open interest on a given derivatives exchange divided by that exchange's on-chain reserve of the asset — an estimate of how much leverage its users are running on average. ## What it measures Open interest on a given derivatives exchange divided by that exchange's on-chain reserve of the asset — an estimate of how much leverage its users are running on average. High values have tended to precede rapid volatility. **📖 Data Guide:** [Estimated Leverage Ratio](/data-guide/market/estimated-leverage-ratio) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` | The default window is `block`. ## Response fields This endpoint serves only `window=block`, so the time key is always `blockheight` plus `datetime`. | Field | Type | Description | | - | - | - | | `estimated_leverage_ratio` | number | Open interest on the exchange divided by the exchange's on-chain reserve of the asset. | # Exchange Shutdown Index Source: https://docs.cryptoquant.com/v2/indicator/exchange-shutdown-index openapi/v2-onchain.json GET /indicator/selling-activity/exchange-shutdown-index Flags intervals in which a given exchange had zero outflow. ## What it measures Flags intervals in which a given exchange had zero outflow. A sudden run of `1`s on an exchange that normally moves coins every block is an early sign of a halt — maintenance, or a hack. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` | The default window is `block`. ## Response fields This endpoint serves only `window=block`, so the time key is always `blockheight` plus `datetime`. | Field | Type | Description | | - | - | - | | `is_shutdown` | integer | `1` when the exchange's total outflow for the interval is zero, `0` otherwise. | # Exchange Supply Ratio Source: https://docs.cryptoquant.com/v2/indicator/exchange-supply-ratio openapi/v2-onchain.json GET /indicator/selling-activity/exchange-supply-ratio Exchange reserve divided by total supply — how much of the asset sits on a given exchange relative to everything in existence. ## What it measures Exchange reserve divided by total supply — how much of the asset sits on a given exchange relative to everything in existence. The response carries both inputs alongside the ratio. **📖 Data Guide:** [Exchange Supply Ratio](/data-guide/exchange/exchange-supply-ratio) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` | The default window is `day`. > [!WARNING] > > **Bitcoin has no default window on this endpoint.** `day` is not served for `btc`, so a request that omits `window` returns `400` for `btc` assets. Pass `window=block` explicitly. ## Response fields This endpoint serves only `window=block`, so the time key is always `blockheight` plus `datetime`. | Field | Type | Description | | - | - | - | | `exchange_supply_ratio` | number | Exchange reserve divided by total supply. | # Exchange Whale Ratio Source: https://docs.cryptoquant.com/v2/indicator/exchange-whale-ratio openapi/v2-onchain.json GET /indicator/selling-activity/exchange-whale-ratio The ten largest inflow transactions of a given exchange as a share of its total inflow. ## What it measures The ten largest inflow transactions of a given exchange as a share of its total inflow. A high ratio means the exchange's inflow is dominated by whales, which tends to precede sharp moves. **📖 Data Guide:** [Exchange Whale Ratio](/data-guide/market/exchange-whale-ratio) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` | The default window is `block`. ## Response fields This endpoint serves only `window=block`, so the time key is always `blockheight` plus `datetime`. | Field | Type | Description | | - | - | - | | `exchange_whale_ratio` | number | The summed amount of the ten largest inflow transactions divided by the total inflow of the exchange. | # Fund Flow Ratio Source: https://docs.cryptoquant.com/v2/indicator/fund-flow-ratio openapi/v2-onchain.json GET /indicator/selling-activity/fund-flow-ratio The amount flowing into or out of a given exchange as a share of everything transferred on the network — how much of on-chain activity is exchange-related, and therefore potentially trading-related. ## What it measures The amount flowing into or out of a given exchange as a share of everything transferred on the network — how much of on-chain activity is exchange-related, and therefore potentially trading-related. **📖 Data Guide:** [Fund Flow Ratio](/data-guide/exchange/fund-flow-ratio) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` | The default window is `block`. ## Response fields This endpoint serves only `window=block`, so the time key is always `blockheight` plus `datetime`. | Field | Type | Description | | - | - | - | | `fund_flow_ratio` | number | The amount flowing into or out of the exchange divided by the total amount transferred on the whole network. | # Mean Coin Age Source: https://docs.cryptoquant.com/v2/indicator/mca openapi/v2-onchain.json GET /indicator/holder-composition/mca Mean Coin Age is the mean, over unspent outputs, of age in days multiplied by amount — like Coin Days Destroyed, but over the coins that are still held rather than the ones being spent. ## What it measures Mean Coin Age is the mean, over unspent outputs, of age in days multiplied by amount — like Coin Days Destroyed, but over the coins that are still held rather than the ones being spent. Mean Coin Dollar Age additionally weights each output by the USD price when it was created. **📖 Data Guide:** [Mean Coin Age (MCA)](/data-guide/utxo/mean-coin-age-mca) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `mca` | number | Mean Coin Age — the mean, over unspent outputs, of the output's age in days multiplied by its amount. | | `mcda` | number | Mean Coin Dollar Age — the mean, over unspent outputs, of the output's age in days multiplied by its amount and by the USD price when it was created. | # Mining Pool Supply Ratio Source: https://docs.cryptoquant.com/v2/indicator/mining-pool-supply-ratio openapi/v2-onchain.json GET /indicator/selling-activity/mining-pool-supply-ratio Mining pool reserve divided by total supply — how much of the asset sits in a given mining pool relative to everything in existence. ## What it measures Mining pool reserve divided by total supply — how much of the asset sits in a given mining pool relative to everything in existence. **📖 Data Guide:** [Miner Supply Ratio](/data-guide/miner/miner-supply-ratio) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` | The default window is `block`. ## Response fields This endpoint serves only `window=block`, so the time key is always `blockheight` plus `datetime`. | Field | Type | Description | | - | - | - | | `miner_supply_ratio` | number | Mining pool reserve divided by total supply. | # MVRV Ratio Source: https://docs.cryptoquant.com/v2/indicator/mvrv openapi/v2-onchain.json GET /indicator/unrealized-pnl/mvrv Market Value to Realized Value — market capitalization divided by realized capitalization. ## What it measures Market Value to Realized Value — market capitalization divided by realized capitalization. It compares what the market values the coins at with what holders paid for them: a very high ratio suggests the asset is overvalued, a very low one that it is undervalued. **📖 Data Guide:** [MVRV (Market Value to Realized Value) Ratio](/data-guide/market/mvrv-ratio) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `mvrv` | number | Market Value to Realized Value — `market_cap` divided by `realized_cap`. | # NRPL Source: https://docs.cryptoquant.com/v2/indicator/nrpl openapi/v2-onchain.json GET /indicator/realized-pnl/nrpl Net Realized Profit and Loss — the net profit or loss, in USD, realized by all holders who spent coins in the window, measured against the price when each coin last moved. ## What it measures Net Realized Profit and Loss — the net profit or loss, in USD, realized by all holders who spent coins in the window, measured against the price when each coin last moved. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `nrpl` | number | Net Realized Profit and Loss — the net USD profit or loss realized by all coins spent in the window, measured against the price when each coin last moved. | # NUPL Source: https://docs.cryptoquant.com/v2/indicator/nupl openapi/v2-onchain.json GET /indicator/unrealized-pnl/nupl Net Unrealized Profit and Loss — the difference between market capitalization and realized capitalization as a share of market capitalization. ## What it measures Net Unrealized Profit and Loss — the difference between market capitalization and realized capitalization as a share of market capitalization. A positive value means holders are, on aggregate, sitting on unrealized profit, which is latent selling pressure. `nup` and `nul` split it into the profit and loss sides. **📖 Data Guide:** [Net Unrealized Profit/Loss (NUPL)](/data-guide/utxo/net-unrealized-profit-and-loss-nupl) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `nupl` | number | Net Unrealized Profit and Loss — (`market_cap` − `realized_cap`) divided by `market_cap`. | | `nup` | number | Net Unrealized Profit — for UTXOs currently in profit, the amount multiplied by the price gain since creation, summed and divided by `market_cap`. | | `nul` | number | Net Unrealized Loss — for UTXOs currently at a loss, the amount multiplied by the price drop since creation, summed and divided by `market_cap`. | # NVM Ratio Source: https://docs.cryptoquant.com/v2/indicator/nvm openapi/v2-onchain.json GET /indicator/valuation/nvm Network Value to Metcalfe ratio — market capitalization divided by the square of daily active addresses, after Metcalfe's law that a network's value grows with the square of its users. ## What it measures Network Value to Metcalfe ratio — market capitalization divided by the square of daily active addresses, after Metcalfe's law that a network's value grows with the square of its users. A relatively low value suggests the network is undervalued for its usage, a high value the opposite. **📖 Data Guide:** [NVM Ratio](/data-guide/network/nvm-ratio) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `hour` · `day` | The default window is `day`. ## Response fields The time key is `datetime` for every window of this endpoint (`hour`, `day`). | Field | Type | Description | | - | - | - | | `nvm` | number | Network Value to Metcalfe ratio — market capitalization divided by the square of daily active addresses, after Metcalfe's law. | # NVT Ratio Source: https://docs.cryptoquant.com/v2/indicator/nvt openapi/v2-onchain.json GET /indicator/valuation/nvt Network Value to Transactions ratio — market capitalization divided by the amount transferred on-chain. ## What it measures Network Value to Transactions ratio — market capitalization divided by the amount transferred on-chain. A high NVT means the network is valued richly relative to the economic activity it carries. **📖 Data Guide:** [NVT Ratio](/data-guide/network/nvt-ratio) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `hour` · `day` | The default window is `day`. ## Response fields The time key is `datetime` for every window of this endpoint (`hour`, `day`). | Field | Type | Description | | - | - | - | | `nvt` | number | Network Value to Transactions ratio — market capitalization (`supply_total` × USD price) divided by `tokens_transferred_total`. | # NVT Golden Cross Source: https://docs.cryptoquant.com/v2/indicator/nvt-golden-cross openapi/v2-onchain.json GET /indicator/valuation/nvt-golden-cross A modified NVT that standardises a short-term NVT against a long-term one to flag local tops and bottoms. ## What it measures A modified NVT that standardises a short-term NVT against a long-term one to flag local tops and bottoms. Values above `2.2` indicate rising downside risk; values below `-1.6` indicate strong upside potential. **📖 Data Guide:** [NVT Golden Cross](/data-guide/network/nvt-golden-cross) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `day` | The default window is `day`. ## Response fields This endpoint serves only `window=day`, so the time key is always `datetime`. | Field | Type | Description | | - | - | - | | `nvt_golden_cross` | number | A modified NVT that standardises a short-term NVT against a long-term one to flag local tops and bottoms. `null` when the long-term standard deviation is zero. May be `null`. | # PnL Index Source: https://docs.cryptoquant.com/v2/indicator/pnl-index openapi/v2-onchain.json GET /indicator/unrealized-pnl/pnl-index A composite valuation index built from the MVRV ratio, NUPL, and long-/short-term-holder SOPR. ## What it measures A composite valuation index built from the MVRV ratio, NUPL, and long-/short-term-holder SOPR. The accompanying bull/bear indicator is the index minus its 365-day moving average, which separates bull regimes (above `0`) from bear regimes (below `0`). The index and its moving average are also published on the community endpoints [Bitcoin PnL Index](/v2/community/bitcoin-pnl-index) and [Bitcoin Bull/Bear Indicator](/v2/community/bitcoin-bull-bear-indicator). ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `day` | The default window is `day`. ## Response fields This endpoint serves only `window=day`, so the time key is always `datetime`. | Field | Type | Description | | - | - | - | | `pnl_index` | number | Profit and Loss Index — a composite valuation index built from the MVRV ratio, NUPL, and LTH/STH SOPR. | | `bull_bear_indicator` | number | The PnL Index minus its 365-day moving average. Above `0` reads as a bull regime, below `0` as a bear regime. | # Puell Multiple Source: https://docs.cryptoquant.com/v2/indicator/puell-multiple openapi/v2-onchain.json GET /indicator/valuation/puell-multiple Daily mining revenue in USD divided by its 365-day moving average. ## What it measures Daily mining revenue in USD divided by its 365-day moving average. It shows when the value of coins issued per day is historically high or low — and historically, where buying has paid off. Created by David Puell. **📖 Data Guide:** [Puell Multiple](/data-guide/network/puell-multiple) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `hour` · `day` | The default window is `day`. ## Response fields The time key is `datetime` for every window of this endpoint (`hour`, `day`). | Field | Type | Description | | - | - | - | | `puell_multiple` | number | Daily mining revenue in USD divided by its 365-day moving average. | # Realized Price Source: https://docs.cryptoquant.com/v2/indicator/realized-price openapi/v2-onchain.json GET /indicator/price-models/realized-price Realized capitalization divided by total supply — the supply-weighted average price at which the market acquired its coins. ## What it measures Realized capitalization divided by total supply — the supply-weighted average price at which the market acquired its coins. It is often read as an on-chain support or resistance level. **📖 Data Guide:** [Realized Price](/data-guide/market/realized-price) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `realized_price` | number | Realized Price — `realized_cap` divided by total supply, in USD: the supply-weighted average price at which the market acquired its coins. | # SOPR Source: https://docs.cryptoquant.com/v2/indicator/sopr openapi/v2-onchain.json GET /indicator/realized-pnl/sopr Spent Output Profit Ratio — the USD value of the outputs spent in the window at spend time divided by their value at creation time, so a value above `1` means spent coins were in profit. ## What it measures Spent Output Profit Ratio — the USD value of the outputs spent in the window at spend time divided by their value at creation time, so a value above `1` means spent coins were in profit. Also reported adjusted (outputs older than an hour), and split into short-term and long-term holders. **📖 Data Guide:** [Spent Output Profit Ratio (SOPR)](/data-guide/utxo/spent-output-profit-ratio-sopr) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `sopr` | number | Spent Output Profit Ratio — the USD value of outputs spent in the window at spend time divided by their USD value at creation time. Above `1` means spent coins were, on aggregate, in profit. | | `a_sopr` | number | Adjusted SOPR — the same ratio counting only outputs that lived longer than one hour. | | `sth_sopr` | number | Short-term-holder SOPR — outputs that lived longer than one hour and less than 155 days. | | `lth_sopr` | number | Long-term-holder SOPR — outputs that lived 155 days or longer. | # SOPR Ratio Source: https://docs.cryptoquant.com/v2/indicator/sopr-ratio openapi/v2-onchain.json GET /indicator/realized-pnl/sopr-ratio Long-term-holder SOPR divided by short-term-holder SOPR. ## What it measures Long-term-holder SOPR divided by short-term-holder SOPR. A high ratio means long-term holders are realizing more profit than short-term holders, which is useful for spotting market tops. **📖 Data Guide:** [SOPR Ratio (LTH-SOPR/STH-SOPR)](/data-guide/utxo/spent-output-profit-ratio-sopr/sopr-ratio-lth-sopr-sth-sopr) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `sopr_ratio` | number | Long-term-holder SOPR divided by short-term-holder SOPR. | # Stablecoin Supply Ratio Source: https://docs.cryptoquant.com/v2/indicator/stablecoin-supply-ratio openapi/v2-onchain.json GET /indicator/selling-activity/stablecoin-supply-ratio The market capitalization of the asset divided by the total supply of stablecoins. ## What it measures The market capitalization of the asset divided by the total supply of stablecoins. Stablecoins are the fiat substitute of crypto trading, so their supply relative to the asset is a gauge of potential buying pressure. The series starts on 2017-11-28. **📖 Data Guide:** [Stablecoin Supply Ratio (SSR)](/data-guide/stablecoin/stablecoin-supply-ratio) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `day` | The default window is `day`. ## Response fields This endpoint serves only `window=day`, so the time key is always `datetime`. | Field | Type | Description | | - | - | - | | `stablecoin_supply_ratio` | number | Stablecoin Supply Ratio — the market capitalization of the asset divided by the total supply of stablecoins, a gauge of potential buying pressure. | # Stock to Flow Source: https://docs.cryptoquant.com/v2/indicator/stock-to-flow openapi/v2-onchain.json GET /indicator/valuation/stock-to-flow Stock-to-Flow values the asset by its scarcity, the way gold and silver are valued: circulating supply divided by newly issued supply. ## What it measures Stock-to-Flow values the asset by its scarcity, the way gold and silver are valued: circulating supply divided by newly issued supply. The reversion variant divides the USD price by that ratio and is used to spot market bottoms. **📖 Data Guide:** [Stock to Flow Ratio](/data-guide/network/stock-to-flow-ratio) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `stock_to_flow` | number | Stock-to-Flow — circulating supply divided by newly issued supply, a measure of scarcity. | | `stock_to_flow_reversion` | number | Stock-to-Flow reversion — the USD price divided by the Stock-to-Flow ratio, used to spot market bottoms. | # Capitalization Source: https://docs.cryptoquant.com/v2/market/capitalization openapi/v2-onchain.json GET /market/capitalization Market capitalization — circulating supply multiplied by the USD price at the close of the interval. ## What it measures Market capitalization — circulating supply multiplied by the USD price at the close of the interval. **📖 Data Guide:** [Capitalization models](/data-guide/market/capitalization-models) — definition, interpretation, and chart examples. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `market_cap` | number | Market capitalization in USD — circulating supply multiplied by the closing USD price of the interval. May be `null`. | | `realized_cap` | number | Realized capitalization — the sum of every UTXO valued at the price when it last moved, in USD. | | `average_cap` | number | Average capitalization — a forever moving average, the cumulative sum of daily market cap divided by the age of the market, in USD. | | `delta_cap` | number | Delta capitalization — `realized_cap` minus `average_cap`, in USD. | | `thermo_cap` | number | Thermo capitalization — the cumulative sum of coins mined, each valued at the price when it was mined, in USD. | # CQ Aggregated Spot OHLCV Source: https://docs.cryptoquant.com/v2/market/cq-spot-ohlcv openapi/v2-market.json GET /market/cq/spot/ohlcv Open / high / low / close prices with base- and quote-denominated volume, aggregated into `day`, `hour`, `10min`, or `min` candles. ## What it measures Open / high / low / close prices with base- and quote-denominated volume, aggregated into `day`, `hour`, `10min`, or `min` candles. This endpoint serves **CryptoQuant aggregated spot** data — all-exchange aggregated symbols (e.g. `btc_all`). # CQ Aggregated Spot Trade Source: https://docs.cryptoquant.com/v2/market/cq-spot-trade openapi/v2-market.json GET /market/cq/spot/trade Per-interval trade statistics — trade count, base/quote volume, taker buy/sell breakdown, VWAP, and buy/sell ratios. ## What it measures Per-interval trade statistics — trade count, base/quote volume, taker buy/sell breakdown, VWAP, and buy/sell ratios. This endpoint serves **CryptoQuant aggregated spot** data — all-exchange aggregated symbols (e.g. `btc_all`). # CQ Aggregated Swap Funding Rate Source: https://docs.cryptoquant.com/v2/market/cq-swap-funding-rate openapi/v2-market.json GET /market/cq/swap/funding-rate Perpetual-swap funding rate — the periodic payment between long and short positions that anchors the perpetual price to the spot index. Positive = longs pay shorts (bullish leverage); negative = shorts pay longs. ## What it measures Perpetual-swap funding rate — the periodic payment between long and short positions that anchors the perpetual price to the spot index. Positive = longs pay shorts (bullish leverage); negative = shorts pay longs. This endpoint serves **CryptoQuant aggregated swap** data — all-exchange aggregated symbols (e.g. `btc_all`). Use `inverse=true` for coin-margined contracts; the default `false` returns linear (USDⓈ-margined) contracts. # CQ Aggregated Swap Liquidation Source: https://docs.cryptoquant.com/v2/market/cq-swap-liquidation openapi/v2-market.json GET /market/cq/swap/liquidation Forced-liquidation activity — count and volume of long/short positions closed by exchanges when margin is exhausted, in both base asset and USD, plus the average liquidation price. ## What it measures Forced-liquidation activity — count and volume of long/short positions closed by exchanges when margin is exhausted, in both base asset and USD, plus the average liquidation price. This endpoint serves **CryptoQuant aggregated swap** data — all-exchange aggregated symbols (e.g. `btc_all`). Use `inverse=true` for coin-margined contracts; the default `false` returns linear (USDⓈ-margined) contracts. # CQ Aggregated Swap OHLCV Source: https://docs.cryptoquant.com/v2/market/cq-swap-ohlcv openapi/v2-market.json GET /market/cq/swap/ohlcv Open / high / low / close prices with base- and quote-denominated volume, aggregated into `day`, `hour`, `10min`, or `min` candles. ## What it measures Open / high / low / close prices with base- and quote-denominated volume, aggregated into `day`, `hour`, `10min`, or `min` candles. This endpoint serves **CryptoQuant aggregated swap** data — all-exchange aggregated symbols (e.g. `btc_all`). Use `inverse=true` for coin-margined contracts; the default `false` returns linear (USDⓈ-margined) contracts. # CQ Aggregated Swap Open Interest Source: https://docs.cryptoquant.com/v2/market/cq-swap-open-interest openapi/v2-market.json GET /market/cq/swap/open-interest Total notional value of outstanding perpetual/futures contracts. Rising open interest signals new leverage entering the market; falling open interest signals positions closing or being liquidated. ## What it measures Total notional value of outstanding perpetual/futures contracts. Rising open interest signals new leverage entering the market; falling open interest signals positions closing or being liquidated. This endpoint serves **CryptoQuant aggregated swap** data — all-exchange aggregated symbols (e.g. `btc_all`). Use `inverse=true` for coin-margined contracts; the default `false` returns linear (USDⓈ-margined) contracts. # CQ Aggregated Swap Trade Source: https://docs.cryptoquant.com/v2/market/cq-swap-trade openapi/v2-market.json GET /market/cq/swap/trade Per-interval trade statistics — trade count, base/quote volume, taker buy/sell breakdown, VWAP, and buy/sell ratios. ## What it measures Per-interval trade statistics — trade count, base/quote volume, taker buy/sell breakdown, VWAP, and buy/sell ratios. This endpoint serves **CryptoQuant aggregated swap** data — all-exchange aggregated symbols (e.g. `btc_all`). Use `inverse=true` for coin-margined contracts; the default `false` returns linear (USDⓈ-margined) contracts. # Exchange Spot OHLCV Source: https://docs.cryptoquant.com/v2/market/exchange-spot-ohlcv openapi/v2-market.json GET /market/exchange/spot/ohlcv Open / high / low / close prices with base- and quote-denominated volume, aggregated into `day`, `hour`, `10min`, or `min` candles. ## What it measures Open / high / low / close prices with base- and quote-denominated volume, aggregated into `day`, `hour`, `10min`, or `min` candles. This endpoint serves **exchange spot** data — per-exchange, per-quote pairs (e.g. `btc_usdt`). # Exchange Spot Trade Source: https://docs.cryptoquant.com/v2/market/exchange-spot-trade openapi/v2-market.json GET /market/exchange/spot/trade Per-interval trade statistics — trade count, base/quote volume, taker buy/sell breakdown, VWAP, and buy/sell ratios. ## What it measures Per-interval trade statistics — trade count, base/quote volume, taker buy/sell breakdown, VWAP, and buy/sell ratios. This endpoint serves **exchange spot** data — per-exchange, per-quote pairs (e.g. `btc_usdt`). # Exchange Swap Funding Rate Source: https://docs.cryptoquant.com/v2/market/exchange-swap-funding-rate openapi/v2-market.json GET /market/exchange/swap/funding-rate Perpetual-swap funding rate — the periodic payment between long and short positions that anchors the perpetual price to the spot index. Positive = longs pay shorts (bullish leverage); negative = shorts pay longs. ## What it measures Perpetual-swap funding rate — the periodic payment between long and short positions that anchors the perpetual price to the spot index. Positive = longs pay shorts (bullish leverage); negative = shorts pay longs. This endpoint serves **exchange swap** data — per-exchange, per-quote pairs (e.g. `btc_usdt`). Use `inverse=true` for coin-margined contracts; the default `false` returns linear (USDⓈ-margined) contracts. > [!NOTE] > > This endpoint is dual-class: pass a per-quote symbol like `btc_usdt` for a single pair, or an aggregated `btc_all` symbol to get that exchange's all-quote aggregate (still that one exchange — not the cross-exchange `cq` aggregate). # Exchange Swap Liquidation Source: https://docs.cryptoquant.com/v2/market/exchange-swap-liquidation openapi/v2-market.json GET /market/exchange/swap/liquidation Forced-liquidation activity — count and volume of long/short positions closed by exchanges when margin is exhausted, in both base asset and USD, plus the average liquidation price. ## What it measures Forced-liquidation activity — count and volume of long/short positions closed by exchanges when margin is exhausted, in both base asset and USD, plus the average liquidation price. This endpoint serves **exchange swap** data — per-exchange, per-quote pairs (e.g. `btc_usdt`). Use `inverse=true` for coin-margined contracts; the default `false` returns linear (USDⓈ-margined) contracts. > [!NOTE] > > This endpoint is dual-class: pass a per-quote symbol like `btc_usdt` for a single pair, or an aggregated `btc_all` symbol to get that exchange's all-quote aggregate (still that one exchange — not the cross-exchange `cq` aggregate). # Exchange Swap OHLCV Source: https://docs.cryptoquant.com/v2/market/exchange-swap-ohlcv openapi/v2-market.json GET /market/exchange/swap/ohlcv Open / high / low / close prices with base- and quote-denominated volume, aggregated into `day`, `hour`, `10min`, or `min` candles. ## What it measures Open / high / low / close prices with base- and quote-denominated volume, aggregated into `day`, `hour`, `10min`, or `min` candles. This endpoint serves **exchange swap** data — per-exchange, per-quote pairs (e.g. `btc_usdt`). Use `inverse=true` for coin-margined contracts; the default `false` returns linear (USDⓈ-margined) contracts. # Exchange Swap Open Interest Source: https://docs.cryptoquant.com/v2/market/exchange-swap-open-interest openapi/v2-market.json GET /market/exchange/swap/open-interest Total notional value of outstanding perpetual/futures contracts. Rising open interest signals new leverage entering the market; falling open interest signals positions closing or being liquidated. ## What it measures Total notional value of outstanding perpetual/futures contracts. Rising open interest signals new leverage entering the market; falling open interest signals positions closing or being liquidated. This endpoint serves **exchange swap** data — per-exchange, per-quote pairs (e.g. `btc_usdt`). Use `inverse=true` for coin-margined contracts; the default `false` returns linear (USDⓈ-margined) contracts. > [!NOTE] > > This endpoint is dual-class: pass a per-quote symbol like `btc_usdt` for a single pair, or an aggregated `btc_all` symbol to get that exchange's all-quote aggregate (still that one exchange — not the cross-exchange `cq` aggregate). # Exchange Swap Trade Source: https://docs.cryptoquant.com/v2/market/exchange-swap-trade openapi/v2-market.json GET /market/exchange/swap/trade Per-interval trade statistics — trade count, base/quote volume, taker buy/sell breakdown, VWAP, and buy/sell ratios. ## What it measures Per-interval trade statistics — trade count, base/quote volume, taker buy/sell breakdown, VWAP, and buy/sell ratios. This endpoint serves **exchange swap** data — per-exchange, per-quote pairs (e.g. `btc_usdt`). Use `inverse=true` for coin-margined contracts; the default `false` returns linear (USDⓈ-margined) contracts. # List Active Exchanges Source: https://docs.cryptoquant.com/v2/market/info-exchanges openapi/v2-market.json GET /market/info/exchanges Discover which exchanges are active and what market data each one supports. ## What it does Discover which exchanges are active and what market data each one supports. The `exchange` and `symbol` parameters on the market data endpoints are open-ended — these discovery endpoints enumerate the values that currently have data. # List Active Symbols Source: https://docs.cryptoquant.com/v2/market/info-symbols openapi/v2-market.json GET /market/info/symbols Discover the active trading symbols for a market endpoint. ## What it does Discover the active trading symbols for a market endpoint. The `exchange` and `symbol` parameters on the market data endpoints are open-ended — these discovery endpoints enumerate the values that currently have data. > [!NOTE] > > The `origin`/`instrument`/`metric` you pass must be a combination that exists as a data endpoint — see the [combination table](/v2/market/overview#endpoint-structure). `funding-rate`, `open-interest`, and `liquidation` are swap-only, so a `spot` request for those returns `404`. # Market Data Overview Source: https://docs.cryptoquant.com/v2/market/overview Exchange-level and CryptoQuant-aggregated spot & derivatives data in API v2 — OHLCV, trade, funding rate, open interest, and liquidation. API v2 Market Data serves raw **market** time-series — prices, volumes, and derivatives metrics — both per individual exchange and as CryptoQuant's cross-exchange aggregate. It uses the same `status`/`result` envelope, Bearer authentication, and `window`/`from`/`to` time convention as the rest of the API. ## Endpoint structure Every market data endpoint follows one shape: ```text theme={null} /v2/market/{origin}/{instrument}/{metric} ``` | Segment | Values | Meaning | | - | - | - | | `origin` | `exchange`, `cq` | Per-exchange data, or CryptoQuant's cross-exchange aggregate | | `instrument` | `spot`, `swap` | Cash (spot) market, or perpetual/futures (swap) | | `metric` | `ohlcv`, `trade`, `funding-rate`, `open-interest`, `liquidation` | The dataset | Not every combination exists — `funding-rate`, `open-interest`, and `liquidation` are derivatives-only (`swap`), so there is no `spot` variant. | Metric | `exchange/spot` | `exchange/swap` | `cq/spot` | `cq/swap` | | - | :-: | :-: | :-: | :-: | | [OHLCV](/v2/market/exchange-spot-ohlcv) | ✓ | ✓ | ✓ | ✓ | | [Trade](/v2/market/exchange-spot-trade) | ✓ | ✓ | ✓ | ✓ | | [Funding Rate](/v2/market/exchange-swap-funding-rate) | — | ✓ | — | ✓ | | [Open Interest](/v2/market/exchange-swap-open-interest) | — | ✓ | — | ✓ | | [Liquidation](/v2/market/exchange-swap-liquidation) | — | ✓ | — | ✓ | ## Origin: `exchange` vs `cq` * **`exchange`** — data for one named exchange. Requires an `exchange` parameter (e.g. `binance`) and per-quote `symbol`s such as `btc_usdt`. * **`cq`** — CryptoQuant's cross-exchange aggregate. Takes **no** `exchange` parameter, and is selected by aggregated `symbol`s such as `btc_all`. ## Symbols The `symbol` parameter selects the trading pair. There are two symbol classes: | Class | Example | Where | | - | - | - | | **Per-quote** | `btc_usdt` | Exchange origin — a specific base/quote pair on one exchange | | **All-quote (aggregated)** | `btc_all` | CQ origin — one base aggregated across all quotes/exchanges | For **funding rate, open interest, and liquidation**, the `exchange` endpoints are *dual-class*: a `btc_usdt` symbol returns the single pair, while `btc_all` returns that exchange's all-quote aggregate across all its quote currencies. Because `exchange` and `symbol` are open-ended, use the discovery endpoints to enumerate valid values: * [List Active Exchanges](/v2/market/info-exchanges) — `/v2/market/info/exchanges` * [List Active Symbols](/v2/market/info-symbols) — `/v2/market/info/symbols` A typical first-time flow: call **exchanges** to pick an exchange, then **symbols** for the endpoint you want, then query the data endpoint with those values. > [!NOTE] > > Discovery returns what has been **active in the last 30 days**. Delisted or illiquid > symbols are hidden there, but can still be queried directly with `from`/`to`. ## Linear vs inverse (`swap` only) Swap endpoints accept an optional `inverse` flag: * `inverse=false` (default) — **linear** contracts (USDⓈ-margined). * `inverse=true` — **inverse** contracts (coin-margined). `inverse` only applies to `swap`. Spot endpoints don't take it — sending `inverse` to a `spot` endpoint is ignored (the request still succeeds). ## Time parameters Identical to the rest of the API — see [Time Convention](/guides/time-convention). | Parameter | Notes | | - | - | | `window` | `day` (default), `hour`, `10min`, `min` | | `from`, `to` | `YYYYMMDDTHHMMSS` (UTC); `YYYYMMDD` also accepted when `window=day` | | `limit` | Max rows returned (default 100, max 10000) | | `format` | `json` (default) or `csv` | Market timestamps are returned as `datetime` in `YYYY-MM-DD HH:MM:SS` (UTC). ## Response envelope ```jsonc theme={null} { "status": { "code": 200, "message": "success" }, "result": { "window": "day", "data": [ { "datetime": "2024-01-01 00:00:00", "symbol": "btc_usdt", "base": "btc", "quote": "usdt", "open": 42280.0, "high": 44200.0, "low": 42120.0, "close": 44180.0, "volume": 18342.5, "quote_volume": 794512000.0 } ] } } ``` Each metric page below documents its own response fields, parameters, and an interactive playground. # Addresses Count Source: https://docs.cryptoquant.com/v2/network/addresses-count openapi/v2-onchain.json GET /network/addresses-count The number of addresses used in the window — active (sender or receiver), senders, and receivers counted separately. ## What it measures The number of addresses used in the window — active (sender or receiver), senders, and receivers counted separately. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `addresses_count_active` | integer | The number of unique addresses active as a sender or a receiver in the window. | | `addresses_count_receiver` | integer | The number of unique addresses active as a receiver. | | `addresses_count_sender` | integer | The number of unique addresses active as a sender. | # Block Bytes Source: https://docs.cryptoquant.com/v2/network/block-bytes openapi/v2-onchain.json GET /network/block-bytes The mean size, in bytes, of the blocks produced in the window. ## What it measures The mean size, in bytes, of the blocks produced in the window. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `block_bytes` | number | The mean size, in bytes, of the blocks produced. | # Block Count Source: https://docs.cryptoquant.com/v2/network/block-count openapi/v2-onchain.json GET /network/block-count The number of blocks produced in the window. ## What it measures The number of blocks produced in the window. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `hour` · `day` | The default window is `day`. ## Response fields The time key is `datetime` for every window of this endpoint (`hour`, `day`). | Field | Type | Description | | - | - | - | | `block_count` | integer | The number of blocks produced in the window. | # Block Interval Source: https://docs.cryptoquant.com/v2/network/block-interval openapi/v2-onchain.json GET /network/block-interval The mean time between blocks, in seconds. ## What it measures The mean time between blocks, in seconds. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `block_interval` | number | The mean time between blocks, in seconds. | # Block Reward Source: https://docs.cryptoquant.com/v2/network/blockreward openapi/v2-onchain.json GET /network/blockreward The sum of block rewards, counting both issuance and the transaction fees collected by the block producer. ## What it measures The sum of block rewards, counting both issuance and the transaction fees collected by the block producer. Reported in the native coin and USD. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `blockreward` | number | The sum of block rewards, including issuance and transaction fees, in the native coin (ETH or BTC). | | `blockreward_usd` | number | The sum of block rewards, in USD. | # Difficulty Source: https://docs.cryptoquant.com/v2/network/difficulty openapi/v2-onchain.json GET /network/difficulty The mean difficulty of producing a block. ## What it measures The mean difficulty of producing a block. For Ethereum this is zero from the Merge onward, when it stopped using proof of work. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `difficulty` | number | The mean difficulty of producing a block. For Ethereum, zero after the Merge, when it stopped using proof of work. | # Fees Source: https://docs.cryptoquant.com/v2/network/fees openapi/v2-onchain.json GET /network/fees Fees paid to execute transactions — the sum for the window, the mean per block, and fees as a share of the total block reward. ## What it measures Fees paid to execute transactions — the sum for the window, the mean per block, and fees as a share of the total block reward. Reported in the native coin and USD. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `fees_block_mean` | number | The mean fee per block, in the native coin. | | `fees_block_mean_usd` | number | The mean fee per block, in USD. | | `fees_reward_percent` | number | Fees as a share of the total block reward. Values run from 0 to 1. | | `fees_total` | number | The sum of all transaction fees paid in the window, in the native coin (ETH or BTC). | | `fees_total_usd` | number | The sum of all transaction fees paid in the window, in USD. | # Fees per Transaction Source: https://docs.cryptoquant.com/v2/network/fees-transaction openapi/v2-onchain.json GET /network/fees-transaction The mean and median fee paid per transaction, in the native coin and USD. ## What it measures The mean and median fee paid per transaction, in the native coin and USD. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `fees_transaction_mean` | number | The mean fee per transaction, in the native coin (ETH or BTC). | | `fees_transaction_mean_usd` | number | The mean fee per transaction, in USD. | | `fees_transaction_median` | number | The median fee per transaction, in the native coin. | | `fees_transaction_median_usd` | number | The median fee per transaction, in USD. | # Hashrate Source: https://docs.cryptoquant.com/v2/network/hashrate openapi/v2-onchain.json GET /network/hashrate The mean rate at which miners were solving hashes across the network, in gigahashes per second. ## What it measures The mean rate at which miners were solving hashes across the network, in gigahashes per second. For Ethereum, zero after the Merge. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `hashrate` | number | The mean rate at which miners solved hashes, in gigahashes per second. For Ethereum, zero after the Merge. | # Supply Source: https://docs.cryptoquant.com/v2/network/supply openapi/v2-onchain.json GET /network/supply Metrics on the supply of the asset — how much of it exists, and how that changed in the window. ## What it measures Metrics on the supply of the asset — how much of it exists, and how that changed in the window. The exact set of fields depends on the asset class: native ETH reports issuance, ERC-20 tokens report mints and burns, and stablecoins additionally separate circulating supply from total supply. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `supply_new` | number | The amount newly issued in the window. Native assets only (`eth`, `btc`) — issuance comes from block rewards. | | `supply_total` | number | The total amount of the asset in existence. | # Tokens Transferred Source: https://docs.cryptoquant.com/v2/network/tokens-transferred openapi/v2-onchain.json GET /network/tokens-transferred Transfer volume — the total amount moved in the window, plus the mean and median per transaction. ## What it measures Transfer volume — the total amount moved in the window, plus the mean and median per transaction. Also reported in USD. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `tokens_transferred_total` | number | The total amount transferred in the window. | | `tokens_transferred_mean` | number | The mean amount transferred per transaction. May be `null`. | | `tokens_transferred_total_usd` | number | The total amount transferred in the window, in USD. | | `tokens_transferred_mean_usd` | number | The mean amount transferred per transaction, in USD. | # Transactions Count Source: https://docs.cryptoquant.com/v2/network/transactions-count openapi/v2-onchain.json GET /network/transactions-count The number of transactions in the window, as a total and as a mean per block. ## What it measures The number of transactions in the window, as a total and as a mean per block. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `transactions_count_total` | integer | The total number of transactions in the window. | | `transactions_count_mean` | number | The mean number of transactions per block. Equals the total when `window=block`. | # UTXO Count Source: https://docs.cryptoquant.com/v2/network/utxo-count openapi/v2-onchain.json GET /network/utxo-count The number of unspent transaction outputs (UTXOs) in existence at the end of the interval. ## What it measures The number of unspent transaction outputs (UTXOs) in existence at the end of the interval. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `utxo_count` | integer | The number of unspent transaction outputs in existence at the end of the interval. | # Velocity Source: https://docs.cryptoquant.com/v2/network/velocity openapi/v2-onchain.json GET /network/velocity Velocity is estimated transaction volume over the trailing year divided by current supply. ## What it measures Velocity is estimated transaction volume over the trailing year divided by current supply. It describes how actively the asset is circulating: a rising velocity means the same supply is changing hands more often. ## Assets and windows | Asset class | What it covers | Assets | Windows | | - | - | - | - | | **Bitcoin** | the native asset of Bitcoin, `asset=btc` | `btc` | `block` · `hour` · `day` | The default window is `day`. ## Response fields The time key depends on the window: `datetime` for `day` and `hour` and `blockheight` plus `datetime` for `block`. | Field | Type | Description | | - | - | - | | `velocity_supply_total` | number | Estimated transaction volume over the trailing year divided by current total supply. | # On-chain Data Overview Source: https://docs.cryptoquant.com/v2/onchain/overview Bitcoin network, entity flow, indicator, and supply data in API v2 — one path per metric, with the asset as a query parameter. API v2 On-chain Data serves network activity, exchange and mining pool flows, on-chain indicators, and supply metrics for **Bitcoin**. It uses the same `status`/`result` envelope, Bearer authentication, and `window`/`from`/`to` time convention as the rest of the API. > [!WARNING] > > **Ethereum on API v2 is temporarily paused** (since October 23, 2026) for performance optimization — > native ETH, ERC-20 tokens, and the stablecoins issued on Ethereum are not served on `/v2` until the > updates are complete; requests for those assets return `400`. The v1 Ethereum endpoints are unaffected. > Re-enabling will be announced in the [changelog](/guides/changelog). > [!NOTE] > > **Beta since October 8, 2026.** The 55 endpoints in this section are open to every > API key — 33 Bitcoin-only endpoints plus 22 shared endpoints whose Ethereum assets are paused, all serving `asset=btc`. Endpoint paths, parameters, and response fields are final; historical values may > still be corrected during the beta, and every correction is listed in the > [changelog](/guides/changelog). ## Endpoints at a glance 55 endpoints. Classes are the asset classes an endpoint serves (`btc`, `eth`, `erc20`, `stablecoin`); windows are the union across those classes — the endpoint page has the exact table per class. Credits are charged per 100 rows returned. ### Network (14) | Endpoint | Path | Classes | Windows | Credit | | - | - | - | - | - | | [Addresses Count](/v2/network/addresses-count) | `/v2/network/addresses-count` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Block Bytes](/v2/network/block-bytes) | `/v2/network/block-bytes` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Block Count](/v2/network/block-count) | `/v2/network/block-count` | `btc` | `hour` `day` | 20 / 100 rows | | [Block Interval](/v2/network/block-interval) | `/v2/network/block-interval` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Block Reward](/v2/network/blockreward) | `/v2/network/blockreward` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Difficulty](/v2/network/difficulty) | `/v2/network/difficulty` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Fees](/v2/network/fees) | `/v2/network/fees` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Fees per Transaction](/v2/network/fees-transaction) | `/v2/network/fees-transaction` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Hashrate](/v2/network/hashrate) | `/v2/network/hashrate` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Supply](/v2/network/supply) | `/v2/network/supply` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Tokens Transferred](/v2/network/tokens-transferred) | `/v2/network/tokens-transferred` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Transactions Count](/v2/network/transactions-count) | `/v2/network/transactions-count` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [UTXO Count](/v2/network/utxo-count) | `/v2/network/utxo-count` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Velocity](/v2/network/velocity) | `/v2/network/velocity` | `btc` | `block` `hour` `day` | 20 / 100 rows | ### Flows (18) | Endpoint | Path | Classes | Windows | Credit | | - | - | - | - | - | | [Addresses Count](/v2/flows/addresses-count) | `/v2/flows/exchange/addresses-count` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [In-House Flow](/v2/flows/in-house-flow) | `/v2/flows/exchange/in-house-flow` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Inflow](/v2/flows/inflow) | `/v2/flows/exchange/inflow` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Netflow](/v2/flows/netflow) | `/v2/flows/exchange/netflow` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Outflow](/v2/flows/outflow) | `/v2/flows/exchange/outflow` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Reserve](/v2/flows/reserve) | `/v2/flows/exchange/reserve` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Transactions Count](/v2/flows/transactions-count) | `/v2/flows/exchange/transactions-count` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Exchange to Exchange](/v2/flows/inter-entity/exchange-to-exchange) | `/v2/flows/inter-entity/exchange-to-exchange` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Exchange to Miner](/v2/flows/inter-entity/exchange-to-miner) | `/v2/flows/inter-entity/exchange-to-miner` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Miner to Exchange](/v2/flows/inter-entity/miner-to-exchange) | `/v2/flows/inter-entity/miner-to-exchange` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Miner to Miner](/v2/flows/inter-entity/miner-to-miner) | `/v2/flows/inter-entity/miner-to-miner` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Mining Pool Addresses Count](/v2/flows/mining-pools/addresses-count) | `/v2/flows/mining-pools/addresses-count` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Mining Pool In-House Flow](/v2/flows/mining-pools/in-house-flow) | `/v2/flows/mining-pools/in-house-flow` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Mining Pool Inflow](/v2/flows/mining-pools/inflow) | `/v2/flows/mining-pools/inflow` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Mining Pool Netflow](/v2/flows/mining-pools/netflow) | `/v2/flows/mining-pools/netflow` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Mining Pool Outflow](/v2/flows/mining-pools/outflow) | `/v2/flows/mining-pools/outflow` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Mining Pool Reserve](/v2/flows/mining-pools/reserve) | `/v2/flows/mining-pools/reserve` | `btc` | `block` `hour` `day` | 40 / 100 rows | | [Mining Pool Transactions Count](/v2/flows/mining-pools/transactions-count) | `/v2/flows/mining-pools/transactions-count` | `btc` | `block` `hour` `day` | 40 / 100 rows | ### Indicator (22) | Endpoint | Path | Classes | Windows | Credit | | - | - | - | - | - | | [Mean Coin Age](/v2/indicator/mca) | `/v2/indicator/holder-composition/mca` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Estimated Leverage Ratio](/v2/indicator/estimated-leverage-ratio) | `/v2/indicator/leverage-risk/estimated-leverage-ratio` | `btc` | `block` | 20 / 100 rows | | [Realized Price](/v2/indicator/realized-price) | `/v2/indicator/price-models/realized-price` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [NRPL](/v2/indicator/nrpl) | `/v2/indicator/realized-pnl/nrpl` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [SOPR](/v2/indicator/sopr) | `/v2/indicator/realized-pnl/sopr` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [SOPR Ratio](/v2/indicator/sopr-ratio) | `/v2/indicator/realized-pnl/sopr-ratio` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Coin Days Destroyed](/v2/indicator/cdd) | `/v2/indicator/selling-activity/cdd` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Dormancy](/v2/indicator/dormancy) | `/v2/indicator/selling-activity/dormancy` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [Exchange Shutdown Index](/v2/indicator/exchange-shutdown-index) | `/v2/indicator/selling-activity/exchange-shutdown-index` | `btc` | `block` | 20 / 100 rows | | [Exchange Supply Ratio](/v2/indicator/exchange-supply-ratio) | `/v2/indicator/selling-activity/exchange-supply-ratio` | `btc` | `block` | 40 / 100 rows | | [Exchange Whale Ratio](/v2/indicator/exchange-whale-ratio) | `/v2/indicator/selling-activity/exchange-whale-ratio` | `btc` | `block` | 40 / 100 rows | | [Fund Flow Ratio](/v2/indicator/fund-flow-ratio) | `/v2/indicator/selling-activity/fund-flow-ratio` | `btc` | `block` | 40 / 100 rows | | [Mining Pool Supply Ratio](/v2/indicator/mining-pool-supply-ratio) | `/v2/indicator/selling-activity/mining-pool-supply-ratio` | `btc` | `block` | 40 / 100 rows | | [Stablecoin Supply Ratio](/v2/indicator/stablecoin-supply-ratio) | `/v2/indicator/selling-activity/stablecoin-supply-ratio` | `btc` | `day` | 20 / 100 rows | | [MVRV Ratio](/v2/indicator/mvrv) | `/v2/indicator/unrealized-pnl/mvrv` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [NUPL](/v2/indicator/nupl) | `/v2/indicator/unrealized-pnl/nupl` | `btc` | `block` `hour` `day` | 20 / 100 rows | | [PnL Index](/v2/indicator/pnl-index) | `/v2/indicator/unrealized-pnl/pnl-index` | `btc` | `day` | 20 / 100 rows | | [NVM Ratio](/v2/indicator/nvm) | `/v2/indicator/valuation/nvm` | `btc` | `hour` `day` | 20 / 100 rows | | [NVT Ratio](/v2/indicator/nvt) | `/v2/indicator/valuation/nvt` | `btc` | `hour` `day` | 20 / 100 rows | | [NVT Golden Cross](/v2/indicator/nvt-golden-cross) | `/v2/indicator/valuation/nvt-golden-cross` | `btc` | `day` | 20 / 100 rows | | [Puell Multiple](/v2/indicator/puell-multiple) | `/v2/indicator/valuation/puell-multiple` | `btc` | `hour` `day` | 20 / 100 rows | | [Stock to Flow](/v2/indicator/stock-to-flow) | `/v2/indicator/valuation/stock-to-flow` | `btc` | `block` `hour` `day` | 20 / 100 rows | ### Market (1) | Endpoint | Path | Classes | Windows | Credit | | - | - | - | - | - | | [Capitalization](/v2/market/capitalization) | `/v2/market/capitalization` | `btc` | `block` `hour` `day` | 10 / 100 rows | ## How much history each window keeps This is the v2-wide rule (see [API v2 Overview](/v2/overview)); it applies to every on-chain endpoint. | `window` | History available | | - | - | | `block`, `10min` | Last **3 months** | | `hour` | Last **12 months** | | `day` | **Full history** | A `from` older than the window keeps returns `400` — `'from' is outside the block retention window (3 months). Use window=day for full history.` — so use `day` for long-range history and the finer windows for recent detail. Bitcoin series are refreshed **hourly**, so for `asset=btc` the latest `block` rows can trail the chain tip by up to about an hour, and the latest completed `hour` row typically appears within the following hour. ## The asset is a parameter, not a path This is the one structural change from v1. Where v1 had a separate path per asset family, v2 has **one path per metric** and takes the asset as a query parameter: ```text theme={null} v1 /v1/btc/network-data/supply /v1/btc/exchange-flows/reserve?exchange=binance v2 /v2/network/supply?asset=btc /v2/flows/exchange/reserve?asset=btc&exchange=binance ``` Two consequences worth knowing before you write any code: * **`asset` takes the plain alias, with no chain suffix.** v1's `/btc/...` paths are `asset=btc` in v2 (and, once Ethereum resumes, v1's `usdt_eth` is `asset=usdt`). Add `chain=bitcoin` when the same alias exists on more than one chain; it is optional otherwise. * **What comes back depends on the asset.** One path serves several asset classes, and the available windows and response fields differ between them. Each endpoint page has a table for both. ## Asset classes | Class | What it is | Assets | `chain` | | - | - | - | - | | `btc` | The native asset of Bitcoin | `btc` | `bitcoin` | | `eth`, `erc20`, `stablecoin` | Native ETH, ERC-20 tokens, and the stablecoins issued on Ethereum — **paused** since October 23, 2026 | — | `ethereum` | While the Ethereum classes are paused, every endpoint in this section serves `btc` only, and an Ethereum asset returns `400` ("Unsupported asset"). The class tables on the endpoint pages and [`/v2/discovery/assets`](/v2/discovery) reflect what is served right now. ## Windows differ by endpoint Each endpoint serves the windows its data is built for, and a window it does not serve returns `400` naming the ones it does. [Estimated Leverage Ratio](/v2/indicator/estimated-leverage-ratio), for example, serves `block` only: ```text theme={null} GET /v2/indicator/leverage-risk/estimated-leverage-ratio?asset=btc&window=day&exchange=all_exchange 400 Bad Request: /v2/indicator/leverage-risk/estimated-leverage-ratio does not support day for btc. Supported: ['block'] ``` When several asset classes share a path, the windows can also differ between them — the endpoint page has the exact table per class. The error names the windows that asset does support, so a `400` here is a usable answer rather than a dead end. The default window is `day` for every endpoint in this section except [Estimated Leverage Ratio](/v2/indicator/estimated-leverage-ratio), [Exchange Shutdown Index](/v2/indicator/exchange-shutdown-index), [Exchange Whale Ratio](/v2/indicator/exchange-whale-ratio), [Fund Flow Ratio](/v2/indicator/fund-flow-ratio), [Mining Pool Supply Ratio](/v2/indicator/mining-pool-supply-ratio), which default to `block`. The default is applied per endpoint, not per asset class, so on a shared endpoint it can name a window one class does not serve: * [Exchange Supply Ratio](/v2/indicator/exchange-supply-ratio) — `/v2/indicator/selling-activity/exchange-supply-ratio` has no default window for `btc`: `day` is not served for that class, so omit `window` and the request returns `400`. Pass `window=block`. > [!NOTE] > > Treat the **endpoint page's asset-class table as the authority** on what a given asset > supports. [`/v2/discovery/endpoints`](/v2/discovery) returns the union across an endpoint's assets, so a value > listed there is a candidate, not a guarantee for every asset. ## Time keys Which time field comes back depends on the window. Unlike v1, every v2 window uses `datetime`; there is no `date` field. | `window` | Time field(s) | | - | - | | `day`, `hour`, `10min` | `datetime` (`YYYY-MM-DD HH:MM:SS`) — a `day` row is its midnight UTC, e.g. `2026-09-21 00:00:00` (v1 used `date` for daily rows; v2 uses `datetime` everywhere) | | `block` | `blockheight` and `datetime` | All timestamps are UTC. Requests use a different, compact format: `from` and `to` take `YYYYMMDDTHHMMSS` (UTC), and `YYYYMMDD` is also accepted when `window=day`. Copying a response value such as `2026-09-01` into `from` returns `400`. ```text theme={null} GET /v2/network/transactions-count?asset=btc&window=hour&from=20260901T000000&to=20260901T030000 ``` ## Response envelope ```jsonc theme={null} { "status": { "code": 200, "message": "success" }, "result": { "window": "day", "data": [ { "datetime": "2026-09-21 00:00:00", "supply_total": 122478455.27907232, "supply_new": 2853.33175743328 } ] } } ``` ## Entity flows take an entity parameter Flow endpoints and the entity-based indicators additionally take the entity they are about: | Parameter | Endpoints | Aggregate value | | - | - | - | | `exchange` | `/v2/flows/exchange/*`, Exchange Supply Ratio, and the Bitcoin exchange indicators (whale ratio, fund flow ratio, shutdown index, estimated leverage ratio) | `all_exchange` | | `miner` | `/v2/flows/mining-pools/*` and Mining Pool Supply Ratio (Bitcoin) | `all_miner` | | `from_exchange` / `to_exchange` / `from_miner` / `to_miner` | `/v2/flows/inter-entity/*` (Bitcoin) — one source and one destination, e.g. `from_exchange=binance&to_exchange=okx`. The two must differ; identical values return `400`. | `all_exchange` / `all_miner` | Pass the aggregate value for the total across every entity CryptoQuant tracks, or a single entity name such as `binance` or `f2pool`. The accepted names come from [`/v2/discovery/endpoints`](/v2/discovery) — they are resolved from the live entity registry, so a newly labelled exchange or mining pool appears without a docs change. ## Coming from v1 Almost every endpoint below has a v1 counterpart. The metric definitions are unchanged; what changed is the path shape and the `token` → `asset` parameter. Bitcoin's v1 groups were regrouped by meaning rather than by data source. The metrics and their fields are unchanged; only the path moved: | v1 group | v2 group | | - | - | | `/v1/btc/network-data/*`, `/v1/btc/exchange-flows/*` | `/v2/network/*`, `/v2/flows/exchange/*` — shared paths (Ethereum assets paused), with `asset=btc` | | `/v1/btc/miner-flows/*` | `/v2/flows/mining-pools/*` (the parameter is still `miner`) | | `/v1/btc/inter-entity-flows/*` | `/v2/flows/inter-entity/*` | | `/v1/btc/flow-indicator/*` | `/v2/indicator/selling-activity/*` (`miner-supply-ratio` is now `mining-pool-supply-ratio`) | | `/v1/btc/network-indicator/*`, `/v1/btc/market-indicator/*` | `/v2/indicator/{valuation,unrealized-pnl,realized-pnl,price-models,holder-composition,leverage-risk,selling-activity}/*` — by what the indicator measures | | `/v1/btc/market-data/capitalization` | `/v2/market/capitalization` with `asset=btc` — all five capitalization models | Not every v1 window carried over at launch: the Bitcoin exchange and mining pool indicators (whale ratio, fund flow ratio, shutdown index, mining pool supply ratio, exchange supply ratio) and the estimated leverage ratio serve `block` only in v2 where v1 also had `day` and `hour`. The endpoint page's asset-class table is authoritative. Two request-side differences trip up code ported from v1: * **`limit` caps at 10,000 rows** (v1 accepted up to 100,000). A larger value returns `400`; page with `from`/`to` instead. * **`from`/`to` are `YYYYMMDDTHHMMSS`** (or `YYYYMMDD` with `window=day`), as described under [Time keys](#time-keys). | v2 | v1 | | - | - | | [Addresses Count](/v2/flows/addresses-count) — `/v2/flows/exchange/addresses-count` | `/v1/btc/exchange-flows/addresses-count` `/v1/eth/exchange-flows/addresses-count` `/v1/erc20/exchange-flows/addresses-count` `/v1/stablecoin/exchange-flows/addresses-count` | | [In-House Flow](/v2/flows/in-house-flow) — `/v2/flows/exchange/in-house-flow` | `/v1/btc/exchange-flows/in-house-flow` | | [Inflow](/v2/flows/inflow) — `/v2/flows/exchange/inflow` | `/v1/btc/exchange-flows/inflow` `/v1/eth/exchange-flows/inflow` `/v1/erc20/exchange-flows/inflow` `/v1/stablecoin/exchange-flows/inflow` | | [Netflow](/v2/flows/netflow) — `/v2/flows/exchange/netflow` | `/v1/btc/exchange-flows/netflow` `/v1/eth/exchange-flows/netflow` `/v1/erc20/exchange-flows/netflow` `/v1/stablecoin/exchange-flows/netflow` | | [Outflow](/v2/flows/outflow) — `/v2/flows/exchange/outflow` | `/v1/btc/exchange-flows/outflow` `/v1/eth/exchange-flows/outflow` `/v1/erc20/exchange-flows/outflow` `/v1/stablecoin/exchange-flows/outflow` | | [Reserve](/v2/flows/reserve) — `/v2/flows/exchange/reserve` | `/v1/btc/exchange-flows/reserve` `/v1/eth/exchange-flows/reserve` `/v1/erc20/exchange-flows/reserve` `/v1/stablecoin/exchange-flows/reserve` | | [Transactions Count](/v2/flows/transactions-count) — `/v2/flows/exchange/transactions-count` | `/v1/btc/exchange-flows/transactions-count` `/v1/eth/exchange-flows/transactions-count` `/v1/erc20/exchange-flows/transactions-count` `/v1/stablecoin/exchange-flows/transactions-count` | | [Exchange to Exchange](/v2/flows/inter-entity/exchange-to-exchange) — `/v2/flows/inter-entity/exchange-to-exchange` | `/v1/btc/inter-entity-flows/exchange-to-exchange` | | [Exchange to Miner](/v2/flows/inter-entity/exchange-to-miner) — `/v2/flows/inter-entity/exchange-to-miner` | `/v1/btc/inter-entity-flows/exchange-to-miner` | | [Miner to Exchange](/v2/flows/inter-entity/miner-to-exchange) — `/v2/flows/inter-entity/miner-to-exchange` | `/v1/btc/inter-entity-flows/miner-to-exchange` | | [Miner to Miner](/v2/flows/inter-entity/miner-to-miner) — `/v2/flows/inter-entity/miner-to-miner` | `/v1/btc/inter-entity-flows/miner-to-miner` | | [Mining Pool Addresses Count](/v2/flows/mining-pools/addresses-count) — `/v2/flows/mining-pools/addresses-count` | `/v1/btc/miner-flows/addresses-count` | | [Mining Pool In-House Flow](/v2/flows/mining-pools/in-house-flow) — `/v2/flows/mining-pools/in-house-flow` | `/v1/btc/miner-flows/in-house-flow` | | [Mining Pool Inflow](/v2/flows/mining-pools/inflow) — `/v2/flows/mining-pools/inflow` | `/v1/btc/miner-flows/inflow` | | [Mining Pool Netflow](/v2/flows/mining-pools/netflow) — `/v2/flows/mining-pools/netflow` | `/v1/btc/miner-flows/netflow` | | [Mining Pool Outflow](/v2/flows/mining-pools/outflow) — `/v2/flows/mining-pools/outflow` | `/v1/btc/miner-flows/outflow` | | [Mining Pool Reserve](/v2/flows/mining-pools/reserve) — `/v2/flows/mining-pools/reserve` | `/v1/btc/miner-flows/reserve` | | [Mining Pool Transactions Count](/v2/flows/mining-pools/transactions-count) — `/v2/flows/mining-pools/transactions-count` | `/v1/btc/miner-flows/transactions-count` | | [Mean Coin Age](/v2/indicator/mca) — `/v2/indicator/holder-composition/mca` | `/v1/btc/network-indicator/mca` | | [Estimated Leverage Ratio](/v2/indicator/estimated-leverage-ratio) — `/v2/indicator/leverage-risk/estimated-leverage-ratio` | `/v1/btc/market-indicator/estimated-leverage-ratio` `/v1/eth/market-indicator/estimated-leverage-ratio` | | [Realized Price](/v2/indicator/realized-price) — `/v2/indicator/price-models/realized-price` | `/v1/btc/market-indicator/realized-price` | | [NRPL](/v2/indicator/nrpl) — `/v2/indicator/realized-pnl/nrpl` | `/v1/btc/network-indicator/nrpl` | | [SOPR](/v2/indicator/sopr) — `/v2/indicator/realized-pnl/sopr` | `/v1/btc/market-indicator/sopr` | | [SOPR Ratio](/v2/indicator/sopr-ratio) — `/v2/indicator/realized-pnl/sopr-ratio` | `/v1/btc/market-indicator/sopr-ratio` | | [Coin Days Destroyed](/v2/indicator/cdd) — `/v2/indicator/selling-activity/cdd` | `/v1/btc/network-indicator/cdd` | | [Dormancy](/v2/indicator/dormancy) — `/v2/indicator/selling-activity/dormancy` | `/v1/btc/network-indicator/dormancy` | | [Exchange Shutdown Index](/v2/indicator/exchange-shutdown-index) — `/v2/indicator/selling-activity/exchange-shutdown-index` | `/v1/btc/flow-indicator/exchange-shutdown-index` | | [Exchange Supply Ratio](/v2/indicator/exchange-supply-ratio) — `/v2/indicator/selling-activity/exchange-supply-ratio` | `/v1/btc/flow-indicator/exchange-supply-ratio` `/v1/eth/flow-indicator/exchange-supply-ratio` `/v1/erc20/flow-indicator/exchange-supply-ratio` `/v1/stablecoin/flow-indicator/exchange-supply-ratio` | | [Exchange Whale Ratio](/v2/indicator/exchange-whale-ratio) — `/v2/indicator/selling-activity/exchange-whale-ratio` | `/v1/btc/flow-indicator/exchange-whale-ratio` | | [Fund Flow Ratio](/v2/indicator/fund-flow-ratio) — `/v2/indicator/selling-activity/fund-flow-ratio` | `/v1/btc/flow-indicator/fund-flow-ratio` | | [Mining Pool Supply Ratio](/v2/indicator/mining-pool-supply-ratio) — `/v2/indicator/selling-activity/mining-pool-supply-ratio` | `/v1/btc/flow-indicator/miner-supply-ratio` | | [Stablecoin Supply Ratio](/v2/indicator/stablecoin-supply-ratio) — `/v2/indicator/selling-activity/stablecoin-supply-ratio` | `/v1/btc/market-indicator/stablecoin-supply-ratio` | | [MVRV Ratio](/v2/indicator/mvrv) — `/v2/indicator/unrealized-pnl/mvrv` | `/v1/btc/market-indicator/mvrv` | | [NUPL](/v2/indicator/nupl) — `/v2/indicator/unrealized-pnl/nupl` | `/v1/btc/network-indicator/nupl` | | [PnL Index](/v2/indicator/pnl-index) — `/v2/indicator/unrealized-pnl/pnl-index` | — new in v2 | | [NVM Ratio](/v2/indicator/nvm) — `/v2/indicator/valuation/nvm` | `/v1/btc/network-indicator/nvm` | | [NVT Ratio](/v2/indicator/nvt) — `/v2/indicator/valuation/nvt` | `/v1/btc/network-indicator/nvt` | | [NVT Golden Cross](/v2/indicator/nvt-golden-cross) — `/v2/indicator/valuation/nvt-golden-cross` | `/v1/btc/network-indicator/nvt-golden-cross` | | [Puell Multiple](/v2/indicator/puell-multiple) — `/v2/indicator/valuation/puell-multiple` | `/v1/btc/network-indicator/puell-multiple` | | [Stock to Flow](/v2/indicator/stock-to-flow) — `/v2/indicator/valuation/stock-to-flow` | `/v1/btc/network-indicator/stock-to-flow` | | [Capitalization](/v2/market/capitalization) — `/v2/market/capitalization` | `/v1/btc/market-data/capitalization` `/v1/eth/market-data/capitalization` `/v1/stablecoin/market-data/capitalization` | | [Addresses Count](/v2/network/addresses-count) — `/v2/network/addresses-count` | `/v1/btc/network-data/addresses-count` `/v1/eth/network-data/addresses-count` `/v1/erc20/network-data/addresses-count` `/v1/stablecoin/network-data/addresses-count` | | [Block Bytes](/v2/network/block-bytes) — `/v2/network/block-bytes` | `/v1/btc/network-data/block-bytes` `/v1/eth/network-data/block-bytes` | | [Block Count](/v2/network/block-count) — `/v2/network/block-count` | `/v1/btc/network-data/block-count` `/v1/eth/network-data/block-count` | | [Block Interval](/v2/network/block-interval) — `/v2/network/block-interval` | `/v1/btc/network-data/block-interval` `/v1/eth/network-data/block-interval` | | [Block Reward](/v2/network/blockreward) — `/v2/network/blockreward` | `/v1/btc/network-data/blockreward` `/v1/eth/network-data/blockreward` | | [Difficulty](/v2/network/difficulty) — `/v2/network/difficulty` | `/v1/btc/network-data/difficulty` `/v1/eth/network-data/difficulty` | | [Fees](/v2/network/fees) — `/v2/network/fees` | `/v1/btc/network-data/fees` `/v1/eth/network-data/fees` | | [Fees per Transaction](/v2/network/fees-transaction) — `/v2/network/fees-transaction` | `/v1/btc/network-data/fees-transaction` `/v1/eth/network-data/fees-transaction` | | [Hashrate](/v2/network/hashrate) — `/v2/network/hashrate` | `/v1/btc/network-data/hashrate` `/v1/eth/network-data/hashrate` | | [Supply](/v2/network/supply) — `/v2/network/supply` | `/v1/btc/network-data/supply` `/v1/eth/network-data/supply` `/v1/erc20/network-data/supply` `/v1/stablecoin/network-data/supply` | | [Tokens Transferred](/v2/network/tokens-transferred) — `/v2/network/tokens-transferred` | `/v1/btc/network-data/tokens-transferred` `/v1/eth/network-data/tokens-transferred` `/v1/erc20/network-data/tokens-transferred` `/v1/stablecoin/network-data/tokens-transferred` | | [Transactions Count](/v2/network/transactions-count) — `/v2/network/transactions-count` | `/v1/btc/network-data/transactions-count` `/v1/eth/network-data/transactions-count` `/v1/erc20/network-data/transactions-count` | | [UTXO Count](/v2/network/utxo-count) — `/v2/network/utxo-count` | `/v1/btc/network-data/utxo-count` | | [Velocity](/v2/network/velocity) — `/v2/network/velocity` | `/v1/btc/network-data/velocity` `/v1/eth/network-data/velocity` `/v1/erc20/network-data/velocity` | > [!NOTE] > > v1 remains fully supported. Any future deprecation will be announced in the > [changelog](/guides/changelog) well in advance. # API v2 Overview Source: https://docs.cryptoquant.com/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. 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 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). | | 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), normalized market data (OHLCV, trade, funding, open interest, liquidation), **and** Ethereum on-chain data (network, flows, supply) | | **Path scheme** | `/v1/{asset}/{category}/{metric}` | `/v2/community/{metric}` `/v2/market/{origin}/{instrument}/{metric}` `/v2/network/{metric}?asset=` | | **Asset selection** | In the path (`/v1/eth/...`, `/v1/erc20/...?token=`) | A query parameter (`?asset=eth`, `?asset=aave`) on the on-chain endpoints | | **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 three 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 │ ├── network/{metric}?asset= // on-chain network activity & supply │ ├── supply // ?asset=eth | aave | usdt │ ├── transactions-count // one path, every asset │ └── ... // fees, gas, blocks, staking │ └── flows/exchange/{metric}?asset=&exchange= // exchange flows ├── inflow // ?asset=eth&exchange=binance └── ... // outflow, netflow, reserve ``` * **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. * **On-chain data** — see the [On-chain Data Overview](/v2/onchain/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 a `window`: | `window` | History available | | - | - | | `min`, `10min`, `block` | Last **3 months** | | `hour` | Last **12 months** | | `day` | **Full history** | 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](/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.