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

# Stablecoins

> Every stablecoin issued on Manta: supply, holders and transfers.

Manta stablecoins are the [Assets](https://tokenterminal.com/docs/catalog/chain-verticals/evm/manta/assets.md) layer under `asset_type = 'stablecoin'`: the registry rows describe each coin's deployments and `metrics_asset_tokens` has their daily supply, holders and transfer activity in one table per measure.

Every column is documented at [Stablecoins](https://tokenterminal.com/docs/catalog/stablecoins/index.md).

## Sample queries

> [tab] Largest stablecoins
>
> **Rank the stablecoins issued on Manta by native circulating supply.**
>
> ```sql theme={null}
> select
>     assets.symbol,
>     daily.market_cap_circulating_native
> from `metrics_asset_tokens.market_cap_circulating_native_daily` as daily
> join `dimensions.asset_tokens` as deployments
>     using (asset_token_id)
> join `dimensions.assets` as assets
>     using (asset_id)
> where daily.timestamp >= timestamp('2026-08-22')
>   and daily.timestamp < timestamp('2026-08-23')
>   and deployments.chain_id = 'manta'
>   and assets.asset_type = 'stablecoin'
> order by daily.market_cap_circulating_native desc
> limit 20
> ```

> [tab] One coin's series
>
> **Read one stablecoin's daily supply and holders on Manta.** Each measure is its own table, so reading two means a join on `asset_token_id` and `timestamp`.
>
> ```sql theme={null}
> with supply as (
>     select
>         timestamp,
>         market_cap_circulating_native
>     from `metrics_asset_tokens.market_cap_circulating_native_daily`
>     where asset_token_id = 'susde-0x211cc4dd073734da055fbf44a2b4667d5e5fe5d2-manta'
>       and timestamp >= timestamp('2026-06-01')
>       and timestamp < timestamp('2026-08-23')
> ),
>
> holders as (
>     select
>         timestamp,
>         holders_native
>     from `metrics_asset_tokens.holders_native_daily`
>     where asset_token_id = 'susde-0x211cc4dd073734da055fbf44a2b4667d5e5fe5d2-manta'
>       and timestamp >= timestamp('2026-06-01')
>       and timestamp < timestamp('2026-08-23')
> )
>
> select
>     timestamp,
>     supply.market_cap_circulating_native,
>     holders.holders_native
> from supply
> left join holders
>     using (timestamp)
> order by timestamp
> ```


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