# Alerts & lifecycle

Every scanner alert CLAUDIA publishes isn't just a ping — it's tracked through its whole life so you can see whether the idea actually worked. An alert starts as **Fired**, becomes **Peaked** if it runs up, goes **Cooling** when momentum reverses, and ends in **Closed** when the move is done. You see the current state in the app and on notifications; nothing is hidden.

## What the states mean

**Fired** — a high-conviction signal just went out. This is the entry moment.

**Peaked** — the call actually worked: the price ran up enough to count as a real move. Orange glow in the UI.

**Cooling** — the alert is no longer the fresh opportunity it was. Either momentum stalled after the peak, or it reversed without ever peaking. Price pings stop at this point so you're not spammed.

**Closed** — the alert's life is over. It closed either because a final take-profit level hit, because a stop-loss level hit, or because it aged out after 72 hours.

The progression only goes forward. An alert never un-closes or un-peaks.

## How you get notified

| State                          | How you hear about it                                                 |
| ------------------------------ | --------------------------------------------------------------------- |
| Fired                          | In-app, Telegram, XMTP                                                |
| Peaked                         | In-app, Telegram (celebratory)                                        |
| Cooling                        | In-app, Telegram (cautionary) — last price-ping you'll get            |
| Closed (final take-profit hit) | In-app, Telegram, XMTP                                                |
| Closed (stop-loss hit)         | In-app, Telegram, XMTP — we tell you honestly when a call didn't work |
| Closed (aged out)              | In-app only, silent                                                   |

## How often

One active alert per ticker at a time. Once an alert closes on a ticker, there's a short cooling-off window before a new one can fire on the same ticker. This keeps you from getting repeatedly pinged about the same token when the scanner keeps re-flagging it.

## What this costs

Reading your active alerts and their history is free. Alerts are an output of the scanner, so you only pay for the scanner itself if you manually refresh (3 credits). Automatic scans are free.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.claudia.wtf/using-the-platform/alerts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.