Introducing the Token Terminal data catalog

Today, we’re exposing the data layer that powers every Token Terminal product.

For most of our history, users have accessed Token Terminal data through a specific interface: our web application, API, spreadsheets, and more recently, our MCP. All of these products have always had the same foundation underneath them: our data warehouse.

The new Token Terminal data catalog makes that foundation visible and directly accessible.

From interface to infrastructure

Historically, we productized the outputs of our data infrastructure. We built interfaces that surfaced standardized metrics, charts, tables, API endpoints, and machine-readable responses on top of the same underlying warehouse.

We are now productizing the infrastructure itself.

The data catalog is an index of the datasets that power Token Terminal. It shows how our data is structured, how datasets relate to each other, and what is available across the different layers of our data warehouse. That warehouse is the foundation for every Token Terminal data product. It retains the underlying blockchain history and supports the transformations that turn raw activity into decoded, structured, and standardized datasets.

Go beyond standardized metrics

Standardized metrics are often the right place to start, but they are not always where sophisticated analysis ends. A protocol-level metric can answer what happened, but deeper work often requires understanding where that activity came from and how it is distributed across the underlying markets, pools, contracts, and assets.

An analyst may want to move from a protocol’s revenue to the individual markets that generated it, from a DEX’s trading volume to individual pools and trades, or from a lending protocol to individual deposits and borrows. For tokenized assets, the same principle applies: analysis can move from market cap into granular data on holders, transfers, underlying assets, issuers, geography, and legal & economic information.

The data catalog is designed for this level of work. Users can move from high-level financial and usage metrics down to the underlying pools, markets, transactions, transfers, and other granular datasets that support them. The objective is simple: make it possible to investigate the data at the level the question requires.

Built for direct warehouse access

The catalog also serves as the map for our data warehouse product. Customers can access Token Terminal datasets directly through BigQuery and Snowflake, inside the same environments where their own analysts and data teams already work.

This matters for customers who do not want to be limited by a predefined API endpoint or interface. Instead of asking only the questions our products anticipate, they can work directly with the underlying datasets, combine them with internal data, define their own methodologies, and build workflows around their specific use cases.

This is the direction we have been building toward for several years: moving from a collection of data products toward a data platform that can sit directly inside institutional data infrastructure.

One data layer, many ways to access it

The web application, API, MCP, and data warehouse are not separate products underneath. They are different access layers to the same data infrastructure.

• The web interface provides an intuitive way to explore standardized data.

• The API provides programmatic access.

• The MCP allows software and agents to work with the same datasets through natural language.

• The data warehouse gives analysts, engineers, and data teams direct access to the underlying data itself.

The data catalog ties these layers together. It provides a common map of the datasets that power all of them and makes the structure of Token Terminal’s data infrastructure much easier to understand.

Built alongside our most demanding customers

The catalog is not intended to be static. Our engineers work directly with sophisticated analysts, institutions, asset issuers, blockchain teams, and application developers to understand what they need from the data.

Because we operate the pipeline end to end, we can go beyond a fixed catalog when a use case requires it. We can expose deeper levels of granularity, build new abstractions, or tailor datasets around a specific analytical or product workflow.

This is where we believe the data warehouse becomes particularly valuable. The goal is not simply to provide more tables. It is to give serious users access to the deepest possible representation of onchain markets, without requiring them to build and maintain the underlying data infrastructure themselves.

Explore the data catalog

The Token Terminal data catalog is now live at https://tokenterminal.com/docs/catalog.

If you are interested in direct access to the Token Terminal data warehouse, or want to understand what datasets are available for your use case, reach out to us.

Our engineers want to build alongside our most demanding customers and can tailor datasets around specific analytical, investment, and product workflows.