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

# Data Coverage & Freshness

> 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`.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.