Terminal

Every other terminal you have used (Photon, BullX, GeckoTerminal, Birdeye) shows you everything. Millions of tokens, every new pool, every micro-cap launch. The burden is on you to find the signal in the noise.

The Prism Terminal only shows tokens launched through the pons launchpad that the engine has already scored and surfaced. By the time a row reaches the feed it has passed through honeypot and wash-flow checks, a dev and holder concentration check, a liquidity floor, momentum and whale-flow scoring, mcap golden-band filtering, and a Claude-powered explanation pass. What you are looking at is the output of the filter, not the raw firehose.

That changes the workflow. Instead of scanning 500 new launches an hour, you read the 18 rows in each column knowing every single one already cleared the bar. The filters at the top let you tighten further (risk band, mcap band, liquidity floor), but you are filtering a pre-filtered set. There is no "all tokens" mode here on purpose.

The Terminal shows a single onchain view: launchpad signals from Robinhood Chain, laid out in three columns with up to 18 rows each. A Market Pulse strip sits above the columns with the live call count for the last hour, a heat state (Active, Steady, or Quiet), tokens per hour, and the daily peak window, which tends to land in the US afternoon, roughly 19:00 to 22:00 UTC.

• New Last 60 minutes, newest first. The freshest stuff still inside the entry window. Rows with a vertical accent stripe are under 1h old.
• Hot Score 60+, last 12 hours, ranked by score. The highest-conviction signals the engine fired today.
• Running Calls currently green from the cheapest entry across all calls, ranked by peak gain within the last 24 hours. This is where you find the tokens that are working right now.

The filter bar sits above the columns. Changes buffer locally until you press Apply, so you can stage several tweaks at once without the page refetching after every keystroke.

• Chains Robinhood Chain. The terminal is scoped to Robinhood Chain.
• Risk LOW, MEDIUM, HIGH. Multi-select. Most early memecoin signals are HIGH; tighten to LOW/MEDIUM if you want a curated view.
• Min score Numeric. Cuts the bottom of the feed. Sensible defaults: 60 for "only the good stuff", 0 to see everything.
• Min / max mcap In USD. Useful for hunting a specific mcap band (eg 300k to 700k).
• Min liquidity In USD. Cuts thin pools that are likely to dump.

The counter in the top right shows how many signals remain after filters, in the current view and across the full feed.

Every selection writes to the query string, so a filtered view is bookmarkable and shareable.

• /terminal?risk=low,medium&min_score=60 Curated view, skip the gamble plays.
• /terminal?min_mcap=300000&max_mcap=700000 A specific mcap band on Robinhood Chain.
• /terminal?min_liq=100000&min_score=65 Deep-liquidity Robinhood Chain picks with strong conviction. The safest end of the feed.

Each row is one signal. Layout, left to right:

• Token logo Pulled from on-chain token metadata. Generated identicon fallback when we have nothing on file.
• Chain badge + ticker The Robinhood Chain badge. Ticker links to the token detail page.
• Risk badge LOW / MED / HIGH.
• Score 0-100. Color tracks the band: green at 80+, accent at 60+, dim below 40.
• Time ago + mcap at call The mcap shown is from the snapshot taken at the moment the signal fired, not now.
• Now and peak gain "now" is the live gain from the cheapest entry across all calls. "pk" is the all-time high-water mark since the first call.
• TRADE button Opens a popover with quick-buy links for the token on Robinhood Chain. The popover handles its own clicks; the rest of the row navigates to the token page.

Click anywhere on a row except the TRADE button to open /token/<address>?chain=<chain>. Hovering also prefetches the token page in the background so the click feels instant. Keyboard users can tab to a row and press Enter or Space.

The feed is server-rendered on every navigation, but the underlying engine call is cached on the backend with a short TTL. Token rows that have not changed in the last 30 seconds will come back from cache instantly. Newly fired signals appear on the next navigation or page refresh.