Create a monitor
Choose rules, a window size, a duration and a spend cap, consent to the price, and receive alerts.
This page walks through creating a Watchtower monitor and managing it afterwards. You need an EVM account with ETH on Robinhood Chain in your AGENTEX balance. See Watchtower for what monitors can watch.
Create the monitor#
- Open Monitors and choose Create monitor (or choose Create monitor on the Watchtower agent page).
- Choose a Watchtower: the listed Watchtower, or your own tested Watchtower version. The Pinned Watchtower version is fixed for the life of the monitor.
- Enter a Name and choose the Chain: Ethereum, Base or Robinhood Chain.
- Add Rules · one to eight. Give each rule a different name, and enter full
0xaddresses. Optional amounts are whole numbers in the token's smallest unit. - Set the duration, and open Advanced settings if you need them:
- Duration · hours: up to 720 hours (30 days);
- window size: 1 to 2,000 blocks per window;
- Log cap per window: 1 to 100 events;
- Start block · optional: start from a past block instead of the current one.
- Optionally choose a Follow-up on a match: a research run started automatically when the first rule fires. See below.
- Set the Spend cap. It is the most this monitor can ever charge.
- Choose Review monitor, check the summary under Review before creating, and choose Consent and create monitor.
Nothing is charged at creation. Each window reserves its price from your balance when it starts and settles when it finishes.
Follow-up runs#
A follow-up starts one research run when the first rule matches, so a match arrives with context:
| Follow-up | Available when the first rule is |
|---|---|
| Check the token that moved for proxy or ownership changes | Any rule |
| Check the sender's approvals on that token | Token transfers, Approvals by an owner or Wallet token movements |
Follow-up runs are paid like any other run and count against the monitor's spend cap. A monitor starts at most five follow-up runs.
Alerts and destinations#
Every event appears in the monitor's detail and in your notifications on the Monitors page. To receive events elsewhere, add a destination:
| Destination | What you enter | How it is confirmed |
|---|---|---|
| HTTPS webhook | An HTTPS endpoint | Verify ownership: AGENTEX sends a code to the endpoint and you confirm it. Deliveries are signed so you can check they came from AGENTEX. |
| Telegram | Your bot token and a chat id or @channel | Send code posts a code to the chat; you confirm it. |
| Discord | A Discord webhook URL | Send code posts a code to the channel; you confirm it. |
When you create a monitor you can also add a Test webhook · optional. Its signing secret is shown once, right after creation.
Each destination keeps a Delivery log of attempts. Revoking a destination cancels its pending deliveries.
Manage a monitor#
From a monitor's detail you can:
- Pause and Resume scheduling;
- Stop it permanently;
- see every window with its coverage, events, reads and charge;
- acknowledge notifications.
A monitor ends when its duration runs out, when you stop it, or when the next window would not fit inside the spend cap (the monitor is then exhausted). Its configuration cannot be edited after creation: to change rules or limits, stop it and create a new one.