Skip to main content
A monitor watches a URL on a schedule and notifies you when it genuinely changes. Use it for recurring checks, a pricing page, a status page, a listing; not for a one-off comparison, that is just two scrapes. The rate is 1 credit per check, whether or not the page changed, so the schedule sets the floor: an hourly monitor is about 720 credits a month. A monitor created with judge: true runs a model over each change it finds, and also bills that model’s usage in credits. See pricing.

Notify targets

Three, and only for a monitor: Discord, Slack, or a bare webhook URL.
Monitor notifications are sent once. They are not retried. If your endpoint is down when a change fires, that notification is gone. monitors.list shows only when each monitor last checked and what it found (lastCheckedAt, lastStatus), not the diff, and there is no call that reads past checks, so keep your endpoint up. This is different from an agent run’s webhook, which does retry, see agent monitoring for the contrast.

Agents

Agent-run webhooks are a different mechanism, and unlike a monitor’s, they do retry: up to 8 attempts over about 3 hours 40 minutes.