ScrapingBee vs Browserbase
ScrapingBee
ScrapingBee
ScrapingBee wins · 26–22 (46 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 BrowserbaseScrapingBee 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/”
A direct probe confirms llms.txt is live at https://docs.browserbase.com/llms.txt returning HTTP 200 with structured agent-oriented content describing the platform, and this is reinforced by extensive agent-oriented docs content across the docs site. missing for 10: no independent third-party confirmation of agents actually consuming/using the llms.txt file in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.browserbase.com/llms.txt # Browserbase Documentation > Browserbase is the Browser Agent Platform: …”
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “The SDK for browser agents. Natural language selectors, self-healing actions, and caching at scale.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to BrowserbaseScrapingBee 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”
Browserbase is explicitly built for programmatic, headless browser sessions accessible via API/SDK, with docs describing scheduling agents to run 'on a schedule or on demand' and spinning up thousands of concurrent sessions — a core CI/automation use case. missing for 10: independent hands-on CI integration examples/case studies and explicit CI-provider (GitHub Actions, etc.) documentation.
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
- [claimed-docs] “Spin up thousands of concurrent browser sessions and return answers immediately”
- [claimed-docs] “Deploy and run browser agents on Browserbase, on a schedule or on demand.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.browserbase.com/llms.txt # Browserbase Documentation > Browserbase is the Browser Agent Platform: …”
ai-native userConnect an agent via an official MCP server
weight 3 · round to BrowserbaseScrapingBee 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/”
Browserbase documents an official MCP server integration allowing agents to connect directly, confirmed by probe evidence at docs.browserbase.com/integrations/mcp/introduction. Missing for 10: independent/hands-on confirmation of MCP server usage and more detail on setup/config beyond the doc link.
- [probe] “official MCP server documented at https://docs.browserbase.com/integrations/mcp/introduction”
ai-native userUse an official CLI
weight 2 · round to ScrapingBeeEvidence 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”
There's a documented official CLI ('browse-cli') referenced in probe evidence, but the pack lacks detailed first-party documentation content (installation, commands, usage examples) or independent/community corroboration of its use. missing for 10: detailed CLI docs/commands, independent hands-on validation, broader community adoption evidence.
- [probe] “official CLI documented at https://docs.browserbase.com/integrations/skills/browse-cli”
ai-native userDrive the product through a documented public API
weight 3 · round drawnScrapingBee'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…”
Browserbase documents a public API for creating/controlling/observing browser sessions programmatically, with an llms.txt confirming API-key-based agent access, plus SDKs and integrations (MCP, CLI) built on top of it. Missing for 10: a discoverable OpenAPI/swagger spec (probe found only 404s) and independent third-party confirmation of API robustness beyond vendor docs.
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.browserbase.com/llms.txt # Browserbase Documentation > Browserbase is the Browser Agent Platform: …”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.browserbase.com/openapi.json, https://docs.browserbase.com/swagger.json, https://docs.b…”
- [probe] “official MCP server documented at https://docs.browserbase.com/integrations/mcp/introduction”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnScrapingBeenone0/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 …”
Browserbasenone0/10No evidence of scoped or least-privilege API key/credential issuance; the only relevant probe explicitly states Browserbase uses a single broad API key ('one API key gives your agent everything it needs'), suggesting no fine-grained scoping exists.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.browserbase.com/llms.txt # Browserbase Documentation > Browserbase is the Browser Agent Platform: …”
ai-native userBuild against official SDKs
weight 2 · round to BrowserbaseScrapingBeenone0/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.
Browserbase documents official SDKs and APIs for programmatic session control, plus a dedicated 'Stagehand' SDK for browser agents and a TypeScript-first agent framework, backed by extensive first-party docs. Missing for 10: independent/hands-on developer corroboration of SDK quality and a discoverable OpenAPI spec (probe found 404s), which limits confidence beyond vendor docs.
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
- [claimed-docs] “The SDK for browser agents. Natural language selectors, self-healing actions, and caching at scale.”
- [claimed-docs] “TypeScript-first agent framework with built-in Browserbase support.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.browserbase.com/llms.txt # Browserbase Documentation > Browserbase is the Browser Agent Platform: …”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.browserbase.com/openapi.json, https://docs.browserbase.com/swagger.json, https://docs.b…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnScrapingBeenone0/10No evidence of any webhook subscription or event notification system in ScrapingBee's documentation; all evidence covers synchronous scraping API parameters, proxies, and rendering options with no mention of webhooks or event-driven callbacks.
Browserbasenone0/10No evidence pack item mentions webhooks or event subscription mechanisms; docs focus on session control, agent frameworks, and scraping but never describe a webhook/event system. This is a fair capability for a browser automation platform (e.g. session status events), so absence of evidence yields 'none' rather than 'na'.
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to ScrapingBeeScrapingBee'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 BrowserbaseScrapingBeenone0/10ScrapingBee is an on-demand scraping API/CLI/MCP server; evidence shows only synchronous request-response scraping calls, with no scheduling, triggers, or background job/automation orchestration features documented.
Docs explicitly describe deploying browser agents 'on a schedule or on demand,' plus session-scaling and monitoring use cases (uptime checks, price/job tracking) that imply persistent background automation. missing for 10: independent/hands-on confirmation of scheduling reliability and details on failure alerting/retry mechanisms.
- [claimed-docs] “Deploy and run browser agents on Browserbase, on a schedule or on demand.”
- [claimed-docs] “Run agents that click through your product continuously and alert you the moment something breaks.”
- [claimed-docs] “Track prices, job listings, product changes, and competitor moves as they happen.”
- [claimed-docs] “Spin up thousands of concurrent browser sessions and return answers immediately”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnScrapingBeenone0/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 userOperate the product with natural-language commands
weight 2 · round drawnScrapingBee'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/”
Browserbase's Stagehand SDK supports 'natural language selectors' for browser actions, and the platform offers MCP server and CLI integrations that let AI agents operate it via natural-language-driven commands rather than raw code. However, this is developer/SDK-mediated natural language (act/extract commands within code) rather than a conversational end-user NL interface, and there's no independent hands-on evidence confirming reliability of the NL selector feature. Missing for 10: independent verification of natural-language selector accuracy, evidence of a direct end-user chat/NL interface (vs SDK-embedded NL), and quality/reliability benchmarks from third parties.
- [claimed-docs] “The SDK for browser agents. Natural language selectors, self-healing actions, and caching at scale.”
- [claimed-docs] “TypeScript-first agent framework with built-in Browserbase support.”
- [probe] “official MCP server documented at https://docs.browserbase.com/integrations/mcp/introduction”
- [probe] “official CLI documented at https://docs.browserbase.com/integrations/skills/browse-cli”
ai-native userApply a preset configuration tuned for research agents that returns structured, citable output
weight 2 · round to ScrapingBeeScrapingBee 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/”
Browserbasenone0/10Browserbase offers general agent tooling (web search, URL-to-markdown/JSON fetching, session control) but there is no evidence of a dedicated 'research agent' preset or configuration that returns structured, citable output with sources. missing for 10: a documented research-agent preset, citation/source-tracking output format, or structured schema tailored to research tasks.
- [claimed-docs] “Web search, built for agents. Let your Agent quickly find relevant websites based on a single query.”
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
- [claimed-docs] “Spin up thousands of concurrent browser sessions and return answers immediately”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnScrapingBeenone0/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…”
Browserbasenone0/10Evidence shows general documentation pages (docs.browserbase.com) and feature descriptions, but no mention of an interactive API reference or runnable code examples; a probe for OpenAPI/swagger specs (which typically power such interactive docs) returned 404 on all candidate paths, indicating no such interactive reference is exposed.
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.browserbase.com/openapi.json, https://docs.browserbase.com/swagger.json, https://docs.b…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnScrapingBeenone0/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.
Browserbasenone0/10A direct probe for OpenAPI/Swagger spec files at common paths returned 404 across all candidates, indicating no downloadable machine-readable API spec is exposed; docs mention an API but not a spec file.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.browserbase.com/openapi.json, https://docs.browserbase.com/swagger.json, https://docs.b…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnScrapingBeenone0/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.)
Browserbasenone0/10The evidence describes Browserbase's core browser-session and agent-automation capabilities but contains no mention of a distinct sandbox/staging mode, test API keys, or any mechanism to isolate testing from production data. Since API/dev platforms commonly offer such sandbox environments, the axis is applicable, but nothing in the pack demonstrates it.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnScrapingBeenone0/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.
Browserbasenone0/10No evidence of API versioning scheme (e.g., v1/v2 paths) or any documented deprecation policy; the OpenAPI spec probe even returned 404s, and no changelog or deprecation notes appear in the pack.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.browserbase.com/openapi.json, https://docs.browserbase.com/swagger.json, https://docs.b…”
data-engineerThe documented rate limit (requests per second or minute) enforced on my API key before throttling kicks in
weight 3 · round drawnScrapingBeenone0/10No evidence pack item mentions a documented rate limit (requests per second/minute) or throttling behavior for API keys; documentation excerpts cover scraping parameters and features but not concurrency/rate-limit thresholds.
Browserbasenone0/10No evidence in the pack documents specific API rate limits (requests per second/minute) or throttling behavior for Browserbase API keys; the OpenAPI spec probe even returned 404s, and no docs page addresses rate limiting.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.browserbase.com/openapi.json, https://docs.browserbase.com/swagger.json, https://docs.b…”
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 BrowserbaseScrapingBee 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”
Vendor docs explicitly claim automatic handling of forms, CAPTCHAs, and logins ('When your workflow requires a form, a CAPTCHA, or a login prompt, it's handled' and 'Your agent logs in, navigates, and pulls data from any website, login walls included'), directly matching the story. However, this is first-party marketing copy without independent hands-on verification or technical detail on CAPTCHA-solving mechanics/success rates, and community evidence is generic praise unrelated to this specific capability. Missing for 10: independent/hands-on confirmation that CAPTCHA bypass works reliably, technical documentation of the anti-bot mechanism, and any real-world case study demonstrating unattended login-wall bypass.
- [claimed-docs] “Your agent logs in, navigates, and pulls data from any website, login walls included.”
- [claimed-docs] “When your workflow requires a form, a CAPTCHA, or a login prompt, it's handled.”
- [claimed-docs] “Job applications, vendor portals, government forms. Agents that act on the web, not just read it.”
data-engineerAutomatically retry through a chain of different proxies when anti-bot detection blocks a request
weight 2 · round to ScrapingBeeScrapingBee 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 ScrapingBeeScrapingBee'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.”
Evidence shows Browserbase handles CAPTCHAs and login walls automatically (docs-8, docs-10), which relates to the anti-bot theme, but there is no explicit mention of a dedicated 'undetected'/stealth browser mode, fingerprint spoofing, or claims about bypassing sophisticated bot-detection systems specifically. Missing for 10: explicit stealth/undetected mode documentation, fingerprint randomization details, and independent evidence of successfully evading bot-detection systems like Cloudflare/PerimeterX.
- [claimed-docs] “Your agent logs in, navigates, and pulls data from any website, login walls included.”
- [claimed-docs] “When your workflow requires a form, a CAPTCHA, or a login prompt, it's handled.”
Proxy rotation
developerRequest a proxy from a specific country to get geolocation-appropriate content
weight 2 · round to ScrapingBeeScrapingBee'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 ScrapingBeeDocs 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”
Browserbasenone0/10The evidence pack describes browser automation, CAPTCHA handling, login walls, and agent tooling, but contains no mention of residential or datacenter proxy offerings for bypassing anti-bot measures. Since proxy infrastructure is a plausible feature for a browser automation platform, the axis applies, but no evidence supports it.
developerRoute requests through a rotating pool of proxy IPs to avoid blocks
weight 3 · round to ScrapingBeeDocs 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”
Browserbasenone0/10The evidence pack contains no mention of proxy IP support, rotation, or anti-blocking proxy features for Browserbase—only general browser automation, agent, and session capabilities are documented. Since proxy routing is a plausible and common feature for a browser automation platform, its absence here counts as 'none' rather than 'na'.
developerRoute multiple requests through the same proxy IP using a session identifier to maintain a consistent identity
weight 2 · round to ScrapingBeeOfficial 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”
Browserbasenone0/10Evidence pack contains only generic Browserbase product descriptions and community sentiment; nothing documents sticky-session proxy identity or session-ID-based proxy routing. Missing for 10: any mention of proxy session persistence, sticky IP configuration, or session-identifier-based proxy routing in docs or hands-on reports.
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 BrowserbaseScrapingBeenone0/10The evidence pack documents single-page scraping parameters (JS scenarios, extraction rules, proxies, screenshots) but never mentions a batch/bulk API endpoint, concurrent job submission, or a mechanism to process many URLs/items in one call.
Browserbase explicitly advertises spinning up thousands of concurrent browser sessions to return answers immediately, plus scheduled/on-demand agent deployment and monitoring across many tracked items (prices, listings, competitors), directly matching bulk cross-item automation for AI agents. Missing for 10: independent/hands-on benchmarks validating claimed concurrency at scale, and more detail on rate limits/orchestration patterns for very large batch jobs.
- [claimed-docs] “Spin up thousands of concurrent browser sessions and return answers immediately”
- [claimed-docs] “Track prices, job listings, product changes, and competitor moves as they happen.”
- [claimed-docs] “Deploy and run browser agents on Browserbase, on a schedule or on demand.”
- [claimed-docs] “Your agent logs in, navigates, and pulls data from any website, login walls included.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to BrowserbaseScrapingBeenone0/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.)
Browserbase supports scheduled/on-demand agent deployment and continuous monitoring use cases (e.g., alerting on breakage, tracking price/job changes), which implies some event-triggered automation, but there's no documented rule-engine or explicit event-trigger/webhook-condition system for defining 'if X happens, do Y' automation. missing for 10: explicit rule-definition interface, event-trigger/webhook configuration docs, condition-action automation examples, independent verification of trigger-based workflows.
- [claimed-docs] “Run agents that click through your product continuously and alert you the moment something breaks.”
- [claimed-docs] “Track prices, job listings, product changes, and competitor moves as they happen.”
- [claimed-docs] “Deploy and run browser agents on Browserbase, on a schedule or on demand.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to BrowserbaseScrapingBeenone0/10ScrapingBee's evidence pack covers API scraping parameters, JS rendering, proxies, and extraction, but contains no mention of scheduling, recurring jobs, cron-like triggers, or workflow orchestration features.
Docs explicitly mention deploying and running browser agents 'on a schedule or on demand' (browserbase-docs-14), directly supporting recurring job scheduling, but there is no detailed documentation of scheduling syntax, retry/monitoring, or independent hands-on confirmation of this feature working in practice. missing for 10: detailed scheduling API/config docs, independent verification of scheduled job reliability, monitoring/alerting details for scheduled runs.
- [claimed-docs] “Deploy and run browser agents on Browserbase, on a schedule or on demand.”
- [claimed-docs] “Run agents that click through your product continuously and alert you the moment something breaks.”
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 drawnScrapingBeenone0/10No evidence in the pack addresses team/organization management, sharing scrapers, or role-based permissions; the documentation excerpts focus entirely on API scraping parameters (JS rendering, proxies, extraction rules), not collaboration or account administration features.
Browserbasenone0/10No evidence in the pack mentions team/organization management, sharing scrapers with teammates, or role-based access control features; all evidence covers browser session automation, agent tooling, and integrations. This is a plausible axis for a dev platform with team accounts, but no supporting documentation or community evidence exists.
Deployment flexibility
developerBuild and deploy custom serverless scraping scripts on the platform without managing my own infrastructure
weight 2 · round to BrowserbaseScrapingBee 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”
Browserbase's docs explicitly describe programmatic session creation/control, full browser automation, 30+ starter templates, and deploying/running agents 'on a schedule or on demand' without infrastructure management, directly matching the story of building and deploying custom scraping scripts serverlessly. Missing for 10: independent developer testimonials confirming ease of deploying custom scripts, and detailed docs/tutorials specifically on writing/deploying custom scraping code (vs. general agent framing).
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
- [claimed-docs] “Start building right away with 30+ ready-made templates.”
- [claimed-docs] “Spin up thousands of concurrent browser sessions and return answers immediately”
- [claimed-docs] “Deploy and run browser agents on Browserbase, on a schedule or on demand.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.browserbase.com/llms.txt # Browserbase Documentation > Browserbase is the Browser Agent Platform: …”
developerDeploy the scraping service via a Docker container for production use
weight 2 · round drawnScrapingBeenone0/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.)
Browserbasenone0/10Browserbase is presented throughout its docs as a hosted, serverless browser API/platform (spin up sessions via API key, no infrastructure to manage) rather than a self-hostable container image; no evidence pack item mentions a Docker image, self-hosted deployment, or on-prem installation. Community discussion even frames a separate open-source project as the alternative for self-hosting, implying Browserbase itself doesn't offer this.
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Spin up thousands of concurrent browser sessions and return answers immediately”
- [community] “Discussion positioned BrowserStation explicitly as an open-source alternative to Browserbase, implying users seek self-hosted options instea…”
developerSelf-host an open-source version of the scraper instead of relying on a hosted cloud service
weight 2 · round drawnScrapingBeenone0/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…”
Browserbasenone0/10All evidence describes Browserbase as a hosted cloud API/platform (session management, agent tooling, MCP, CLI) with no mention of an open-source or self-hostable version; community discussion explicitly frames a separate project (BrowserStation) as 'an open-source alternative to Browserbase,' implying Browserbase itself is not self-hostable.
- [community] “Discussion positioned BrowserStation explicitly as an open-source alternative to Browserbase, implying users seek self-hosted options instea…”
- [community] “A commenter's terse reaction ('Cool') to the open-source Browserbase alternative suggests casual approval of having a non-commercial option.”
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.browserbase.com/llms.txt # Browserbase Documentation > Browserbase is the Browser Agent Platform: …”
Integrations
developerConnect the scraping API to no-code automation platforms like n8n or Zapier through a prebuilt connector
weight 2 · round drawnScrapingBeenone0/10No evidence of a prebuilt n8n or Zapier connector; the docs cover API parameters, an MCP server, and a CLI, 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 drawnScrapingBeenone0/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 drawnScrapingBeenone0/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 drawnScrapingBeenone0/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 to BrowserbaseScrapingBeenone0/10Evidence shows only API parameters/docs for building custom scraping requests; there is no marketplace of pre-built, ready-made scrapers a developer could pick and run instead of building their own.
Browserbase advertises '30+ ready-made templates' to start building quickly, which is the closest evidence to a marketplace of pre-built scrapers, but this is framed as starter templates for building agents/browser automations rather than a curated marketplace of finished, run-as-is scrapers. Missing for 10: explicit scraper marketplace, evidence of running a template unmodified to scrape a target site, and any community/hands-on account of using a template instead of coding one.
- [claimed-docs] “Start building right away with 30+ ready-made templates.”
developerStart building immediately using a library of ready-made project templates
weight 1 · round to BrowserbaseScrapingBeenone0/10No evidence of ready-made project templates or scaffolding to jumpstart development; documentation only covers API parameters and usage, not starter templates or boilerplate projects.
First-party docs explicitly state '30+ ready-made templates' to start building right away, directly matching the story. Quality is capped since there's no independent/hands-on corroboration of the template library's breadth or ease of use. missing for 10: independent verification of template quality/quantity, examples of specific templates or hands-on developer feedback using them.
- [claimed-docs] “Start building right away with 30+ ready-made templates.”
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 ScrapingBeeScrapingBee'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”
Browserbase's ecosystem includes Stagehand, described as 'Natural language selectors, self-healing actions, and caching at scale,' which directly supports natural-language-driven extraction instead of manual selectors, and other docs mention agents 'pulling data from any website.' However, the evidence is thin first-party marketing copy with no concrete extraction API examples, no structured-data-specific documentation, and no independent/hands-on corroboration of extraction quality. Missing for 10: detailed extraction API docs/examples, structured-output schema support details, and independent verification of extraction accuracy.
- [claimed-docs] “The SDK for browser agents. Natural language selectors, self-healing actions, and caching at scale.”
- [claimed-docs] “Your agent logs in, navigates, and pulls data from any website, login walls included.”
developerPass a JSON schema so the API returns structured data matching that schema
weight 2 · round to ScrapingBeeScrapingBee 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”
Browserbasenone0/10Evidence mentions fetching web context and converting URLs into HTML/JSON/markdown, but nothing describes accepting a JSON schema parameter to enforce structured output matching that schema. Missing for 10: any documentation of a schema-based extraction API, parameter naming, or example request/response validating against a user-supplied schema.
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
ai-native userHave an LLM read a page and decide what structured fields to pull out without pre-written selectors
weight 2 · round drawnScrapingBee 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”
Browserbase's ecosystem includes Stagehand, described as an SDK with 'natural language selectors, self-healing actions' (browserbase-docs-5) and URL-to-JSON/markdown conversion (browserbase-docs-3), which supports LLM-driven extraction without hardcoded selectors. However, there's no explicit documentation of a schema-based 'extract structured fields' API or example showing an LLM inferring fields dynamically. Missing for 10: a dedicated extraction API/schema example, independent hands-on validation of extraction accuracy without selectors.
- [claimed-docs] “The SDK for browser agents. Natural language selectors, self-healing actions, and caching at scale.”
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
- [claimed-docs] “Your agent logs in, navigates, and pulls data from any website, login walls included.”
developerPlug in a local or self-hosted LLM as the extraction backend instead of a cloud-only model
weight 2 · round drawnScrapingBeenone0/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”
Browserbasenone0/10No evidence that Browserbase allows configuring a local or self-hosted LLM as the extraction backend; all documented extraction features (e.g., Stagehand, web search, URL-to-markdown) reference cloud-based agent tooling with no mention of BYO-model or self-hosted model support.
- [claimed-docs] “The SDK for browser agents. Natural language selectors, self-healing actions, and caching at scale.”
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
Basic scraping
developerScrape a web page with a single API call and get its raw HTML back
weight 3 · round to ScrapingBeeDocs 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.”
Docs describe a URL-to-content endpoint that can convert any URL into HTML, JSON, or markdown, directly supporting single-call scraping with raw HTML output, but this is framed as 'fetch web context' rather than a dedicated documented scrape API with clear parameters/examples. Missing for 10: explicit API reference/example showing a single call returning raw HTML, independent hands-on verification of output fidelity, and confirmation of an OpenAPI spec (openapi probe returned 404s).
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.browserbase.com/llms.txt # Browserbase Documentation > Browserbase is the Browser Agent Platform: …”
Data safety
data-engineerAutomatically detect and filter personally identifiable information out of scraped content before it reaches storage
weight 2 · round drawnScrapingBeenone0/10No evidence of any PII detection, redaction, or filtering feature in ScrapingBee's documentation or capabilities; the product offers extraction rules and AI query tools but nothing about identifying or stripping personal data before storage.
Browserbasenone0/10No evidence of any PII detection, redaction, or filtering capability in Browserbase's docs or community sources; the product focuses on browser session control, automation, and data extraction infrastructure without mentioning content sanitization or privacy filtering before storage.
Document extraction
data-engineerExtract text content from PDFs, Word, Excel, and PowerPoint files without hosting them myself
weight 2 · round drawnScrapingBeenone0/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.)
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 drawnScrapingBeenone0/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 BrowserbaseScrapingBeenone0/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…”
Browserbase separately advertises a 'Web search' tool for finding relevant URLs (docs-2) and a distinct 'Contents' tool to convert a URL into HTML/JSON/markdown (docs-3), but the evidence never shows these unified into a single call that returns full page content directly from search results. Missing for 10: documentation of a combined search+extract endpoint, example code showing one call returning both links and full content, and independent verification of extraction quality/accuracy.
- [claimed-docs] “Web search, built for agents. Let your Agent quickly find relevant websites based on a single query.”
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
Selector extraction
developerExtract specific fields from a page using CSS or XPath selector rules
weight 3 · round to ScrapingBeeDocs 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.”
Browserbasenone0/10Browserbase's evidence describes full browser control, natural-language selectors, and general data extraction, but nothing explicitly confirms support for CSS or XPath selector-based field extraction. Missing for 10: explicit documentation or example of CSS/XPath selector usage for extraction, API reference showing selector parameters.
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
- [claimed-docs] “The SDK for browser agents. Natural language selectors, self-healing actions, and caching at scale.”
- [claimed-docs] “Your agent logs in, navigates, and pulls data from any website, login walls included.”
Structured data handling
data-engineerExtract data from very large tables using intelligent chunking so it fits within processing limits
weight 1 · round drawnScrapingBeenone0/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 ScrapingBeeScrapingBee'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”
Browserbase runs real browser sessions (docs-1, docs-4) and explicitly offers converting any URL into HTML/JSON/markdown (docs-3), which requires rendering JS-heavy pages in a real browser before extraction—directly matching the story. Missing for 10: explicit mention of SPA-specific rendering guarantees and independent hands-on verification of rendered HTML fidelity.
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
developerHave the API wait for a specific selector to appear before returning the rendered page
weight 2 · round to ScrapingBeeScrapingBee'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.”
Browserbase docs mention 'auto-waits' as part of full browser control (docs-4), implying the underlying Playwright/Puppeteer session supports waiting for elements, but no explicit documentation of a selector-wait API or parameter is provided. Missing for 10: explicit API/parameter documentation for waiting on a specific selector, code examples, and independent confirmation of this exact behavior.
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
Interactive automation
developerAccess a managed remote browser sandbox for interactive, manual browsing workflows
weight 2 · round to BrowserbaseScrapingBeenone0/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…”
Browserbase clearly provides managed remote browser sessions that can be created, controlled and observed via API (browserbase-docs-1, browserbase-docs-4), and a CLI/skill integration exists (browserbase-probe-4) that could support manual, interactive use. However, the evidence is overwhelmingly focused on programmatic/agent-driven automation rather than a human-in-the-loop, manual browsing experience (e.g., a live-view iframe or interactive debugger), which is never explicitly documented. Missing for 10: explicit documentation of a live/interactive session viewer for manual human browsing, and independent corroboration that developers actually use it for hands-on manual sessions rather than purely automated agent tasks.
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
- [probe] “official CLI documented at https://docs.browserbase.com/integrations/skills/browse-cli”
developerKeep interacting with an already-scraped page, clicking and filling forms to reach content behind a login wall
weight 2 · round to BrowserbaseScrapingBee'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”
Browserbase provides persistent programmatic sessions with full browser control (auto-waits, network interception, multi-tab), and docs explicitly describe agents logging in, navigating, and pulling data behind login walls, with forms/CAPTCHAs/logins handled. This directly supports interacting further with an already-scraped page to reach gated content. Missing for 10: independent hands-on verification of session persistence across multi-step interactions and concrete code examples showing continued interaction post-scrape.
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
- [claimed-docs] “Your agent logs in, navigates, and pulls data from any website, login walls included.”
- [claimed-docs] “When your workflow requires a form, a CAPTCHA, or a login prompt, it's handled.”
- [claimed-docs] “Job applications, vendor portals, government forms. Agents that act on the web, not just read it.”
developerScript page interactions like clicking, filling inputs, and scrolling before content is returned
weight 3 · round to ScrapingBeeScrapingBee'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.”
Browserbase's docs describe full programmatic browser control—auto-waits, network interception, multi-tab support, and agents that log in, fill forms, and navigate pages—implying developers can script click/fill/scroll actions before returning content, and it integrates with frameworks like Playwright/Stagehand for such control. However, the evidence pack lacks explicit code examples or docs naming click/fill/scroll actions directly, and there's no independent hands-on confirmation of these specific interactions. missing for 10: explicit API/code snippets demonstrating click, fill, and scroll actions; independent developer corroboration of these specific interactions.
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
- [claimed-docs] “Your agent logs in, navigates, and pulls data from any website, login walls included.”
- [claimed-docs] “When your workflow requires a form, a CAPTCHA, or a login prompt, it's handled.”
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
Render configuration
developerControl the browser viewport width and height when rendering a page
weight 1 · round to ScrapingBeeOfficial 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…”
Browserbasenone0/10The evidence pack contains no documentation or mention of session creation parameters such as viewport width/height, browser dimensions, or rendering resolution controls; it only covers general browser control, agent frameworks, and integrations. Missing for 10: any docs page, API parameter, or example showing viewport configuration during session creation.
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
Session persistence
developerPass my own session cookies so the API fetches pages requiring authentication
weight 2 · round drawnScrapingBeenone0/10No evidence pack item mentions passing custom cookies or headers for authenticated sessions; docs cover JS rendering, proxies, extraction, screenshots, but nothing about supplying session cookies for authenticated page fetches.
Browserbasenone0/10Evidence shows Browserbase can handle logins, CAPTCHAs, and full browser control (network interception, multi-tab) but never mentions a documented API/param for developers to inject their own session cookies to bypass authentication. Missing for 10: explicit cookie-injection/session-context API docs, code sample showing custom cookies passed to a session, and independent confirmation it works for authenticated fetches.
- [claimed-docs] “Your agent logs in, navigates, and pulls data from any website, login walls included.”
- [claimed-docs] “When your workflow requires a form, a CAPTCHA, or a login prompt, it's handled.”
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
developerReuse a persistent browser profile with saved cookies and login state across multiple requests
weight 2 · round drawnScrapingBeenone0/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”
Browserbasenone0/10The evidence pack contains no mention of persistent browser profiles, contexts, or reusable cookie/login state across sessions—only generic mentions of handling logins/login walls during a single session (browserbase-docs-8, browserbase-docs-10). No documentation of a profile/context object, storage of cookies, or reuse across multiple requests is present. missing for 10: any mention of a persistent context/profile object, cookie storage/reuse mechanism, or documentation showing login state persisting across separate sessions.
- [claimed-docs] “Your agent logs in, navigates, and pulls data from any website, login walls included.”
- [claimed-docs] “When your workflow requires a form, a CAPTCHA, or a login prompt, it's handled.”
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 BrowserbaseScrapingBee 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”
Browserbase is fundamentally API-first ('one API key gives your agent everything it needs') with docs showing session creation, control, and observability programmatically, suggesting the dashboard largely mirrors API capabilities rather than gating features behind UI-only workflows. However, there is no explicit documentation stating full UI/API parity, and the openapi spec probe returned 404s at all candidate locations, undermining confidence that a complete, discoverable API surface matches every UI capability. Missing for 10: explicit UI/API parity documentation, a public OpenAPI spec, and independent confirmation that no dashboard-only features exist.
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.browserbase.com/llms.txt # Browserbase Documentation > Browserbase is the Browser Agent Platform: …”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.browserbase.com/openapi.json, https://docs.browserbase.com/swagger.json, https://docs.b…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to ScrapingBeeScrapingBee 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”
Browserbasenone0/10No evidence of any data export feature, open-format download, or account portability tooling in Browserbase's docs; the only related community signal is that users seeking self-hosted/open alternatives turn to a separate third-party project (BrowserStation), not an export path from Browserbase itself.
- [community] “Discussion positioned BrowserStation explicitly as an open-source alternative to Browserbase, implying users seek self-hosted options instea…”
ai-native userRead the product's source under an open license
weight 2 · round drawnScrapingBeenone0/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?”
Browserbasenone0/10No evidence Browserbase source code is available under any open license; documentation only describes hosted API/SDK features. Community discussion explicitly frames another project (BrowserStation) as 'an open-source alternative to Browserbase', implying Browserbase itself is closed-source/proprietary.
- [community] “Discussion positioned BrowserStation explicitly as an open-source alternative to Browserbase, implying users seek self-hosted options instea…”
- [community] “A commenter's terse reaction ('Cool') to the open-source Browserbase alternative suggests casual approval of having a non-commercial option.”
ai-native userSelf-host the core product
weight 3 · round drawnScrapingBeenone0/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…”
Browserbasenone0/10Browserbase is offered exclusively as a hosted cloud API/service; no docs or product pages mention a self-hosted or on-prem deployment option. Community evidence even points to a separate open-source project (BrowserStation) as the self-hosted alternative, underscoring that Browserbase itself cannot be self-hosted.
- [community] “Discussion positioned BrowserStation explicitly as an open-source alternative to Browserbase, implying users seek self-hosted options instea…”
- [community] “A commenter's terse reaction ('Cool') to the open-source Browserbase alternative suggests casual approval of having a non-commercial option.”
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
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 ScrapingBeeScrapingBee'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”
Browserbase's URL-fetch/context tool explicitly supports converting any URL into HTML, JSON, or markdown, directly enabling clean markdown output instead of raw HTML. However, evidence is limited to a single doc snippet with no detail on markdown fidelity, cleaning quality, or independent validation. Missing for 10: detailed docs/examples showing markdown extraction quality, independent/hands-on confirmation of clean output, and coverage across the main scraping API (not just the URL-context tool).
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
developerChoose exactly which output format is returned, such as markdown, HTML, text, or frontmatter
weight 2 · round to ScrapingBeeDocs 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”
Browserbase's URL-to-context tool explicitly converts pages into HTML, JSON, or markdown, showing some format choice, but there is no evidence of a full selectable set including plain text or frontmatter, nor documentation of a unified output-format parameter across its APIs. missing for 10: explicit text/frontmatter options, unified API-level format parameter documentation, independent confirmation of format selection.
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
developerReceive scraped content as structured JSON
weight 3 · round to ScrapingBeeScrapingBee 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”
Docs mention converting URLs into HTML, JSON, or markdown (browserbase-docs-3), which directly supports structured JSON output for scraped content, but there's no detailed schema documentation, examples of JSON output format, or independent verification of this capability. missing for 10: detailed JSON schema/response examples, API reference documentation, independent hands-on confirmation of JSON output quality.
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
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 BrowserbaseScrapingBee 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.”
Browserbase explicitly offers a URL-to-content conversion feature that outputs HTML, JSON, or markdown, directly targeting the LLM-ready text use case, and provides an llms.txt for agent consumption. This clearly addresses avoiding messy HTML/rendering, though there's no independent hands-on validation of output cleanliness or completeness. Missing for 10: independent/third-party verification of extraction quality, and more detail on how CAPTCHA/login-walled content is cleaned before conversion.
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
- [claimed-docs] “Your agent logs in, navigates, and pulls data from any website, login walls included.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.browserbase.com/llms.txt # Browserbase Documentation > Browserbase is the Browser Agent Platform: …”
ai-native userRequest semantically chunked output instead of one large content blob, so it feeds cleanly into a retrieval pipeline
weight 2 · round drawnScrapingBeenone0/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”
Browserbasenone0/10Browserbase's docs mention converting URLs into HTML/JSON/markdown (browserbase-docs-3) but there is no evidence of a semantic-chunking output mode or configurable chunk size for retrieval pipelines specifically.
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
Visual capture
developerCapture a screenshot of a full page or a specific selected area
weight 2 · round to ScrapingBeeDocs 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”
Browserbasenone0/10Browserbase's evidence pack covers session control, web search, data extraction, and agent tooling, but nothing explicitly documents full-page or selector-based screenshot capture. Missing for 10: any documentation or docs snippet referencing screenshot/image capture APIs, selector-based capture options, or hands-on confirmation of this output format.
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
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 ScrapingBeeScrapingBee'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 ScrapingBeeOfficial 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`”
Browserbasenone0/10The evidence pack mentions general network interception capability (browserbase-docs-4) but no explicit ad-blocking feature, flag, or documentation is cited that lets developers block ads on target pages to speed up scraping. Missing for 10: dedicated ad-blocking API/flag, performance benchmarks showing speed gains, and any documentation referencing ad or resource blocking specifically.
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
developerBlock images and CSS resources by default to reduce bandwidth and speed up requests
weight 1 · round to ScrapingBeeOfficial 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…”
Browserbasenone0/10The evidence only mentions generic 'network interception' capability (browserbase-docs-4) but nowhere documents blocking images/CSS by default to reduce bandwidth or speed up requests; missing for 10: explicit resource-blocking config, default image/CSS blocking behavior, bandwidth-savings documentation.
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
ai-native userSet how much reasoning effort an autonomous agent spends on a data-gathering task (low, medium, high)
weight 2 · round drawnScrapingBeenone0/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.)
Browserbasenone0/10Browserbase provides browser session infrastructure, scraping, and agent deployment tools, but no evidence describes any 'reasoning effort' control (low/medium/high) for agent tasks — this is a model-level parameter, not something exposed in Browserbase's docs. Missing for 10: any mention of reasoning-effort settings, task budget controls, or configurable agent 'thinking' levels.
Cost transparency
developerWhether exceeding my plan's monthly credit or request quota triggers overage charges or a hard cutoff
weight 3 · round drawnScrapingBeenone0/10No evidence in the pack addresses billing behavior when exceeding plan credits/requests—no mention of overage charges, hard cutoffs, or quota enforcement policy.
developerWhether failed, blocked, or empty-result requests still consume my billing quota
weight 2 · round drawnScrapingBeenone0/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 drawnScrapingBeenone0/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 ScrapingBeeScrapingBee 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”
Browserbasenone0/10Browserbase's evidence covers session control, auto-waits, and content extraction generally, but nothing describes developer-facing controls for choosing when to return content (e.g., wait strategies, streaming vs full-page load, timeout tuning) to trade latency for completeness. missing for 10: explicit wait/timeout configuration options, streaming or partial-content return APIs, documentation on latency-completeness tradeoffs.
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
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 drawnScrapingBeenone0/10No evidence in the pack specifies concurrent session/request limits per pricing tier or the cost to increase that cap; documentation snippets cover feature parameters (JS scenario, proxies, extraction) but not concurrency caps or upgrade pricing.
Browserbasenone0/10The evidence pack contains no pricing page, tier comparison, or concurrency-cap documentation; only marketing claims about spinning up 'thousands of concurrent sessions' with no tier-specific limits or upgrade costs cited. No mention of what concurrency cap applies at each plan or how much raising it costs.
- [claimed-docs] “Spin up thousands of concurrent browser sessions and return answers immediately”
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 drawnScrapingBeenone0/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 drawnScrapingBeenone0/10No evidence in the pack addresses data-use, training-data opt-out, or AI-training privacy policies for ScrapingBee's service; nothing documents a mechanism to prevent scraped/customer data from being used to train AI models.
ai-native userControl data retention and deletion
weight 2 · round drawnScrapingBeenone0/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 drawnScrapingBeenone0/10No evidence pack mentions telemetry, usage tracking, or an opt-out mechanism for ScrapingBee's own product usage; documentation excerpts focus solely on scraping API parameters.
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 drawnScrapingBeenone0/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 BrowserbaseScrapingBeenone0/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.
Browserbase docs claim it can spin up thousands of concurrent browser sessions and return answers immediately, directly supporting async batch scraping at scale, plus scheduling/deploying agents on demand. However, there is no explicit documentation of a batch-job API, queueing semantics, rate-limit/backoff guidance, or independent hands-on evidence confirming reliability at thousands-of-URL scale. missing for 10: dedicated batch/queue API docs, independent benchmarks or case studies validating thousands-of-URL scraping, and error-handling/retry guarantees at scale.
- [claimed-docs] “Spin up thousands of concurrent browser sessions and return answers immediately”
- [claimed-docs] “Deploy and run browser agents on Browserbase, on a schedule or on demand.”
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
developerApply different crawl configurations to different URL patterns within a single batch job
weight 1 · round drawnScrapingBeenone0/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.
Browserbasenone0/10Browserbase's evidence covers session management, agent tooling, scraping/search APIs, and scheduling, but nothing describes a batch job mechanism where different crawl configurations can be applied per URL pattern within one job. This is a plausible axis for a browser automation platform, but no feature or doc supports it.
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
- [claimed-docs] “Spin up thousands of concurrent browser sessions and return answers immediately”
- [claimed-docs] “Deploy and run browser agents on Browserbase, on a schedule or on demand.”
Concurrency
data-engineerSpin up many concurrent scraping sessions to gather data at scale
weight 3 · round to BrowserbaseScrapingBee 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”
Docs explicitly claim ability to 'spin up thousands of concurrent browser sessions' with programmatic session creation/control and scraping-focused features (login walls, CAPTCHAs, data extraction), directly matching the story. Missing for 10: independent/hands-on benchmarks validating concurrency at scale and no third-party performance corroboration beyond vendor docs.
- [claimed-docs] “Spin up thousands of concurrent browser sessions and return answers immediately”
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Full browser control with auto-waits, network interception, and multi-tab support.”
- [claimed-docs] “Your agent logs in, navigates, and pulls data from any website, login walls included.”
- [claimed-docs] “When your workflow requires a form, a CAPTCHA, or a login prompt, it's handled.”
Crawl compliance
data-engineerConfigure the crawler to respect robots.txt rules and target-site rate limits automatically
weight 2 · round drawnScrapingBeenone0/10No evidence that ScrapingBee offers robots.txt compliance settings or automatic rate-limit throttling per target site; docs cover proxies, JS rendering, extraction, and viewport settings but nothing about robots.txt or rate-limiting configuration.
Browserbasenone0/10No evidence in the pack mentions robots.txt compliance, rate-limit configuration, or crawl politeness controls; Browserbase docs focus on session control, agent tooling, and captcha/login handling but nothing about respecting robots.txt or throttling requests to target sites.
Fault tolerance
data-engineerResume a crashed deep crawl from a saved checkpoint instead of restarting from scratch
weight 2 · round drawnScrapingBeenone0/10No evidence of any crawl checkpoint/resume feature; ScrapingBee's docs describe single-page API requests, sessions, and proxy parameters but nothing about deep crawl state persistence or resuming crashed crawls.
Operational transparency
data-engineerCheck a public status page showing uptime history and past incident postmortems before committing to the service
weight 2 · round drawnScrapingBeenone0/10No evidence of a public status page, uptime history, or incident postmortems anywhere in the evidence pack; docs focus on API features and community items discuss cost/alternatives, not reliability 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 to BrowserbaseScrapingBeenone0/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.
Marketing copy explicitly promises tracking price/listing changes 'as they happen' and alerting when something breaks, and agents can be scheduled or run on demand, aligning with the monitoring+notify story. However there's no documented notification mechanism (webhooks, email/Slack alerts), no dedicated 'change detection' API, and no independent/hands-on evidence confirming this works in practice. Missing for 10: concrete alerting/notification API or integration docs, hands-on validation of change-monitoring workflows, independent user reports of this specific use case.
- [claimed-docs] “Run agents that click through your product continuously and alert you the moment something breaks.”
- [claimed-docs] “Track prices, job listings, product changes, and competitor moves as they happen.”
- [claimed-docs] “Deploy and run browser agents on Browserbase, on a schedule or on demand.”
data-engineerMonitor job performance, validate data quality, and receive alerts when something fails
weight 2 · round to BrowserbaseScrapingBeenone0/10Evidence covers scraping features (JS rendering, extraction, proxies) but nothing about job monitoring dashboards, data quality validation, or failure alerting mechanisms; community comments focus on cost/alternatives, not reliability tooling.
Browserbase supports observing browser sessions (browserbase-docs-1) and explicitly offers agents that 'click through your product continuously and alert you the moment something breaks' (browserbase-docs-11), which covers basic failure alerting for scraping/monitoring jobs. However, there is no evidence of structured job performance dashboards, metrics, or explicit data-quality validation tooling for extracted data. Missing for 10: dedicated job performance monitoring/metrics dashboard, data quality validation checks, and integration with alerting channels (email/Slack/webhooks) beyond a generic marketing claim.
- [claimed-docs] “Create, control, and observe browser sessions programmatically.”
- [claimed-docs] “Run agents that click through your product continuously and alert you the moment something breaks.”
developerMonitor live system metrics and worker/browser pool status through a real-time dashboard
weight 1 · round drawnScrapingBeenone0/10The evidence pack covers API parameters, docs, and community discussion but contains no mention of a real-time dashboard for monitoring system metrics or worker/browser pool status; ScrapingBee's dashboard (if any) is not documented here.
developerSchedule scraping jobs to run automatically at specific times
weight 2 · round to BrowserbaseScrapingBeenone0/10ScrapingBee's evidence describes only on-demand API scraping (parameters, JS rendering, proxies, extraction) with no mention of a scheduling feature, cron-like triggers, or job scheduler UI. No evidence supports automated, time-based recurring scraping jobs.
Docs explicitly state agents can be deployed 'on Browserbase, on a schedule or on demand,' directly supporting scheduled scraping jobs, but there's no detail on scheduling configuration, cron-like syntax, retry/failure handling, or independent hands-on confirmation. missing for 10: detailed scheduling API/config docs, examples of recurring job setup, independent verification of schedule reliability.
- [claimed-docs] “Deploy and run browser agents on Browserbase, on a schedule or on demand.”
- [claimed-docs] “Spin up thousands of concurrent browser sessions and return answers immediately”
- [claimed-docs] “Track prices, job listings, product changes, and competitor moves as they happen.”
Site crawling
data-engineerRun a deep crawl using a breadth-first strategy with a configurable maximum page limit
weight 2 · round drawnScrapingBeenone0/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”
Browserbasenone0/10Browserbase provides browser session infrastructure, session control, and agent tooling, but there is no evidence of a deep-crawl feature with breadth-first traversal or a configurable max page limit; crawling logic would need to be built by the customer on top of the raw browser sessions.
developerCrawl an entire website and get content from all its pages with one request
weight 3 · round drawnScrapingBeenone0/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.”
Browserbasenone0/10Browserbase's docs describe session control, single-URL-to-content conversion, web search, and scaling concurrent sessions, but no evidence describes a one-request whole-site crawl capability that traverses all pages and aggregates content.
- [claimed-docs] “Quickly fetch web context for your agent by converting any URL into HTML, JSON or markdown”
- [claimed-docs] “Spin up thousands of concurrent browser sessions and return answers immediately”
developerInstantly discover all URLs on a website without fully crawling it
weight 2 · round drawnScrapingBeenone0/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.
Browserbasenone0/10Browserbase's docs cover session control, web search, URL-to-content conversion, and full browsing/automation, but nothing describes a lightweight URL-discovery or sitemap-extraction capability that avoids full crawling. Missing for 10: any sitemap parsing, link-graph extraction, or 'list all URLs' feature distinct from full page rendering/crawling.
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableScrapingBeen/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/”
Browserbasen/aBrowserbase is a browser automation infrastructure/platform, not itself an AI agent that would consume other MCP servers' tools — evidence shows the reverse (Browserbase exposes its own official MCP server for other agents to plug into, per browserbase-probe-3), which is a different axis than 'plugging MCP servers into this product.' There's no evidence Browserbase itself acts as an MCP client consuming external tool servers.
- [probe] “official MCP server documented at https://docs.browserbase.com/integrations/mcp/introduction”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableScrapingBeen/aScrapingBee is a web scraping API/proxy service, not an automation-building platform with workflows to version or roll back; versioning/review/rollback of automations is a category error for this product type.