Firecrawl logo

Firecrawl Review: Search, Scrape, Crawl and Monitor the Web

Search, scrape, crawl, parse, monitor, and structure web context for applications and AI agents.

AI, Coding and Development
Visit Firecrawl → Join Discussion
WHATAI LATEST · AUG 16, 2026

Firecrawl Expands Its Free Research Index With 41 Million Life Sciences Papers

The new category gives research agents abstract search, paper identifiers, relevant passages, and citation expansion, but Firecrawl's own recall claims and broad corpus still require independent verification.

By WhatAI Editorial Team ·

Firecrawl has expanded from general web retrieval into a larger piece of scientific-research infrastructure. On August 13, 2026, the company added a Life Sciences category to its Research Index, announcing coverage of more than 41 million papers across drug discovery, clinical trials, biology, and related biomedical literature. Firecrawl also made all current Research Index categories free to query, including the AI and machine-learning collection launched in June.

The current documentation describes the combined index as roughly 43 million paper abstracts. Most of the corpus comes from PubMed, bioRxiv, and medRxiv, with arXiv adding physics, mathematics, computer-science, and other technical research. Agents can search abstracts in natural language, inspect canonical metadata and source identifiers, retrieve passages relevant to a question, and expand from a seed paper to similar papers, citations, or references.

That is a meaningful addition for builders who would otherwise combine several source APIs, parsers, identifier systems, ranking layers, and full-text tools. It is also easy to overstate. A large index is not a completed review, a relevant passage is not an appraisal, and a high recall score from the vendor is not independent evidence that a query found everything that matters. The feature is valuable precisely when it is used as a retrieval layer with documented checks around it.

### A paper index is different from web search

Firecrawl now has two features that can sound like the same thing. The dedicated Research Index searches a corpus of paper abstracts and returns paper records with identifiers, titles, abstracts, scores, and optional ranking signals. Ordinary Firecrawl Search can also be restricted to a research category, but that searches the open web across a limited set of academic websites and returns standard web results.

The distinction matters in an agent workflow. A paper record can be addressed through identifiers such as PMID, PMCID, DOI, or arXiv ID. The agent can pass that identifier into a second request to inspect the paper or retrieve question-relevant passages. It can then expand from strong seeds through similar papers, citers, or references. Ordinary web search is better suited to pages on journal, preprint, or institutional sites, but it does not provide the same paper-specific graph and passage tools.

The safer implementation makes this distinction explicit in code and in the audit log. A user asking for peer-reviewed trials should not silently receive a mixture of ordinary web pages, PubMed records, bioRxiv preprints, and medRxiv preprints under one label. Each result should retain its source ID, publication type, publication or update date, abstract, retrieved passages, and current status. Preprints should be marked as preprints until their publication status is verified.

### The retrieval claim needs context

Firecrawl reports that the Life Sciences category achieved 90 percent recall at 10 on its paper-retrieval evaluation. In plain terms, the company says the system found relevant papers within the first ten results for nine out of ten benchmark cases. That would be useful for agents because a strong first page reduces the number of papers and tokens needed before a relevant source appears.

The figure remains a vendor-run benchmark. The announcement does not establish that the same performance holds across every clinical specialty, rare disease, molecular target, language, study design, publication date, or ambiguous real-world question. Recall at 10 is also different from comprehensive recall. A systematic review may need nearly every eligible study, including older terminology, negative results, regional journals, registry records, corrections, and grey literature.

Teams should reproduce the evaluation on their own question set. Build a gold set of known relevant papers, include easy and difficult queries, test synonyms and identifiers, and measure recall separately for recent work, older work, preprints, reviews, trials, and niche topics. Compare the index with discipline databases and direct source searches. Record both missed papers and irrelevant papers so ranking quality and total retrieval quality are visible.

Firecrawl's June announcement also cited strong performance on arXivQA and an internal benchmark from a customer. Those results are useful product signals, not universal guarantees. The WhatAI view is straightforward: benchmark claims should guide a pilot, not replace one.

### Abstract search and passage reading solve different problems

The Research Index searches roughly 43 million abstracts. Abstracts are efficient for broad discovery, but they compress methods, eligibility rules, subgroup results, uncertainty, adverse events, and limitations. They can emphasize a primary result while omitting details that change whether the finding applies to a specific population or decision.

Firecrawl's passage endpoint helps by retrieving full-text sections relevant to a natural-language question. An agent can ask whether a paper used a particular assay, population, comparator, benchmark, or evaluation method before including it. This is much better than treating an abstract as the complete paper. It still requires verification. The passage may omit surrounding qualifiers, come from a cited discussion of another paper, or fail to expose a table, figure, correction, or supplementary method.

A robust pipeline stores the paper identifier, passage, section or location when available, retrieval query, retrieval date, and source link. A human or a separate verification stage checks the original document around that passage. If the full paper cannot be inspected, the system should say so rather than convert an abstract or isolated excerpt into a strong claim.

