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

# Blockworks Docs

> One account and one API key for institutional-grade crypto data, delivered as a REST API, an event feed, an MCP server, warehouse Datashares, and plugins.

Onchain activity, market and asset coverage, protocol and sector fundamentals, and the
events moving them, all from one set of warehouse models. Pick the surface that fits how
you work: a number is the same number wherever you get it.

<Frame>
  <img className="block dark:hidden" src="https://mintcdn.com/blockworksdocs/-ENWwrZfsdTblfGI/images/overview/surfaces-light.svg?fit=max&auto=format&n=-ENWwrZfsdTblfGI&q=85&s=c92f6609b51133e45d8a900108fb9422" alt="Blockworks warehouse models delivered through five surfaces: Data API, Monitoring, MCP Server, Datashares, and Plugins." width="880" height="372" data-path="images/overview/surfaces-light.svg" />

  <img className="hidden dark:block" src="https://mintcdn.com/blockworksdocs/-ENWwrZfsdTblfGI/images/overview/surfaces-dark.svg?fit=max&auto=format&n=-ENWwrZfsdTblfGI&q=85&s=a3e96ecd456127adc006ad34de8250f4" alt="Blockworks warehouse models delivered through five surfaces: Data API, Monitoring, MCP Server, Datashares, and Plugins." width="880" height="372" data-path="images/overview/surfaces-dark.svg" />
</Frame>

## Products

<CardGroup cols={2}>
  <Card title="Data API" icon="table" href="/getting-started/data-api">
    Query assets, protocols, networks, exchanges, and stablecoins: tabular models for
    entity and metric lookups, timeseries models for history.
  </Card>

  <Card title="Monitoring" icon="bell" href="/api-reference/monitoring/overview">
    Track governance proposals, unlocks, exploits, and funding across the assets and
    protocols you cover, by poll or webhook.
  </Card>

  <Card title="Token Unlocks" icon="calendar" href="/api-reference/token-unlocks/overview">
    Vesting schedules as data: allocations by recipient, dated cliffs, and how much supply
    unlocks in any window.
  </Card>

  <Card title="MCP Server" icon="robot" href="/mcp/overview">
    Connect Claude, ChatGPT, Cursor, or any MCP-capable agent to Blockworks data with no
    retrieval layer of your own.
  </Card>

  <Card title="Datashares" icon="database" href="/datashare/overview">
    The same datasets natively in your warehouse for full-scale SQL, joins against your
    own tables, and BI workloads.
  </Card>

  <Card title="Plugins" icon="puzzle" href="/spreadsheets/overview">
    <span className="surface-tag">Plugins</span>
    Blockworks data inside the tools you already use: Google Sheets and Excel today, with
    plugins for ChatGPT and Claude next.
  </Card>

  <Card title="Data API quickstart" icon="rocket" href="/getting-started/quickstart">
    <span className="surface-tag">5 minutes</span>
    Get a key and make your first request. One key covers every product.
  </Card>
</CardGroup>

## Choosing a surface

| What you want                                             | Use                                                    |
| --------------------------------------------------------- | ------------------------------------------------------ |
| Serve data inside an application, at low latency          | [Data API](/getting-started/data-api)                  |
| React to something happening, rather than poll for state  | [Monitoring](/api-reference/monitoring/overview)       |
| Know when locked supply hits the market, and who holds it | [Token Unlocks](/api-reference/token-unlocks/overview) |
| Let an agent answer questions against the data            | [MCP Server](/mcp/overview)                            |
| Run arbitrary SQL, or join Blockworks data to your own    | [Datashares](/datashare/overview)                      |
| Work inside a spreadsheet or an AI assistant              | [Plugins](/spreadsheets/overview)                      |

## What you can build

* **Dashboards and terminals**: asset, protocol, and sector screens backed by
  research-grade metrics rather than scraped aggregates.
* **Quant and research pipelines**: reproducible timeseries pulls with explicit
  granularity and point-in-time semantics, or the full dataset via a Datashare.
* **Risk and coverage monitoring**: programmatic alerting on unlocks, governance votes,
  and security events for the entities you hold or track.
* **Agentic workflows**: let an LLM answer questions against live Blockworks data over
  MCP, without writing a client.
* **Supply and unlock analysis**: model vesting schedules and upcoming cliffs across the
  assets you cover, per recipient and per interval.

<Note>
  One key covers every product. Create and manage keys from
  [app.blockworks.com/account/api](https://app.blockworks.com/account/api).
</Note>