Filtered token directory (PRO+)

Browse tokens by market-cap band, liquidity floor, recent-activity window, primary DEX, authority/safety flags, computed 1h volume, MEV-share ceiling, and MC change. Momentum sorts surface movers (mc_change_5m_desc, mc_change_1h_desc, volume_1h_desc) and a composite trending board. Complements /token/{mint} (single lookup), /tokens/almost-bonded (pre-bond pump.fun), and the KOL-scoped /kol/tokens/{hot,trending}.

Default min_liq is 2000 USD to filter the long tail of phantom-MC tokens from low-liquidity pools. Pass min_liq=0 to opt out.

Default max_mc is 100,000,000,000 USD ($100B) — a sanity ceiling that drops phantom market caps (a genuine ~1e12 token supply trading near $1, or a thin-pool price blow-up). No real tracked memecoin approaches it. Pass a higher explicit max_mc to opt out.

Momentum sorts + filters are DB-native (via the token_prices_trending view): min_volume_1h_usd, max_mev_share_pct, min_liq_mc_ratio, max_liq_mc_ratio, mc_change_1h_min_pct, mc_change_1h_max_pct and the momentum sorts paginate correctly with no over-fetch. The trending sort = recent-volume × positive-momentum composite, recency-bounded to the last 1h, and echoes filters.trending_version: "v1".

Only deployer_tier and launchpad remain post-filters (joined from deployer_tokens, not the view). They are served by a bounded SCAN: candidates are walked in pages until limit matches, the candidates run out, or the scan budget is spent. has_more:false only when the candidates ran out; pagination.scan_truncated:true = the budget ran out first and more matches MAY exist — continue with offset = pagination.next_offset (a RAW candidate offset, not a match count). Offset pages walk a LIVE order (pagination.order_is_live: true): MC and activity move between calls, so rows can shift across pages — treat the screener as a ranking, not a ledger.

LP burn (2026-09-21): lp_burned / lp_burn_status come from LP-custody evidence only (lp_burnt_pct). No Solana writer populates it yet, so lp_burn_status is unknown and lp_burned null for every token, and lp_burned=true|false currently matches nothing. lp_burned is DEPRECATED: true = verified burned/locked, false = verified NOT burned, and a token with unknown LP custody matches neither (false never turns unknown into "unburned"); a request that sends it gets a deprecations entry. The old lp_burned flag was the token-SUPPLY burn — filter that with supply_burn and read it as token_supply_burn_detected.