Skip to main content
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

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

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

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

​
Attribution

Every public payload carries page_url (link it), cite_as and data_by (“Data by CryptoQuant Consensus”) — show the attribution with the numbers.