Dataset builders
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.
Request says
"FirecrawlAgent"
Checked against
Nothing published
Live check
No operator check exists for FirecrawlAgent. This still shows what the address really is.
Reference
| User agent | FirecrawlAgentToken only: match on the substring. |
|---|---|
| Operator | Firecrawl |
| Purpose | Dataset builders |
| Respects robots.txt | Honours |
| Verification method | Claim onlyNone 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. |
| 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
Paste one at the root of your domain. Rules are per token.
User-agent: FirecrawlAgent
Disallow: /User-agent: FirecrawlAgent
Allow: /User-agent: FirecrawlAgent
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
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.
Build a file for every crawlerFAQ
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.
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.
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.
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.
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.