Does FirecrawlAgent respect robots.txt?

Yes. The operator documents that FirecrawlAgent reads robots.txt and follows Disallow rules for its own token. Rules take effect on the next fetch of the file, which can be hours or days after you publish them.

How do I block FirecrawlAgent?

Add the FirecrawlAgent token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.

IPScanner

Dataset builders

FirecrawlAgent

Q: How do I verify a request really came from FirecrawlAgent?

You cannot, at least not from the request itself. Firecrawl runs crawls on behalf of its customers, so the traffic belongs to whichever developer called the API rather than to Firecrawl itself. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.

FirecrawlAgent is a bot operated by Firecrawl that crawls pages into a dataset that may be reused or shared with third parties. FirecrawlAgent is a web crawler operated by Firecrawl that extracts web content and converts it into structured data for use in LLM and AI applications. It is documented as honouring robots.txt, but no IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine.

Verify an IP that claimed to be FirecrawlAgent

No operator check exists for FirecrawlAgent, so this will not be able to confirm the name. What it can still tell you is what the address actually is: which network announces it, and whether it is a hosting range, a residential proxy or a Tor exit.

The check needs JavaScript. The evidence it uses is public either way: the operator's own documentation says how a request claiming to be FirecrawlAgent can be verified, and the table below repeats it.

FirecrawlAgent at a glance

Reference data for the FirecrawlAgent crawler
User agent	`FirecrawlAgent` Token only. The operator has not published a full user-agent string, so match on the substring rather than an exact header.
Operator	Firecrawl
Purpose	Dataset builders
Respects robots.txt	Yes, documented
Verification method	None published, user agent only Firecrawl runs crawls on behalf of its customers, so the traffic belongs to whichever developer called the API rather than to Firecrawl itself. https://docs.firecrawl.dev
Crawl pattern	Not published
Robots.txt tokens	`FirecrawlAgent`
Operator documentation	None published

FirecrawlAgent is a web crawler operated by Firecrawl that extracts web content and converts it into structured data for use in LLM and AI applications.

robots.txt

Allow or block FirecrawlAgent

Paste one of these into the robots.txt file at the root of your domain. Rules are per token, so a block on one crawler leaves every other bot untouched.

Block FirecrawlAgent

User-agent: FirecrawlAgent
Disallow: /

Blocks every path for this crawler only.

Allow FirecrawlAgent

User-agent: FirecrawlAgent
Allow: /

Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.

Allow, except the pages you never want quoted

User-agent: FirecrawlAgent
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /search

Edit the Disallow paths to match your own account, checkout and search URLs.

What blocking actually costs you

Blocking FirecrawlAgent keeps your pages out of the datasets it builds from future crawls. It does not remove anything collected earlier, and how each operator uses or shares its data varies, so check their policy.

Block every crawler in the directory at once

Verification

Is that really FirecrawlAgent?

A user-agent header is a string the client chooses. Scrapers copy FirecrawlAgent precisely because site owners allow it. Firecrawl runs crawls on behalf of its customers, so the traffic belongs to whichever developer called the API rather than to Firecrawl itself.

Paste the IP address from your access log below. You will see whether it belongs to a hosting provider, a residential proxy pool or a Tor exit, plus the ASN that announces it, which is what tells you whether the claim holds up.

Datacenter IP detectionNearly every real AI crawler egresses from cloud ranges. A residential IP claiming to be one is the first thing to check.IP reputation checkSee whether the address behind a fake crawler hit has a history of abuse elsewhere.Residential proxy detectionScrapers that get blocked by user agent often come back through residential proxy pools.

Related crawlers

YandexAdditionalYandex · Dataset builders AgentTimesThe Agent Times · Dataset builders aiHitBotaiHit · Dataset builders ApifyBotOperator unknown · Dataset builders ApifyWebsiteContentCrawlerOperator unknown · Dataset builders

Agentscan

Identify crawlers automatically instead of by hand

Agentscan checks a request against published crawler ranges, reverse DNS and hosting data, then returns a verdict your edge can act on. One call per request, no range files to keep up to date.

How Agentscan works API reference Pricing What is my IP

FAQ