The same rule applies to citation expansion. Similarity, co-citation, bibliographic coupling, references, and citers are discovery signals. They can surface a research neighborhood and help an agent find terminology that its first query missed. Citation count and network position are not measures of methodological quality, truth, or applicability. A widely cited paper can be flawed, outdated, or cited because it is controversial.

### Life sciences raises the stakes

Research retrieval in AI and software can lead to a poor implementation or wasted engineering time. Life-science retrieval can influence clinical information, drug discovery, biological models, and public-health decisions. That does not make automated retrieval inappropriate, but it raises the standard for how the results are labelled and reviewed.

The new corpus includes PubMed alongside bioRxiv and medRxiv. Those sources serve different roles. PubMed indexes biomedical literature and includes records with different publication types and statuses. bioRxiv and medRxiv distribute preprints before peer review. An agent should never describe every result as a peer-reviewed paper merely because it came from a scientific index.

Clinical work also needs more than papers. Current guidelines, regulatory notices, trial registries, safety communications, retractions, corrections, and local standards may matter more than a highly ranked article. A high-stakes workflow should search the appropriate primary systems, verify dates and jurisdictions, and involve qualified domain judgment. Firecrawl can improve discovery and evidence routing, but it does not provide medical advice or a complete clinical decision process.

Developers should design the output schema around uncertainty. Useful fields include source namespace, identifier, publication status, peer-review status when verified, date, study design, population, intervention or exposure, comparator, outcome, passage, limitations, correction or retraction status, full-text availability, and verification state. Missing values should remain null. A language model should not infer peer review, trial design, sample size, or effect direction from a title.

### Free endpoints lower the barrier, not the operating cost

Firecrawl says the Research Index paper endpoints are now free across categories. That lowers the direct cost of paper search, inspection, passage retrieval, and related-paper expansion. Unauthenticated requests can get started without an API key, while an account and key provide higher limits. The free status is a current product term and can change, so production systems should monitor the official pricing and documentation.

The complete research system still has costs. An agent may use paid web Search to find guidelines or current announcements, Scrape to collect source pages, Parse to process files, Monitor to track updates, and language models to classify, summarize, compare, and verify evidence. Storage, deduplication, evaluation, human review, and additional database access also remain. Free retrieval should not be confused with a free end-to-end review.

Firecrawl's broader pricing now starts with 1,000 monthly credits at no cost. Standard Scrape, Crawl, Map, and Monitor requests generally cost one credit per page, Search costs two credits per ten results, and browser Interact costs two credits per minute. Advanced formats and modes can add cost. Teams that mix the free paper index with the paid context API should record which endpoint generated each charge and cap retries and recursive exploration.

### A defensible research-agent workflow

Start with a written question and intended use. Define the population, concept, intervention or exposure, comparator, outcome, timeframe, publication types, languages, and sources that matter. Run several Research Index queries using synonyms, technical terms, and known identifiers. Keep the exact queries and dates.

Next, inspect the returned records and verify publication status. Build an evidence table rather than asking the model for a conclusion immediately. Use passage retrieval to test whether each candidate actually contains the method, dataset, population, or result relevant to the question. Expand from the best seeds through references and citers, but preserve why each paper entered the set.

Then search outside the index. Use appropriate bibliographic databases, clinical-trial registries, guideline repositories, regulatory sources, and direct publisher records. Check corrections and retractions. Deduplicate by DOI, PMID, PMCID, arXiv ID, title, and authors rather than relying on a single field. For a formal review, apply a documented protocol, independent screening, critical appraisal, and transparent inclusion and exclusion decisions.

Finally, separate retrieval quality from answer quality. Measure whether the right papers were found, whether the right passages were returned, whether extracted fields match the paper, and whether the final synthesis represents uncertainty and disagreement. A fluent answer can conceal failure at any earlier stage.

Firecrawl's Life Sciences expansion gives developers a useful paper-specific retrieval layer with unusually broad biomedical coverage, source identifiers, passage access, and graph expansion. Making it free increases its practical value for experimentation and open research tooling. The responsible conclusion is narrower than the launch headline: it can help agents find and inspect evidence, but it does not prove completeness, peer review, methodological quality, or clinical applicability. Those judgments still belong in the workflow.

ℹ️

WhatAI Decision Box

Best for:

Developers and AI teams that need one managed layer for search, scraping, crawling, document parsing, change monitoring, structured extraction, and agent-ready web context.

Not for:

Users seeking permission to copy restricted data, a guaranteed complete research database, a no-review factual authority, or visual browser automation without engineering, security, legal, and cost controls.

⇆ Often compared with

Apify Bright Data ScrapingBee Exa Tavily

ℹ️ WhatAI Field Note

  • Choose the smallest endpoint that solves the job. Firecrawl is most economical and reliable when Search, Scrape, Map, Crawl, Parse, Monitor, Interact, and Research Index are used deliberately rather than interchangeably.
  • Compare effective cost per validated record, not the headline page allowance. Rendering, JSON extraction, document pages, search scraping, browser minutes, monitor frequency, failures, validation, and storage determine production cost.

