Firecrawl launched /monitor, a feature that pings your AI agent the moment a webpage you care about actually changes — instead of having the agent re-scrape and re-summarise the whole page on every check.
## A goal in English, a webhook on change
You point it at a URL, describe in plain English what to watch — “alert me when the Claude Code docs add new slash commands” — and /monitor configures the URLs, schema, and schedule for you. Cadence can be every 5 minutes, hourly, daily, or a custom cron expression, with the estimated monthly cost shown before you flip it on. Every change fires a signed webhook with custom headers and per-event subscriptions, or arrives by email with the diff in the body.
## The token math
The feature claims up to 90% fewer LLM tokens consumed, because the agent only ingests what actually changed — the diff — instead of re-reading the full page. For an agent watching a dozen pages on a 5-minute cadence, that’s the difference between a viable side process and a runaway bill.
## Why it matters
A surprising amount of “agentic” workflow is just polling: check the docs, the changelog, the competitor page, the support thread. Putting an event-driven layer underneath that — with a one-line English description configuring it — is the kind of plumbing that quietly moves agents from “expensive demo” to “running in the background.”

Leave a comment