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

# Metrics

> Daily tokenized asset supply, holders, transfer activity and price.

Tokenized asset metrics are the shared asset tables under `asset_type in ('tokenized-stocks', 'tokenized-funds', 'tokenized-commodities', 'tokenized-cryptoasset')`; both tables carry the column, so most queries need no join.

* [`metrics.assets_daily`](/docs/catalog/assets/metrics): one row per asset per day.
* [`metrics.asset_tokens_daily`](/docs/catalog/assets/metrics): one row per deployment per day, the asset's contract on one chain.

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

## Sample queries

<Tabs>
  <Tab title="Asset">
    One row per asset per day, keyed `(asset_id, timestamp)`. Supply, price and yield are published here.

    **Read one tokenized fund's daily supply, holders and price.**

    ```sql theme={null}
    select
        timestamp,
        market_cap_circulating_total,
        holders_native,
        price,
        apy
    from `metrics.assets_daily`
    where asset_type = 'tokenized-funds'
      and asset_id = 'buidl'
      and timestamp >= timestamp('2026-06-01')
    order by timestamp
    ```

    **Rank tokenized stocks by circulating supply on one day.**

    ```sql theme={null}
    select
        asset_id,
        symbol,
        market_cap_circulating_native,
        holders_native
    from `metrics.assets_daily`
    where asset_type = 'tokenized-stocks'
      and timestamp = timestamp('2026-08-01')
      and market_cap_circulating_native is not null
    order by market_cap_circulating_native desc
    limit 25
    ```

    `apy` is a rate, so it never adds up, not across assets and not across days. Average it with a supply weight, or read it one asset at a time. `off_peg` measures how far a token has drifted from a currency peg, which only stablecoins have; it does not apply to tokenized assets, whose references are not currencies.
  </Tab>

  <Tab title="Deployment">
    One row per deployment per day, keyed `(asset_token_id, timestamp)`. This is where the per-chain breakdown lives, and the native-versus-bridged split.

    **Break one asset's supply down by chain.**

    ```sql theme={null}
    select
        timestamp,
        chain_id,
        bridged_status,
        market_cap_circulating_native,
        market_cap_circulating_bridged
    from `metrics.asset_tokens_daily`
    where asset_type = 'tokenized-funds'
      and asset_id = 'buidl'
      and timestamp = timestamp('2026-08-01')
    order by market_cap_circulating_native desc
    ```

    **Compare tokenized asset supply across chains on one day.**

    ```sql theme={null}
    select
        chain_id,
        count(distinct asset_id) as instruments,
        sum(market_cap_circulating_native) as native_supply
    from `metrics.asset_tokens_daily`
    where asset_type in (
        'tokenized-stocks', 'tokenized-funds',
        'tokenized-commodities', 'tokenized-cryptoasset'
    )
      and timestamp = timestamp('2026-08-01')
    group by chain_id
    order by native_supply desc
    ```

    For anything measured in dollars or in counted events, the asset's own row equals the sum of its deployment rows. The one exception is supply an issuer reports offchain, which appears on the asset's row and on no deployment's. A deployment is either native, meaning the issuer minted it there, or bridged, meaning it is a stand-in for supply issued elsewhere. Never both, so the two columns split the rows between them and summing a `_native` column never counts a stand-in as well.
  </Tab>
</Tabs>