Firecrawl vs ScrapingBee
Firecrawl
Mendable AI, Inc.
Firecrawl wins · 27–25 (42 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to ScrapingBeeA direct probe confirms Firecrawl publishes a working llms.txt at docs.firecrawl.dev/llms.txt with structured agent-readable documentation links, letting an AI agent be pointed directly at it to navigate Firecrawl's docs. Missing for 10: explicit first-party announcement/documentation describing llms.txt support as a deliberate feature, and independent community confirmation of agents successfully using it.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.firecrawl.dev/llms.txt # Firecrawl Docs ## English ### v2 #### Documentation ##### Get Started …”
ScrapingBee has a confirmed live llms.txt at the documented URL (HTTP 200) serving an index of its documentation, directly satisfying the story of pointing an agent at agent-oriented docs; it also has an official MCP server further supporting agentic access. Missing for 10: a per-page markdown/docs.md mirror (probe shows 404) and an OpenAPI spec discoverable at standard paths, which would round out machine-readable doc coverage.
- [probe] “PROBE llms.txt: HTTP 200 at https://www.scrapingbee.com/llms.txt # ScrapingBee Documentation > Official documentation index for ScrapingBee…”
- [probe] “PROBE docs-md: HTTP 404 at https://www.scrapingbee.com/documentation.md”
- [probe] “official MCP server documented at https://mcp.scrapingbee.com/”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to ScrapingBeeFirecrawl offers an API-first product (async scraping, webhooks, CLI, SDKs) that is well-suited to headless/CI use, and docs confirm a CLI and webhook-based async event delivery for automation pipelines. However, there's no explicit CI-specific documentation (e.g., GitHub Actions examples, Docker image for CI), and community comments note some daemon/CLI limitations rather than confirming robust CI usage. missing for 10: explicit CI/headless deployment docs or examples, independent confirmation of stable CLI/daemon behavior in automated pipelines, containerization guidance for CI environments.
- [claimed-docs] “Webhooks Async event delivery”
- [probe] “official CLI documented at https://docs.firecrawl.dev/sdks/cli”
- [github] “Scrape thousands of URLs asynchronously”
- [community] “It being vibe coded aside, does it support screenshots? I noticed the daemon mode has a lot of weird limitations too like not being able to …”
ScrapingBee is a pure API service (API key + HTTP calls) designed for programmatic use, and it ships an official CLI (scrapingbee-cli) enabling scripted/headless invocation suitable for CI pipelines. Missing for 10: explicit CI/CD pipeline examples (e.g., GitHub Actions), and no independent hands-on confirmation of CLI use in automation contexts.
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
- [probe] “official CLI documented at https://github.com/ScrapingBee/scrapingbee-cli”
ai-native userConnect an agent via an official MCP server
weight 3 · round to FirecrawlFirecrawl is a scraping/data-extraction service (not itself an agent), and it documents an official MCP server for connecting AI tools/agents to Firecrawl, corroborated by a dedicated GitHub repo (firecrawl-mcp-server). Missing for 10: independent hands-on testing of the MCP server itself and details on tool/resource coverage exposed via MCP.
- [claimed-docs] “MCP Server: Connect Firecrawl to any AI tool via the Model Context Protocol”
- [probe] “official MCP server documented at https://github.com/mendableai/firecrawl-mcp-server”
ScrapingBee is a scraping API/service (not itself an agent), so publishing an official MCP server is a valid axis; a probe confirms an official MCP server is documented at mcp.scrapingbee.com. However, there is no first-party documentation detail on the MCP server's tool set, setup, or independent/community corroboration of it working. Missing for 10: detailed official docs on MCP server capabilities/setup, independent hands-on confirmation.
- [probe] “official MCP server documented at https://mcp.scrapingbee.com/”
ai-native userUse an official CLI
weight 2 · round to ScrapingBeeFirecrawl ships an official CLI (docs.firecrawl.dev/sdks/cli) that installs, authenticates, and adds skills to coding agents, directly matching an AI-native CLI story. However, community feedback notes real limitations in CLI/daemon mode (e.g., inability to return HTML), suggesting it's not fully mature. Missing for 10: independent hands-on verification of full CLI feature parity, and no comparison data beyond one critical community comment.
- [claimed-docs] “One command installs the Firecrawl CLI, authenticates in your browser, and adds skills to every detected coding agent.”
- [probe] “official CLI documented at https://docs.firecrawl.dev/sdks/cli”
- [community] “It being vibe coded aside, does it support screenshots? I noticed the daemon mode has a lot of weird limitations too like not being able to …”
Evidence shows an official CLI repo published by ScrapingBee (scrapingbee-cli on GitHub), directly satisfying the story. However, there's no documentation excerpt describing CLI features, installation, or usage details, nor independent community corroboration of its use. Missing for 10: detailed CLI documentation/usage examples, independent/hands-on validation, and confirmation of active maintenance.
- [probe] “official CLI documented at https://github.com/ScrapingBee/scrapingbee-cli”
ai-native userDrive the product through a documented public API
weight 3 · round drawnFirecrawl is API-first: docs cover scrape/crawl/search/extract endpoints, schema-based structured output, webhooks, and SDKs/CLI, all confirmed by an extensive llms.txt-indexed documentation site and GitHub feature list. Missing for 10: a discoverable machine-readable OpenAPI/Swagger spec (probe returned 404s) and independent third-party confirmation of API completeness.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [claimed-docs] “Search the web and get full page content from results in one call.”
- [claimed-docs] “Scrape a page, then keep working with it: click, fill forms, extract dynamic content, or navigate deeper.”
- [github] “Use a schema to get structured data:”
- [claimed-docs] “Webhooks Async event delivery”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.firecrawl.dev/llms.txt # Firecrawl Docs ## English ### v2 #### Documentation ##### Get Started …”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.firecrawl.dev/openapi.json, https://docs.firecrawl.dev/swagger.json, https://docs.firec…”
- [probe] “official CLI documented at https://docs.firecrawl.dev/sdks/cli”
ScrapingBee's entire product is a documented public REST API with extensive parameter documentation (docs-1 to docs-15) and an llms.txt index for AI discoverability (probe-1), plus official CLI and MCP server (probe-4, probe-5) enabling agentic access. Missing for 10: a machine-readable OpenAPI/Swagger spec (probe-2 and probe-3 both 404) and independent hands-on confirmation of API integration ease.
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
- [probe] “PROBE llms.txt: HTTP 200 at https://www.scrapingbee.com/llms.txt # ScrapingBee Documentation > Official documentation index for ScrapingBee…”
- [probe] “official MCP server documented at https://mcp.scrapingbee.com/”
- [probe] “official CLI documented at https://github.com/ScrapingBee/scrapingbee-cli”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.scrapingbee.com/openapi.json, https://www.scrapingbee.com/swagger.json, https://www.scra…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnFirecrawlnone0/10No evidence of scoped or least-privilege API key/credential management for agents; documentation covers scraping, crawling, MCP, CLI, and webhooks but nothing about API key scopes, permissions, or credential issuance controls.
ScrapingBeenone0/10Evidence only shows a single API key model for authentication with no mention of scoped, restricted-permission, or per-agent credential issuance; the community note about using two API keys does not indicate least-privilege scoping. Missing for 10: any documentation of scoped/restricted API keys, role-based permissions, or credential issuance mechanisms for agents.
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
- [community] “cool idea, but I don't like how I need to use two separate API keys to connect to this API (which relies on ScrapingBee for scraping) - can …”
ai-native userBuild against official SDKs
weight 2 · round to FirecrawlThe only concrete artifact tied to 'SDKs' in the evidence is the CLI documented at docs.firecrawl.dev/sdks/cli, implying an SDKs section exists, but no evidence pack item names or links a Python/Node/other language SDK, shows install/usage snippets, or corroborates community usage. Missing for 10: explicit language SDK docs/links, code examples, independent/community confirmation of SDK usage.
- [probe] “official CLI documented at https://docs.firecrawl.dev/sdks/cli”
- [claimed-docs] “One command installs the Firecrawl CLI, authenticates in your browser, and adds skills to every detected coding agent.”
ScrapingBeenone0/10The evidence pack documents ScrapingBee's REST API parameters, an official CLI, and an MCP server, but contains no mention of official SDKs (e.g., Python, Node.js, PHP client libraries) that AI-native developers could build against. Absence of evidence for this applicable capability warrants a 'none' verdict.
ai-native userSubscribe to events via webhooks
weight 2 · round to FirecrawlFirecrawl's docs explicitly document a Webhooks feature for async event delivery, directly matching the story. Missing for 10: details on event types, payload schema, retry/security guarantees, and independent/hands-on confirmation of webhook usage.
- [claimed-docs] “Webhooks Async event delivery”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to ScrapingBeeFirecrawlnone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
ScrapingBee's `ai_query` parameter lets users ask AI to extract specific information from scraped pages, which is a limited AI capability applied to data the product handles, but it's user-directed extraction rather than proactive AI-generated insights or suggestions surfaced inside the product. Missing for 10: evidence of automated insight generation, trend/anomaly detection, or suggestion features beyond on-demand query-based extraction.
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to FirecrawlFirecrawl supports webhooks for async event delivery and crawling jobs that run without blocking, which enables background/autonomous data-retrieval workflows, and its MCP server/CLI let agents trigger these jobs programmatically. However there's no evidence of a scheduling/trigger system (e.g., cron-like recurring jobs) or persistent autonomous 'automation' orchestration beyond one-off crawl/extract jobs with webhook callbacks. Missing for 10: scheduled/recurring job support, autonomous multi-step automation orchestration, independent confirmation of long-running background automation reliability.
- [claimed-docs] “Webhooks Async event delivery”
- [github] “Scrape thousands of URLs asynchronously”
- [claimed-docs] “MCP Server: Connect Firecrawl to any AI tool via the Model Context Protocol”
- [probe] “official MCP server documented at https://github.com/mendableai/firecrawl-mcp-server”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to FirecrawlFirecrawl exposes an 'AI agent' mode where a user describes what they need and the agent searches/navigates/retrieves without URLs, with configurable reasoning effort (firecrawl-gh-1, firecrawl-gh-2) — a limited form of task delegation to an embedded AI. However, this is a narrow scraping/search agent, not a general-purpose in-product assistant, and there's no evidence of a broader conversational assistant UI for delegating arbitrary tasks. Missing for 10: evidence of a general-purpose conversational assistant interface, examples of delegated multi-step tasks beyond search/navigate, and independent confirmation of this agent's real-world reliability.
ai-native userOperate the product with natural-language commands
weight 2 · round drawnFirecrawl offers a natural-language 'search agent' mode ('Describe what you need... No URLs required') and lets users tune agent reasoning effort, which supports NL-driven operation, and its MCP/CLI integrations let AI agents invoke it conversationally through coding assistants. However, most of the product's core surface (scrape, crawl, extract, map) is still driven by structured API calls/schemas rather than free-form natural language commands. Missing for 10: evidence of full NL command coverage across all core endpoints (not just the search agent), and independent hands-on confirmation that NL commands reliably work end-to-end.
- [github] “Describe what you need, and our AI agent searches, navigates, and retrieves it. No URLs required.”
- [github] “Set how much reasoning the agent spends on the task”
- [claimed-docs] “One command installs the Firecrawl CLI, authenticates in your browser, and adds skills to every detected coding agent.”
- [claimed-docs] “MCP Server: Connect Firecrawl to any AI tool via the Model Context Protocol”
- [probe] “official MCP server documented at https://github.com/mendableai/firecrawl-mcp-server”
ScrapingBee's `ai_query` parameter lets users specify what to extract from a page using natural language, and there is a documented official MCP server (mcp.scrapingbee.com) that would let AI agents invoke ScrapingBee via natural-language tool calls. However, the core product interface remains a structured REST API with many typed parameters, not a natural-language command interface itself. Missing for 10: evidence of a chat/NL interface for configuring scrapes beyond ai_query, and independent confirmation the MCP server supports full natural-language operation.
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
- [probe] “official MCP server documented at https://mcp.scrapingbee.com/”
ai-native userApply a preset configuration tuned for research agents that returns structured, citable output
weight 2 · round to ScrapingBeeFirecrawlnone0/10Firecrawl offers general scraping, structured JSON extraction, and search, but the evidence pack shows no dedicated preset/mode tuned specifically for research agents that returns citable, source-attributed output — no citation formatting, source-tracking, or research-agent-specific configuration is documented.
ScrapingBee offers markdown output (return_page_markdown), AI-driven extraction (ai_query), and structured extraction (extract_rules) which can produce citable, structured output usable by research agents, plus an MCP server for agentic integration. However, there is no evidence of a dedicated 'preset configuration tuned for research agents' — no named research-agent mode, no citation metadata, and no documentation bundling these features into a single agent-oriented preset. missing for 10: a documented research-agent preset/mode, citation/source-attribution output, and evidence of agent-specific tuning beyond generic AI extraction params.
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
- [claimed-docs] “return_page_markdown [boolean] (false) Return the page content in markdown format”
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
- [probe] “official MCP server documented at https://mcp.scrapingbee.com/”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnFirecrawlnone0/10No evidence of an interactive API reference or runnable-example playground; the OpenAPI/swagger probe explicitly returned 404s at all candidate paths, and docs items only describe features, not an interactive reference experience.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.firecrawl.dev/openapi.json, https://docs.firecrawl.dev/swagger.json, https://docs.firec…”
ScrapingBeenone0/10The evidence pack shows only static parameter documentation and no mention of an interactive API reference, live 'try it' console, or runnable code examples; probes even show no OpenAPI/swagger spec and a 404 on a machine-readable docs endpoint, suggesting no interactive explorer exists.
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
- [probe] “PROBE docs-md: HTTP 404 at https://www.scrapingbee.com/documentation.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.scrapingbee.com/openapi.json, https://www.scrapingbee.com/swagger.json, https://www.scra…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnFirecrawlnone0/10A direct probe for OpenAPI/Swagger spec files at all standard locations (openapi.json, swagger.json, etc.) returned 404s, and no other evidence pack item mentions a downloadable machine-readable API spec; only an llms.txt documentation index was found, which is not an OpenAPI-equivalent spec.
ScrapingBeenone0/10Direct probes for an OpenAPI/Swagger spec at all standard locations returned 404, and no evidence pack item shows a downloadable machine-readable API spec being offered elsewhere; only an llms.txt index and human-readable docs exist.
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnFirecrawlnone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnFirecrawlnone0/10The docs reference a 'v2' API version (firecrawl-probe-1), showing some versioning exists, but there is no evidence of a documented deprecation policy, version support timelines, or migration guides, and an OpenAPI spec could not even be located (firecrawl-probe-2). Missing for 10: explicit deprecation policy documentation, versioning/support lifecycle statements, migration guidance for older API versions.
ScrapingBeenone0/10No evidence of API versioning scheme or a documented deprecation policy; OpenAPI spec probes 404 and docs don't mention versioning/deprecation terms at all.
data-engineerThe documented rate limit (requests per second or minute) enforced on my API key before throttling kicks in
weight 3 · round drawnFirecrawlnone0/10No evidence pack item documents specific rate limits (requests per second/minute) per API key or plan tier; only general product features and community commentary are present.
Anti bot — getting past bot defenses — CAPTCHAs, fingerprinting, blocksAnti bot
Getting past bot defenses — CAPTCHAs, fingerprinting, blocks
Block evasion
ai-native userHave an agent automatically get past a CAPTCHA, login, or form wall without my manual intervention
weight 2 · round to ScrapingBeeFirecrawl's docs support form-filling, clicking, and navigating via a 'Browser Sandbox' for interactive workflows (firecrawl-docs-3, firecrawl-docs-8), and community comments reference actual CAPTCHA 'solves' being consumed at cost (firecrawl-comm-6), suggesting some automated CAPTCHA handling exists in practice. However, there is no first-party documentation explicitly claiming automatic CAPTCHA bypass or login-wall traversal, and community sentiment flags cost/reliability friction rather than seamless unattended operation. Missing for 10: explicit vendor documentation of CAPTCHA-solving/login automation, and independent hands-on confirmation that it reliably completes login flows without manual steps.
- [claimed-docs] “Scrape a page, then keep working with it: click, fill forms, extract dynamic content, or navigate deeper.”
- [claimed-docs] “Browser Sandbox Managed browser sessions for interactive workflows”
- [community] “same setup here for news pages. tier 3 is where my money went, 320 solves a day and 10gb of proxy gone in two days.”
- [community] “Quite useful. Currently we do overpay for the services [referring to Firecrawl-like scraping services].”
ScrapingBee provides premium proxies to bypass hard-to-scrape sites and JS 'scenario' scripting to interact with pages (e.g., click/fill forms), which could support login flows, but there is no explicit claim or evidence of automatic CAPTCHA solving or a documented login-automation workflow that removes manual intervention entirely. missing for 10: explicit CAPTCHA-solving mechanism, documented login/form-wall bypass workflow, and independent evidence of successful autonomous bypass.
- [claimed-docs] “If you want to interact with pages you want to scrape before we return your the HTML you can add JavaScript scenario to your API call.”
- [claimed-docs] “premium_proxy [boolean] (false) Use premium proxies to bypass difficult to scrape websites”
- [claimed-docs] “session_id [integer] ("") Route multiple API requests through the same IP address”
data-engineerAutomatically retry through a chain of different proxies when anti-bot detection blocks a request
weight 2 · round to ScrapingBeeFirecrawlnone0/10No evidence describes proxy rotation or anti-bot retry chains; the only relevant community comment explicitly states Firecrawl lacks a proxy service, which is core to bypassing anti-bot blocks.
- [community] “As I see, you use Puppeteer, not Playwright. Also, both Firecrawl and Firecrawl Simple are really simple, and most importantly don't have pr…”
ScrapingBee offers premium_proxy and country_code parameters and an 'auto' mode that picks the cheapest configuration that succeeds, implying some automatic fallback/retry logic, but there's no explicit documentation of a chained multi-proxy retry mechanism specifically triggered by anti-bot detection. missing for 10: explicit documentation of automatic retry chains across multiple proxies upon anti-bot block detection, and independent verification of this retry behavior.
- [claimed-docs] “premium_proxy [boolean] (false) Use premium proxies to bypass difficult to scrape websites”
- [claimed-docs] “country_code [string] ("") Premium proxy geolocation”
- [claimed-docs] “mode [string] ("") Let ScrapingBee pick the cheapest configuration that succeeds. Only value is auto”
developerUse an undetected browser mode to bypass sophisticated bot detection systems
weight 3 · round to ScrapingBeeFirecrawlnone0/10Evidence mentions a 'Browser Sandbox' for managed browser sessions and general scraping/crawling features, but there is no documentation or claim of a stealth/undetected browser mode specifically designed to bypass sophisticated bot detection. Community comments (e.g., proxy tiers, captcha solves) hint indirectly at anti-bot infrastructure but do not confirm an official 'undetected mode' feature. missing for 10: explicit stealth/undetected browser mode docs, technical details on bypassing bot detection (fingerprint spoofing, TLS/JA3 randomization, etc.), independent verification of bypass success.
- [claimed-docs] “Browser Sandbox Managed browser sessions for interactive workflows”
- [community] “same setup here for news pages. tier 3 is where my money went, 320 solves a day and 10gb of proxy gone in two days.”
ScrapingBee's docs mention `premium_proxy` explicitly for bypassing 'difficult to scrape websites' and headless browser rendering with JS scenarios, which implies anti-bot capability, but the evidence never uses 'undetected browser' or 'stealth mode' terminology or details specific bot-detection bypass techniques (fingerprint spoofing, TLS/JA3 evasion, etc.). Missing for 10: explicit stealth/undetected-mode documentation, technical detail on fingerprint evasion, and independent verification that it defeats sophisticated bot detection.
- [claimed-docs] “premium_proxy [boolean] (false) Use premium proxies to bypass difficult to scrape websites”
- [claimed-docs] “If you want to interact with pages you want to scrape before we return your the HTML you can add JavaScript scenario to your API call.”
- [claimed-docs] “Our headless browsers will wait for the CSS / Xpath selector passed in the parameter before returning the HTML.”
Proxy rotation
developerRequest a proxy from a specific country to get geolocation-appropriate content
weight 2 · round to ScrapingBeeFirecrawlnone0/10No evidence in the pack shows Firecrawl offering country-specific or geolocation proxy selection; in fact a community comment explicitly states Firecrawl lacks a proxy service entirely, and no docs or GitHub references mention proxy/geolocation features.
- [community] “As I see, you use Puppeteer, not Playwright. Also, both Firecrawl and Firecrawl Simple are really simple, and most importantly don't have pr…”
ScrapingBee's docs explicitly document a `country_code` parameter for premium proxy geolocation, directly enabling country-specific proxy requests, alongside `premium_proxy` to enable this feature. missing for 10: independent/hands-on confirmation of geolocation accuracy and no list of supported countries in the evidence.
- [claimed-docs] “premium_proxy [boolean] (false) Use premium proxies to bypass difficult to scrape websites”
- [claimed-docs] “country_code [string] ("") Premium proxy geolocation”
developerUse premium residential or datacenter proxies to bypass sites that are hard to scrape
weight 3 · round to ScrapingBeeFirecrawlnone0/10The evidence pack contains no vendor documentation mentioning residential or datacenter proxy support; in fact a community source explicitly states 'Firecrawl... don't have proxy service which is the heart of any crawler and scraper' (firecrawl-comm-3). No official docs or GitHub features reference proxy rotation, IP pools, or anti-bot proxy tiers.
- [community] “As I see, you use Puppeteer, not Playwright. Also, both Firecrawl and Firecrawl Simple are really simple, and most importantly don't have pr…”
Docs explicitly document `premium_proxy` for bypassing hard-to-scrape sites, plus `country_code` for geolocation and `session_id` for sticky IP sessions, directly matching the story. Missing for 10: explicit distinction/documentation of residential vs datacenter proxy types and independent third-party validation of bypass success rates.
- [claimed-docs] “premium_proxy [boolean] (false) Use premium proxies to bypass difficult to scrape websites”
- [claimed-docs] “country_code [string] ("") Premium proxy geolocation”
- [claimed-docs] “session_id [integer] ("") Route multiple API requests through the same IP address”
developerRoute requests through a rotating pool of proxy IPs to avoid blocks
weight 3 · round to ScrapingBeeFirecrawlnone0/10No first-party documentation or GitHub evidence claims a rotating proxy pool feature; in fact community commentary explicitly states Firecrawl 'don't have proxy service which is the heart of any crawler and scraper.' Without vendor claims to dispute, this is simply unevidenced.
- [community] “As I see, you use Puppeteer, not Playwright. Also, both Firecrawl and Firecrawl Simple are really simple, and most importantly don't have pr…”
Docs confirm premium/rotating proxy usage (premium_proxy, country_code) to bypass blocks, plus session_id to pin a single IP when needed, indicating an underlying rotating proxy pool by default with control options. Missing for 10: no independent/hands-on evidence confirming rotation effectiveness against real anti-bot defenses, and no explicit documentation describing pool size or rotation algorithm.
- [claimed-docs] “premium_proxy [boolean] (false) Use premium proxies to bypass difficult to scrape websites”
- [claimed-docs] “country_code [string] ("") Premium proxy geolocation”
- [claimed-docs] “session_id [integer] ("") Route multiple API requests through the same IP address”
developerRoute multiple requests through the same proxy IP using a session identifier to maintain a consistent identity
weight 2 · round to ScrapingBeeFirecrawlnone0/10No evidence that Firecrawl exposes a session-identifier parameter to pin requests to the same proxy IP; the closest evidence is a community comment stating Firecrawl lacks its own proxy service entirely, which undercuts rather than supports this specific anti-bot capability.
- [community] “As I see, you use Puppeteer, not Playwright. Also, both Firecrawl and Firecrawl Simple are really simple, and most importantly don't have pr…”
Official docs explicitly document a `session_id` parameter to route multiple API requests through the same proxy IP, directly matching the story. Missing for 10: independent/hands-on corroboration of session persistence behavior beyond first-party docs.
- [claimed-docs] “session_id [integer] ("") Route multiple API requests through the same IP address”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to FirecrawlFirecrawl explicitly supports bulk operations at scale: crawling entire websites, scraping thousands of URLs asynchronously, batch discovery of URLs, and async webhook delivery for large jobs. This directly matches an AI-native user's need to operate across many items at once. Missing for 10: independent hands-on benchmarks validating throughput/reliability at scale and more detail on rate limits/error handling for bulk jobs.
- [github] “Crawl an entire website and get content from all pages.”
- [github] “Discover all URLs on a website instantly.”
- [github] “Scrape thousands of URLs asynchronously”
- [claimed-docs] “Webhooks Async event delivery”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to FirecrawlFirecrawl offers webhooks for async event delivery (e.g., notifying when a crawl job completes), which is the only automation-adjacent capability in the evidence; there's no documented rule-definition engine or conditional trigger system for defining custom actions on events. Missing for 10: a rules/trigger engine, conditional logic, or action-chaining beyond simple webhook notifications, and any independent confirmation of automation depth.
- [claimed-docs] “Webhooks Async event delivery”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnFirecrawlnone0/10Firecrawl offers webhooks for async event delivery and async crawling/scraping, but there is no evidence of a scheduler or recurring-job/workflow feature (e.g., cron-based crawls or scheduled scrape jobs).
Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience
Day-to-day developer experience — setup friction, docs, debugging, iteration speed
Collaboration
developerShare scrapers with teammates and manage organizations and role-based permissions
weight 2 · round drawnFirecrawlnone0/10No evidence pack items mention team collaboration, organizations, workspaces, or role-based access control for sharing scrapers; documentation focuses on scraping, extraction, CLI, and MCP features only.
Deployment flexibility
developerBuild and deploy custom serverless scraping scripts on the platform without managing my own infrastructure
weight 2 · round to ScrapingBeeFirecrawlnone0/10Firecrawl's evidence shows a fixed API/SDK/CLI for scraping, crawling, extracting, and search, plus webhooks and an MCP server — but nothing about writing and deploying custom serverless scripts or actor-style code that runs on Firecrawl's own infrastructure (unlike platforms such as Apify Actors). No docs, GitHub, or community evidence mentions custom script deployment or a functions/actors runtime.
ScrapingBee is a managed scraping API (no infrastructure to manage) and supports JS 'scenarios' for custom page interaction plus extraction rules, which is a lightweight form of custom scraping logic. However, there is no evidence of a true serverless scripting/deployment platform (e.g., custom code upload, scheduled jobs, or a scripting runtime) — the story's 'build and deploy custom scripts' aspect is only partially matched by parameterized API calls. Missing for 10: evidence of a script/job deployment mechanism, scheduling, or custom code execution beyond JS scenario snippets, and independent developer confirmation of this workflow.
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
- [claimed-docs] “If you want to interact with pages you want to scrape before we return your the HTML you can add JavaScript scenario to your API call.”
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
developerDeploy the scraping service via a Docker container for production use
weight 2 · round drawnFirecrawlnone0/10The evidence confirms Firecrawl is open source (AGPL-3.0) and self-hostable, but no citation mentions Docker, docker-compose, or containerized deployment instructions for production use.
- [github] “Firecrawl is open source under the AGPL-3.0 license. The cloud version at firecrawl.dev includes additional features”
developerSelf-host an open-source version of the scraper instead of relying on a hosted cloud service
weight 2 · round to FirecrawlFirecrawl is explicitly confirmed open source under AGPL-3.0 with the cloud version noted as having 'additional features', confirming self-hosting is possible but with reduced functionality (firecrawl-gh-6). Community commentary corroborates this, noting the self-hosted version lacks the proxy service considered 'the heart' of a scraper and other missing capabilities like screenshots (firecrawl-comm-3, firecrawl-comm-4). Missing for 10: first-party self-hosting setup/docker docs, explicit feature-parity comparison, and independent hands-on confirmation of a smooth self-host deployment experience.
- [github] “Firecrawl is open source under the AGPL-3.0 license. The cloud version at firecrawl.dev includes additional features”
- [community] “As I see, you use Puppeteer, not Playwright. Also, both Firecrawl and Firecrawl Simple are really simple, and most importantly don't have pr…”
- [community] “It being vibe coded aside, does it support screenshots? I noticed the daemon mode has a lot of weird limitations too like not being able to …”
- [community] “Interesting... Looks like it would be good for RAG. Maybe add Ollama support for local hosting?”
ScrapingBeenone0/10ScrapingBee is a hosted cloud scraping API with no evidence of an open-source, self-hostable version; community comments explicitly ask about open-sourcing the stack, confirming none exists.
- [community] “Any plans on open sourcing any part of your stack instead of relying on paid services like ScrapingBee? What does your SaaS setup look like?”
- [community] “Have you looked at running something locally instead of paying for ScrapingBee? I'm using Laravel and considering Dusk to retrieve page cont…”
Integrations
developerConnect the scraping API to no-code automation platforms like n8n or Zapier through a prebuilt connector
weight 2 · round drawnFirecrawlnone0/10No evidence of a prebuilt n8n or Zapier connector; docs mention MCP server, CLI, SDKs, and webhooks but nothing about no-code automation platform integrations.
Library compatibility
developerBuild scrapers using popular open-source automation libraries like Playwright, Puppeteer, Selenium, or Scrapy
weight 2 · round drawnFirecrawlnone0/10Firecrawl is a hosted scraping/crawling API with its own primitives (scrape, crawl, extract, browser sandbox) rather than a framework for developers to write Playwright/Puppeteer/Selenium/Scrapy scripts; there is no documented support for plugging in or building on these open-source libraries. A community comment even notes Firecrawl internally uses Puppeteer (not user-selectable) and lacks the openness these libraries provide, contradicting any claim of multi-library dev flexibility.
- [community] “As I see, you use Puppeteer, not Playwright. Also, both Firecrawl and Firecrawl Simple are really simple, and most importantly don't have pr…”
- [claimed-docs] “Browser Sandbox Managed browser sessions for interactive workflows”
- [github] “Firecrawl is open source under the AGPL-3.0 license. The cloud version at firecrawl.dev includes additional features”
ScrapingBeenone0/10The evidence pack describes ScrapingBee's own API parameters (JS scenario, screenshots, extraction rules, proxies) but contains no mention of official integrations, SDKs, or middleware for Playwright, Puppeteer, Selenium, or Scrapy. No documentation, probe, or community evidence shows developers can plug ScrapingBee into these specific open-source automation libraries.
Migration lock in
developerExport my scraped data and job configurations in a portable format to migrate to another provider without lock-in
weight 3 · round to FirecrawlFirecrawl's outputs (markdown/HTML/structured JSON) are inherently portable formats, and its open-source AGPL-3.0 license means self-hosting/forking is possible, reducing lock-in — but there is no documented feature for exporting job configurations, crawl settings, or webhooks setups for migration to another provider. missing for 10: explicit job-configuration export/import tooling, migration guides, or documented data-portability features beyond raw scrape output formats.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [github] “Firecrawl is open source under the AGPL-3.0 license. The cloud version at firecrawl.dev includes additional features”
- [community] “Finally, people starting to realize that AGPL means you can just fork and remove everything you don't like (including branding).”
ScrapingBeenone0/10No evidence of any export/migration tooling for scraped data or job configs in a portable format; the docs cover API parameters and scraping features but nothing about data portability or provider migration. missing for 10: export format documentation, job/config export mechanism, migration guides or tooling, any mention of avoiding vendor lock-in.
Quickstart
developerPublish my custom scraper to a public marketplace and earn revenue when others use it
weight 1 · round drawnFirecrawlnone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
developerRun a ready-made scraper from a marketplace instead of building one from scratch
weight 2 · round drawnFirecrawlnone0/10No evidence of a marketplace of ready-made scrapers/templates that developers can pick up and run; Firecrawl's evidence covers building scraping/crawling calls via API, CLI, MCP, and SDKs, not a curated marketplace of pre-built scrapers.
developerStart building immediately using a library of ready-made project templates
weight 1 · round drawnFirecrawlnone0/10Evidence shows CLI, SDKs, MCP server, and API docs, but nothing about a library of ready-made project templates or starter projects to jumpstart development.
Extraction quality — how faithfully content is extracted — structure, fidelity, edge casesExtraction quality
How faithfully content is extracted — structure, fidelity, edge cases
Ai extraction
developerExtract structured data from a page using natural language instructions instead of writing selectors
weight 3 · round to ScrapingBeeFirecrawl's Extract feature lets developers get structured JSON via schemas and its agent can be described in natural language to find/retrieve content without URLs, but the evidence pack shows schema-based extraction more than fully free-form natural-language field extraction replacing selectors. Missing for 10: explicit documentation of prompt-only (no schema) extraction, and independent hands-on confirmation of extraction accuracy.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [github] “Use a schema to get structured data:”
- [github] “Describe what you need, and our AI agent searches, navigates, and retrieves it. No URLs required.”
- [claimed-docs] “Scrape a page, then keep working with it: click, fill forms, extract dynamic content, or navigate deeper.”
ScrapingBee's ai_query parameter lets developers specify in natural language the information they want extracted from a webpage, avoiding manual CSS/XPath selectors, as an alternative to the selector-based extract_rules feature. missing for 10: independent/hands-on validation of AI extraction accuracy, and details on structured output schema/reliability beyond the docs blurb.
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
developerPass a JSON schema so the API returns structured data matching that schema
weight 2 · round to FirecrawlFirecrawl's docs and GitHub explicitly advertise passing a JSON schema to extract structured data ("Use a schema to get structured data") and general structured JSON extraction from URLs, PDFs, and other formats. Missing for 10: independent/hands-on confirmation of schema-conformance accuracy and edge-case handling beyond vendor docs.
- [github] “Use a schema to get structured data:”
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [claimed-docs] “Turn local PDFs, DOCX, XLSX, HTML, and more into Markdown or structured JSON”
ScrapingBee offers extract_rules (CSS-selector based structured extraction) and ai_query (AI-driven extraction), which let developers get structured data, but there is no evidence of accepting a formal JSON Schema definition that the API validates/conforms output to — extract_rules is a custom stringified JSON of selectors, not a schema spec. missing for 10: explicit JSON Schema input support, schema validation/conformance guarantee, examples of schema-driven structured output.
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
ai-native userHave an LLM read a page and decide what structured fields to pull out without pre-written selectors
weight 2 · round drawnFirecrawl's docs and GitHub note schema-based structured extraction ("Use a schema to get structured data") and general LLM-driven content extraction to JSON, which aligns with selector-free, LLM-decided field extraction. However, evidence doesn't show prompt-only (schema-less) extraction quality, nor independent verification of how well the LLM infers fields without any schema hints. missing for 10: evidence of extraction working from a pure natural-language prompt without any schema, and independent/hands-on validation of extraction accuracy.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [github] “Use a schema to get structured data:”
- [github] “Describe what you need, and our AI agent searches, navigates, and retrieves it. No URLs required.”
ScrapingBee has an ai_query parameter that lets an LLM extract requested information from a page without pre-written CSS/XPath selectors, directly matching the story's intent, but this is described only in a single doc line rather than deeply documented with examples of dynamic field discovery. missing for 10: no documentation showing the AI deciding on its own what structured fields/schema to output (vs. a user-specified query), no independent/hands-on evidence of extraction quality or reliability, and no example of full structured JSON field inference without any query guidance.
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
developerPlug in a local or self-hosted LLM as the extraction backend instead of a cloud-only model
weight 2 · round drawnFirecrawlnone0/10No evidence that Firecrawl allows swapping in a local or self-hosted LLM as the extraction backend; a community comment even suggests adding Ollama support as a future wish, implying it isn't currently offered.
- [community] “Interesting... Looks like it would be good for RAG. Maybe add Ollama support for local hosting?”
ScrapingBeenone0/10ScrapingBee's AI extraction (ai_query) uses its own cloud-based AI backend with no documented option to plug in a local or self-hosted LLM; evidence shows only a fixed AI extraction parameter, not a configurable backend.
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
Basic scraping
developerScrape a web page with a single API call and get its raw HTML back
weight 3 · round to ScrapingBeeFirst-party docs explicitly state that Firecrawl's scrape endpoint extracts content from any URL as markdown, HTML, or structured JSON in a single call, directly matching the story. A community comment raises a narrow caveat about HTML not being returned in a separate 'daemon mode', but this does not contradict the main scrape API. Missing for 10: independent hands-on confirmation of raw HTML output quality/fidelity for the primary scrape endpoint.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [community] “It being vibe coded aside, does it support screenshots? I noticed the daemon mode has a lot of weird limitations too like not being able to …”
Docs confirm a single API call with just an API key and target URL returns the page's HTML, with straightforward defaults (docs-1) and no complex setup required. Additional options (JS rendering, wait selectors, markdown/extract_rules) show this basic case is well-supported and flexible, though there's no independent hands-on confirmation of raw HTML fidelity. Missing for 10: independent/community verification of raw HTML output quality.
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
- [claimed-docs] “If you want to interact with pages you want to scrape before we return your the HTML you can add JavaScript scenario to your API call.”
- [claimed-docs] “Our headless browsers will wait for the CSS / Xpath selector passed in the parameter before returning the HTML.”
Data safety
data-engineerAutomatically detect and filter personally identifiable information out of scraped content before it reaches storage
weight 2 · round drawnFirecrawlnone0/10No evidence in the pack mentions PII detection, redaction, or filtering capabilities; Firecrawl's documented features cover scraping, extraction, crawling, and structured output but nothing about privacy/PII compliance controls.
Document extraction
data-engineerExtract text content from PDFs, Word, Excel, and PowerPoint files without hosting them myself
weight 2 · round to FirecrawlFirecrawl explicitly documents converting local PDFs, DOCX, XLSX, HTML and more into Markdown or structured JSON as a hosted (cloud) service, directly matching the story of extracting text from PDFs/Word/Excel/PowerPoint without self-hosting. Missing for 10: explicit mention of PowerPoint (.pptx) support and independent hands-on confirmation of file-parsing quality/accuracy.
- [claimed-docs] “Turn local PDFs, DOCX, XLSX, HTML, and more into Markdown or structured JSON”
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
Multimodal extraction
ai-native userGet automatic captions for images on a page so a text-only model can reason about visual content
weight 2 · round drawnFirecrawlnone0/10No evidence Firecrawl generates automatic image captions or alt-text descriptions for visual content; evidence only covers text/HTML/markdown extraction, crawling, and structured data extraction.
ScrapingBeenone0/10No evidence of an image-captioning or alt-text generation feature; ScrapingBee's AI features (ai_query) extract structured data from page text/HTML, not image captions for visual content, and by default it blocks images entirely. Missing for 10: any documented image captioning/vision-to-text capability, alt-text generation, or multimodal image description output.
- [claimed-docs] “By default, and to speed up requests, ScrapingBee blocks all images and CSS in the scraped page, but to scrape them, use `block_resources=fa…”
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
Search integration
developerSearch the web and get full page content from results in a single call instead of just links and snippets
weight 3 · round to FirecrawlFirecrawl's docs explicitly advertise a search endpoint that returns full page content from results in one call, matching the story exactly, and this is backed by broader scrape/extract capabilities showing it can fetch full markdown/HTML/structured content rather than just snippets. Missing for 10: independent hands-on verification of the search+content endpoint specifically (community evidence discusses scraping/crawling generally but not this exact combined search feature).
- [claimed-docs] “Search the web and get full page content from results in one call.”
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [github] “Describe what you need, and our AI agent searches, navigates, and retrieves it. No URLs required.”
ScrapingBeenone0/10Evidence shows ScrapingBee scrapes a given URL (with JS rendering, markdown output, extract_rules, ai_query) but nothing indicates a single API call that performs a web search and returns full page content for each result — the llms.txt probe mentions 'search' only in passing with no supporting detail. Missing for 10: any documented search endpoint, example combining query+results with full page bodies, or independent confirmation of this workflow.
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
- [probe] “PROBE llms.txt: HTTP 200 at https://www.scrapingbee.com/llms.txt # ScrapingBee Documentation > Official documentation index for ScrapingBee…”
Selector extraction
developerExtract specific fields from a page using CSS or XPath selector rules
weight 3 · round to ScrapingBeeFirecrawlnone0/10Evidence shows Firecrawl's extraction relies on schema-based/LLM extraction (firecrawl-gh-7) and general markdown/HTML/JSON output (firecrawl-docs-1), but nothing in the pack documents CSS or XPath selector-based field extraction rules. Missing for 10: any mention of CSS selector or XPath rule support in scrape/extract config, docs page confirming selector-based extraction, or independent confirmation of this capability.
- [github] “Use a schema to get structured data:”
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
Docs explicitly document extract_rules for CSS-based field extraction and confirm the headless browser waits on CSS/XPath selectors, directly supporting structured field extraction. missing for 10: no independent/hands-on corroboration of extraction accuracy or XPath-specific examples.
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
- [claimed-docs] “Our headless browsers will wait for the CSS / Xpath selector passed in the parameter before returning the HTML.”
Structured data handling
data-engineerExtract data from very large tables using intelligent chunking so it fits within processing limits
weight 1 · round drawnFirecrawlnone0/10No evidence pack items mention table extraction, large-table handling, or intelligent chunking strategies for oversized data; the evidence only covers general scraping, crawling, and structured extraction features. missing for 10: any mention of table-specific extraction, chunking mechanisms, or handling of oversized documents/tables to fit token/processing limits.
ScrapingBeenone0/10ScrapingBee's evidence covers web scraping features (JS rendering, proxies, extraction rules, AI queries) but nothing addresses handling very large tables, chunking data to fit processing/token limits, or pagination strategies for oversized datasets. Missing for 10: any mention of table extraction, chunking mechanism, size-limit handling, or pagination/splitting of large data outputs.
Js rendering — handling JavaScript-heavy pages — rendering, waiting, dynamic contentJs rendering
Handling JavaScript-heavy pages — rendering, waiting, dynamic content
Headless rendering
developerRender JavaScript-heavy single-page applications and get the fully rendered HTML
weight 3 · round to ScrapingBeeDocs confirm Firecrawl scrapes pages with an actual browser session ('Browser Sandbox... managed browser sessions for interactive workflows', 'click, fill forms, extract dynamic content'), and community evidence confirms it uses a real headless browser (Puppeteer) to render pages rather than static HTTP fetch, which supports JS-heavy SPA rendering. Output can be returned as HTML per docs-1. Missing for 10: independent benchmark/proof of correctly rendering complex SPAs, and community notes it uses Puppeteer not Playwright with some limitations in certain modes.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [claimed-docs] “Scrape a page, then keep working with it: click, fill forms, extract dynamic content, or navigate deeper.”
- [claimed-docs] “Browser Sandbox Managed browser sessions for interactive workflows”
- [community] “As I see, you use Puppeteer, not Playwright. Also, both Firecrawl and Firecrawl Simple are really simple, and most importantly don't have pr…”
ScrapingBee's docs explicitly describe headless-browser rendering of JS-heavy SPAs built with React/Angular/Vue/JQuery, with support for waiting on selectors and running JS scenarios before returning fully rendered HTML. This directly matches the story's core capability, though evidence lacks independent hands-on corroboration of rendering fidelity. Missing for 10: independent/hands-on verification of rendered output quality, benchmarks against specific SPA frameworks.
- [claimed-docs] “This can be useful for scraping a Single Page Application built with frameworks such as React.js, Angular.js, JQuery or Vue.”
- [claimed-docs] “If you want to interact with pages you want to scrape before we return your the HTML you can add JavaScript scenario to your API call.”
- [claimed-docs] “Our headless browsers will wait for the CSS / Xpath selector passed in the parameter before returning the HTML.”
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
developerHave the API wait for a specific selector to appear before returning the rendered page
weight 2 · round to ScrapingBeeFirecrawlnone0/10No evidence pack item mentions waiting for a specific CSS selector before returning rendered content; only general mentions of scraping, interactive actions, and browser sandboxing are present without detail on selector-based wait conditions.
ScrapingBee's docs explicitly state headless browsers wait for a CSS/XPath selector before returning HTML, directly matching the story. Missing for 10: independent/hands-on confirmation of this specific wait-for-selector behavior beyond vendor docs, and example code showing the parameter in use.
- [claimed-docs] “Our headless browsers will wait for the CSS / Xpath selector passed in the parameter before returning the HTML.”
- [claimed-docs] “If you want to interact with pages you want to scrape before we return your the HTML you can add JavaScript scenario to your API call.”
Interactive automation
developerAccess a managed remote browser sandbox for interactive, manual browsing workflows
weight 2 · round to FirecrawlFirecrawl docs explicitly mention a 'Browser Sandbox' offering managed browser sessions for interactive workflows, plus 'scrape, then keep working with it: click, fill forms, extract dynamic content' — directly matching the story. However, this is only a single doc snippet with no detail on session persistence, remote access UI, or manual/human-driven browsing versus API-driven automation, and no independent/community corroboration of this specific feature. Missing for 10: detailed documentation on session duration/access model, evidence of true manual/interactive human use (vs agent-driven), and third-party confirmation.
- [claimed-docs] “Browser Sandbox Managed browser sessions for interactive workflows”
- [claimed-docs] “Scrape a page, then keep working with it: click, fill forms, extract dynamic content, or navigate deeper.”
ScrapingBeenone0/10ScrapingBee's documentation describes a headless browser API for automated scraping (JS scenarios, screenshots, extraction rules) but no evidence of an interactive, manual remote-browser sandbox session a developer could drive by hand.
- [claimed-docs] “If you want to interact with pages you want to scrape before we return your the HTML you can add JavaScript scenario to your API call.”
- [claimed-docs] “Our headless browsers will wait for the CSS / Xpath selector passed in the parameter before returning the HTML.”
- [claimed-docs] “If you need to change the dimension of the browser's viewport (window) when scraping the target page you can use the `window_width` and `win…”
developerKeep interacting with an already-scraped page, clicking and filling forms to reach content behind a login wall
weight 2 · round to FirecrawlFirecrawl's docs explicitly describe an interactive workflow — 'Scrape a page, then keep working with it: click, fill forms, extract dynamic content, or navigate deeper' — plus a 'Browser Sandbox' for managed interactive browser sessions, directly matching the story. Missing for 10: independent/hands-on corroboration that clicking/filling forms actually reaches login-walled content, and more detail on session persistence across interactions.
- [claimed-docs] “Scrape a page, then keep working with it: click, fill forms, extract dynamic content, or navigate deeper.”
- [claimed-docs] “Browser Sandbox Managed browser sessions for interactive workflows”
ScrapingBee's JS 'scenario' feature lets you script click/fill actions before the page HTML is returned, and session_id lets you reuse the same IP across multiple API calls to preserve login state — enabling a login-wall workflow. However, evidence shows only a stateless-per-request model (scenario executed once, then HTML returned) rather than a persistent, continuously interactive browser session across multiple later calls. Missing for 10: documentation of a true persistent/interactive session object you can repeatedly command, and any hands-on confirmation this pattern reliably defeats login walls.
- [claimed-docs] “If you want to interact with pages you want to scrape before we return your the HTML you can add JavaScript scenario to your API call.”
- [claimed-docs] “Our headless browsers will wait for the CSS / Xpath selector passed in the parameter before returning the HTML.”
- [claimed-docs] “session_id [integer] ("") Route multiple API requests through the same IP address”
developerScript page interactions like clicking, filling inputs, and scrolling before content is returned
weight 3 · round to ScrapingBeeFirecrawl's docs explicitly describe scripting page interactions—click, fill forms, extract dynamic content, navigate deeper—after an initial scrape, and mention a managed Browser Sandbox for interactive workflows, directly matching the story of clicking/filling/scrolling before content is returned. Missing for 10: detailed API reference for the specific 'actions' parameter (e.g. scroll behavior), and independent/hands-on confirmation from community sources that these interaction primitives work reliably in practice.
- [claimed-docs] “Scrape a page, then keep working with it: click, fill forms, extract dynamic content, or navigate deeper.”
- [claimed-docs] “Browser Sandbox Managed browser sessions for interactive workflows”
ScrapingBee's docs explicitly describe a 'JavaScript scenario' feature to interact with pages (click, fill, scroll, etc.) before HTML is returned, plus wait-for-selector support to ensure content loads after interactions. This directly matches the story of scripting interactions before content is returned, though evidence lacks a full list of supported actions or independent hands-on confirmation. Missing for 10: detailed enumeration of supported interaction commands (click/fill/scroll) beyond generic 'JavaScript scenario' mention, and independent/community validation of this specific feature.
- [claimed-docs] “If you want to interact with pages you want to scrape before we return your the HTML you can add JavaScript scenario to your API call.”
- [claimed-docs] “Our headless browsers will wait for the CSS / Xpath selector passed in the parameter before returning the HTML.”
- [claimed-docs] “This can be useful for scraping a Single Page Application built with frameworks such as React.js, Angular.js, JQuery or Vue.”
Render configuration
developerControl the browser viewport width and height when rendering a page
weight 1 · round to ScrapingBeeFirecrawlnone0/10No evidence in the pack mentions viewport width/height, mobile emulation, or screen size configuration for rendering pages; the docs mention scraping, actions, and a browser sandbox but nothing about viewport control.
Official docs explicitly state window_width and window_height parameters let developers change the browser viewport dimensions when rendering the target page. missing for 10: no independent/hands-on corroboration beyond first-party docs.
- [claimed-docs] “If you need to change the dimension of the browser's viewport (window) when scraping the target page you can use the `window_width` and `win…”
Session persistence
developerPass my own session cookies so the API fetches pages requiring authentication
weight 2 · round drawnFirecrawlnone0/10No evidence pack item mentions passing custom cookies, headers, or session/auth tokens to Firecrawl's scrape API; only generic scraping, crawling, and browser-sandbox features are documented.
developerReuse a persistent browser profile with saved cookies and login state across multiple requests
weight 2 · round drawnFirecrawlnone0/10The evidence mentions a 'Browser Sandbox' for managed sessions and interactive workflows, but nothing describes persisting cookies/login state or reusing a browser profile across multiple separate requests. No docs, SDK, or community evidence confirms this capability.
- [claimed-docs] “Browser Sandbox Managed browser sessions for interactive workflows”
ScrapingBeenone0/10ScrapingBee's docs mention session_id only for routing requests through the same IP address, not for persisting cookies or login state across requests; no evidence of a saved browser profile or session state reuse mechanism.
- [claimed-docs] “session_id [integer] ("") Route multiple API requests through the same IP address”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to FirecrawlFirecrawl is fundamentally API-first — scrape, crawl, extract, search, and structured data features are all exposed via API/SDKs and docs, and there is no evidence of a rich standalone UI with capabilities withheld from the API. However, the evidence pack lacks a discoverable OpenAPI spec (probe found 404s) and does not explicitly confirm dashboard-only features (e.g., billing, team management, job monitoring) are also API-accessible. missing for 10: a published OpenAPI/swagger spec, explicit confirmation that all dashboard/UI-only functions (usage analytics, team/billing management, job history) are API-reachable, and independent verification of full UI/API parity.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [claimed-docs] “Search the web and get full page content from results in one call.”
- [claimed-docs] “Scrape a page, then keep working with it: click, fill forms, extract dynamic content, or navigate deeper.”
- [github] “Crawl an entire website and get content from all pages.”
- [github] “Scrape thousands of URLs asynchronously”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.firecrawl.dev/openapi.json, https://docs.firecrawl.dev/swagger.json, https://docs.firec…”
- [probe] “official CLI documented at https://docs.firecrawl.dev/sdks/cli”
ScrapingBee is API-first, and the docs show an extensive, feature-rich API surface (JS rendering, screenshots, extraction rules, AI query, proxies, session control) covering essentially all scraping functionality (scrapingbee-docs-1 through 15). However, there is no explicit statement comparing the API's capabilities to what's available in ScrapingBee's dashboard/UI, so full parity can't be confirmed from evidence. Missing for 10: explicit UI-vs-API feature parity documentation, confirmation that dashboard-only tools (e.g. request builder, account settings) have no capabilities absent from the API.
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
- [claimed-docs] “If you want to interact with pages you want to scrape before we return your the HTML you can add JavaScript scenario to your API call.”
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
- [claimed-docs] “screenshot_selector [string] ("") Return a screenshot of a particular area of the page, targeted by a CSS selector”
ai-native userExport all of my data in open formats and leave
weight 3 · round to FirecrawlFirecrawl outputs are natively in open formats (markdown, HTML, structured JSON) and the core engine is open source (AGPL-3.0), letting a user self-host and avoid lock-in to the hosted service. However there's no explicit 'export all your account/config data' feature documented, and community notes only touch on forking rights, not a formal data-export path. Missing for 10: a documented account-data export/migration flow, evidence of exporting crawl history/settings, and independent confirmation users have actually migrated off the hosted service.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [github] “Firecrawl is open source under the AGPL-3.0 license. The cloud version at firecrawl.dev includes additional features”
- [community] “Finally, people starting to realize that AGPL means you can just fork and remove everything you don't like (including branding).”
ScrapingBee returns scraped content in open formats such as raw HTML, JSON (extract_rules) and Markdown (return_page_markdown), so output data is not locked into a proprietary format. However, there is no evidence of account-level data export, no mention of stored user data portability, and no explicit 'leave anytime with your data' commitment—since it's a stateless scraping API, the 'export and leave' framing only partially applies. Missing for 10: account/usage data export tooling, explicit data-portability statement, independent confirmation of format openness beyond docs.
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
- [claimed-docs] “return_page_markdown [boolean] (false) Return the page content in markdown format”
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
ai-native userRead the product's source under an open license
weight 2 · round to FirecrawlFirecrawl's GitHub repo confirms it is open source under the AGPL-3.0 license, with community discussion also confirming this (including implications of AGPL forking rights). Source is publicly readable on GitHub with an OSI-approved-family open license. Missing for 10: no evidence of clarity on which parts of the cloud-only features are excluded from the open license, and no independent audit of full repo completeness.
- [github] “Firecrawl is open source under the AGPL-3.0 license. The cloud version at firecrawl.dev includes additional features”
- [community] “Finally, people starting to realize that AGPL means you can just fork and remove everything you don't like (including branding).”
ScrapingBeenone0/10No evidence ScrapingBee's core product source is available under an open license; it is a closed, paid SaaS API. A community comment even asks whether the vendor plans to open source any part of their stack, implying it currently is not.
- [community] “Any plans on open sourcing any part of your stack instead of relying on paid services like ScrapingBee? What does your SaaS setup look like?”
ai-native userSelf-host the core product
weight 3 · round to FirecrawlFirecrawl's GitHub repo confirms the core product is open source under AGPL-3.0 and can be self-hosted, with the hosted cloud version offering extra features (firecrawl-gh-6). However, community reports note self-hosted/simple versions lack key production features like proxy support and have functional limitations (e.g., daemon mode restrictions, no HTML return) compared to the cloud offering (firecrawl-comm-3, firecrawl-comm-4). Missing for 10: official self-hosting setup docs/guide in the evidence pack, and confirmation that self-hosted deployment achieves full feature parity with the hosted service.
- [github] “Firecrawl is open source under the AGPL-3.0 license. The cloud version at firecrawl.dev includes additional features”
- [community] “As I see, you use Puppeteer, not Playwright. Also, both Firecrawl and Firecrawl Simple are really simple, and most importantly don't have pr…”
- [community] “It being vibe coded aside, does it support screenshots? I noticed the daemon mode has a lot of weird limitations too like not being able to …”
ScrapingBeenone0/10ScrapingBee is a hosted SaaS API; no evidence of any self-hostable core product, on-premise deployment option, or open-source release. Community comment explicitly asks whether ScrapingBee plans to open-source its stack, with no vendor response indicating such an offering exists.
- [community] “Any plans on open sourcing any part of your stack instead of relying on paid services like ScrapingBee? What does your SaaS setup look like?”
- [community] “Have you looked at running something locally instead of paying for ScrapingBee? I'm using Laravel and considering Dusk to retrieve page cont…”
Output formats — stories about output formats in this arenaOutput formats
Stories about output formats in this arena
Content formats
developerReceive scraped content as clean markdown instead of raw HTML
weight 3 · round to FirecrawlFirst-party docs explicitly state extraction as markdown (alongside HTML/JSON) and support converting local files to markdown, confirming clean markdown output is a core, well-documented feature. Missing for 10: independent hands-on confirmation specifically praising markdown output quality/cleanliness.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [claimed-docs] “Turn local PDFs, DOCX, XLSX, HTML, and more into Markdown or structured JSON”
ScrapingBee's docs explicitly offer a `return_page_markdown` parameter to return page content as markdown instead of raw HTML, directly matching the story. Missing for 10: independent/hands-on confirmation of markdown output quality and any community corroboration of this specific feature.
- [claimed-docs] “return_page_markdown [boolean] (false) Return the page content in markdown format”
developerChoose exactly which output format is returned, such as markdown, HTML, text, or frontmatter
weight 2 · round drawnDocs confirm output as markdown, HTML, or structured JSON (firecrawl-docs-1, firecrawl-docs-6), and a community comment notes a daemon-mode limitation where HTML return is unsupported in some contexts, suggesting partial reliability. No explicit mention of 'frontmatter' or 'text' formats, and no documentation snippet showing a format-selection parameter/API example. Missing for 10: explicit mention of frontmatter/text format options, and a documented parameter/example showing developers selecting formats.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [claimed-docs] “Turn local PDFs, DOCX, XLSX, HTML, and more into Markdown or structured JSON”
- [community] “It being vibe coded aside, does it support screenshots? I noticed the daemon mode has a lot of weird limitations too like not being able to …”
Docs confirm HTML is the default output and a dedicated `return_page_markdown` parameter lets developers get markdown instead, but there's no documented option for a plain-text-only extraction or a frontmatter output format, and extract_rules/ai_query only allow custom JSON-style extraction, not those specific formats. Missing for 10: explicit plain-text output mode, frontmatter output support, independent confirmation of format switching.
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
- [claimed-docs] “return_page_markdown [boolean] (false) Return the page content in markdown format”
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
developerReceive scraped content as structured JSON
weight 3 · round to FirecrawlFirecrawl docs explicitly support extracting content as structured JSON, including with a defined schema, alongside markdown/HTML options, and this extends to document formats like PDFs/DOCX as well. Missing for 10: independent hands-on confirmation of JSON output quality/schema fidelity beyond vendor docs and GitHub README.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [github] “Use a schema to get structured data:”
- [claimed-docs] “Turn local PDFs, DOCX, XLSX, HTML, and more into Markdown or structured JSON”
ScrapingBee offers extract_rules for CSS-selector-based structured data extraction and ai_query for AI-driven extraction, plus return_page_markdown for markdown output, indicating structured output beyond raw HTML. However, there's no explicit documented 'return as JSON' toggle or example showing a full JSON schema response, and no independent/community confirmation of structured JSON output quality. Missing for 10: explicit JSON output examples/schema, independent verification of structured JSON extraction reliability.
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
- [claimed-docs] “return_page_markdown [boolean] (false) Return the page content in markdown format”
Llm ready output
ai-native userGet clean LLM-ready text directly instead of dealing with blocking, rendering, and messy HTML myself
weight 3 · round to FirecrawlFirecrawl's core value proposition is turning any URL into clean markdown/structured JSON, handling rendering, JS-heavy pages, and blocking via a managed browser sandbox, explicitly for LLM/RAG use cases. Docs and GitHub confirm markdown/HTML/JSON extraction, PDF/DOCX conversion, and managed browser sessions abstracting away rendering complexity, though community comments note some limitations (e.g., proxy/anti-bot gaps, missing HTML in some modes). Missing for 10: independent benchmark of output cleanliness vs raw HTML scraping, and resolution of community-reported edge-case limitations (daemon mode HTML issue).
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [claimed-docs] “Scrape a page, then keep working with it: click, fill forms, extract dynamic content, or navigate deeper.”
- [claimed-docs] “Turn local PDFs, DOCX, XLSX, HTML, and more into Markdown or structured JSON”
- [claimed-docs] “Browser Sandbox Managed browser sessions for interactive workflows”
- [github] “Crawl an entire website and get content from all pages.”
- [community] “It being vibe coded aside, does it support screenshots? I noticed the daemon mode has a lot of weird limitations too like not being able to …”
ScrapingBee offers return_page_markdown to get markdown output plus ai_query for AI-driven extraction and premium proxies/JS rendering to avoid blocking, directly addressing the LLM-ready text need. However, evidence doesn't show a dedicated 'clean text extraction' mode beyond markdown/extract_rules, and no independent benchmarks confirm output quality for LLM consumption. missing for 10: independent validation of markdown/text cleanliness, dedicated boilerplate-removal/reader-mode feature, hands-on confirmation from users of LLM-ready output.
- [claimed-docs] “return_page_markdown [boolean] (false) Return the page content in markdown format”
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
- [claimed-docs] “premium_proxy [boolean] (false) Use premium proxies to bypass difficult to scrape websites”
- [claimed-docs] “Our headless browsers will wait for the CSS / Xpath selector passed in the parameter before returning the HTML.”
ai-native userRequest semantically chunked output instead of one large content blob, so it feeds cleanly into a retrieval pipeline
weight 2 · round drawnFirecrawlnone0/10Firecrawl's evidence covers markdown/HTML/structured JSON extraction, crawling, and PDF/DOCX conversion, but nothing describes a semantic chunking feature or chunked output mode for retrieval pipelines. The axis applies (chunked output is a plausible feature for a scraping/RAG-prep tool) but no evidence shows it exists.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [claimed-docs] “Turn local PDFs, DOCX, XLSX, HTML, and more into Markdown or structured JSON”
- [github] “Use a schema to get structured data:”
ScrapingBeenone0/10ScrapingBee offers markdown conversion, CSS-based extraction rules, and AI query extraction, but no evidence of semantic/chunked output splitting content into retrieval-ready segments. The docs list output options (HTML, markdown, screenshots, extract_rules) but never mention chunking or segmenting content for RAG pipelines.
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
- [claimed-docs] “return_page_markdown [boolean] (false) Return the page content in markdown format”
Visual capture
developerCapture a screenshot of a full page or a specific selected area
weight 2 · round to ScrapingBeeFirecrawlnone0/10The evidence pack lists output formats as markdown/HTML/JSON but never mentions screenshot capture, full-page or selector-based, as a capability. A community comment even raises it as an open question ('does it support screenshots?') without confirmation, so there's no evidence the capability exists.
- [claimed-docs] “Extract content from any URL as markdown, HTML, or structured JSON”
- [community] “It being vibe coded aside, does it support screenshots? I noticed the daemon mode has a lot of weird limitations too like not being able to …”
Docs confirm a `screenshot_selector` parameter for capturing a specific CSS-selected area of a page, directly supporting selected-area screenshots. However, no evidence explicitly documents a full-page screenshot parameter or option, so only half the story is substantiated. Missing for 10: explicit full-page screenshot parameter/documentation, independent/hands-on confirmation of screenshot output quality.
- [claimed-docs] “screenshot_selector [string] ("") Return a screenshot of a particular area of the page, targeted by a CSS selector”
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits
Free-tier ceilings, usage caps, and rate limits before you have to pay
Cost optimization
developerLet the API automatically pick the cheapest configuration that still succeeds
weight 2 · round to ScrapingBeeFirecrawlnone0/10No evidence of automatic cost-optimal configuration selection; docs mention manual controls like reasoning effort but nothing about the API choosing cheapest successful config automatically.
ScrapingBee's docs explicitly describe a `mode=auto` parameter that lets the API pick the cheapest configuration that still succeeds, directly matching the story. This is first-party documented evidence, though there's no independent/hands-on corroboration of its effectiveness. Missing for 10: independent verification that auto mode reliably picks the cheapest successful config in practice.
- [claimed-docs] “mode [string] ("") Let ScrapingBee pick the cheapest configuration that succeeds. Only value is auto”
developerBlock ads on the target page to speed up scraping requests
weight 1 · round to ScrapingBeeFirecrawlnone0/10No evidence pack item mentions ad-blocking or any option to strip ads/trackers on target pages to speed up scraping; only general scraping, crawling, and extraction features are documented.
Official docs explicitly document the `block_ads=true` parameter to prevent ad loading and speed up scraping requests, directly matching the story. Missing for 10: independent/hands-on corroboration of the speed benefit and no third-party benchmark confirming the claim.
- [claimed-docs] “By default, ScrapingBee does not block ads. To avoid scraping them (e.g.,to speed up your request), use `block_ads=true`”
developerBlock images and CSS resources by default to reduce bandwidth and speed up requests
weight 1 · round to ScrapingBeeFirecrawlnone0/10No evidence pack mentions blocking images or CSS resources, resource-type filtering, or bandwidth-saving scrape options; only general scraping/crawling features are documented.
Official docs explicitly state ScrapingBee blocks all images and CSS by default to speed up requests, with an opt-out via block_resources=false, directly matching the story. Missing for 10: independent/hands-on corroboration beyond vendor docs.
- [claimed-docs] “By default, and to speed up requests, ScrapingBee blocks all images and CSS in the scraped page, but to scrape them, use `block_resources=fa…”
ai-native userSet how much reasoning effort an autonomous agent spends on a data-gathering task (low, medium, high)
weight 2 · round to FirecrawlGitHub README explicitly states the agent lets users 'set how much reasoning the agent spends on the task,' directly matching the story, but there's no detailed documentation confirming discrete low/medium/high levels or pricing-tied reasoning-effort controls. Missing for 10: first-party docs specifying the exact reasoning-effort parameter/levels, independent confirmation of how this affects cost/limits.
Cost transparency
developerWhether exceeding my plan's monthly credit or request quota triggers overage charges or a hard cutoff
weight 3 · round drawnFirecrawlnone0/10No evidence in the pack addresses billing behavior when a plan's credit/request quota is exceeded — nothing on overage charges vs. hard cutoffs. This is a fair pricing question for a paid API product, so absence of evidence yields none. Missing for 10: any pricing/billing docs describing quota overage policy, hard-stop vs auto-billing behavior, or community reports confirming either.
developerWhether failed, blocked, or empty-result requests still consume my billing quota
weight 2 · round drawnFirecrawlnone0/10No evidence pack items discuss billing/credit treatment for failed, blocked, or empty-result requests; documentation snippets cover features (scrape, crawl, MCP, webhooks) but not quota/credit consumption policy.
ScrapingBeenone0/10The evidence pack contains no documentation or discussion of billing behavior for failed, blocked, or empty-result requests—no mention of credit refunds, only-charge-on-success policies, or how failed/blocked scrapes affect quota consumption. Community comments discuss cost/pricing generally but not this specific billing mechanic.
developerSet a spending cap or usage alert so proxy/credit consumption doesn't silently blow past my budget
weight 3 · round drawnFirecrawlnone0/10No evidence of spending caps, budget alerts, or usage-limit notifications; community comments even describe unexpectedly high consumption ('10gb of proxy gone in two days') with no mention of a cap/alert mechanism to prevent overage.
- [community] “same setup here for news pages. tier 3 is where my money went, 320 solves a day and 10gb of proxy gone in two days.”
- [community] “Quite useful. Currently we do overpay for the services [referring to Firecrawl-like scraping services].”
ScrapingBeenone0/10No evidence of any spending cap, usage alert, or budget notification feature in ScrapingBee's docs or community reports; community comments even highlight cost as a pain point without mentioning any budget-control tooling.
- [community] “Using ScrapingBee is expensive; I've brought the cost of a CRM creation down to about 1.5 cents (+3 cents for a custom cover image) by looki…”
Performance tuning
developerTrade off latency against completeness by controlling exactly when content is returned
weight 1 · round to ScrapingBeeFirecrawl offers async webhooks for event delivery and an agent 'reasoning effort' setting that trades speed for thoroughness, plus async bulk scraping — all of which let a developer influence when/how much content comes back, but there's no explicit documented parameter (e.g., wait-time or completeness threshold) framed as a direct latency-vs-completeness control on the standard scrape/crawl endpoints. missing for 10: explicit sync-return timeout/partial-completeness parameter, independent benchmarking of latency vs completeness tradeoffs, and hands-on confirmation of the reasoning-effort knob's effect.
- [github] “Set how much reasoning the agent spends on the task”
- [claimed-docs] “Webhooks Async event delivery”
- [github] “Scrape thousands of URLs asynchronously”
ScrapingBee lets developers control timing/completeness tradeoffs via wait-for-selector, JS scenarios, block_ads/block_resources flags, and an 'auto' mode that picks the cheapest successful configuration, giving direct levers over latency vs. completeness. However, this is all documented capability with no independent benchmarking or hands-on confirmation of actual latency impact. Missing for 10: independent/hands-on verification of latency-completeness tradeoffs, explicit 'wait' or timeout parameter documentation, and real-world performance data beyond vendor docs.
- [claimed-docs] “If you want to interact with pages you want to scrape before we return your the HTML you can add JavaScript scenario to your API call.”
- [claimed-docs] “Our headless browsers will wait for the CSS / Xpath selector passed in the parameter before returning the HTML.”
- [claimed-docs] “By default, ScrapingBee does not block ads. To avoid scraping them (e.g.,to speed up your request), use `block_ads=true`”
- [claimed-docs] “By default, and to speed up requests, ScrapingBee blocks all images and CSS in the scraped page, but to scrape them, use `block_resources=fa…”
- [claimed-docs] “mode [string] ("") Let ScrapingBee pick the cheapest configuration that succeeds. Only value is auto”
Plan scale limits
data-engineerThe maximum concurrent sessions or requests allowed on my pricing tier and the cost to raise that cap
weight 2 · round drawnFirecrawlnone0/10No evidence pack item documents rate limits, concurrency caps per pricing tier, or the cost to raise them; only unrelated product feature docs and community anecdotes about usage cost are present. missing for 10: documented per-tier concurrency/request limits, documented pricing to upgrade limits, any rate-limit or quota API reference.
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnFirecrawlnone0/10No evidence in the pack mentions data residency, regional storage options, or compliance controls for where scraped data is processed/stored; the open-source AGPL version could theoretically be self-hosted for residency control, but this is not documented anywhere in the evidence.
ScrapingBeenone0/10Evidence covers proxy geolocation for scraping targets (country_code) but no mention of data residency or storage region controls for ScrapingBee's own data handling/storage; no privacy/compliance documentation is present. Missing for 10: any documentation of data storage regions, residency options, or compliance certifications (e.g., EU data hosting).
- [claimed-docs] “country_code [string] ("") Premium proxy geolocation”
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnFirecrawlnone0/10No evidence pack item mentions any data-training opt-out, privacy policy on model training use, or data retention/DPA controls for Firecrawl's scraped or user data; the only related community comment raises concerns about scraping others' data, not about protecting the user's own data from AI training use.
ai-native userControl data retention and deletion
weight 2 · round drawnFirecrawlnone0/10No evidence pack item mentions data retention policies, deletion controls, or privacy settings for stored crawl/scrape data; this is a fair question for a cloud scraping/data API but no documentation addresses it.
ScrapingBeenone0/10No evidence in the pack addresses data retention policies, deletion controls, or privacy/data lifecycle management for ScrapingBee; documentation excerpts focus solely on scraping features and API parameters. Missing for 10: any mention of data retention windows, deletion APIs/requests, privacy policy details, or compliance certifications.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnFirecrawlnone0/10No evidence in the pack mentions telemetry, usage tracking, analytics collection, or an opt-out setting/flag for Firecrawl's CLI, SDK, or self-hosted deployment; while the open-source AGPL nature suggests self-hosting is possible, nothing documents a telemetry toggle or privacy control.
Scale reliability — behavior under load — scaling limits, uptime, failure handlingScale reliability
Behavior under load — scaling limits, uptime, failure handling
Ai driven crawling
ai-native userRely on adaptive crawling that automatically stops once enough information has been gathered to answer my query
weight 2 · round drawnFirecrawlnone0/10The evidence describes crawling, scraping, and AI agent search/reasoning controls (e.g., firecrawl-gh-1, firecrawl-gh-2), but nothing documents adaptive crawling that automatically halts once sufficient information has been gathered to answer a specific query — crawls appear to run to full site discovery or fixed limits rather than stopping based on information sufficiency.
ScrapingBeenone0/10ScrapingBee's docs describe single-page scraping, AI-based extraction (ai_query), and cost-optimizing 'auto' mode, but there is no evidence of adaptive multi-step crawling that dynamically decides when enough information has been gathered to stop. No crawling/agentic loop or stopping-criteria feature is documented.
- [claimed-docs] “ai_query [string] ("") The information you want to extract from the webpage using AI”
- [claimed-docs] “mode [string] ("") Let ScrapingBee pick the cheapest configuration that succeeds. Only value is auto”
Batch processing
data-engineerBatch scrape thousands of URLs asynchronously
weight 3 · round to FirecrawlFirecrawl's GitHub docs explicitly advertise batch/async scraping of thousands of URLs, plus webhook-based async event delivery for pipeline integration, and crawl/map endpoints for URL discovery at scale, aligning well with the data-engineer scale story. Missing for 10: independent hands-on benchmarks proving reliability at thousands-of-URL scale and details on rate limits/retry/error handling under batch load.
- [github] “Scrape thousands of URLs asynchronously”
- [claimed-docs] “Webhooks Async event delivery”
- [github] “Crawl an entire website and get content from all pages.”
- [github] “Discover all URLs on a website instantly.”
ScrapingBeenone0/10The evidence pack only documents single-URL synchronous scraping API parameters (JS rendering, extraction rules, proxies, screenshots) with no mention of batch job submission, async processing, concurrency limits, or a queue/webhook system for handling thousands of URLs at scale.
developerApply different crawl configurations to different URL patterns within a single batch job
weight 1 · round drawnFirecrawlnone0/10The evidence pack covers crawling, scraping, extraction, webhooks, and CLI/MCP features, but nothing describes per-URL-pattern configuration overrides within a single crawl/batch job (e.g., different scrape options for different path patterns). No docs or community evidence mention such rule-based configuration.
ScrapingBeenone0/10ScrapingBee's API is per-URL request based with configuration parameters set per call; there is no evidence of a 'batch job' concept or a way to define per-URL-pattern rules within a single job. The docs describe single-page scraping options (JS scenario, extract_rules, proxies, etc.) but nothing about batch jobs with pattern-based configuration.
Concurrency
data-engineerSpin up many concurrent scraping sessions to gather data at scale
weight 3 · round to FirecrawlFirecrawl explicitly supports scraping 'thousands of URLs asynchronously' and full-site crawling with async webhooks for event delivery, which supports scaling to many concurrent scrape jobs. However, there is no documentation of concurrency limits, session management, or dedicated infrastructure for spinning up many parallel sessions, and community feedback raises cost/efficiency concerns at scale (proxy usage, cost overpay) without directly disputing the concurrency capability itself. Missing for 10: explicit concurrency/rate-limit documentation, first-party benchmarks or case studies of large-scale concurrent scraping, and independent verification of scale claims.
- [github] “Scrape thousands of URLs asynchronously”
- [github] “Crawl an entire website and get content from all pages.”
- [claimed-docs] “Webhooks Async event delivery”
- [community] “same setup here for news pages. tier 3 is where my money went, 320 solves a day and 10gb of proxy gone in two days.”
- [community] “I made newsagents.app and I ended up using the extract API from kagi and falling back to cloudflare's browser API for problem pages. That lo…”
ScrapingBee is inherently an API you can call many times, and docs mention session_id for routing multiple requests through the same IP, but the evidence pack contains no explicit documentation of concurrency limits, parallel-request quotas, or scaling architecture for high-volume data-engineering workloads. Missing for 10: explicit concurrency/rate-limit specs, documented plan-based concurrent request caps, and independent evidence of successful large-scale concurrent scraping.
- [claimed-docs] “session_id [integer] ("") Route multiple API requests through the same IP address”
- [claimed-docs] “premium_proxy [boolean] (false) Use premium proxies to bypass difficult to scrape websites”
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
Crawl compliance
data-engineerConfigure the crawler to respect robots.txt rules and target-site rate limits automatically
weight 2 · round drawnFirecrawlnone0/10No documentation or evidence describes robots.txt compliance settings or automatic rate-limit throttling; the only related community comment (firecrawl-comm-8) suggests sites must proactively disallow the crawler, which doesn't confirm built-in respect for robots.txt as a configurable, automatic behavior.
- [community] “Excellent, another kind of copyright theft as a service that assumes your site is ripe for scraping unless you disallow yet another agent (F…”
Fault tolerance
data-engineerResume a crashed deep crawl from a saved checkpoint instead of restarting from scratch
weight 2 · round drawnFirecrawlnone0/10No evidence of checkpointing or resuming crawls from saved state; docs mention crawling, webhooks, and async scraping but nothing about crash recovery or resumable checkpoints.
Operational transparency
data-engineerCheck a public status page showing uptime history and past incident postmortems before committing to the service
weight 2 · round drawnFirecrawlnone0/10No evidence pack item mentions a public status page, uptime history, or incident postmortems for Firecrawl; the docs and community threads cover product features and complaints but nothing about SLA/uptime transparency.
Scheduling monitoring
data-engineerMonitor target pages for content changes, such as price or listing updates, and get notified as they happen
weight 2 · round drawnFirecrawlnone0/10The evidence pack shows scraping, crawling, extraction, and webhook-based async event delivery, but no dedicated change-tracking/monitoring feature (e.g., diffing pages over time, price/listing change alerts) is documented anywhere in the pack.
- [claimed-docs] “Webhooks Async event delivery”
- [github] “Crawl an entire website and get content from all pages.”
- [github] “Scrape thousands of URLs asynchronously”
ScrapingBeenone0/10ScrapingBee is an on-demand scraping API (fetch a page, extract data, render JS) with no evidence of scheduled monitoring, change-detection, diffing, or notification/webhook features for tracking content changes over time. The evidence pack only covers single-request scraping parameters, proxies, and rendering options, not continuous monitoring or alerting.
data-engineerMonitor job performance, validate data quality, and receive alerts when something fails
weight 2 · round drawnFirecrawlnone0/10Evidence shows webhooks for async event delivery but nothing about job performance dashboards, data quality validation, or failure alerting mechanisms for a data-engineering monitoring workflow.
developerMonitor live system metrics and worker/browser pool status through a real-time dashboard
weight 1 · round drawnFirecrawlnone0/10No evidence of a real-time dashboard for monitoring system metrics, worker pool, or browser pool status; evidence only covers scraping/crawling features, CLI, MCP server, and community discussion unrelated to monitoring dashboards.
developerSchedule scraping jobs to run automatically at specific times
weight 2 · round drawnFirecrawlnone0/10No evidence of scheduled/cron-based scraping jobs; Firecrawl's evidence covers crawling, scraping, webhooks, and async batch scraping, but nothing about scheduling jobs to run at specific times.
Site crawling
data-engineerRun a deep crawl using a breadth-first strategy with a configurable maximum page limit
weight 2 · round to FirecrawlEvidence confirms Firecrawl can crawl an entire website and discover all URLs (firecrawl-gh-3, firecrawl-gh-4), which implies a crawl feature suitable for a data-engineer's bulk scraping needs, but nothing in the pack explicitly documents a breadth-first crawl strategy or a configurable maximum page limit parameter. Missing for 10: explicit mention of BFS traversal mode, documented maxPages/limit parameter, and independent confirmation that these controls work at scale.
ScrapingBeenone0/10ScrapingBee's documented API is per-page scraping (single URL requests with rendering, extraction, proxy options) with no evidence of a crawl orchestration feature supporting breadth-first traversal or a configurable max-page limit for multi-page crawls.
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
- [claimed-docs] “extract_rules [stringified JSON] ("") Data extraction from CSS selectors”
developerCrawl an entire website and get content from all its pages with one request
weight 3 · round to FirecrawlGitHub docs explicitly state 'Crawl an entire website and get content from all pages' with supporting features like URL discovery and async scraping of thousands of URLs, directly matching the story. Missing for 10: independent hands-on validation specifically of full-site crawl completeness/reliability at scale (community comments discuss cost/proxy issues but not crawl-completeness failures).
ScrapingBeenone0/10ScrapingBee's API is designed for single-page scraping requests (one URL per call); the evidence shows no crawler feature that follows links across a domain or aggregates content from multiple pages in one request. No mention of a 'crawl' endpoint, sitemap traversal, or multi-page job in a single API call.
- [claimed-docs] “To scrape a web page, you only need two things: Your API key... The encoded web page URL you want to scrape”
- [claimed-docs] “This can be useful for scraping a Single Page Application built with frameworks such as React.js, Angular.js, JQuery or Vue.”
developerInstantly discover all URLs on a website without fully crawling it
weight 2 · round to FirecrawlFirecrawl explicitly offers a 'Map' capability described as 'Discover all URLs on a website instantly,' distinct from full crawling, directly matching the story. This is a first-party GitHub claim but lacks independent hands-on corroboration or detail on accuracy/limits at scale. missing for 10: independent/hands-on verification of speed and completeness, documentation of limits on very large sites.
ScrapingBeenone0/10ScrapingBee's evidence covers page scraping, JS rendering, extraction rules, proxies, and AI queries, but nothing describes a sitemap/URL-discovery feature that lists all URLs on a site without crawling each page. No sitemap parsing, URL enumeration, or site-mapping endpoint is documented.
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableFirecrawln/aFirecrawl is a web-scraping/crawling API/service that itself exposes an MCP server for other AI tools to consume (firecrawl-docs-5, firecrawl-probe-3); it is not an agent or orchestration platform designed to consume external MCP servers as a client. The evidence pack shows no capability for Firecrawl to import/plug in third-party MCP servers to extend its own tool use, and this is not a fair capability to expect of a scraping API — it's the reverse role.
- [claimed-docs] “MCP Server: Connect Firecrawl to any AI tool via the Model Context Protocol”
- [probe] “official MCP server documented at https://github.com/mendableai/firecrawl-mcp-server”
ScrapingBeen/aScrapingBee is a web-scraping API/SaaS product, not an agent or orchestration platform that would itself consume other MCP servers' tools; evidence only shows it exposes its own MCP server (mcp.scrapingbee.com), i.e., it is the tool provider, not a tool consumer. Plugging external MCP servers into ScrapingBee to gain their tools is a category error for this kind of product.
- [probe] “official MCP server documented at https://mcp.scrapingbee.com/”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableFirecrawlnone0/10Firecrawl is a web scraping/extraction API and toolset; there is no evidence of automation versioning, review workflows, or rollback capabilities for crawl/scrape configurations or workflows in any of the docs, GitHub, or community sources.