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

> ## Agent Instructions
> To query the Token Terminal data catalog, read https://tokenterminal.com/docs/catalog/agents-manual.md first. It is the whole catalog as one page: table naming grammar, key columns, partition and cluster rules, units, additivity, and the tables that are documented but not served yet.
> Never query a catalog table on a time bound alone. Also filter its cluster key, which you read from INFORMATION_SCHEMA.COLUMNS; an empty result means the object is a view, whose pruning contract is on its page. Compute is billed to the caller's own Google Cloud project.

# Hyperliquid

> Everything the catalog holds for HyperCore, from the raw exchange streams to the markets that trade on it.

Hyperliquid runs two chains. HyperCore is the exchange itself: the matching engine, the perpetual markets and the spot order books, keyed `chain_id = 'hypercore'`. HyperEVM is its general-purpose EVM chain, keyed `chain_id = 'hyperevm'`, and it has its own section at [HyperEVM](https://tokenterminal.com/docs/catalog/chain-verticals/evm/hyperevm.md). This section covers HyperCore.

The chain's own record sits in the `hypercore` dataset: one row per block, fill, order, book change and funding settlement. Everything above that sits in the catalog, where the HyperCore rows are selected with `chain_id = 'hypercore'`.

The section mirrors the catalog itself: the core entities, then the market verticals with data on HyperCore.

## Layers

<table>
  <thead>
    <tr>
      <th width="180">Layer</th>
      <th width="110">Since</th>
      <th>What it holds</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>[Raw](https://tokenterminal.com/docs/catalog/chain-verticals/hyperliquid/raw.md)</td>
      <td>2025-03</td>
      <td>Blocks and the exchange streams beneath them: fills, orders, book changes, funding and TWAPs.</td>
    </tr>

    <tr>
      <td>[Projects](https://tokenterminal.com/docs/catalog/chain-verticals/hyperliquid/projects.md)</td>
      <td>2025-05</td>
      <td>Daily Notional volume, Fees and Revenue for each tracked project, broken out to HyperCore.</td>
    </tr>

    <tr>
      <td>[Apps](https://tokenterminal.com/docs/catalog/chain-verticals/hyperliquid/apps.md)</td>
      <td>2025-05</td>
      <td>Daily Notional volume, Trading volume, Fees and Revenue for each tracked app, broken out to HyperCore.</td>
    </tr>

    <tr>
      <td>[Perpetuals](https://tokenterminal.com/docs/catalog/chain-verticals/hyperliquid/perpetuals.md)</td>
      <td>2025-05</td>
      <td>Perpetual markets and the spot and outcome-market order books, with their volume, open interest, funding and fees.</td>
    </tr>
  </tbody>
</table>

## Filtering

`chain_id` reads `hypercore` wherever a catalog table has a chain, so the same filter selects HyperCore everywhere. Some shapes ask for something else. Project and app totals span every chain a project runs on, so one chain's share reads from `metrics_projects_by_chain` and `metrics_apps_by_chain`. The perpetual position and trader tables key on the market alone, so the chain comes from `dimensions.perp_markets`, as the query below does.

> [!WARNING]
>
> Every table splits by day: the raw and event tables on `block_timestamp`, the daily tables on `timestamp`. Bound that column in every query; without a bound the query reads the whole table.

```sql theme={null}
select
    daily.timestamp,
    markets.name,
    daily.open_interest
from `metrics_perp_markets.open_interest_daily` as daily
join `dimensions.perp_markets` as markets
    using (perp_market_id)
where markets.chain_id = 'hypercore'
  and daily.timestamp >= timestamp('2026-08-01')
  and daily.timestamp < timestamp('2026-08-02')
order by daily.open_interest desc
limit 100
```


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