# Screen the market

> Scan the whole crypto universe for a setup happening right now, the live counterpart to a backtest.

Source: https://docs.texttoquant.com/guides/screener

---

The screener answers a different question from a backtest. Not *"would this have worked?"* but
*"where is this setup happening right now?"* It ranks the tradable crypto universe against a
condition or a strength score, on fresh data. Find it at [/alpha](/alpha).

## What it does

A backtest simulates one strategy over history. The screener does the opposite, it evaluates *many
symbols at once, right now*, and hands you a ranked table. It's a discovery tool: use it to find
candidates, then take the interesting ones to the terminal to backtest properly.

## Scan types

| Scan | What it returns |
| --- | --- |
| Market scan | The tradable universe with per-token strength scores, price, 24h move and volume |
| Market regime (RSPS) | A `RUN` / `REVIEW` / `SKIP` verdict per timeframe. RSPS = Relative Strength Pairwise Scores |
| Token stats | Forward-outcome base rates for a signal condition on a token + timeframe |
| Sectors | Crypto sector performance |
| Dominance matrix | Pairwise dominance across the top tokens |
| Custom benchmark | Correlation and beta of the universe vs a benchmark you choose |
| Token multi-TF | One token's recent OHLCV plus its screener rows across timeframes |
| Perfect Token Profiler | A deeper async profile of a single token |

## Run your first scan

<Steps>
  <Step n={1} title="Open the screener">
    Go to [/alpha](/alpha). The core scans need no login; alerts and the heavier scans are plan-gated.
  </Step>
  <Step n={2} title="Pick a scan and set filters">
    Choose a scan type, a timeframe, and any condition or universe filter.
  </Step>
  <Step n={3} title="Read the ranked table">
    Rows are ranked by strength/score. Each row links out to a chart and to the terminal.
  </Step>
  <Step n={4} title="Save it">
    Save a filter you'll reuse as a **saved scan**, so you can re-run it in one click later.
  </Step>
</Steps>

## Scan alerts & notifications

Turn a scan into a standing alert: get pinged when it starts matching, instead of checking manually.

- Create an alert from a scan; manage them in the screener.
- Delivery goes to **Telegram or email**, link a channel under your account first (the API exposes
  `GET /v1/me/notification-channels` to check which will deliver).
- Alerts are a **paid** feature.

<Callout variant="info" title="Screener vs backtest">
  A screener hit is not a backtested edge, it's a live signal. Confirm it by backtesting the setup
  in the [terminal](/terminal) before you act on it.
</Callout>

Over an AI client, the same scans are available as tools on the [MCP server](/docs/api/mcp), and over
HTTP under `/v1/screener/*`; see the [endpoint reference](/docs/api/endpoints). Plans and limits are
on the [pricing page](/pricing).
