Firecrawl Monitor: Let AI Watch the Web for You
You check the same five websites every morning. Competitor pricing, job boards, documentation updates, industry news — rinse and repeat. It eats 30 minutes before you even start working, and you still miss things. What if an AI agent could watch all of those pages for you and only ping you when something actually matters? That’s exactly what Firecrawl Monitor does.
Why You’re Wasting Time Checking Websites Manually
Here’s the thing about manually refreshing pages: it doesn’t scale. You start with three URLs, then it’s ten, then you’re tab-hoarding and hoping nothing important slipped through. Worse, most of the time nothing has changed — you just wasted a click. Meanwhile, the one time a competitor drops their prices or a dream job posting goes live, you’re in a meeting.
If you check even 5 websites twice a day, that’s over 70 manual refreshes every week — time a machine could handle in seconds. The real cost isn’t just the minutes lost, either. It’s the opportunities you miss because you can’t watch everything at once.
What Is Firecrawl Monitor?
Firecrawl Monitor is a feature from Firecrawl — the web scraping platform that developers already trust — that lets you set up AI-powered web monitoring with a single API call. No servers. No cron jobs. No infrastructure headaches.
Essentially, you tell it which pages to watch and what you care about in plain English. Then Firecrawl scrapes those pages on your schedule, compares each new version against the last snapshot, and uses AI to decide whether the change actually matters to you. If it does, you get a notification via webhook or email. If nothing meaningful changed, you hear nothing.
For instance, the feature launched on May 27, 2026, and it fills a gap that nobody else has quite nailed yet — intelligent web monitoring that understands context, not just pixel differences.
How It Works in 3 Steps
The whole process is simpler than you’d expect:
-
You describe your goal. Tell Firecrawl what you care about in plain English — for example, “alert me when a new AI-related story enters the top 10 on Hacker News.” No regular expressions, no CSS selectors.
-
Firecrawl watches on your schedule. It scrapes your target pages (or crawls entire sites) at intervals you set — every 15 minutes, hourly, daily at 9am, whatever works. Each new version gets compared to the previous snapshot.
-
You get notified when it matters. If the AI judge decides the change is relevant to your goal, you receive a structured notification with a diff showing exactly what changed. If it’s just a layout tweak or a timestamp update, you get nothing. As a result, this approach saves up to 90% on LLM tokens compared to re-processing entire pages every time.
Key Features That Make It Different
Most web monitoring tools do one thing: tell you something changed. Firecrawl Monitor does something more useful — it tells you whether the change matters.
Describe What You Want in Plain English
Instead of writing complex rules about which elements to watch, you just type what you care about. “Alert me when a pricing tier changes” or “let me know when new job postings appear.” The AI handles the interpretation.
AI Judges What Matters
Every detected change goes through an AI evaluation that returns a confidence score and a reason. This filters out noise like ads loading differently, session tokens updating, or minor formatting shifts. Consequently, you only see meaningful changes — which means fewer false alarms and less notification fatigue.
Monitor One Page or an Entire Site
You can watch a single URL or crawl an entire website with up to 50 targets per monitor. For example, you could monitor a competitor’s entire docs site to catch API changes across all their documentation pages.
Set Your Own Schedule
Type schedules in natural language — “every 30 minutes,” “daily at 9am,” “weekly on Mondays.” Firecrawl converts it automatically. The minimum interval is 15 minutes, and schedules are spread across monitors to prevent traffic spikes.
See the Cost Before You Commit
Every monitor creation returns an estimated monthly credit cost upfront. No surprises on your bill.
How to Set Up Firecrawl Monitor in 5 Minutes
Here’s how to create your first monitor right now.
Step 1: Get a Firecrawl API Key
Sign up at firecrawl.dev — the free tier gives you 1,000 credits per month, no credit card required. That’s enough to monitor several URLs on a daily schedule.
Step 2: Create Your First Monitor
Here’s a Python example that monitors Hacker News for AI-related stories:
from firecrawl import Firecrawl
firecrawl = Firecrawl(api_key="fc-YOUR-API-KEY")
monitor = firecrawl.create_monitor(
name="Hacker News AI monitor",
schedule={"text": "every 30 minutes", "timezone": "UTC"},
goal=(
"Alert when a new AI story enters the top 10. "
"Ignore changes to stories that are not about AI."
),
targets=[
{
"type": "scrape",
"urls": ["https://news.ycombinator.com"],
}
],
notification={
"email": {
"enabled": True,
"recipients": ["you@example.com"],
"includeDiffs": True,
}
},
)
print(monitor.id)
Or if you prefer cURL, here’s how to monitor an entire docs site:
curl -s -X POST "https://api.firecrawl.dev/v2/monitor" \
-H "Authorization: Bearer $FIRECRAWL_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Docs change monitor",
"schedule": {"text": "every 2 hours", "timezone": "UTC"},
"goal": "Notify me when docs pages add, remove, or change API behavior",
"targets": [{
"type": "crawl",
"url": "https://example.com/docs",
"crawlOptions": {"limit": 100, "maxDiscoveryDepth": 3}
}],
"webhook": {
"url": "https://your-app.com/webhooks/firecrawl",
"events": ["monitor.page", "monitor.check.completed"]
}
}'
Step 3: Choose Your Notification Channel
Firecrawl supports two notification types. Webhooks send signed payloads to any endpoint — perfect for feeding changes into autonomous AI agents or triggering automations. Email notifications, on the other hand, go to up to 25 recipients with diffs included in the message body.
Step 4: Let It Run
That’s it. Firecrawl handles the rest — scraping, diffing, AI evaluation, and notifications. You’ll only hear when something meaningful happens.
Real-World Use Cases
Here are four ways people are already using Firecrawl Monitor to save time.
Track Competitor Prices Automatically
E-commerce companies monitor competitor pricing pages every hour. With JSON-mode monitoring, you get per-field diffs — so you see exactly which price changed, not just that “something on the page moved.” In the past, this kind of automated competitor monitoring required custom scrapers and databases. Now it’s one API call.
Monitor Job Listings and New Openings
Job seekers and recruiters set up monitors on company career pages with goals like “alert me when a new engineering role is posted.” The AI filters out changes to existing listings (like updated descriptions) and only notifies you about genuinely new postings. Schedule it for “daily at 9am” and you’ll never miss a fresh opportunity.
Keep Your RAG Pipeline Fresh
If you’re building AI applications that rely on up-to-date web knowledge, Firecrawl Monitor’s webhooks can trigger targeted document updates. Instead of re-ingesting entire sites, you only update the pages that actually changed — saving up to 90% on processing tokens and keeping your knowledge base accurate.
Watch Documentation and Changelogs
Developers use crawl monitors to track entire documentation sites. When an API endpoint changes or a new feature gets documented, they get a diff showing exactly what was added, removed, or modified. This is especially valuable for teams building integrations against third-party APIs.
How Much Does Firecrawl Monitor Cost?
Firecrawl uses a credit-based pricing model. Monitoring costs 1 credit per page per check, and the AI judge costs an additional 1 credit per changed page it evaluates. Pages with no changes cost nothing beyond the base scrape credit.
The free tier includes 1,000 credits per month — enough to monitor a handful of URLs on a daily schedule without spending a dime. For example, monitoring 3 URLs once per day uses roughly 90 credits per month (3 URLs × 30 days), leaving plenty of room for other Firecrawl features.
Paid plans (Hobby, Standard, Growth) offer higher credit limits and rate limits for heavier use. The key advantage is the cost preview — you always know what a monitor will cost before activating it.
Alternatives: How Firecrawl Monitor Compares
Cron + BeautifulSoup (the DIY approach) is the old-school way. You write a Python script, schedule it with cron, store snapshots in a database, build your own diff logic, and set up your own notifications. It works, but it takes hours to set up and requires ongoing maintenance. Firecrawl Monitor replaces all of that with a single API call.
Visualping.io takes a different approach — visual screenshot comparison. It’s great for business users who want to see what a page looks like, not what the text says. However, it offers limited API access and no structured data output. Firecrawl, by contrast, gives you both markdown and JSON diffs, plus webhook integrations for programmatic workflows.
changedetection.io is a popular open-source option that supports up to 5,000 URLs with 85+ notification integrations. It’s strong for high-volume monitoring but lacks AI-powered change evaluation — you filter changes manually using CSS selectors and text rules. If you want AI to decide what matters, Firecrawl has the edge.
Overall, for most beginners and developers, Firecrawl Monitor offers the best balance of simplicity, intelligence, and developer-friendly APIs.
Advanced: JSON Change Tracking for Structured Data
If you need more than text diffs, JSON mode lets you extract specific data points from pages:
curl -X POST https://api.firecrawl.dev/v2/monitor \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://competitor.com/pricing",
"schedule": "hourly",
"changeTracking": {
"mode": "json",
"prompt": "Extract the plan names, monthly prices, and features for each tier"
},
"notifyUrl": "https://your-webhook-url.com/notify"
}'
Instead of a raw text diff, you get per-field changes with before and after values for each extracted field. This is perfect for tracking prices, stock levels, job requirements, or any structured data on a page.
You can also use a JSON schema instead of a prompt for more predictable extraction results.
How Much Does Firecrawl Monitor Cost?
Firecrawl uses a credit system. Here’s the breakdown:
- Each page check costs 1 credit
- AI judging adds 1 credit per changed page
- Free plan: 1,000 credits/month
- No per-use option — you upgrade to a monthly subscription for more credits
- Credits don’t roll over (except enterprise plans)
Some practical examples:
| Setup | Checks/Month | Credits/Month | Fits Free Plan? |
|---|---|---|---|
| 1 URL, every 30 min | ~1,440 | ~1,440 | Yes (barely) |
| 1 URL, hourly | ~720 | ~720 | Yes |
| 5 URLs, hourly | ~3,600 | ~3,600 | No (need paid) |
| 1 URL, daily | ~30 | ~30 | Yes (easily) |
The free plan works well for monitoring a few pages on a reasonable schedule. If you need to track dozens of URLs or check every 15 minutes, you’ll need a paid tier.
Firecrawl Monitor vs. Other Monitoring Tools
| Feature | Firecrawl Monitor | Visualping | Distill.io | Google Alerts |
|---|---|---|---|---|
| AI change detection | ✅ | ❌ | ❌ | ❌ |
| Structured data extraction | ✅ (JSON mode) | ❌ | ❌ | ❌ |
| Webhook integrations | ✅ | Limited | ❌ | ❌ |
| Built for AI agents | ✅ | ❌ | ❌ | ❌ |
| Free tier | ✅ (1,000 credits) | ✅ (limited) | ✅ (extension) | ✅ |
| API access | ✅ | ❌ | ❌ | ❌ |
| Crawl entire sites | ✅ | ❌ | ❌ | ❌ |
Google Alerts only tracks search results, not specific page content. Visualping compares screenshots visually but can’t extract structured data. Distill.io is a browser extension with no API.
Firecrawl Monitor is the only option that combines AI-powered relevance filtering with structured data extraction and webhook notifications. It’s built specifically for people who want to do something with their alerts — not just read them.
Scheduling: From Every 15 Minutes to Monthly
The minimum interval between checks is 15 minutes. You can schedule checks using:
- Natural language: “every 30 minutes”, “hourly”, “daily at 9am”, “weekly on Mondays”
- Cron expressions: For precise control, like
0 */2 * * *for every 2 hours
Natural language schedules are automatically spread across time slots by monitor ID. This prevents all your monitors from hitting the same pages at the exact same moment — a nice touch that avoids rate limits and keeps costs predictable.
Frequently Asked Questions
Do I need to know how to code?
Not at all. You can create and manage monitors through the dashboard at firecrawl.dev/app/monitoring/. The API is there if you want deeper control, but it’s not required.
How fast are the alerts?
Firecrawl reports a P95 latency of 3.4 seconds for page scraping. After that, AI judging adds a few more seconds. So from a page changing to you getting a webhook, you’re looking at under 10 seconds in most cases.
Can I monitor sites that require login?
Yes — Firecrawl supports authentication headers. You can pass cookies or tokens with your monitor configuration.
What happens if a page errors out?
Failed requests are not charged. Pages tagged as error don’t cost credits, so you won’t pay for pages that are temporarily down.
Is there an open-source version?
Yes — Firecrawl is open source on GitHub (github.com/firecrawl/firecrawl with 25k+ stars). The open-source version includes monitoring capabilities through Firecrawl Observer.
Final Verdict: Should You Use Firecrawl Monitor?
If you’re tired of manually checking websites — whether it’s competitor prices, job boards, documentation, or any page that matters to your workflow — Firecrawl Monitor is worth trying today. The free tier gives you 1,000 credits per month with no credit card, so there’s zero risk to getting started. Set up your first monitor in five minutes and let AI do the watching for you.