Monitoring API, told only what changed

You create a monitor with targets, fixed URLs or a section to re-crawl, a schedule and optionally a goal. The first check records a baseline. Every check after it fetches each page again, marks it same, new, changed, removed or error, attaches a diff, and posts the changes that matter to your webhook.

As often as every 5 minutes, or as rarely as monthly. Write schedules as phrases such as "every weekday at 9am" or as five-field cron, in any IANA timezone; they follow daylight-saving changes.

Leave page furniture out with exclude_selectors, track specific fields with the json mode, or add a goal. With a goal, each change is judged against it, and changes ruled not meaningful are recorded but send no webhook.

One credit per page checked, so the 75,000-credit Pro plan covers 75,000 page checks a month, and Starter 5,000. Creating and managing monitors is free. Pages tracked as JSON cost 4 a check, and each change judged against your goal adds 1. Failed pages and skipped checks are never charged. The free plan includes 1,000 credits every month, 1,000 page checks, with no card required.

Up to 50 monitors per API key, 50 targets per monitor, 100 URLs per scrape target and 500 pages per check, with check history kept for 30 days by default and up to 365.

Yes. Over MCP, prefetch_create_monitor, prefetch_run_monitor and prefetch_get_monitor_check let an agent set up a watch and read back what changed, billed the same way as the REST API.