> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/investor-intel/alerts.md).

# Alerts

Alerts watch the market so you do not have to. Define what counts as a notable move, and Investor Intel notifies you when it happens, with an AI explanation of why it matters attached to every alert.

### Trigger types

Six trigger types cover the moves that matter:

* **Price move** - an asset moves past your threshold
* **Liquidity drop** - available liquidity falls sharply. Often the earliest hard warning sign on smaller tokens.
* **Volume spike** - trading activity jumps well above normal
* **Wallet activity** - a wallet you track makes a significant move (see [Wallet Watch](/thecontentforge-docs/investor-intel/wallet-watch.md))
* **Narrative heat** - a narrative you follow accelerates (see [Narrative Radar](/thecontentforge-docs/investor-intel/narrative-radar.md))
* **Holder shift** - the holder structure of a token changes notably

### Thresholds and quality badges

Each alert has a threshold you control, so "notable" means what you say it means. Set them wide enough that an alert firing is genuinely worth your attention.

To make that easier, every rule carries a quality badge based on how often it has been firing. A rule that has been well behaved shows a clean quality badge; one that fires too often earns a **Noisy** badge so you can spot it at a glance. Noisy rules come with a suggested threshold you can apply in one click, tuned to cut the chatter without silencing the moves that matter.

### Cooldowns

Each rule has its own cooldown, so a single ongoing move does not fire the same alert over and over. Choose 6, 12, 24, or 48 hours per rule. Once a rule fires, it stays quiet for the cooldown window before it can fire again, which keeps a choppy market from flooding your history with near-duplicates.

### "Why it matters" explanations

Every fired alert includes an AI explanation: what happened, the context around it, and why it might matter. You get understanding with the notification, not just a number that forces you to go digging.

Alongside the explanation, each fired alert carries two plain lines drawn straight from the data behind the trigger, with no waiting on any AI: a **why this fired now** line stating exactly what crossed your threshold, and a **what would confirm or weaken this** line pointing to the signals that would strengthen or undercut it. A signal-direction badge marks whether the move reads as bullish, bearish, or neutral, so you can gauge each alert in a glance before reading further.

### Digest cards

When several related rules fire together on the same asset or narrative, Investor Intel groups them into a single digest card instead of a stream of separate alerts. One card, the full picture, less noise, so a token making a coordinated move reaches you as one clear story rather than five pings.

### Event history

Fired alerts are kept in a history, so you can review what triggered, when, and what the explanation was at the time. Useful for checking how often a rule fires before deciding to keep, retune, or delete it.

### How to use it

1. Create alerts for your watchlist core: price moves you would act on researching, liquidity drops on anything small-cap
2. Add wallet activity alerts for the addresses where timing matters
3. Add narrative heat alerts on followed narratives you want to catch early
4. Review the event history occasionally and retune noisy rules

### Tips

* An alert that fires daily is a setting, not a signal. Raise the threshold.
* Liquidity drop alerts on small tokens are the closest thing to a smoke detector this market has
* An alert tells you something happened and why it might matter. Whether to do anything about it remains your decision.

### Limits

Active alerts depend on your plan, from 3 on trial up to 200 on Elite. Event history is preserved either way. See [Pricing](/thecontentforge-docs/reference/pricing.md).

### Related

* [My Watchlist](/thecontentforge-docs/investor-intel/watchlist.md) - the natural source of alert targets
* [Wallet Watch](/thecontentforge-docs/investor-intel/wallet-watch.md) - the wallet activity trigger
* [Narrative Radar](/thecontentforge-docs/investor-intel/narrative-radar.md) - the narrative heat trigger


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://thecontentforge.gitbook.io/thecontentforge-docs/investor-intel/alerts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
