---
title: "Token Terminal (standardized onchain financials)"
url: "https://caper.network/wiki/dao-governance/tooling/analytics/token-terminal"
updated: 2026-09-16
license: CC-BY-4.0
license_url: "https://creativecommons.org/licenses/by/4.0/"
---

# Token Terminal (standardized onchain financials)

|  |  |
| --- | --- |
| **Category** | Onchain financial data · standardized KPIs · [DAO analytics](/wiki/dao-governance/concepts/analysis/dao-metrics-and-analytics) |
| **Public since** | 2020 — [first archived capture, 30 August 2020](https://web.archive.org/web/20200830210212/https://www.tokenterminal.com/) |
| **What it does** | Ingests raw blockchain data and turns it into GAAP-style income statements — fees, revenue, expenses, earnings — on a basis that is comparable across protocols and chains ([about](https://tokenterminal.com/about)) |
| **Coverage** | 100+ chains, 1,200+ applications and 3,000+ tokenized assets; 11,000+ decoded smart contracts ([tokenterminal.com](https://tokenterminal.com/), [Data Room](https://tokenterminal.com/products/data-room), checked 1 August 2026) |
| **Access** | Free tier carries full historical data, CSV exports and MCP; Pro $350/month; REST API at 250,000 requests/day; warehouse sharing via BigQuery/Snowflake ([pricing](https://tokenterminal.com/pricing)) |
| **Status** | 🟢 Active — site, docs and API all live (checked 1 August 2026; front page, pricing and Data Room re-read unchanged 16 September 2026) |
| **Site** | [tokenterminal.com](https://tokenterminal.com/) · [docs](https://tokenterminal.com/docs) · [API reference](https://tokenterminal.com/docs/api-reference/introduction) |
| **Related** | [DeepDAO](/wiki/dao-governance/tooling/analytics/deepdao) · [Boardroom](/wiki/dao-governance/tooling/analytics/boardroom) · [Karma](/wiki/dao-governance/tooling/analytics/karma) · [DAOstar](/wiki/dao-governance/tooling/analytics/daostar) · [tooling stack](/wiki/dao-governance/tooling/dao-tooling-overview) |

**Token Terminal** is the financial-reporting layer of the [DAO tooling stack](/wiki/dao-governance/tooling/dao-tooling-overview). It does not host a forum, hold a treasury or count a vote; it answers a narrower question that governance keeps running into — _what does this protocol actually earn, and how does that compare to the one next to it?_ The platform ingests raw blocks, logs and traces from its own nodes, decodes smart-contract activity, and maps each project's idiosyncratic business logic onto [a single set of standardized financial and usage metrics](https://tokenterminal.com/about). The output is an income statement a treasurer or a delegate can read without first learning the protocol's internal accounting.

That matters for [DAOs](/wiki/dao-governance/concepts/fundamentals/what-is-a-dao) because the arguments that decide real money — [whether to turn on a fee switch](/wiki/economics/fee-switches-and-value-accrual), how long the [treasury](/wiki/dao-governance/concepts/treasury/dao-treasury-management) lasts, whether [emissions](/wiki/economics/liquidity-mining) are buying growth or renting it — are arguments about numbers, and until those numbers are defined the same way for every protocol, a forum thread is a fight over methodology rather than over the decision.

## The protocol income statement

Token Terminal's core abstraction is an ordinary income statement applied to a network. Its own worked example on the [front page](https://tokenterminal.com/) runs an Ethereum statement in four lines: **fees** of $103.72m in October 2024, of which **supply-side fees** of $35.51m are paid out to the parties providing the service, leaving **revenue** of $68.22m to the protocol, against **expenses** of $197.39m — overwhelmingly token issuance.

The gap between the first line and the third is the one governance most often confuses. Total fees measure how much users paid; revenue measures how much the protocol itself kept. A [DEX](/wiki/daos/dexs/uniswap-dao) that routes every basis point to liquidity providers can carry enormous fees and zero protocol revenue — which is precisely the state a fee-switch proposal exists to change, and precisely why quoting fees as if they were revenue distorts the vote. The fourth line is the one delegates skip: a protocol can be revenue-positive and earnings-negative at the same time, because [token incentives](/wiki/dao-governance/concepts/treasury/dao-tokenomics) are booked as an expense rather than treated as free.

## Where the numbers come from

Most crypto data products are aggregators: they read other people's APIs. Token Terminal [runs the pipeline end to end](https://tokenterminal.com/about) — direct ingestion of raw blocks, logs, traces and events from RPC nodes, a full backfill from genesis, storage in a BigQuery warehouse, contract-level decoding, then standardization into comparable KPIs served over API. Its FAQ is more precise about the boundary than the marketing copy: the company [runs its own blockchain infrastructure for 14+ chains and relies on third-party APIs for some metrics](https://tokenterminal.com/docs/faq), with the source named on each dashboard.

The pipeline is deliberately **ELT** rather than ETL — raw data is stored first and transformed afterwards. Token Terminal's [own justification](https://tokenterminal.com/docs/data-approach) is that in this industry the definitions move: protocols ship upgrades that break schemas, deploy new contracts across new chains, and the accepted meaning of “fees” or “active users” itself evolves. Keeping the raw data means a methodology change can be re-applied to history in minutes instead of re-ingested over days. For a DAO the practical consequence is _traceability_: a disputed figure can be walked back to the block and transaction that produced it, which is the property a governance forum needs and a screenshot of a chart does not have.

## What DAOs use it for

- **Fee-switch and value-accrual debates.** The question of whether a protocol should divert fees from suppliers to the treasury or the token is a question about the size and stability of the fee line — see [fee switches and value accrual](/wiki/economics/fee-switches-and-value-accrual).
- **Treasury reporting and runway.** Standardized revenue against standardized expenses is what turns a treasury balance into a runway estimate; the practice is covered on [treasury management](/wiki/dao-governance/concepts/treasury/dao-treasury-management).
- **Comparables for valuation.** Price-to-fees and price-to-revenue multiples only mean anything if the denominator is computed the same way across the peer set — see [token valuation](/wiki/economics/token-valuation).
- **Index construction and outside capital.** [MarketVector Indexes, a VanEck subsidiary, uses Token Terminal data as benchmark data for index construction](https://tokenterminal.com/customers), and the investment firm Theia runs its underwriting engine on the API. A DAO's reported fundamentals are increasingly an input to whether its token is held by anyone other than its own community.
- **Agent and LLM access.** The platform ships [an MCP server](https://tokenterminal.com/products/mcp) for natural-language queries against the same metrics — the emerging way analysis actually gets done during a proposal cycle.

## Access and cost

Coverage matters less than whether a DAO's contributors can get at it. Per Token Terminal's [published pricing](https://tokenterminal.com/pricing) (1 August 2026, re-read unchanged 16 September 2026), the free tier is unusually deep for this category: full historical data, three custom dashboards, the Google Sheets and Excel plugins, CSV exports and MCP access, at no cost. Pro removes the dashboard cap at $350 per month. The REST API is custom-priced with a 250,000 requests/day ceiling and startup discounts, and the Data Room tier delivers [raw block, transaction and event data plus 11,000+ decoded contracts](https://tokenterminal.com/products/data-room) into a customer's own BigQuery or Snowflake warehouse.

For a governance working group the free and Pro tiers are usually enough to source a proposal; the API tier is where a DAO would sit if it wanted a live treasury dashboard maintained by its own contributors rather than a vendor.

## Where it sits in the analytics layer

Until 2026 the closest thing to a single cross-DAO index was [DeepDAO](/wiki/dao-governance/tooling/analytics/deepdao), which put treasuries, membership and voter turnout for thousands of organizations behind one search box. Its public site went dark in mid-2026 and returned before the end of August, but as a static snapshot frozen at 24 November 2025 that its own operator tells readers not to use for research or decision-making — and by [September 2026](/wiki/dao-governance/tooling/analytics/deepdao) the site's front door had become a [final sale of that dataset](https://deepdao.io/products) to academic researchers, which answers the question of whether the pipeline was coming back. No live successor covers the same ground. What replaced it is a split:

- **Financials** — Token Terminal: fees, revenue, expenses and earnings, standardized for comparison.
- **Governance activity** — [Boardroom](/wiki/dao-governance/tooling/analytics/boardroom) for proposals and delegates across protocols, [Karma](/wiki/dao-governance/tooling/analytics/karma) for delegate participation scores.
- **Self-published data** — [DAOstar](/wiki/dao-governance/tooling/analytics/daostar), whose [EIP-4824](/wiki/dao-governance/concepts/analysis/eip-4824) standard has DAOs publish their own machine-readable index rather than relying on a third party to scrape them.
- **Bespoke queries** — [Dune](https://dune.com/) and similar SQL platforms, where anything not covered by a standard metric ends up.

The distinction to hold on to is that Token Terminal answers _how the business is doing_ and the governance tools answer _who is deciding_. A DAO that reads only the first cannot tell that its revenue is being set by four delegates; a DAO that reads only the second cannot tell that its treasury has eighteen months left.

## Limitations

Three caveats belong on any figure sourced from a standardized platform, and Token Terminal states two of them itself.

- **Methodology is a choice, not a fact.** Token Terminal's [FAQ acknowledges](https://tokenterminal.com/docs/faq) that its numbers differ from other providers because it uses a different methodology and tracks different versions and chains. Two honest sources can report different revenue for the same protocol; a proposal should name which one it used.
- **Coverage is partly opt-in.** New projects are added weekly, but listing runs through [a submission form, with submissions carrying complete smart-contract descriptions prioritized](https://tokenterminal.com/docs/faq). Absence from the platform is evidence about a project's data hygiene, not about its size.
- **Protocol financials are not DAO financials.** Fees accruing to a protocol contract are not the same as assets a DAO can spend; the treasury may hold a different set of tokens under a different mandate. The two lines belong in separate columns — a distinction [treasury management](/wiki/dao-governance/concepts/treasury/dao-treasury-management) takes further.

## How Caper approaches this

Token Terminal exists because a protocol's economics are scattered across contracts nobody outside the team can read, and someone has to reconstruct them. A [caper](/wiki/foundations/what-is-a-caper) starts from the other end: its token supply, its treasury and every buy and exit are component state on the Radix ledger, written by the same contract that enforces them, so the figures a reporting platform normally reassembles are the numbers the mechanism is already using. That does not remove the need for comparison across organizations — which is exactly what a standardized platform is for — but it does mean a holder can check the [current state](/wiki/markets/trading) at the source rather than trusting a pipeline to have decoded it correctly.

## References

- [Token Terminal — front page and worked Ethereum income statement](https://tokenterminal.com/)
- [Token Terminal — About: data infrastructure and standardization](https://tokenterminal.com/about)
- [Token Terminal docs — Our data approach (ELT, traceability, reproducibility)](https://tokenterminal.com/docs/data-approach)
- [Token Terminal docs — General FAQ (data sources, listing process, methodology differences)](https://tokenterminal.com/docs/faq)
- [Token Terminal — Pricing tiers and limits](https://tokenterminal.com/pricing)
- [Token Terminal — Data Room (raw and decoded datasets)](https://tokenterminal.com/products/data-room)
- [Token Terminal — MCP server](https://tokenterminal.com/products/mcp)
- [Token Terminal — Customer stories (MarketVector, Theia, Matter Labs)](https://tokenterminal.com/customers)
- [Internet Archive — tokenterminal.com, first capture 30 August 2020](https://web.archive.org/web/20200830210212/https://www.tokenterminal.com/)