Firecrawl provides one developer platform for live web search, page scraping, site crawling, URL mapping, structured extraction, document parsing, browser interaction, monitoring, and agent-driven research. Its central value is converting complex web and file content into predictable Markdown or JSON that an application or language model can use.

How Firecrawl Works for AI Agents and Data Pipelines

Use Search when the destination URLs are unknown, Scrape for a known page, Map to inventory a domain, Crawl for multi-page extraction, Parse for uploaded documents, Interact for browser actions, Monitor for recurring change detection, and Agent for preview-stage autonomous gathering. The Research Index provides a separate paper-specific API for abstracts, metadata, passages, and related work.

Who Should Choose Firecrawl?

Firecrawl suits developers, AI teams, researchers, and data engineers that want managed extraction instead of maintaining browsers, proxies, parsers, queues, and document cleaners. It is not a permission layer or a guarantee of accurate data. Teams must define lawful sources, respect target controls, defend against prompt injection, validate schemas, monitor credit use, retain source URLs, and review consequential outputs.

About Firecrawl

Firecrawl is a web context platform for developers and AI agents. Its API can search the live web, scrape a known URL, map links, crawl a site, parse documents, interact with browser sessions, monitor pages for changes, or let a preview Agent gather structured information across multiple sources. Results can be returned as clean Markdown, processed or raw HTML, links, images, screenshots, summaries, branding data, or schema-constrained JSON. The managed service handles JavaScript rendering, proxies, caching, rate limits, sitemaps, crawl queues, PDFs, document parsing, and signed webhooks. Developers can use REST, official SDKs, a CLI, an MCP server, a browser playground, and integrations with agent and automation frameworks. The open-source edition can be self-hosted, but the operator owns authentication, upgrades, storage, monitoring, proxies, security, recovery, and any cloud-only capability it needs. Firecrawl also offers Monitoring, a free Research Index for scientific-paper retrieval, a Developer Index, cache-only Lockdown Mode, and Enterprise controls such as zero-data retention, SSO, IP allowlisting, and a support SLA. It is best treated as retrieval infrastructure rather than a guarantee that content is complete, lawful to reuse, current, accurate, or safe. Production systems still need target authorization, robots and terms review, privacy controls, schema validation, source attribution, injection defenses, deduplication, cost limits, and human review for consequential outputs.

Use Cases

Give an AI assistant live web search with clean, cited source contextBuild a retrieval-augmented generation pipeline from a documentation siteImport a public website into a searchable knowledge baseExtract typed product, pricing, location, or listing data into JSONMonitor competitor pricing, release notes, job listings, and product catalogsRefresh only changed documents in a retrieval indexTrack government, regulatory, legal, scientific, and developer sources for updatesCollect public company information for a reviewed enrichment workflowParse PDF, office, EPUB, CSV, and HTML documents into Markdown or JSONDiscover every relevant URL before launching an expensive crawlRun multi-step research that needs search, scraping, and browser interactionSearch scientific papers, inspect metadata, read relevant passages, and follow citationsConnect web retrieval to n8n, agent frameworks, coding assistants, or custom applicationsUse a cache-only mode to stop untrusted agent inputs from making arbitrary outbound requestsSelf-host the open-source stack where infrastructure control justifies the operational workCreate content briefs and market reports grounded in traceable web sources

Key Features

  • Scrape endpoint for turning a known URL into clean data
  • Crawl endpoint for recursive discovery and extraction across a site
  • Map endpoint for quickly discovering URLs on a domain
  • Search endpoint for ranked web results with query-relevant highlights
  • Optional full-page scraping of every search result
  • Monitor endpoint for scheduled page, site, and web-wide change detection
  • Interact endpoint for managed browser sessions and web actions
  • Preview Agent for autonomous multi-source data gathering
  • Research Index for paper search, metadata, passages, and related work
  • Developer Index for code, documentation, issues, and repository context
  • Document parsing for PDF, Word, Excel, PowerPoint, OpenDocument, EPUB, CSV, and HTML
  • PDF text extraction with automatic, fast, and OCR parsing modes
  • JavaScript rendering for dynamic websites
  • Markdown, processed HTML, raw HTML, links, images, summary, and branding formats
  • Schema-constrained JSON extraction using prompts and JSON Schema
  • Screenshots and higher-fidelity browser output
  • Sitemap discovery, recursive traversal, depth limits, path filters, and subdomain controls
  • Polling, WebSocket, and signed-webhook crawl delivery
  • Structured diffs and notification delivery through webhook, email, or Slack
  • Lockdown Mode for cache-only scrape requests without outbound access
  • Playground for testing requests without building an interface
  • REST API and official Python, Node.js, Go, Rust, Java, and Elixir SDKs
  • CLI and MCP access for coding agents and automated workflows
  • Open-source self-hosting with Docker Compose
  • Enterprise zero-data retention, SSO, IP restrictions, rollover, SLA, and support
  • SOC 2 Type II controls for the managed service

Pricing

Free

$0

  • • 1,000 credits each month
  • • Equivalent to 1,000 standard scraped pages
  • • 2 concurrent requests
  • • Low rate limits
  • • No payment card required

