> ## 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. # Data catalog > Every table in the catalog, queryable from your own BigQuery project. Write your BigQuery Project ID in the top bar. Every sample query rewrites to use it and runs in your project as-is. Two manuals cover the catalog. The [Human's manual](/docs/catalog/humans-manual) explains how these pages are laid out and how to read a table name, a page and a number. The [Agent's manual](/docs/catalog/agents-manual) is the same catalog as one page a model reads before it writes a query: the naming grammar, the key columns, the partition rules, the units and the tables that are documented but not served yet. The Agent's manual is written in [caveman](https://github.com/juliusbrussee/caveman) format, which cuts English to the words that carry the rule: no articles, no auxiliary verbs, no hedging, no transitions. *Why use many token when few token do trick.* Identifiers, types, numbers and negations stay exact. Only the grammar goes. ## Popular datasets Datasets that belong to no single market and no single chain: financial statements, prices, agentic payments, yields, token transfers, geographic intelligence and P\&L. A protocol's income statement and treasury, by reporting period. One USD price per token and per curated asset, per day. Payments software makes without a person in the loop, by asset. The yield an asset pays, per asset and per deployment. Every fungible token transfer, joined to the entity that issued it. Region of activity for an address: a UTC-offset band derived from transaction timing, never a country. What an account paid for its tokens and what they are worth now. **In progress.** ## Market verticals Curated verticals for every market, stablecoins to bridges, each followed across every chain. Every stablecoin: supply, holders, transfers and off-peg, across every chain. Every tokenized stock, fund and commodity: supply, holders and price against the underlying, across every chain. Every trading pool: swaps, volume, TVL and fees, across every DEX. Every perpetual and order-book market: trades, open interest, funding and liquidations, across every venue. Every lending market: supply, borrows and rates, across every protocol. Every cross-chain transfer: matched legs, USD value and daily volume, across every bridge. Every liquid staking protocol: staked value, flows and yield, across every chain. **In progress.** Every outcome market: trades, volume and positions, across every venue. **In progress.** Every aggregator: routed swaps and volume, across every venue. **In progress.** Every managed vault: deposits, value locked and returns, across every protocol. **In progress.** ## Chain ecosystems Everything on one chain, from raw blocks to asset and project metrics, across every market. Chains that work the same way internally share a family, so they carry the same tables and a query written for one runs on another with the chain name swapped. Solana from raw slots up: projects, apps, assets, tokens, contracts and its trading pools. HyperCore's exchange: raw fills and funding, and the perpetual and order-book markets above them. Ethereum, Base, Arbitrum and the wider EVM family: blocks, transactions, logs and traces. Bitcoin, Litecoin, Dogecoin and Stacks: blocks, transactions, inputs and outputs. Aptos, Sui and Movement: transactions, events and objects. Cosmos Hub, Injective and the wider Cosmos SDK family: blocks, transactions and messages. Polkadot and the wider Substrate family: blocks, extrinsics and events. Chains that match no family, each with its own table shape. ## Core entities The core actors in almost every blockchain transaction. A business that operates a network, deploys apps or issues assets, such as Ethereum, Aave or Circle. The blockchain a project's apps run on, such as Ethereum or Solana. One deployed version of a protocol that a project runs, such as Uniswap v3 or Aave v3. A venue where a trade, a loan or a position happens, such as a Uniswap v3 pool or the BTC perpetual. A financial instrument issued onchain, such as a stablecoin or a tokenized fund. A token contract on one chain, such as USDC on Ethereum. A wallet or a contract, such as an exchange wallet or a Uniswap pool. Code deployed to an address, such as the Uniswap v3 factory on Ethereum.