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

> Daily Notional volume, Trading volume, Fees and Revenue for each tracked app, broken out to HyperCore.

An app is one deployed version of a protocol that a project runs, such as `hyperliquid-perps` or `hyperliquid-spot`. The project level sits on [Projects](/docs/catalog/chain-verticals/hyperliquid/projects).

* `metrics_app_chains`: one table per measure, one row per app per chain per day.

An app's figure on HyperCore for one day rolls into its project's figure on the Projects page, worked out once and served at both levels. An app's chain rows for one day sum to what `metrics_apps` serves without the chain breakout, so use these tables when the chain breakdown is the question.

An app's activity has a finer table beneath it: perpetual volume breaks down market by market, and spot and outcome-market volume breaks down book by book, both on [Perpetuals](/docs/catalog/chain-verticals/hyperliquid/perpetuals). Start with the daily figures and drop down when the question needs the detail.

Every column is documented at [Apps ▸ Metrics](/docs/catalog/apps/metrics).

## Sample queries

<Tabs>
  <Tab title="Apps on HyperCore">
    **Rank the apps active on HyperCore by the fees their users paid over one week.** Fees is the measure the venue apps and the builder apps both report, so it ranks them on one scale.

    ```sql theme={null}
    select
        apps.name,
        sum(daily.fees) as fees
    from `metrics_app_chains.fees_daily` as daily
    join `dimensions.apps` as apps
        using (app_id)
    where daily.timestamp >= timestamp('2026-08-16')
      and daily.timestamp < timestamp('2026-08-23')
      and daily.chain_id = 'hypercore'
    group by apps.name
    order by fees desc
    ```
  </Tab>

  <Tab title="What the venue kept">
    **Split one app's fees into what it retained and what it passed on.** Revenue plus supply-side fees is total fees, and on HyperCore the supply side is the builder tip plus a HIP-3 deployer's cut.

    ```sql theme={null}
    select
        charged.timestamp,
        charged.fees,
        retained.revenue,
        passed_on.fees_supply_side
    from `metrics_app_chains.fees_daily` as charged
    join `metrics_app_chains.revenue_daily` as retained
        using (timestamp, app_id, chain_id)
    join `metrics_app_chains.fees_supply_side_daily` as passed_on
        using (timestamp, app_id, chain_id)
    where charged.timestamp >= timestamp('2026-08-16')
      and charged.timestamp < timestamp('2026-08-23')
      and charged.chain_id = 'hypercore'
      and charged.app_id = 'hyperliquid-perps'
    order by charged.timestamp
    ```
  </Tab>
</Tabs>