Hobby

$16/mo billed yearly

  • • 5,000 credits each month
  • • Equivalent to 5,000 standard scraped pages
  • • 5 concurrent requests
  • • Basic support
  • • Designed for side projects and small tools

Standard

$83/mo billed yearly

  • • 100,000 credits each month
  • • Equivalent to 100,000 standard scraped pages
  • • 50 concurrent requests
  • • Standard support
  • • Recommended self-serve plan

Growth

$333/mo billed yearly

  • • 500,000 credits each month
  • • Equivalent to 500,000 standard scraped pages
  • • 100 concurrent requests
  • • Priority support
  • • Designed for higher-volume data pipelines

Scale

$599/mo billed yearly

  • • 1,000,000 credits each month
  • • Equivalent to 1,000,000 standard scraped pages
  • • 150 concurrent requests
  • • Priority support
  • • $397 per additional 350,000 credits
  • • Credit rollover subject to plan terms

Enterprise

Custom

  • • Custom credits and concurrency
  • • Unlimited-page scope subject to contract
  • • Dedicated support and SLA
  • • Bulk discounts
  • • Zero-data retention
  • • SSO, IP controls, and advanced security

Pricing varies by plan and region — see current pricing.

Plan features change — last updated: 2026-08-16.

Details

Categories: AI, Coding and DevelopmentAgents & AutomationResearch & Knowledge Work
Skill Level: technical
Access Methods: API, browser playground, CLI, MCP, self-hosted

Tags

web scrapingweb crawlingweb search APIdata extractionLLM contextRAG pipelinewebsite monitoringdocument parsingbrowser interactionResearch IndexMCPopen source

Firecrawl Community Discussions

Explore community discussions. Ask and answer questions on Firecrawl to grow and learn together.

jamiemills · Firecrawl AI, Coding and Development

Firecrawl MCP Server is the update that connects it directly to Claude and other LLM workflows

The Firecrawl core features overview covers the Scrape, Search, Map and Crawl capabilities but the Firecrawl Model Context Protocol Server update buried in it is the piece worth pulling out. The MCP Server integration allowing Claude and other LLMs to use Firecrawl's capabilities directly without API wrangling is the developer experience improvement that changes who can integrate web scraping into an AI workflow. A developer building a Claude-powered agent that needs to pull current web data no longer needs to build a custom API integration layer between the two tools. The Scrape capability returning clean Markdown, JSON, HTML or screenshots is the output format variety that matches different downstream use cases. Markdown for LLM ingestion in RAG pipelines. JSON for structured data storage. HTML for cases where the rendering matters. Screenshots for visual verification. The Search returning full content from top search results alongside the standard scraping is what makes… Read full discussion →
♥ 0 💬 2 👁 12 View 2 replies →
joe101 · Firecrawl AI, Coding and Development

Firecrawl's Extract with AI Agent changed how I pull structured data out of websites for my AI pipeline

I had been writing custom scrapers for each new data source I needed. The Extract with AI Agent feature in Firecrawl, covered in the new features video made me stop doing that for a large proportion of my use cases. Natural language prompts to pull structured data from single or multiple pages without writing complex code is what it does. You describe what you want in plain English and the agent navigates the site, finds the relevant information and returns it in the structure you specified. For sites with consistent page structures the accuracy is high enough to be genuinely useful without significant post-processing. The Search feature retrieving clean content from top search results for a given query is the complementary capability that handles research-style data gathering rather than site-specific extraction. The Map feature generating the full URL structure before crawling is the workflow I use to understand a site's… Read full discussion →
♥ 1 💬 3 👁 9 View 3 replies →
blake_walker · Firecrawl AI, Coding and Development

Firecrawl's Interact endpoint unifying agent and browser for complex scraping is the update I had been waiting for

The Interact endpoint introduction covers a three-step scraping workflow that handles the cases previous Firecrawl versions could not. Step one: attempt a standard scrape. Step two: if it fails, use the returned scrapeId to initiate an interaction session using either a natural language prompt through Firecrawl's Agent or custom Playwright code through the Custom Agent. Step three: close the session. The natural language prompt path for interacting with pages requiring login, dynamic content loading or specific user actions is the accessibility layer that makes complex scraping achievable without writing Playwright code for every site. The Custom Agent Playwright path is the precision option for sites with specific interaction requirements that natural language does not handle reliably. The session-based approach with a unique session ID is what makes multi-step interactions maintainable. Each interaction within a session preserves the state of the previous step rather than starting fresh. The combination of natural… Read full discussion →
♥ 1 💬 2 👁 12 View 2 replies →
tyler63 · Firecrawl AI, Coding and Development

Firecrawl is what I use when I need web data inside an AI agent and it has saved me weeks of scraping headaches

