Firecrawl launches /monitor for whole-web tracking across API, CLI, and MCP

• Firecrawl expanded /monitor from page or site watching to a web-wide search product that can ping a user or an agent when something new appears, according to firecrawl's launch post.
• The launch examples are unusually concrete: firecrawl's regulatory example covers FDA approvals, clinical trials, and court filings, while firecrawl's competitor example watches for new products, fundraising, and hiring ramps.
• firecrawl's news example positions the feature for breaking articles, M&A filings, and company announcements, which makes /monitor look closer to persistent search than a simple webpage diff.
• Availability shipped on day one across the firecrawl availability post, which lists the API, Playground, CLI, and Firecrawl MCP.

You can jump from the launch thread to regulatory tracking, competitor monitoring, and breaking-news alerts, then straight into the product page for the surfaces Firecrawl exposed on day one.

The core change is scope. Firecrawl says /monitor used to work for a single page or website, and now the same mechanism can watch the entire web.

That shifts the feature from change detection into always-on retrieval. Firecrawl's own wording, "an always-on search," is the important bit in firecrawl's launch post, because the output is meant to trigger a person or an agent when new information crosses the query.

The launch thread breaks the first use cases into three buckets:

• Regulatory and legal changes: FDA approvals, clinical trial postings, court filings, per firecrawl's regulatory example.
• Competitor changes: new products, fundraising, hiring ramps, per firecrawl's competitor example.
• News flow: new articles, M&A filings, and announcements, per firecrawl's breaking-news example.

Those examples are broader than site monitoring. They imply query-based discovery across many sources, then alerting when a matching document or event appears.

Firecrawl shipped /monitor across four entry points on day one:

• API
• Playground
• CLI
• Firecrawl MCP

That last item is the most agent-native detail in firecrawl's availability post. Shipping the monitor feature into MCP means it is exposed directly inside tool-using workflows, not just through a dashboard or raw API call.