Ten checks run against every tokenized stock in the universe — how far its
on-chain price sits from a reference price, how much liquidity stands behind it, whether the
24-hour flow looks like traders or bots, what share of the sampled swaps reverted, how
concentrated the holders are, how strong the issuer's reserve evidence is, how the authority
keys are held, whether trading is paused, whether any top-20 account is frozen, and how far
apart the venues price it. A token's status is the worst check that could be JUDGED.
A check whose inputs are missing is unknown, and an unknown is never
counted as a pass — "we did not measure this" must not read as "this is fine".
Universe built · … mints in the API · newest snapshot …. · new mints
Loading…
Mints this pipeline's universe crawl first saw in the last 14 days — when Jupiter's search first returned the mint to us, which is not necessarily when it was minted. Hover or tab in to stop the strip.
Each tile filters the table below; click it again to clear, and click
a second status to see both. The counts are the API's health facet, which
excludes its OWN filter — so with warning selected the other three still say how
many tokens you would get by switching, rather than collapsing to the one you are on.
Across the tokens that have a worst rule at all — the bar is that
rule's share of them. The API's worst_rule facet, and these filter too.
The panel is every facet the API reports, with the count of tokens
behind each value. Two values inside one facet are OR; two facets are AND, and each
facet's counts exclude its own filter, so a count always says what you would get by
clicking it. A symbol links to that token's card. Premium is the
on-chain price against the reference price for the same underlying share;
spread is the gap between the cheapest and dearest venue pricing it;
gap is the after-hours premium minus the open-session premium — the one
column that is still read from stocks-afterhours.json, because the API's
slim row does not carry it — and exists only for mints with enough trades on both sides
of the session boundary. A dash is a missing measurement, never a zero.
| Token | Issuer | Status | Worst rule | Liquidity | Premium | Venue spread | After-hours gap | Top-1 share | Last trade |
|---|
Only the columns with an arrow are sortable:
the sort runs in Postgres, and /api/tokens accepts a whitelist of
keys rather than any column, so a column it does not sort is not offered here as
one that does.
A snapshot of the universe is frozen every day
(stocks/data/history/<date>/) and consecutive days are diffed. Only
moves worth a line are reported: a pause, a rebase, a pool that halved from real
liquidity, a venue spread crossing 5 %, a health status changing, a frozen account
appearing, a control flag flipping. A field that was not measured on either day
can never produce a change — an initial snapshot may therefore contain many
newly measurable fields without implying that all of them changed on-chain that day.
Hand-picked, dated incidents from the issuer dossiers — each one is
already recorded with its source under stocks/data/issuers/ or in
stocks/findings.md. This is not a feed; it is a reading list of what has
actually happened to these programmes.
One row per Meteora pool, with the facts DexScreener does not report:
which Meteora product the pool is (a single meteora dexId covers DLMM and the
bonding curve), its bin step, its real fee configuration and its 24-hour FEES rather than
just volume. Premium is that pool's own price against the token's
reference price, so a pool quoting away from the venue aggregate shows up.
Failed is the reverted share of the signatures the trade collector
sampled on that pool — a dash means the collector never reached it, not that nothing
failed.
| Token | Pool | Bin step | Fee | Liquidity | 24 h volume | 24 h fees | Premium | Failed / last trade |
|---|