If you build AI agents or automation pipelines that need to pull data from the web you know how much time goes into the infrastructure before you even get to the interesting part. Proxies, anti-bot detection, parsing inconsistent HTML, cleaning the output. Firecrawl handles all of that and returns data that is already clean and ready for an LLM. The core functionality comes in a few modes. Scrape converts a single web page into clean markdown with one API call. Crawl automatically works through an entire website. Map instantly generates a list of all URLs on a domain, which is useful before you commit to a full crawl. Search combines Google results with full content extraction so you are not just getting links, you are getting the actual content. The Agent mode is the more advanced one. You describe the data you want in plain language and it figures out… Read full discussion →
♥ 2 💬 4 👁 6 View 4 replies →
jane_d · Firecrawl AI, Coding and Development

Firecrawl feeds documentation sites directly into my RAG pipelines and it replaced three steps in my workflow

Specific use case post for people building RAG applications or AI agents that need current documentation as a knowledge source. The problem I kept running into: documentation changes. A library updates, an API gets new endpoints, a service changes its authentication flow. If your RAG system was seeded from a documentation snapshot taken three months ago it is working from stale information and the AI will confidently generate code or instructions based on what no longer exists. Firecrawl's Intelligent Crawling follows all internal links on a documentation site recursively and scrapes the full content, outputting clean Markdown formatted for LLM ingestion. The MCP Server Integration connects directly to AI IDEs like Cursor so the AI can read documentation in real time while you code rather than working from training data that has a cutoff date. The Structured Data Extraction is the other feature I use regularly. You define a JSON… Read full discussion →
♥ 0 💬 4 👁 6 View 4 replies →
View All Firecrawl Discussions
Gallery

Firecrawl Showcase

5 items
Firecrawl MCP Server is the update that connects it directly to Claude and other LLM workflows

Firecrawl MCP Server is the update that connects it directly to Claude and other LLM workflows

jamiemills

Firecrawl's Extract with AI Agent changed how I pull structured data out of websites for my AI pipeline

Firecrawl's Extract with AI Agent changed how I pull structured data out of websites for my AI pipeline

joe101

Firecrawl's Interact endpoint unifying agent and browser for complex scraping is the update I had been waiting for

Firecrawl's Interact endpoint unifying agent and browser for complex scraping is the update I had been waiting for

blake_walker

Firecrawl is what I use when I need web data inside an AI agent and it has saved me weeks of scraping headaches

Firecrawl is what I use when I need web data inside an AI agent and it has saved me weeks of scraping headaches

tyler63

Firecrawl feeds documentation sites directly into my RAG pipelines and it replaced three steps in my workflow

Firecrawl feeds documentation sites directly into my RAG pipelines and it replaced three steps in my workflow

jane_d

👍 👎

Firecrawl Pros & Cons

Unified retrieval

👍 Pro

One platform covers search, scraping, crawling, mapping, parsing, interaction, monitoring, and research retrieval.

👎 Con

Teams still need endpoint selection, validation, storage, source governance, and downstream model controls.

LLM-ready output

👍 Pro

Markdown, highlights, and schema-constrained JSON reduce custom cleaning before model use.

👎 Con

Clean formatting can hide missing content, extraction errors, stale pages, or unsupported schema values.

Dynamic websites

👍 Pro

Managed rendering, proxies, caching, and browser tools handle many sites that defeat simple HTTP scrapers.

👎 Con

Authentication, anti-bot defenses, unstable interfaces, and complex actions can still fail or require configuration.

Monitoring

👍 Pro

Structured diffs and event delivery let agents process changes instead of repeatedly ingesting whole pages.

👎 Con

Frequent schedules, false changes, removed pages, and large sites can create noise and ongoing credit cost.

Research Index

👍 Pro

Free paper endpoints combine abstract search, metadata, passages, and related-paper expansion.

👎 Con

Coverage and vendor benchmarks do not replace database searches, publication checks, appraisal, or reading the paper.

Open source

👍 Pro

Self-hosting provides source and infrastructure control for teams prepared to operate the stack.

👎 Con

The basic Compose guide lacks production authentication, TLS, durability, high availability, and some cloud features.

Predictable base credits

👍 Pro

Standard page operations have simple credit units and failed requests are not charged according to Firecrawl.

👎 Con

Advanced formats, AI extraction, browser minutes, monitors, and large crawls can make the effective cost less obvious.

Enterprise controls

👍 Pro

Enterprise offers SOC 2 Type II controls, zero retention, SSO, IP restrictions, rollover, and an SLA.

👎 Con

The strongest privacy and administration controls require a custom contract and do not remove customer obligations.

