Registry - Token Terminal Docs

The identity table behind every app figure. Every metric joins to it, and Coverage introduces the grain.

Columns

Column	Type	Description
`app_id`	`STRING`	Identifier of the app. Every table that mentions an app joins on this.
`project_id`	`STRING`	Project that runs the app. Joins `dimensions.projects`.
`name`	`STRING`	Display name.
`market_sectors`	`ARRAY<STRING>`	Every market sector tag on the app.
`primary_market_sector`	`STRING`	The first element of `market_sectors`. One value per row.
`created_at`	`TIMESTAMP`	When the app was added to the registry.

Sample queries

Apps of one project
Apps by sector
Apps with their project

project_id is the same key the daily tables use, and one project has several rows here.

select
    app_id,
    name,
    market_sectors,
    created_at
from `dimensions.apps`
where project_id = 'hyperliquid'
order by app_id

primary_market_sector keeps one row per app however the tagging changes later. market_sectors is a list, so joining through unnest(market_sectors) yields one row per tag and any total taken off it comes out too high.

select
    primary_market_sector,
    count(*) as apps
from `dimensions.apps`
group by primary_market_sector
order by apps desc

The app’s name lives here and the project’s in dimensions.projects, so a row naming both is a join on project_id.

select
    apps.app_id,
    apps.name,
    projects.name as project_name
from `dimensions.apps` as apps
join `dimensions.projects` as projects
    using (project_id)
where apps.primary_market_sector = 'lending'
order by project_name, apps.app_id