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

# Introduction

> Overview of the BlockDB Historic REST API — authentication, pagination, compute units, and onboarding for EVM blockchain data.

## Video walkthrough

**BlockDB Free Account, API Key & First Query in 2 Minutes** — sign up, create a key, and run your first query:

<iframe className="w-full aspect-video rounded-xl" src="https://www.youtube.com/embed/JqLto9qY0KY" title="BlockDB Free Account, API Key & First Query in 2 Minutes" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowFullScreen />

For written steps, see the [Quick Start Guide](/user-guide/about-blockdb/quick-start-guide).

**Version:** `v1`\
**Last Updated:** `2026-05-12`

## Base URL

```http theme={null}
https://api.blockdb.io/v1
```

Use HTTPS for every request. Data endpoints are `POST` with a JSON body and typically return an envelope with `data`, `cursor`, and `count` for pagination. Account endpoints such as [`GET /usage`](/api-reference/account-and-usage/usage) and [`GET /health`](/api-reference/account-and-usage/health) use `GET` with no body.

## Authentication

Authentication uses **API keys** from **[dashboard.blockdb.io](https://dashboard.blockdb.io)** (up to **five** active keys per account). Send the key on every request as `Authorization: Bearer <API_KEY>`. Entitlements (datasets and chains) are tied to your account; **monthly compute units and RPS are account-wide and shared across all keys**—you cannot assign separate usage or rate limits to individual keys. Requests without a valid key return `401`. See [Authorization](/api-reference/overview/authorization) and [Rate limiting](/api-reference/overview/rate-limiting).

<Callout icon="lightbulb" color="#3B82F6" iconType="regular">
  The API never accepts query parameters for filters. Always place filters in the JSON body (for example, `chain_id`, block ranges, or address lists).
</Callout>

## Endpoint families

<CardGroup cols={2}>
  <Card title="Ledger & execution" icon="square-binary" href="/api-reference/evm/primitives/blocks">
    Blocks, transactions, logs, internal traces, contracts, and function results.
  </Card>

  <Card title="Tokens & liquidity" icon="hexagon-vertical-nft" href="/api-reference/evm/entities/tokens-erc20">
    ERC-20/721/1155 registries, pools, fee terms, reserves, transfers, and swap fees.
  </Card>

  <Card title="Pricing & TVL" icon="chart-line" href="/api-reference/evm/prices/overview">
    Swap prints, OHLC, per-pool and cross-pool VWAP, token-to-USD VWAP, yields, and TVL.
  </Card>

  <Card title="Flash loans & arbitrage" icon="bolt" href="/api-reference/evm/flash-loans/overview">
    Flash loan prints, arb paths, path status, and opportunities.
  </Card>
</CardGroup>

## Lineage, verification, and JSON-RPC

* **[Lineage](/api-reference/evm/lineage/overview)** — Resolve records, genesis artifacts, and parent graphs from `_tracing_id`.
* **[Verification](/api-reference/evm/verification/overview)** — Recompute receipt trie roots and log blooms for integrity checks.
* **[JSON-RPC](/api-reference/evm/rpc/overview)** — Proxied Ethereum JSON-RPC methods with `chain_id` routing.

## Enumerations & shared metadata

* [Dataset index](/data-catalog/evm/dataset-index) — All EVM dataset IDs, `blockdb_evm` table names, and catalog links
* [Chain](/api-reference/enumerations/chain)
* [Digital Exchange](/api-reference/enumerations/digital-exchange)
* [Dataset ID](/api-reference/enumerations/dataset-id)
* [Pool Type](/api-reference/enumerations/pool-type)
* [Asset Class](/api-reference/enumerations/asset-class)
* [Fiat Currency](/api-reference/enumerations/fiat-currency)
* [Market Kind](/api-reference/enumerations/market-kind)

## Contact & support

[support@blockdb.io](mailto:support@blockdb.io)