How to Get Results with Firecrawl: Step-by-Step Workflow

  1. Define the lawful source set

    List approved domains, paths, document types, intended use, target terms, robots rules, attribution, retention, personal-data exclusions, and who may access the collected material.

  2. Choose the narrow endpoint

    Use Search for unknown sources, Scrape for one known page, Map for site inventory, Crawl for multiple linked pages, Parse for files, Monitor for changes, and Interact only when retrieval is insufficient.

  3. Estimate credits and scale

    Calculate pages, search results, advanced formats, browser minutes, monitor frequency, concurrency, retries, and growth. Set request, daily, and monthly limits before using a production key.

  4. Map before crawling

    Inventory the site, remove irrelevant paths, duplicates, language mirrors, calendars, faceted navigation, authentication routes, private areas, and external domains, then approve the final URL scope.

  5. Define the output contract

    Choose Markdown or a strict JSON Schema, require canonical URL and observed timestamp, preserve supporting text, use null for missing data, and define validation and rejection rules.

  6. Secure the request path

    Keep API keys server-side, allowlist targets, block private and metadata networks, inspect redirects, limit headers and actions, separate scraped instructions from system prompts, and verify webhook signatures.

  7. Run a representative pilot

    Test static, JavaScript, PDF, image-heavy, paginated, redirected, blocked, missing, changed, duplicate, and malicious pages. Record completeness, failures, latency, credit use, and parsing accuracy.

  8. Validate and deduplicate

    Check schema types, required fields, source support, canonical URLs, content hashes, timestamps, publication status, and extraction confidence before storage or model use.

  9. Add monitored refresh

    Monitor only sources that need freshness, set a justified cadence, filter cosmetic noise, deliver signed idempotent events, and update only changed documents instead of recrawling everything.

  10. Operate and audit

    Track success rate, missing fields, drift, duplicates, target complaints, robots changes, injection attempts, webhook failures, storage growth, credit use, source deletions, and access. Reapprove scope regularly.

Firecrawl Gotchas and Limits to Know Before You Start

  • Firecrawl is retrieval infrastructure, not legal permission to collect, store, republish, train on, or commercialize target content.
  • Review target terms, robots directives, copyright, database rights, privacy laws, contractual restrictions, and rate limits before collection.
  • The Crawl endpoint respects FirecrawlAgent robots rules, but users should not assume every endpoint or target policy is equivalent.
  • Never let untrusted users provide arbitrary URLs without blocking private networks, metadata endpoints, internal hosts, credential-bearing URLs, and unsafe redirects.
  • Scraped pages can contain prompt injection intended to manipulate an agent or expose secrets through tools and outbound requests.
  • Treat retrieved content as untrusted data, separate it from system instructions, and restrict downstream tools and credentials.
  • Markdown or JSON that parses successfully can still omit hidden tabs, pagination, lazy-loaded content, images, tables, or gated sections.
  • JavaScript rendering improves coverage but does not guarantee success against authentication, CAPTCHAs, anti-bot controls, or unusual single-page applications.
  • Schema extraction can hallucinate, normalize incorrectly, or fill a field from unrelated page content.
  • Preserve source URLs, observed timestamps, supporting passages, and null values so every extracted record can be audited.
  • Map results should be reviewed before Crawl because an unexpected site graph can consume far more pages than planned.
  • Set page limits, depth, path rules, domain rules, concurrency, timeout, and budget before launching a crawl.
  • Crawl results can contain duplicates, canonical variants, faceted pages, calendar traps, language mirrors, and session-specific URLs.
  • A successful request is billed according to the endpoint and enabled features; advanced JSON, Enhanced Mode, and other options can cost extra credits.
  • Search costs 2 credits per 10 results before optional scraping and advanced output costs are considered.
  • Interact costs 2 credits per browser minute, so stuck navigation and open sessions need strict time limits.
  • Monitor costs 1 credit per page per check, making short intervals across large sites expensive.
  • Self-serve credits do not roll over; Scale and Enterprise rollover is subject to their terms.
  • The public pricing page shows Hobby, Standard, Growth, and Scale monthly equivalents with annual billing.
  • Agent is in preview with 5 free daily runs and dynamic pricing, so limits and behavior can change.
  • Research Index paper endpoints are currently free, but unauthenticated and authenticated rate limits can differ and the offer can change.
  • The Research Index searches roughly 43 million abstracts, not every scholarly paper or every discipline equally.
  • The research corpus includes PubMed, bioRxiv, medRxiv, and arXiv, so results can include preprints that are not peer reviewed.
  • Firecrawl's 90% recall at 10 claim for life-science retrieval is a vendor evaluation and should not be treated as independent proof of comprehensive recall.
  • Passage retrieval helps verify a paper, but it does not replace reading methods, results, limitations, corrections, and publication status.
  • The Research Index is different from ordinary web Search with the research category; the latter searches a small set of academic websites.
  • Lockdown Mode works only with Scrape and returns a cache-miss error rather than making a live request.
  • Lockdown content can be up to two years old and is unsuitable for live prices, breaking news, current availability, or other freshness-sensitive facts.
  • Lockdown ignores conflicting live options such as actions, wait settings, custom headers, proxy settings, and change tracking.
  • Monitoring can report cosmetic or noisy changes unless goals, filters, canonicalization, and diff rules are tested.
  • Webhook consumers must verify signatures, deduplicate events, handle retries, and make downstream actions idempotent.
  • Standard cloud handling and Enterprise zero-data retention are different service configurations and should not be conflated.
  • The Enterprise page states that scraped content is processed and immediately deleted under its zero-retention configuration.
  • Self-hosting does not make scraping offline; target requests and optional proxy, AI, or parser providers create outbound data flows.
  • The self-host quickstart disables API authentication and lacks durable storage, TLS, high availability, and every cloud feature.
  • Self-hosted operators own secrets, patching, security, storage, backups, queues, monitoring, recovery, and incident response.
  • Firecrawl's terms prohibit several uses involving personal information, intelligence, law-enforcement evidence, hard background checks, and Fair Credit Reporting Act purposes.
  • The affiliate program requires a unique approved referral link; the official commission page is not itself a WhatAI tracking URL.

