Skip to content

Set up monitoring and drift alerts

Schedule recurring checks and get emailed when a passing check starts failing.

An audit is a snapshot. Sites change, and the usual way agent readiness degrades is that somebody ships a redesign and nobody re-checks. Monitoring runs a Quick check on a schedule and emails you when something that used to pass stops passing.

Adding a site

  1. Open Monitoring in the app.
  2. Under Start monitoring, pick a site from your portfolio. If it is not there yet, add it in the portfolio first.
  3. Choose Whole site or Single page. A single page watch also asks for the path, for example /pricing.
  4. Pick a cadence: daily, weekly or monthly. Cadence is per entry, so a checkout page can be watched daily while a brochure site is watched monthly.

Whole site or a single page

A whole-site watch checks the homepage plus every site-wide signal: agent files such as llms.txt and AGENTS.md, commerce manifests, and whether an agent can reach your key pages.

A single-page watch checks only that URL, and only the things that can differ page to page: content structure, performance, the accessibility tree, security headers, and any WebMCP tools the page registers. Site-wide files are left to the whole-site watch, so you do not get the same drift alert twice.

How many sites and pages you can monitor depends on your plan. Each entry uses one slot, so watching a site and two of its key pages uses three. Your current usage and limit are shown on the Monitoring page.

Drift alerts

When a scheduled check finds that a previously passing check now fails or warns, that is drift, and it triggers an email. We deliberately do not email you a full report every time nothing has changed.

Recent drift alerts are listed on the Monitoring page, so you can see what changed and when even if the email was missed.

Full audits on a schedule

A subscription also includes a monthly pool of Full audits shared across your workspace, so behavioural coverage keeps pace with the scheduled Quick checks rather than going stale.

Pausing a site keeps its history and stops the schedule. You do not need to delete a site to stop checking it.

Still stuck? The API reference covers the developer side, and support answers within one working day.