> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xhuntr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How XHuntr works

> Baselines, polling, and why the first snapshot matters.

XHuntr does not read your wallet, your DMs, or anything private. It reads public X data — the same communities anyone could open in a browser — and watches them continuously so you do not have to.

## The baseline

When you add an account, XHuntr records every community that account is **currently** in. That record is the baseline.

From then on, you are alerted on the **difference** between the baseline and what the account looks like now.

<Warning>
  This is why you do not get a flood of alerts the moment you add someone. Their existing communities are the starting point, not news. The first real alert arrives the next time they actually move.
</Warning>

```mermaid theme={null}
flowchart LR
    A["You add @somedev"] --> B["Snapshot every community<br/>they are in right now"]
    B --> C["This is the BASELINE"]
    C --> D["Re-check continuously"]
    D --> E{"Anything different<br/>from the baseline?"}
    E -->|No| D
    E -->|Yes| F["Alert you, then update<br/>the baseline"]
    F --> D
```

## The polling loop

Every tracked account is re-checked on a continuous cycle. When a check finds something the baseline does not have — a new community, a rename, a contract address — that becomes an alert and the baseline updates.

A few consequences worth knowing:

* **Alerts are near-real-time, not instant.** There is a short gap between a KOL clicking create and your phone buzzing.
* **Private accounts limit what is visible.** If an account locks its profile, XHuntr can still monitor it by ID, but community visibility may be reduced.
* **A deleted community produces an alert too.** Things disappearing is signal.

## What happens when you re-add someone

Removing an account and adding it back takes a **fresh** baseline. You will not be re-alerted about everything they did while you were not watching — only about what happens after the new snapshot.

## Returning after a break

If your plan lapsed and you come back later, XHuntr deliberately re-seeds your baselines and stays quiet for a short window before resuming alerts. Without that, every change that happened while you were away would arrive at once as a false flood.

<Card title="Alert types" icon="bell" horizontal href="/alerts/types">
  Now that you know how detection works, learn what each alert actually means.
</Card>