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

# Accounts

> Addresses on chains: wallets and contracts, and where they appear.

An account is an address on a chain, a wallet or a contract:

* Uniswap's `Factory` on `ethereum`, `0x1f98431c8ad98523631ae4a59f267346ea31f984`
* the `USDC-WETH pool` it deployed, `0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640`

[Registry](https://tokenterminal.com/docs/catalog/accounts/registry.md) gives an address its type, its project and its label where somebody has attributed it, and the region, funding venue and attested country held for it.

Addresses appear as columns on the other sections: `from_address` and `to_address` on [transfers](https://tokenterminal.com/docs/catalog/tokens/transfers.md), `account_address` in the [balance functions](https://tokenterminal.com/docs/catalog/tokens/balances.md), `sender_address` on the [sender table](https://tokenterminal.com/docs/catalog/assets/senders.md). Where an account is a contract, [Contracts](https://tokenterminal.com/docs/catalog/contracts/index.md) has its deployment, and the two registries join on `account_id`.

## Coverage

Every chain we label accounts on.

`alephzeroevm`
`algorand`
`aptos`
`arbitrum`
`avalanche`
`base`
`berachain`
`bitcoin`
`blast`
`bob`
`bobanetwork`
`bsc`
`cardano`
`celo`
`citrea`
`ethereum`
`fantom`
`flow`
`flowevm`
`fraxtal`
`gnosis`
`gravityalpha`
`hedera`
`hederaevm`
`hyperevm`
`immutablezkevm`
`injective`
`injectiveevm`
`ink`
`iota`
`iotex`
`katananetwork`
`linea`
`manta`
`mantraevm`
`megaeth`
`monad`
`movement`
`near`
`opbnb`
`optimism`
`osmosis`
`plasma`
`polygon`
`ripple`
`robinhoodchain`
`ronin`
`rootstock`
`scroll`
`seievm`
`solana`
`sonic`
`stacks`
`starknet`
`stellar`
`sui`
`tempo`
`terra`
`ton`
`tron`
`unichain`
`viction`
`worldchain`
`xai`
`xdc`
`xlayer`
`zksyncera`

## Tables

[Registry](https://tokenterminal.com/docs/catalog/accounts/registry.md) holds the identity table: one row per attributed address, with the chain it sits on, the project behind it, its type and its label. [Activity hours](https://tokenterminal.com/docs/catalog/accounts/activity-hours.md) holds the transaction counts and native value behind `region`, by address, chain, date and hour. [Activity coverage](https://tokenterminal.com/docs/catalog/accounts/activity-coverage.md) holds the share of each chain's daily activity that is attributed and regioned, by sender, transaction and value.

[Region distribution](https://tokenterminal.com/docs/catalog/accounts/region-distribution.md) holds region as a distribution, by chain, trailing 90-day window, region and confidence, across every sender on the chain, attributed or not: the only per-address-free view for region. [Region hit rate](https://tokenterminal.com/docs/catalog/accounts/region-hit-rate.md) holds how often the derived region matches the expected band for attributed accounts whose band is known in advance.

Registry's Venues tab, [Funding](https://tokenterminal.com/docs/catalog/accounts/funding.md) and [Venue edges](https://tokenterminal.com/docs/catalog/accounts/venue-edges.md) hold the venue a wallet was funded from: the venue's identity and jurisdiction gate, the tag itself keyed on `account_id` regardless of attribution, and the funding edges the tag is built from. [Funding coverage](https://tokenterminal.com/docs/catalog/accounts/funding-coverage.md) and [funding venue distribution](https://tokenterminal.com/docs/catalog/accounts/funding-venue-distribution.md) hold the same shape for funding that region distribution holds for region: the share of each chain's wallets that resolve to a venue, and those wallets broken out by venue and confidence tier. [Funding region agreement](https://tokenterminal.com/docs/catalog/accounts/funding-region-agreement.md) holds how often a wallet's region of activity matches its funding venue's expected band, and [funding hit rate](https://tokenterminal.com/docs/catalog/accounts/funding-hit-rate.md) holds how often a venue's curated deposit anchors also appear as detected deposit addresses.

[Attested country](https://tokenterminal.com/docs/catalog/accounts/attested-country.md) holds the country of residence Coinbase attested for a wallet, by address and chain family, for the holders who opted in.


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