Which Firecrawl Feature Fits Your Use Case

Feature Good for Common mistake Fix
Search Finding current pages and relevant excerpts Scraping every result without source filters Restrict domains, dates, result count, and scrape formats
Scrape Converting a known page into clean data Trusting structured output without source evidence Store URL, timestamp, passages, and validation errors
Map Inventorying a site before extraction Launching a full crawl from an unknown URL graph Review mapped paths and approve an explicit crawl scope
Crawl Building multi-page documentation or knowledge sets Leaving depth, page count, and paths unrestricted Set allowlists, exclusions, caps, and canonical deduplication
Parse Turning documents into Markdown or structured JSON Forcing OCR on every text-based PDF Use automatic mode and preserve page references for review
Monitor Triggering workflows only when a source changes Checking too frequently without filtering noise Set a precise goal, sensible cadence, and cost ceiling
Interact Browser tasks beyond static page retrieval Letting sessions run without action and time limits Constrain domains, steps, credentials, minutes, and outputs
Research Index Paper discovery, passages, and citation expansion Calling a retrieved list a completed review Verify publication status and search other databases
Lockdown Mode Preventing outbound requests from sensitive workflows Using cached output for current facts Inspect cache age and fail closed when freshness matters
Self-hosting Source and infrastructure control Deploying the unauthenticated quickstart publicly Design production identity, TLS, storage, HA, and recovery

Starter Prompts for Firecrawl

Map our public documentation domain, exclude account, legal, search, and duplicate-language paths, return URLs with titles and last-modified metadata where available, and stop after 5,000 URLs so I can approve the crawl scope.
Crawl the approved documentation paths and return clean Markdown with source URL, title, heading hierarchy, code blocks, and crawl timestamp. Deduplicate canonical pages, keep failed URLs in an error report, and do not follow external links.
Scrape these ten approved product pages and extract JSON matching our schema for product name, current price, currency, billing interval, availability, source URL, and observed timestamp. Leave missing fields null and preserve the exact supporting text for review.
Create a page monitor for our five critical vendor pricing pages. Check daily, alert only when a named plan, price, billing interval, limit, or cancellation term changes, deliver a signed webhook, and cap the estimated monthly credit cost before activation.
Use Search to find official documentation for this API behavior from the last 30 days. Return at most ten results with relevant highlights, publication or update date, source domain, and URL. Exclude forums, scraped copies, affiliates, and AI-generated summaries.
Use the Research Index to find papers on CRISPR base-editing off-target effects in primary human T cells. Return paper IDs, publication status, date, title, abstract, source IDs, and relevant passages, then expand from the strongest seeds to references and citers without writing a medical conclusion.
Parse these approved PDF and DOCX files into Markdown and structured JSON. Use OCR only when embedded text is inadequate, preserve page references, identify tables and figures, flag low-confidence text, and do not infer missing values.
Design a RAG ingestion workflow that maps before crawling, stores canonical URL and fetched timestamp, hashes content for deduplication, validates output, blocks prompt instructions found in scraped pages, chunks by headings, and reindexes only changed documents from Monitor events.
Test Lockdown Mode for these sensitive URLs. Record cache hits, cache age, and cache misses, never fall back to a live request, reject redirects to unapproved domains, and mark every result as unsuitable for time-sensitive facts unless freshness is verified.
Audit our Firecrawl implementation for API-key exposure, unrestricted user URLs, server-side request forgery, prompt injection, personal-data collection, target terms, robots rules, page and concurrency caps, webhook verification, retries, deduplication, deletion, and credit alerts. Return fixes without running a crawl.

Firecrawl — Frequently Asked Questions

What is Firecrawl?

Firecrawl is a developer platform that searches, scrapes, crawls, parses, monitors, and interacts with web content, returning formats such as Markdown, HTML, screenshots, links, summaries, or schema-constrained JSON.

How much does Firecrawl cost?

As verified on August 16, 2026, Free is $0, Hobby is $16 monthly billed yearly, Standard is $83, Growth is $333, Scale is $599, and Enterprise is custom. Self-serve plan prices shown here use annual billing.

What does the Firecrawl Free plan include?

The Free plan includes 1,000 credits per month, 2 concurrent requests, and low rate limits. A standard Scrape, Crawl, Map, or Monitor operation generally costs 1 credit per page.

How do Firecrawl credits work?

Standard Scrape, Crawl, Map, and Monitor requests cost 1 credit per page or check. Search costs 2 credits per 10 results, and Interact costs 2 credits per browser minute. Advanced formats and modes can cost more.

Do unused Firecrawl credits roll over?

Unused credits do not roll over on self-serve plans. Firecrawl says rollover is available on Scale and Enterprise subject to their plan or contract terms.

