Networks and coverage
| Chain | Canonical ingestion | Telegram analysis | Ordinary push alerts | Lifecycle feeds | Agent handlers |
|---|---|---|---|---|---|
| Base | Live | Live | Live | Migration | Deployed |
| Robinhood | Live | Live | Live | Pons Graduation, Migration | Deployed |
| Ethereum | Tracked V4 markets | Live | Not admitted | None public | Deployed |
“Deployed” means the route handler is running. Public access uses x402; the data chain and payment network are independent.
Boundaries that matter
- Chain registration, ingestion, evaluation, API admission, and Telegram delivery are separate controls.
- Ethereum data and command support do not imply Ethereum alert evaluation.
- The public recent-alerts API is a subset of the Telegram product.
- A launch source can be attributed without being judged safe.
- Wallet quality is pooled across verified indexed EVM history; token and market evidence remains chain-scoped.
Public API alert types
strong_launch, dormant_buy, strong_volume, and second_life are the only
types returned by GET /alerts/recent. Telegram also carries Sniper Volume and
canonical lifecycle feeds.