> ## 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.

# Sentiment Data 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).
</Note>

## Who can use it

The Analyst Consensus API is available on the **Premium** plan and the **Enterprise** plan. Choose
the path that fits you:

<CardGroup cols={2}>
  <Card title="Premium plan" icon="user" href="https://cryptoquant.com/pricing">
    **Individuals and small teams.** Subscribe to CryptoQuant Premium and use the API as part of
    your subscription.
  </Card>

  <Card title="Enterprise plan" icon="building" href="https://cryptoquant.com/contact-us">
    **Institutions and research teams.** Full history, higher rate limits and dedicated
    onboarding. Pricing is custom per institution.
  </Card>
</CardGroup>

## Quick start

<Steps>
  <Step title="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"
    ```
  </Step>

  <Step title="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: <YOUR_API_KEY>"
    ```
  </Step>

  <Step title="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).
  </Step>
</Steps>

## 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

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/sentiment/authentication">
    `X-API-Key` header or `api_key` query parameter — and how it differs from the Data API.
  </Card>

  <Card title="Plans & Access" icon="layer-group" href="/sentiment/plans-and-access">
    What No key, Free, Premium and Enterprise can read; rate and daily limits; raw source text.
  </Card>

  <Card title="Data Coverage & Freshness" icon="database" href="/sentiment/data-coverage">
    1,712 assets, history since 2021-06-01, end-of-day UTC, sources and conventions.
  </Card>

  <Card title="Errors" icon="triangle-exclamation" href="/sentiment/errors">
    Every error code with its HTTP status and what to do; rate-limit headers.
  </Card>

  <Card title="Methodology" icon="flask" href="https://consensus.cryptoquant.com/methodology">
    How the consensus index, the accuracy scores and the tier badges are calculated.
  </Card>

  <Card title="Support" icon="life-ring" href="https://cryptoquant.com/contact-us">
    Questions or issues? Contact us.
  </Card>
</CardGroup>


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