What is the difference between Scrape and Crawl?

Scrape processes a known URL. Crawl begins at a URL, discovers linked pages through sitemaps and traversal, then scrapes the permitted pages according to depth, path, domain, and page-limit settings.

What is the difference between Search and Map?

Search finds ranked pages across the web for a query and can scrape their contents. Map inventories URLs on a particular website, which is useful for choosing scope before a more expensive crawl.

Can Firecrawl extract structured JSON?

Yes. The JSON output format accepts a natural-language extraction prompt, a JSON Schema, or both. The result still needs type, completeness, source, and business-rule validation before use.

Does Firecrawl handle JavaScript-heavy websites?

Yes. The managed service renders dynamic sites and handles proxies, caching, rate limits, and browser behavior. Difficult authentication, anti-bot controls, unusual applications, and target changes can still cause missing or failed extraction.

Can Firecrawl parse PDFs and office documents?

Yes. Parse supports PDF, Word, Excel, PowerPoint, OpenDocument, EPUB, CSV, HTML, and additional file types, with files up to 50 MB per request. PDF parsing offers automatic, fast text, and OCR modes.

What does Firecrawl Monitor do?

Monitor runs scheduled checks against pages, sites, or recurring web searches, records structured changes, and can notify a webhook, email address, or Slack channel when a relevant change or error occurs.

What is Firecrawl Lockdown Mode?

Lockdown Mode serves Scrape results only from Firecrawl's existing cache and prevents an outbound request. A cache miss returns an error. It can return stale content and currently does not cover Crawl, Map, or Search.

What is the Firecrawl Research Index?

It is a paper-specific index covering roughly 43 million abstracts from sources including PubMed, bioRxiv, medRxiv, and arXiv. Agents can search papers, inspect metadata, retrieve relevant passages, and expand to related papers.

Is the Firecrawl Research Index free?

Firecrawl currently states that its Research Index paper endpoints are free across all available categories, including AI and machine learning plus life sciences. Higher unauthenticated and authenticated limits can differ.

Can Firecrawl be self-hosted?

Yes. The open-source stack can be run with Docker Compose. The quickstart is not a production architecture and does not include every cloud capability. Operators own authentication, TLS, storage, scaling, monitoring, recovery, upgrades, and providers.

Does Firecrawl respect robots.txt?

Firecrawl says Crawl respects rules set for the FirecrawlAgent directive. Endpoint behavior is not a substitute for authorization. Users remain responsible for target terms, privacy, copyright, robots rules, rate limits, and applicable law.

Does Firecrawl have an affiliate program?

Yes. The official program currently lists 25% of subscription revenue for the first 12 months and 15% ongoing for active referred subscriptions. Applications and tracking use Dub.

Related AI, Coding and Development Tools

8 tools
ChatGPT logo

ChatGPT

$0/mo – Custom

Devin Desktop (formerly Codeium) logo

Devin Desktop (formerly Codeium)

$0/mo – Custom

Genspark logo

Genspark

$0/mo – Custom

GitHub Copilot logo

GitHub Copilot

$0–$100/mo

Refact.ai logo

Refact.ai

Free

Replit AI logo

Replit AI

$0/mo – Custom

Sourcegraph Cody logo

Sourcegraph Cody

$0/mo – Custom

Tabnine logo

Tabnine

$0/mo – Custom

Explore the Network

People discussing Firecrawl also discuss...

Alternatives to Firecrawl

ChatGPT ChatGPT $0/mo – Custom Compare Devin Desktop (formerly Codeium) Devin Desktop (formerly Codeium) $0/mo – Custom Compare Genspark Genspark $0/mo – Custom Compare GitHub Copilot GitHub Copilot $0–$100/mo Compare

Pairs well with Firecrawl

Sources & References

  1. Official Firecrawl website ↗
  2. Official Firecrawl pricing and credit table ↗
  3. Firecrawl documentation introduction ↗
  4. Firecrawl Scrape documentation ↗
  5. Firecrawl Search documentation ↗
  6. Firecrawl Crawl documentation ↗
  7. Firecrawl Monitoring documentation ↗
  8. Firecrawl Parse documentation ↗
  9. Firecrawl Research Index documentation ↗
  10. Advanced scraping and output formats ↗
  11. Firecrawl CLI and agent skills ↗
  12. Firecrawl self-hosting guide and limits ↗
  13. Life Sciences Research Index announcement ↗
  14. Original Firecrawl Research Index announcement ↗
  15. Firecrawl Search relevance-model update ↗
  16. Firecrawl Monitoring announcement ↗
  17. Firecrawl Lockdown Mode announcement ↗
  18. Firecrawl Enterprise security and reliability ↗
  19. Firecrawl terms of service ↗
  20. Official Firecrawl affiliate program ↗

Try Firecrawl

Visit the official website to get started with Firecrawl today.

Visit Firecrawl →

Explore More

More AI, Coding and Development Tools

Browse similar AI tools in this category

Compare AI Tools

Side-by-side comparison of features

Community Forum

Discuss Firecrawl with other users