Protocol indexes
An index page is the catalog for one protocol: the tokens, names, or
collections that exist under it, with whatever figures that protocol publishes.
Its address is /index/<protocol>.
Not every protocol has one. The in-app coverage page marks the rows that do, and a row with no index shows only a market link.
What an index shows
Section titled “What an index shows”- The protocol’s assets, in a sortable, searchable table.
- Supply, holder counts, and mint progress where the protocol publishes them. Where it does not, the column is absent rather than filled with zeroes.
- A read source, on the protocols whose data your browser fetches directly.
Each index page loads only the protocol you opened. The others load when you switch, so opening one index does not download the code for all of them.
The Pending column
Section titled “The Pending column”Where a protocol’s index also reads the mempool, its table carries a Pending column with the number of unconfirmed mints per token. Alkanes has one today.
A protocol whose source cannot answer that question shows no Pending column at all, rather than a column of zeroes. This is the unmeasured-figures rule applied to a whole column: an absent column means the question was not answerable, and a zero in a present column means the answer was zero.
Three protocols your browser reads directly
Section titled “Three protocols your browser reads directly”TAP, DMT, and UNAT are a step further out than everything else. Their deployments, mint progress, and holder counts are fetched by your own browser from a host Universe does not operate. They do not pass through a Universe index at all, so their availability and freshness are that host’s.
Those three rows name their read source on the coverage page, and the same
sentence appears again on /index/tap, /index/dmt, and /index/unat beside
the numbers it applies to.
Everything else is read through the Core API, which may in turn read an
external provider for a given protocol.
/indexer-health names the source it used for each
one.
Supply figures and duplicate rows
Section titled “Supply figures and duplicate rows”An index does not trust a first page to be a complete count. Bitmap supply, for example, comes from the authoritative index status unless a complete first page proves an exact unique total, so duplicate history rows cannot inflate a collection grid or its count.
Filters, totals, and search cover the whole index
Section titled “Filters, totals, and search cover the whole index”Where an index offers a status filter, a search box, or summary cards, they are answered by the index itself and not by the rows that happen to be on screen. The OP-20 index works this way: choosing Mintable asks for every mintable deployment and returns to page one, the deployment counts above the table describe everything matching your search rather than the current page, and searching a holder finds them wherever they sit in the ranking.
Searching a ticker matches the characters you typed. op_return finds the token
called op_return, not every ticker with something between op and return.
An asset whose supply the ledger does not record is shown as unknown. It is counted separately from mintable and minted out, because an unreadable supply is a gap in the data rather than an invitation to mint.
Holder counts are the addresses that actually hold a positive balance. An address that has spent everything is not counted as a holder, and a holder percentage always states the supply it is a percentage of.
Freshness is the block it read, not the moment you loaded it
Section titled “Freshness is the block it read, not the moment you loaded it”Where an index knows how far its source has processed, it shows that block height. Reloading a page does not make old data new, so the figure you see is the chain position behind the numbers, not the time of your request.
When an index cannot be read
Section titled “When an index cannot be read”The market, token pages, holder rankings, and portfolio balances for that protocol all report the data as unavailable and offer a retry. They never substitute sample rows and never show an unreadable balance as zero, so an outage stays distinguishable from a genuinely empty market or wallet.