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

# Projects

> Daily Fees and Revenue for each tracked project, broken out to Katana.

The top of the catalog breaks activity down by who ran it. A project is the entity behind a protocol, such as Uniswap.

* [`metrics_projects_by_chain`](https://tokenterminal.com/docs/catalog/projects/metrics): one table per measure, one row per project per chain per day.

A project figure for one chain and one day is the sum of its apps on that chain and day, worked out once and served at both levels. The same holds across chains: a project's chain rows for one day sum to what `metrics_projects` serves without the chain breakout, so use these tables when the chain breakdown is the question.

Every column is documented at [Projects ▸ Metrics](https://tokenterminal.com/docs/catalog/projects/metrics.md).

## Sample queries

**One project's series**

**Read one project's daily Katana fees.**

```sql theme={null}
select
    daily.timestamp,
    daily.fees
from `metrics_projects_by_chain.fees_daily` as daily
where daily.timestamp >= timestamp('2026-08-16')
  and daily.timestamp < timestamp('2026-08-23')
  and daily.chain_id = 'katananetwork'
  and daily.project_id = 'uniswap'
order by daily.timestamp
```

**Katana's share**

**Work out how much of a project runs on Katana.** Dropping the chain filter and grouping by chain turns the same table into a comparison across every chain the project operates on.

```sql theme={null}
with by_chain as (
    select
        chain_id,
        sum(fees) as fees
    from `metrics_projects_by_chain.fees_daily`
    where timestamp >= timestamp('2026-08-16')
      and timestamp < timestamp('2026-08-23')
      and project_id = 'uniswap'
    group by chain_id
)

select
    chain_id,
    fees,
    fees / sum(fees) over () as share
from by_chain
order by fees desc
limit 20
```


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