Introducing /monitor: Notify AI agents when the web changes
Eric CiarlaMay 27, 2026
Agents can easily scrape any web page with Firecrawl. But knowing the moment a page changes — and staying focused on the changes that actually matter — is trickier. Traditionally, this required writing a cron job, standing up snapshot storage, diffing old against new, building a webhook layer with retries, and filtering out the noise (ads, timestamps, session tokens).
Today we're launching Firecrawl /monitor — the whole monitoring stack in one endpoint, only pinging your agent when something meaningful changes.
What is Firecrawl Monitoring?
/monitor runs scheduled checks on pages or entire sites, and notifies your agent when something you care about changes. Simply describe what you want to monitor in plain English, and Firecrawl configures the URLs, logic, and schedule for you.
The output is a structured diff: what was added, what was removed, what changed. Your agent only ingests what changes on a page, skipping unchanged content and noisy diffs — using up to 90% fewer LLM tokens.
How does Firecrawl /monitor keep your agents current?
Know the moment a page changes
Set a cadence (every 5 minutes, hourly, daily, or a custom cron schedule) and Firecrawl checks the page for you. When a change is detected, your agent gets a notification. When nothing has changed, nothing is sent. No polling loops, no wasted checks.
Watch only what matters
You can monitor a single page or an entire site, and track the whole page or drill down to specific fields. You can also edit content filters and scrape behavior manually if you need more precise control.
See exactly what's different
Every notification includes a rich diff (what was added, what was removed, what changed), formatted for easy reading by a human or an agent. Each check also gets a permalink so you can share a specific change with a teammate or hand it directly to an agent for further processing.
Deliver changes straight to your agent
Changes fire as signed webhooks with custom headers and per-event subscriptions. Your agent only wakes for the events it cares about. Email delivery works the same way, with the diff already in the message body.
Know your costs before you commit
See the estimated monthly cost before you turn a monitor on. You know exactly what your chosen schedule will cost before you commit to it.
How the /monitor pipeline works
- Create a monitor for one or more web pages, or an entire site
- Firecrawl scrapes the pages on your schedule and stores a snapshot
- On each check, the new version is diffed against the last stored snapshot
- If something changed, Firecrawl sends a signed webhook or email with the structured diff and a permalink
What you can build with /monitor
| Use case | What it looks like |
|---|---|
| Triggering agents on change | A deep research agent monitoring dozens of sources can generate a fresh summary the moment one of them updates. |
| Keeping RAG pipelines fresh | When a watched page changes, Firecrawl pings your pipeline with the diff so you can refresh just that document instead of rescraping everything. |
| Tracking competitors and markets | Watch competitor pricing pages, product catalogs, or job listings and know within minutes when something shifts: a price drop, a new SKU, a new role. |
| Monitoring sources you rely on | Get updates for new research papers, developer docs, changelogs, financial filings, and government regulations. |
Try it today
Firecrawl Monitoring is live for all Firecrawl users. Create your first monitor from the dashboard or via the API.
