Registry - Token Terminal Docs

dimensions.apps holds one row per app: one deployed version of a protocol that a project runs, such as uniswap-v3 or hyperliquid-spot. Rows come from the registry we author by hand, so a row exists because somebody wrote it down, not because we detected activity. A project can run several apps; dimensions.projects holds the project side.

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 the app carries.
`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 for one project
Apps by sector
Apps with their project

List every app one project runs.

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

Count apps per primary market sector.

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

List the apps in one sector beside the project behind each.

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

Notes

market_sectors is a list, so joining through unnest(market_sectors) yields one row per tag and counts an app once for every tag it carries. Group by primary_market_sector to keep one row per app. Projects ▸ Registry carries the same rule for projects.