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

# Apps

> Deployed protocol versions, the project behind each one, and their metrics per chain.

An app is one deployed version of a protocol: `uniswap-v3`, `aave-v3`, `hyperliquid-perps`. Every table that names an app carries `app_id`, and every app row carries the `project_id` of the [project](/docs/catalog/projects/index) that runs it.

## Pages

<CardGroup cols={2}>
  <Card title="Registry" icon="table-list" href="/docs/catalog/apps/registry">
    App names, the project that runs each one, and market sectors.
  </Card>

  <Card title="Metrics" icon="chart-line" href="/docs/catalog/apps/metrics">
    TVL, Fees, Revenue, Token incentives and Active users per app, and TVL, Fees and Revenue per app on one chain.
  </Card>
</CardGroup>

## Apps and chains

An app can run on several chains, and the app-and-chain level is the narrowest one published: `uniswap-v3` reads one row per chain per day there and one row per day at the app level. Where a measure adds up, the app row is its chain rows added together. [Metrics](/docs/catalog/apps/metrics) carries both levels.