Browserbase vs Context.dev
Browserbase
Browserbase, Inc.
Context.dev wins · 17–26 (51 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 drawnA 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.”
Context.dev has a confirmed live llms.txt at docs.context.dev/llms.txt (HTTP 200, agent-oriented index of docs), plus agent-oriented docs, MCP server, CLI, and a coding-agent skill install guide, directly enabling an agent to be pointed at agent-native documentation. Missing for 10: independent third-party confirmation that agents successfully consume the llms.txt in practice beyond the probe check.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.context.dev/llms.txt # Context.dev - [The go-to web data API](https://docs.context.dev/introductio…”
- [claimed-docs] “Connect your AI client to Context.dev tools for live web and company data.”
- [claimed-docs] “Call Context.dev from your terminal and use JSON responses in scripts or CI.”
- [claimed-docs] “Teach your coding agent how to choose and use the Context.dev API.”
- [probe] “official MCP server documented at https://mcp.context.dev/mcp”
- [probe] “official CLI documented at https://docs.context.dev/install-cli”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnBrowserbase 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: …”
Context.dev ships a CLI explicitly documented for scripting and CI use ('Call Context.dev from your terminal and use JSON responses in scripts or CI'), backed by a full REST API with OpenAPI spec, async batch jobs for long-running headless crawls, and documented rate-limit/timeout handling suited to automated pipelines. Missing for 10: no explicit CI/CD pipeline example (e.g., GitHub Actions), and no independent/community confirmation of headless CI usage beyond vendor docs.
- [claimed-docs] “Call Context.dev from your terminal and use JSON responses in scripts or CI.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “`return-partial` | Return usable completed work with a completion marker. If no usable result exists, fail without a charge.”
- [claimed-docs] “Authenticated API responses expose these headers when a per-minute limit applies”
- [probe] “PROBE openapi: HTTP 200 at https://docs.context.dev/openapi.json — contains "openapi" key”
- [probe] “official CLI documented at https://docs.context.dev/install-cli”
ai-native userConnect an agent via an official MCP server
weight 3 · round drawnBrowserbase 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”
Context.dev is a web-data API (not itself an agent), so the MCP-server axis applies, and it publishes an official hosted MCP endpoint (mcp.context.dev/mcp) plus install docs for connecting AI clients to its tools for live web/company data. Missing for 10: independent/hands-on verification of the MCP server working in practice beyond first-party docs and a probe confirming the endpoint exists.
- [probe] “official MCP server documented at https://mcp.context.dev/mcp”
- [claimed-docs] “Connect your AI client to Context.dev tools for live web and company data.”
ai-native userUse an official CLI
weight 2 · round drawnThere'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”
Docs and probe confirm an official CLI exists ('Call Context.dev from your terminal and use JSON responses in scripts or CI') with a dedicated install page, supporting agentic/CI workflows. However, there's no independent/hands-on corroboration of the CLI's functionality or depth beyond first-party docs. Missing for 10: independent verification/hands-on review of CLI usage, details on CLI command coverage vs the full API surface.
- [claimed-docs] “Call Context.dev from your terminal and use JSON responses in scripts or CI.”
- [probe] “official CLI documented at https://docs.context.dev/install-cli”
ai-native userDrive the product through a documented public API
weight 3 · round to Context.devBrowserbase 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”
Context.dev is fundamentally an API product with a public OpenAPI spec, documented endpoints (crawl, extract, screenshot, brand data, auth), API key management, rate-limit headers, plus a CLI and MCP server built on top of the same API — clear evidence of a documented, drivable public API for AI-native consumption. Missing for 10: independent third-party developer confirmation of full API coverage beyond docs/probes.
- [probe] “PROBE openapi: HTTP 200 at https://docs.context.dev/openapi.json — contains "openapi" key”
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
- [claimed-docs] “Choose **Restricted** when an integration needs only selected operations; a restricted key with no permissions cannot call the API.”
- [claimed-docs] “Call Context.dev from your terminal and use JSON responses in scripts or CI.”
- [claimed-docs] “Authenticated API responses expose these headers when a per-minute limit applies”
- [claimed-docs] “discover → register → deliver setup link & code to the user → user completes claim in browser → poll for access_token → call API.”
- [probe] “official CLI documented at https://docs.context.dev/install-cli”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to Context.devBrowserbasenone0/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: …”
Docs explicitly describe restricted API keys scoped to selected operations only, with a no-permission key unable to call the API at all, directly supporting least-privilege credential issuance for agents; the OAuth-like device flow (discover→register→claim→poll) also supports scoped token issuance per client. missing for 10: no evidence of fine-grained scoping beyond operation-level (e.g., resource/data scoping), and no independent/hands-on confirmation of restricted-key behavior in production.
- [claimed-docs] “Choose **Restricted** when an integration needs only selected operations; a restricted key with no permissions cannot call the API.”
- [claimed-docs] “discover → register → deliver setup link & code to the user → user completes claim in browser → poll for access_token → call API.”
ai-native userBuild against official SDKs
weight 2 · round to BrowserbaseBrowserbase 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…”
Context.devnone0/10The evidence shows an OpenAPI spec, CLI, MCP server, and 'skill' for coding agents, but there is no mention of official SDK client libraries (e.g., Python, JS, Go packages) for Context.dev. Missing for 10: explicit official SDK packages/documentation, language-specific client libraries, versioning/release notes for SDKs.
- [probe] “PROBE openapi: HTTP 200 at https://docs.context.dev/openapi.json — contains "openapi" key”
- [probe] “official CLI documented at https://docs.context.dev/install-cli”
- [claimed-docs] “Call Context.dev from your terminal and use JSON responses in scripts or CI.”
ai-native userSubscribe to events via webhooks
weight 2 · round to Context.devBrowserbasenone0/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'.
Context.dev supports monitoring pages/sitemaps/datasets and receiving 'signed change events' on a schedule, which functions as a webhook-like event delivery mechanism, but the docs never explicitly describe a subscribe/webhook API, event types, delivery retries, or webhook management endpoints. missing for 10: explicit webhook subscription/management API docs, event schema/type documentation, delivery reliability/retry details, and independent confirmation of webhook functionality.
- [claimed-docs] “Watch a page, sitemap, or structured dataset on a schedule and receive signed change events.”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round drawnBrowserbasenone0/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.)
Context.devnone0/10Context.dev is a data-extraction/scraping API (Markdown, structured JSON extraction, screenshots, brand data) intended to feed external AI agents and applications, but there is no evidence of the product itself surfacing AI-generated insights, recommendations, or analysis inside a Context.dev interface — it delivers raw/structured data, not in-product AI insight generation.
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
- [claimed-docs] “retrieve brand profiles with logos, colors, descriptions, and social links through the same API.”
- [claimed-docs] “Connect your AI client to Context.dev tools for live web and company data.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to BrowserbaseDocs 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”
Context.dev supports background automation via async batch crawling that runs as a tracked job until completion, and scheduled monitoring of pages/sitemaps/datasets that emits signed change events without user intervention — both run autonomously once configured. However, there's no evidence of a broader automation/workflow engine (e.g., chaining actions, triggering downstream agent tasks, retries/orchestration) beyond these two specific background job types. Missing for 10: evidence of workflow chaining or agent-triggered automation, independent confirmation of monitoring reliability, and details on scheduling flexibility.
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Watch a page, sitemap, or structured dataset on a schedule and receive signed change events.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnBrowserbasenone0/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 drawnBrowserbase'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”
Context.dev ships an official MCP server ('Connect your AI client to Context.dev tools for live web and company data') and an agent 'skill' file that teaches coding agents how to call the API, which together let AI-native users issue natural-language requests that get translated into API calls; there is also a CLI for scripted/terminal use. However, all natural-language operation is mediated through third-party AI clients (Claude, agents) rather than a native NL interface in Context.dev itself, and no community/hands-on evidence confirms this NL workflow works smoothly in practice. Missing for 10: first-party or independent evidence of actual natural-language usage/output quality via the MCP or skill integration, and any native chat/NL interface within the product itself.
- [claimed-docs] “Connect your AI client to Context.dev tools for live web and company data.”
- [claimed-docs] “Teach your coding agent how to choose and use the Context.dev API.”
- [claimed-docs] “Call Context.dev from your terminal and use JSON responses in scripts or CI.”
- [probe] “official MCP server documented at https://mcp.context.dev/mcp”
- [probe] “official CLI documented at https://docs.context.dev/install-cli”
ai-native userApply a preset configuration tuned for research agents that returns structured, citable output
weight 2 · round drawnBrowserbasenone0/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”
Context.devnone0/10Context.dev is a web scraping/data extraction API with structured extraction, crawling, and monitoring features, but there is no evidence of a preset or configuration profile specifically tuned for 'research agents' that returns structured, citable output (e.g., with source attribution/citations). The extraction guide supports JSON Schema output but nothing about citation tracking or a research-agent preset.
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnBrowserbasenone0/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…”
Context.devnone0/10Evidence confirms docs, guides, and an OpenAPI spec exist, but nothing indicates an interactive reference with runnable/try-it-out examples (no Swagger/Redoc playground, no 'try it' feature mentioned).
- [probe] “PROBE openapi: HTTP 200 at https://docs.context.dev/openapi.json — contains "openapi" key”
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to Context.devBrowserbasenone0/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…”
A probe confirms a live OpenAPI JSON spec at docs.context.dev/openapi.json (HTTP 200, contains 'openapi' key), directly satisfying the machine-readable spec requirement, alongside first-party docs describing the API surface. Missing for 10: independent third-party corroboration of spec completeness/versioning beyond the probe check.
- [probe] “PROBE openapi: HTTP 200 at https://docs.context.dev/openapi.json — contains "openapi" key”
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnBrowserbasenone0/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 drawnBrowserbasenone0/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 to Context.devBrowserbasenone0/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…”
Docs confirm a per-minute rate limit exists and that authenticated responses expose rate-limit headers, but no specific numeric threshold (requests/sec or /min) is given in the evidence. Missing for 10: the actual documented numeric limit value, guidance on limits per plan/key tier, and confirmation via headers example showing remaining/limit values.
- [claimed-docs] “Authenticated API responses expose these headers when a per-minute limit applies”
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 BrowserbaseVendor 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.”
Context.devnone0/10Context.dev is a web scraping/crawling/data-extraction API; there is no evidence of CAPTCHA-solving, login/session automation, or form-wall bypass capability. Community comments even question its handling of restricted/anti-scraping sites, and no docs describe login or CAPTCHA handling.
- [community] “Seems wildly expensive, furthermore not a single mention of "ip" on homepage? Not using rotating ip's, residential proxies? AKA unusable for…”
- [community] “\"Websites can opt out of our service, and we respect these requests and add them to our block list.\" I.e: robots.txt already exists and is…”
- [community] “Are you using residential proxies? How do you handle websites that don't want to be scraped. EG if I start passing in Linkedin pages what is…”
- [claimed-docs] “Click, wait, or scroll before scraping or extracting a page, then check which interactions succeeded.”
data-engineerAutomatically retry through a chain of different proxies when anti-bot detection blocks a request
weight 2 · round drawnBrowserbasenone0/10Evidence shows Browserbase offers CAPTCHA handling, proxy support, and session management generally, but there is no mention of automatic retry chaining across multiple proxies upon anti-bot detection failures.
Context.devnone0/10No documentation or evidence describes proxy rotation, proxy-chain retries, or anti-bot bypass mechanisms; a community comment explicitly notes the homepage never mentions IP rotation or residential proxies, reinforcing the absence of this capability.
- [community] “Seems wildly expensive, furthermore not a single mention of "ip" on homepage? Not using rotating ip's, residential proxies? AKA unusable for…”
- [community] “Are you using residential proxies? How do you handle websites that don't want to be scraped. EG if I start passing in Linkedin pages what is…”
developerUse an undetected browser mode to bypass sophisticated bot detection systems
weight 3 · round to BrowserbaseEvidence 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.”
Context.devnone0/10No evidence in the pack claims an 'undetected browser' or anti-bot-bypass mode; the docs describe scraping, crawling, screenshots, and browser actions but never mention stealth/anti-detection techniques, and community comments explicitly question whether the product uses rotating/residential IPs at all, suggesting no such capability is documented.
- [claimed-docs] “Click, wait, or scroll before scraping or extracting a page, then check which interactions succeeded.”
- [community] “Seems wildly expensive, furthermore not a single mention of "ip" on homepage? Not using rotating ip's, residential proxies? AKA unusable for…”
- [community] “Are you using residential proxies? How do you handle websites that don't want to be scraped. EG if I start passing in Linkedin pages what is…”
Proxy rotation
developerRequest a proxy from a specific country to get geolocation-appropriate content
weight 2 · round drawnBrowserbasenone0/10The evidence pack contains no mention of proxy configuration, geolocation targeting, or country-specific proxy selection features—only general session/agent capabilities and unrelated community commentary.
Context.devnone0/10No documentation or feature mentions country-specific proxy selection or geolocation control; community comments even question whether Context.dev uses rotating/residential proxies at all, suggesting no such capability exists.
- [community] “Seems wildly expensive, furthermore not a single mention of "ip" on homepage? Not using rotating ip's, residential proxies? AKA unusable for…”
- [community] “Are you using residential proxies? How do you handle websites that don't want to be scraped. EG if I start passing in Linkedin pages what is…”
developerUse premium residential or datacenter proxies to bypass sites that are hard to scrape
weight 3 · round drawnBrowserbasenone0/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.
Context.devnone0/10No documentation or product page mentions residential/datacenter proxies, IP rotation, or anti-bot bypass infrastructure; community comments explicitly note the absence of any proxy mention and question whether the product can handle high-value/anti-scraping targets like LinkedIn.
- [community] “Seems wildly expensive, furthermore not a single mention of "ip" on homepage? Not using rotating ip's, residential proxies? AKA unusable for…”
- [community] “Are you using residential proxies? How do you handle websites that don't want to be scraped. EG if I start passing in Linkedin pages what is…”
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
developerRoute requests through a rotating pool of proxy IPs to avoid blocks
weight 3 · round drawnBrowserbasenone0/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'.
Context.devnone0/10No documentation or product page mentions proxy IP rotation, residential proxies, or anti-blocking infrastructure; a community comment on Hacker News explicitly notes the homepage never mentions 'ip' and questions whether rotating/residential proxies are used at all.
- [community] “Seems wildly expensive, furthermore not a single mention of "ip" on homepage? Not using rotating ip's, residential proxies? AKA unusable for…”
- [community] “Are you using residential proxies? How do you handle websites that don't want to be scraped. EG if I start passing in Linkedin pages what is…”
developerRoute multiple requests through the same proxy IP using a session identifier to maintain a consistent identity
weight 2 · round drawnBrowserbasenone0/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.
Context.devnone0/10No documentation or product page mentions session-based IP persistence, sticky sessions, or proxy identity management; the crawl/scrape/extract guides only cover content retrieval, not proxy control. A community comment even flags the total absence of any IP/residential-proxy discussion on the site, reinforcing that this capability isn't offered.
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Click, wait, or scroll before scraping or extracting a page, then check which interactions succeeded.”
- [community] “Seems wildly expensive, furthermore not a single mention of "ip" on homepage? Not using rotating ip's, residential proxies? AKA unusable for…”
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 BrowserbaseBrowserbase 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.”
Docs describe genuine bulk capability: async crawl jobs processing up to 25,000 pages in the background with progress tracking, plus a smaller 500-page synchronous crawl mode, which cover bulk operations across many web pages. However, evidence doesn't show bulk operations across arbitrary item sets (e.g., batch brand lookups, batch document parsing, or bulk extraction across a list of disparate items) beyond website crawling, and there's no independent/hands-on corroboration of large-scale batch reliability. Missing for 10: evidence of bulk/batch endpoints beyond crawling (e.g., batch document conversion, batch structured extraction across arbitrary item lists), and third-party validation of large-scale batch performance.
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to Context.devBrowserbase 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.”
Context.dev supports watching a page, sitemap, or dataset on a schedule and receiving signed change events, which functions as an event-trigger mechanism, but this is presented as a single monitoring feature rather than a general rule-definition system with configurable conditions and varied actions. Missing for 10: evidence of a rules/conditions engine, multiple trigger types beyond scheduled monitoring, and configurable downstream actions (e.g., webhooks to arbitrary endpoints, multi-step workflows).
- [claimed-docs] “Watch a page, sitemap, or structured dataset on a schedule and receive signed change events.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to BrowserbaseDocs 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.”
The docs describe a monitoring feature that watches a page, sitemap, or dataset 'on a schedule' and emits signed change events (context-dev-docs-9), which is a form of recurring job scheduling, but this is scoped only to change-detection, not general recurring crawl/extract/workflow jobs. Missing for 10: evidence of cron-style scheduling for arbitrary crawl/extract jobs, workflow chaining, or a broader job-scheduling API beyond the single 'monitor' feature.
- [claimed-docs] “Watch a page, sitemap, or structured dataset on a schedule and receive signed change events.”
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 drawnBrowserbasenone0/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.
Context.devnone0/10No evidence of team/organization features, shared scraper workflows, or role-based permission management beyond restricted API keys, which is a single-key scoping mechanism, not team/org collaboration. Missing for 10: organization/team creation, member invites, role-based access control across users, shared scraper/workflow assets.
- [claimed-docs] “Choose **Restricted** when an integration needs only selected operations; a restricted key with no permissions cannot call the API.”
Deployment flexibility
developerBuild and deploy custom serverless scraping scripts on the platform without managing my own infrastructure
weight 2 · round to BrowserbaseBrowserbase'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: …”
Context.devnone0/10Context.dev exposes a fixed set of hosted scraping endpoints (crawl, extract, screenshot, monitor, parse) accessed via API/CLI/MCP, but there is no evidence of a mechanism for developers to write and deploy their own custom scraping scripts or actors on the platform's infrastructure. This is a fair question for a web-scraping-as-a-service category, so absence of evidence yields 'none' rather than 'na'.
developerDeploy the scraping service via a Docker container for production use
weight 2 · round drawnBrowserbasenone0/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 drawnBrowserbasenone0/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: …”
Context.devnone0/10No evidence anywhere in the pack of an open-source or self-hostable version of Context.dev; it is presented exclusively as a hosted cloud API/service with CLI, MCP server, and SDKs pointing to context.dev endpoints. Missing for 10: any open-source repo, self-hosting instructions, Docker image, or license permitting local deployment.
Integrations
developerConnect the scraping API to no-code automation platforms like n8n or Zapier through a prebuilt connector
weight 2 · round drawnBrowserbasenone0/10No evidence of a prebuilt n8n or Zapier connector; the pack shows SDKs, MCP server, CLI, and agent framework integrations but nothing about no-code automation platforms.
Library compatibility
developerBuild scrapers using popular open-source automation libraries like Playwright, Puppeteer, Selenium, or Scrapy
weight 2 · round drawnBrowserbasenone0/10The evidence pack describes Browserbase's own control APIs, agent framework integrations, and web-scraping use cases, but never mentions compatibility or connection methods (e.g., CDP endpoints) for Playwright, Puppeteer, Selenium, or Scrapy specifically.
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 drawnBrowserbasenone0/10No evidence of any export/migration feature for scraped data or job configurations in a portable format; documentation covers session control, agent SDKs, and MCP/CLI integrations but nothing about data portability or avoiding lock-in.
Quickstart
developerPublish my custom scraper to a public marketplace and earn revenue when others use it
weight 1 · round drawnBrowserbasenone0/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 BrowserbaseBrowserbase 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.”
Context.devnone0/10Context.dev's evidence describes a general-purpose scraping/crawling/extraction API, CLI, and MCP server that developers configure themselves, but no marketplace of pre-built, ready-made scrapers for specific sites/use-cases is mentioned anywhere in the docs, community discussion, or probes.
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
developerStart building immediately using a library of ready-made project templates
weight 1 · round to BrowserbaseFirst-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 Context.devBrowserbase'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.”
Docs describe an extract endpoint that crawls relevant pages and returns an object matching a JSON Schema with controls for grounding, coverage, and freshness—no CSS/XPath selectors required, just a schema/instructions-driven approach. Missing for 10: no explicit mention of natural-language instruction fields (vs. schema-only), no independent hands-on benchmark of extraction accuracy/quality.
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
- [claimed-docs] “retrieve brand profiles with logos, colors, descriptions, and social links through the same API.”
developerPass a JSON schema so the API returns structured data matching that schema
weight 2 · round to Context.devBrowserbasenone0/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”
Docs explicitly describe extracting structured data by supplying a JSON Schema, with the API returning an object matching it, plus controls for grounding, coverage, and freshness; an OpenAPI spec is also available for verification. Missing for 10: independent hands-on confirmation of schema-conformance accuracy and no explicit mention of schema validation/error handling edge cases.
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
- [probe] “PROBE openapi: HTTP 200 at https://docs.context.dev/openapi.json — contains "openapi" key”
ai-native userHave an LLM read a page and decide what structured fields to pull out without pre-written selectors
weight 2 · round drawnBrowserbase'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.”
The extract-structured-data guide shows the product accepts a JSON Schema and returns matching structured data with grounding/coverage controls, which fits an LLM-driven extraction without pre-written CSS/XPath selectors. However, the evidence doesn't explicitly describe the underlying mechanism as an LLM 'deciding' fields freely versus schema-guided extraction, and there's no example of open-ended field discovery without a supplied schema. Missing for 10: evidence of schema-less/free-form field discovery, and independent hands-on confirmation of extraction quality without selectors.
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
developerPlug in a local or self-hosted LLM as the extraction backend instead of a cloud-only model
weight 2 · round drawnBrowserbasenone0/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 BrowserbaseDocs 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: …”
Context.dev's primary scrape endpoints convert pages to Markdown by default (docs-1, docs-2), and raw HTML is only mentioned as an output option for the async batch-crawl job that must be polled for completion (docs-3), not as an immediate single-call response for a single page. This satisfies the general 'scrape a page via API' need but not the specific 'single call → raw HTML' expectation. Missing for 10: documented synchronous single-page endpoint that returns raw HTML directly, independent confirmation of HTML fidelity/quality.
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
Data safety
data-engineerAutomatically detect and filter personally identifiable information out of scraped content before it reaches storage
weight 2 · round drawnBrowserbasenone0/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 to Context.devBrowserbasenone0/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.)
Docs explicitly describe a 'parse-documents' API that converts PDFs, Office documents, and spreadsheets into Markdown, including OCR recovery for scanned PDFs, delivered as a hosted API (no self-hosting required). Missing for 10: independent/hands-on verification of extraction quality and no explicit mention of PowerPoint file type beyond generic 'Office documents'.
- [claimed-docs] “Convert PDFs, Office documents, spreadsheets, and other files into Markdown. Recover scanned PDF pages with optional OCR.”
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 drawnBrowserbasenone0/10No evidence Browserbase provides automatic image captioning/alt-text generation for text-only model reasoning; docs mention browser control, scraping, markdown/HTML/JSON extraction but nothing about vision-to-text captioning of images.
Context.devnone0/10No evidence of automatic image captioning or alt-text generation for visual content; the product's extraction focuses on Markdown/JSON/screenshots and document parsing, not describing images for text-only models. Missing for 10: any mention of image captioning, vision-to-text description, or alt-text generation feature.
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 BrowserbaseBrowserbase 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”
Context.devnone0/10Context.dev's documented capabilities are URL-based (crawl, scrape, extract, sitemap discovery, screenshot, document parsing, monitoring) but no evidence shows a web-search endpoint that returns full page content for search results in one call — 'discover website URLs' only reads a site's own sitemap, not the open web.
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
- [claimed-docs] “Read a website's public sitemaps and return a filtered URL list without rendering each page.”
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
Selector extraction
developerExtract specific fields from a page using CSS or XPath selector rules
weight 3 · round drawnBrowserbasenone0/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 drawnBrowserbasenone0/10Browserbase's evidence covers browser session infrastructure, agent tooling, scraping, and automation, but there is no mention of intelligent chunking of large tables or any mechanism to fit extracted data within processing/context limits.
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 BrowserbaseBrowserbase 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.”
Context.dev supports browser actions (click/wait/scroll) before scraping, and screenshot rendering, implying JS execution via a real browser, and crawl/scrape guides return Markdown/HTML output — suggesting rendered SPA content is retrievable. However, there is no explicit statement that scraping fully executes JavaScript-heavy SPAs or waits for hydration/network-idle by default, and no independent/hands-on confirmation of SPA rendering fidelity. missing for 10: explicit documentation confirming full JS/SPA rendering (e.g., wait-for-network-idle, headless browser execution) as default behavior, and independent verification of rendered output correctness for JS-heavy sites.
- [claimed-docs] “Click, wait, or scroll before scraping or extracting a page, then check which interactions succeeded.”
- [claimed-docs] “Render an exact URL or a resolved site page and return a viewport, full-page, or offset PNG capture.”
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
developerHave the API wait for a specific selector to appear before returning the rendered page
weight 2 · round to Context.devBrowserbase 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.”
Docs describe browser actions supporting 'wait' among click/scroll before scraping or extracting a page, which directly matches waiting for content before returning rendered output, but there's no explicit mention of waiting for a CSS/DOM selector specifically (vs. fixed delays) nor independent confirmation of this behavior. missing for 10: explicit selector-based wait documentation, example showing selector syntax, independent/hands-on verification.
- [claimed-docs] “Click, wait, or scroll before scraping or extracting a page, then check which interactions succeeded.”
Interactive automation
developerAccess a managed remote browser sandbox for interactive, manual browsing workflows
weight 2 · round to BrowserbaseBrowserbase 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 BrowserbaseBrowserbase 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.”
Context.dev documents browser actions (click, wait, scroll) that can run before a scrape or extraction, which supports some interactive page manipulation, but there is no evidence of form-filling, typing credentials, or a persistent multi-step session capable of reaching authenticated/login-walled content. Missing for 10: explicit support for filling login forms/typing input, session/cookie persistence across interactions, and any documented login-wall use case or example.
- [claimed-docs] “Click, wait, or scroll before scraping or extracting a page, then check which interactions succeeded.”
developerScript page interactions like clicking, filling inputs, and scrolling before content is returned
weight 3 · round to Context.devBrowserbase'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.”
Docs explicitly describe a browser-actions capability allowing click, wait, or scroll before scraping/extracting content, with success verification, directly matching the story. Missing for 10: independent/hands-on corroboration of scripted interactions beyond first-party docs, and no detail on filling form inputs specifically.
- [claimed-docs] “Click, wait, or scroll before scraping or extracting a page, then check which interactions succeeded.”
Render configuration
developerControl the browser viewport width and height when rendering a page
weight 1 · round to Context.devBrowserbasenone0/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.”
The screenshot guide mentions a 'viewport' capture mode alongside full-page and offset options, implying some viewport-based rendering, but no evidence specifies developer control over exact width/height dimensions. missing for 10: explicit API parameters for setting viewport width and height, documentation confirming custom viewport sizing, and any hands-on confirmation.
- [claimed-docs] “Render an exact URL or a resolved site page and return a viewport, full-page, or offset PNG capture.”
Session persistence
developerPass my own session cookies so the API fetches pages requiring authentication
weight 2 · round drawnBrowserbasenone0/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 drawnBrowserbasenone0/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.”
Context.devnone0/10No evidence of persistent browser profiles, saved cookies, or reusable login/session state across requests; browser-actions doc only covers click/wait/scroll per single request. Missing for 10: any mention of persistent sessions, cookie storage, authentication state reuse, or profile management across multiple API calls.
- [claimed-docs] “Click, wait, or scroll before scraping or extracting a page, then check which interactions succeeded.”
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 Context.devBrowserbase 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…”
Context.dev is API-first: the product's core functions (crawl, extract, screenshot, monitor, brand data) are all documented as API endpoints with an OpenAPI spec, and the CLI/MCP/skill installs are just wrappers around that same API, implying no UI-exclusive functionality. missing for 10: explicit confirmation that the web UI itself exposes zero features unavailable via API (e.g., dashboard-only settings) and independent hands-on verification of full parity.
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
- [claimed-docs] “Watch a page, sitemap, or structured dataset on a schedule and receive signed change events.”
- [claimed-docs] “Call Context.dev from your terminal and use JSON responses in scripts or CI.”
- [probe] “PROBE openapi: HTTP 200 at https://docs.context.dev/openapi.json — contains "openapi" key”
- [probe] “official CLI documented at https://docs.context.dev/install-cli”
ai-native userExport all of my data in open formats and leave
weight 3 · round to Context.devBrowserbasenone0/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…”
Context.dev's outputs (Markdown, JSON, HTML) are inherently open, portable formats rather than proprietary lock-in formats, and structured extraction lets users get their scraped/monitored data in JSON Schema-conformant form (docs-1, docs-3, docs-4, docs-9). However there is no explicit account-level 'export all your data and leave' feature (e.g., bulk export of saved crawls, monitors, API key configs, or account deletion with data portability) documented anywhere in the evidence. Missing for 10: dedicated account/data export tooling, documentation of account deletion/data portability guarantees, and independent confirmation that historical crawl/monitor data can be bulk-exported.
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
- [claimed-docs] “Watch a page, sitemap, or structured dataset on a schedule and receive signed change events.”
ai-native userRead the product's source under an open license
weight 2 · round drawnBrowserbasenone0/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 drawnBrowserbasenone0/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 Context.devBrowserbase'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”
First-party docs consistently describe scraping/crawling output as Markdown (sync and async crawl endpoints, single-page scrape, document parsing all return Markdown rather than raw HTML), and this is corroborated by a customer case study (SiteGPT) using it to build a knowledge base. Missing for 10: independent hands-on verification of markdown output quality/cleanliness and no explicit sample output shown.
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Convert PDFs, Office documents, spreadsheets, and other files into Markdown. Recover scanned PDF pages with optional OCR.”
- [claimed-docs] “SiteGPT, the AI chatbot platform for customer support, switched from Firecrawl to Context.dev to scrape entire websites and turn them into t…”
developerChoose exactly which output format is returned, such as markdown, HTML, text, or frontmatter
weight 2 · round to Context.devBrowserbase'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”
Docs show explicit format choice for Markdown (sync/async crawl) and HTML (async crawl), plus JSON output via structured extraction, but no mention of plain 'text' or 'frontmatter' output options anywhere in the docs. missing for 10: explicit text output mode, frontmatter output mode, independent confirmation of format selection working in practice.
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
developerReceive scraped content as structured JSON
weight 3 · round to Context.devDocs 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”
Docs explicitly describe extracting structured JSON matching a user-supplied JSON Schema from crawled pages, with controls for grounding, coverage, and freshness, plus an OpenAPI spec confirming API-driven JSON responses and a CLI that returns JSON for scripting/CI. missing for 10: independent hands-on verification of JSON extraction accuracy/quality beyond vendor docs.
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
- [probe] “PROBE openapi: HTTP 200 at https://docs.context.dev/openapi.json — contains "openapi" key”
- [claimed-docs] “Call Context.dev from your terminal and use JSON responses in scripts or CI.”
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 Context.devBrowserbase 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: …”
Context.dev's core offering is scraping/crawling websites directly into clean Markdown (and JSON) for AI agents, handling rendering, browser actions, and document parsing so the user doesn't deal with raw HTML; this is corroborated by docs and a real-world migration story (SiteGPT switching from Firecrawl). missing for 10: independent hands-on benchmark of output cleanliness/quality versus alternatives, and no detail on how well it strips boilerplate/ads beyond doc claims.
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Click, wait, or scroll before scraping or extracting a page, then check which interactions succeeded.”
- [claimed-docs] “Convert PDFs, Office documents, spreadsheets, and other files into Markdown. Recover scanned PDF pages with optional OCR.”
- [claimed-docs] “SiteGPT, the AI chatbot platform for customer support, switched from Firecrawl to Context.dev to scrape entire websites and turn them into t…”
ai-native userRequest semantically chunked output instead of one large content blob, so it feeds cleanly into a retrieval pipeline
weight 2 · round drawnBrowserbasenone0/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”
Context.devnone0/10Context.dev's docs describe scraping/crawling into full-page Markdown, JSON extraction, and document parsing, but nowhere mention a chunking feature (e.g., configurable chunk size, semantic segmentation, or overlap controls) intended for retrieval pipelines. Output is delivered as whole-page Markdown/HTML/JSON blobs per page, not sub-page semantic chunks.
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Convert PDFs, Office documents, spreadsheets, and other files into Markdown. Recover scanned PDF pages with optional OCR.”
Visual capture
developerCapture a screenshot of a full page or a specific selected area
weight 2 · round to Context.devBrowserbasenone0/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.”
Docs explicitly describe rendering an exact URL or resolved page and returning a viewport, full-page, or offset PNG capture, directly matching the story of full-page or selected-area screenshots. Missing for 10: independent/hands-on corroboration of screenshot quality or selector-based area capture beyond viewport/offset options.
- [claimed-docs] “Render an exact URL or a resolved site page and return a viewport, full-page, or offset PNG capture.”
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 drawnBrowserbasenone0/10No evidence in the pack indicates any feature for automatic cost-optimized configuration selection; Browserbase docs focus on session control, agent tooling, and scaling but never mention cost-aware auto-selection of configurations.
developerBlock ads on the target page to speed up scraping requests
weight 1 · round drawnBrowserbasenone0/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.”
Context.devnone0/10No evidence pack item mentions ad-blocking, resource blocking, or any performance optimization feature to skip ads/media during scraping; the docs cover crawling, extraction, screenshots, and browser actions but never ad-blocking specifically. Missing for 10: any documentation of an ad-block or resource-blocking option, any performance/speed benefit tied to blocking ads.
developerBlock images and CSS resources by default to reduce bandwidth and speed up requests
weight 1 · round drawnBrowserbasenone0/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 drawnBrowserbasenone0/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 drawnBrowserbasenone0/10No evidence in the pack addresses billing behavior when plan quotas are exceeded—nothing on overage charges vs hard cutoffs is documented.
developerWhether failed, blocked, or empty-result requests still consume my billing quota
weight 2 · round to Context.devBrowserbasenone0/10No evidence in the pack addresses billing treatment of failed, blocked, or empty-result sessions—pricing docs, session lifecycle, or FAQ content on quota consumption for unsuccessful requests are absent.
Docs explicitly state that in the timeout/return-partial flow, if no usable result exists the request 'fails without a charge,' directly addressing billing behavior on failure. However, there's no broader documentation covering all failure modes (e.g., blocked requests, empty-result extractions, rate-limited calls) confirming whether they also skip billing. Missing for 10: explicit policy for blocked requests, empty JSON extraction results, and general error responses beyond the timeout optimization guide; independent/community confirmation of billing behavior.
- [claimed-docs] “`return-partial` | Return usable completed work with a completion marker. If no usable result exists, fail without a charge.”
developerSet a spending cap or usage alert so proxy/credit consumption doesn't silently blow past my budget
weight 3 · round drawnBrowserbasenone0/10No evidence of spending caps, budget alerts, or usage-limit controls anywhere in the docs or community pack; all citations concern browser automation features, not billing/usage controls.
Performance tuning
developerTrade off latency against completeness by controlling exactly when content is returned
weight 1 · round to Context.devBrowserbasenone0/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”
Context.dev offers explicit controls that trade off latency vs completeness: synchronous small crawls (fast, limited to 500 pages) vs async background crawls up to 25,000 pages, plus a 'return-partial' timeout policy that returns usable completed work with a completion marker rather than waiting for full completion. This directly supports controlling when content is returned along a latency/completeness axis, though it's documented only in claimed-docs with no independent hands-on validation of the tradeoff behavior. Missing for 10: independent/community confirmation of the return-partial and sync/async tradeoff working as documented, and more granular mid-request streaming or partial-result controls beyond the two crawl modes and timeout policy.
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “`return-partial` | Return usable completed work with a completion marker. If no usable result exists, fail without a charge.”
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 drawnBrowserbasenone0/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”
Context.devnone0/10Docs mention rate-limit headers exist and per-minute limits apply, but there is no evidence of tier-specific concurrency/session caps or the cost to raise them. Missing for 10: documented tier limits table, concrete numeric caps per plan, and pricing/upgrade path to raise the cap.
- [claimed-docs] “Authenticated API responses expose these headers when a per-minute limit applies”
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 drawnBrowserbasenone0/10No evidence in the pack mentions data residency, region selection, or storage location controls for Browserbase sessions or data; all evidence covers browser automation features and community sentiment unrelated to data location.
Context.devnone0/10No evidence anywhere in the pack mentions data residency, region selection, or storage location options for Context.dev; the product is a web-scraping/data API with no documented control over where data is stored. Missing for 10: any mention of regional hosting, data residency options, or compliance certifications tied to storage location.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnBrowserbasenone0/10No evidence pack item mentions data usage policies, AI training opt-outs, or privacy commitments regarding customer data; all citations focus on browser automation features and product capabilities, not privacy posture.
ai-native userControl data retention and deletion
weight 2 · round drawnBrowserbasenone0/10No evidence in the pack addresses data retention policies, session data deletion controls, or privacy/compliance settings for stored session artifacts. The docs focus entirely on browser automation capabilities, not data lifecycle management.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnBrowserbasenone0/10No evidence pack item mentions telemetry, usage tracking, opt-out settings, or privacy controls for Browserbase; the axis is applicable to a cloud service handling browser sessions/data but no supporting documentation is present.
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 drawnBrowserbasenone0/10Browserbase offers browser automation, session infrastructure, web search, and URL-to-content extraction, but no evidence describes adaptive crawling logic that autonomously determines when 'enough' information has been gathered to stop crawling further.
Context.devnone0/10The docs describe crawling with fixed page caps (500 for sync, 25,000 for async) and extraction with 'coverage' controls, but there is no evidence of an adaptive mechanism that halts crawling once sufficient information for a query has been gathered.
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
Batch processing
data-engineerBatch scrape thousands of URLs asynchronously
weight 3 · round to Context.devBrowserbase 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.”
Docs explicitly describe an async background crawl job handling up to 25,000 pages with progress tracking and retrieval on completion, plus rate-limit headers and partial-result timeout handling that support reliability at scale. However, this is framed as crawling one site rather than an arbitrary list of thousands of distinct URLs, and there is no independent/hands-on evidence confirming real-world throughput or reliability at that scale. Missing for 10: evidence of scraping an arbitrary batch/list of thousands of URLs (not just one site's crawl), independent benchmarks or user reports validating async batch reliability at scale.
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “`return-partial` | Return usable completed work with a completion marker. If no usable result exists, fail without a charge.”
- [claimed-docs] “Authenticated API responses expose these headers when a per-minute limit applies”
developerApply different crawl configurations to different URL patterns within a single batch job
weight 1 · round drawnBrowserbasenone0/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.”
Context.devnone0/10The docs describe a single batch crawl job (up to 25,000 pages) with one set of settings, but there is no evidence of applying different crawl configurations to different URL patterns within the same job.
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
Concurrency
data-engineerSpin up many concurrent scraping sessions to gather data at scale
weight 3 · round to BrowserbaseDocs 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.”
Context.dev supports large single crawls (up to 25,000 pages async) and exposes rate-limit headers, implying some capacity for scaled scraping, but there is no explicit documentation of running many concurrent scraping sessions or session-level concurrency controls. Community feedback also raises doubts about scaling to high-volume/high-value scraping due to lack of rotating/residential proxy support. missing for 10: explicit concurrency/session-limit documentation, evidence of parallel job orchestration, and independent benchmarks confirming multi-session scale.
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Authenticated API responses expose these headers when a per-minute limit applies”
- [community] “Seems wildly expensive, furthermore not a single mention of "ip" on homepage? Not using rotating ip's, residential proxies? AKA unusable for…”
- [community] “Are you using residential proxies? How do you handle websites that don't want to be scraped. EG if I start passing in Linkedin pages what is…”
Crawl compliance
data-engineerConfigure the crawler to respect robots.txt rules and target-site rate limits automatically
weight 2 · round drawnBrowserbasenone0/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.
Context.devnone0/10No documentation describes automatic robots.txt compliance or target-site rate-limiting; the only rate-limit doc (context-dev-docs-18) covers API-caller limits, not crawl politeness. Community evidence (context-dev-comm-4) even states the company relies on a manual opt-out blocklist rather than respecting robots.txt automatically, undercutting the story further.
- [claimed-docs] “Authenticated API responses expose these headers when a per-minute limit applies”
- [community] “\"Websites can opt out of our service, and we respect these requests and add them to our block list.\" I.e: robots.txt already exists and is…”
Fault tolerance
data-engineerResume a crashed deep crawl from a saved checkpoint instead of restarting from scratch
weight 2 · round drawnBrowserbasenone0/10No evidence of checkpointing or resumable crawl functionality; Browserbase docs describe session creation, control, and scaling but nothing about saving/restoring crawl state after a crash.
Context.devnone0/10Evidence shows async batch crawling with progress tracking (up to 25,000 pages) but no mention of checkpointing or resuming a crashed crawl from a saved state; only completed-job retrieval or partial-result return on timeout is documented, not crash recovery/resume.
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “`return-partial` | Return usable completed work with a completion marker. If no usable result exists, fail without a charge.”
Operational transparency
data-engineerCheck a public status page showing uptime history and past incident postmortems before committing to the service
weight 2 · round drawnBrowserbasenone0/10No evidence of a public status page, uptime history, or incident postmortems anywhere in the evidence pack; only product feature docs and unrelated community comments are provided.
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 Context.devMarketing 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.”
Docs explicitly describe a monitoring feature that watches a page, sitemap, or dataset on a schedule and delivers signed change events, directly matching the story's core ask. However, there's no independent/hands-on corroboration of this feature working in practice, and no detail on notification channels (webhooks, email, etc.) or reliability at scale. Missing for 10: independent evidence of monitoring reliability, details on notification delivery mechanisms/channels, and evidence of scale/performance under continuous monitoring.
- [claimed-docs] “Watch a page, sitemap, or structured dataset on a schedule and receive signed change events.”
data-engineerMonitor job performance, validate data quality, and receive alerts when something fails
weight 2 · round to BrowserbaseBrowserbase 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.”
Context.dev offers async crawl jobs with progress tracking (docs-3), some quality controls like grounding/coverage/freshness for extraction (docs-4), and scheduled change monitoring with signed events (docs-9), which loosely cover job status and alerting. However there is no dedicated job-performance dashboard, no explicit failure-alert/webhook system for scraping jobs, and no formal data-quality validation framework described. Missing for 10: job performance metrics/dashboard, explicit failure alerting (e.g. webhooks on job error), and structured data quality checks beyond extraction fidelity.
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “Crawl relevant pages and return an object that matches your JSON Schema, with controls for grounding, coverage, and freshness.”
- [claimed-docs] “Watch a page, sitemap, or structured dataset on a schedule and receive signed change events.”
- [claimed-docs] “`return-partial` | Return usable completed work with a completion marker. If no usable result exists, fail without a charge.”
- [claimed-docs] “Authenticated API responses expose these headers when a per-minute limit applies”
developerMonitor live system metrics and worker/browser pool status through a real-time dashboard
weight 1 · round drawnBrowserbasenone0/10Evidence covers session control, agent frameworks, and scraping use cases but contains no mention of a real-time dashboard for monitoring live system metrics or worker/browser pool status; no dashboard UI, metrics endpoint, or observability feature is documented.
developerSchedule scraping jobs to run automatically at specific times
weight 2 · round to BrowserbaseDocs 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.”
Context.dev's monitor-website-changes feature watches a page, sitemap, or dataset "on a schedule" and emits change events, which functions as scheduled recurring scraping, but this is framed narrowly as change-detection rather than a general-purpose cron/scheduler for arbitrary scrape/crawl jobs. Missing for 10: explicit documentation of configurable schedule intervals/cron syntax, ability to schedule full crawl or extract jobs (not just change monitors), and any independent/hands-on confirmation of scheduling reliability.
- [claimed-docs] “Watch a page, sitemap, or structured dataset on a schedule and receive signed change events.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
Site crawling
data-engineerRun a deep crawl using a breadth-first strategy with a configurable maximum page limit
weight 2 · round to Context.devBrowserbasenone0/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.
Context.dev documents crawling with configurable maximum page limits (500 for sync, up to 25,000 for async batch crawls), satisfying the page-limit part of the story, but no evidence describes a selectable crawl strategy (e.g., breadth-first vs depth-first) as a configurable parameter. Missing for 10: explicit breadth-first strategy option/documentation, evidence of strategy configurability alongside the page limit.
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
developerCrawl an entire website and get content from all its pages with one request
weight 3 · round to Context.devBrowserbasenone0/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”
Docs describe a one-request crawl endpoint that returns page Markdown for a site (up to 500 pages synchronously) plus an async option for up to 25,000 pages, and a real customer (SiteGPT) is cited using it to scrape entire websites into a knowledge base. Missing for 10: independent hands-on verification of crawl completeness/accuracy at scale and no third-party benchmark of crawl reliability beyond vendor docs and one customer quote.
- [claimed-docs] “Crawl a small website section and return page Markdown in one response, with a maximum of 500 pages.”
- [claimed-docs] “Crawl up to 25,000 pages in a background batch, track progress, and retrieve Markdown or HTML when the job finishes.”
- [claimed-docs] “SiteGPT, the AI chatbot platform for customer support, switched from Firecrawl to Context.dev to scrape entire websites and turn them into t…”
- [claimed-docs] “Scrape websites into Markdown, crawl linked pages, and extract JSON for AI agents and applications.”
developerInstantly discover all URLs on a website without fully crawling it
weight 2 · round to Context.devBrowserbasenone0/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.
Context.dev has a dedicated URL discovery endpoint that reads a site's public sitemaps and returns a filtered URL list "without rendering each page," explicitly avoiding a full crawl — directly matching the story. Missing for 10: independent/hands-on corroboration of discovery speed or scale beyond vendor docs.
- [claimed-docs] “Read a website's public sitemaps and return a filtered URL list without rendering each page.”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableBrowserbasen/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”
Context.devn/aContext.dev is a web-scraping/data-extraction API/service that itself exposes an MCP server (context-dev-docs-13, context-dev-probe-3) so that AI clients can call ITS tools — it is not an agentic product that would consume other MCP servers' tools. The 'plug MCP servers in' client-role story is a category error for this kind of product.
- [claimed-docs] “Connect your AI client to Context.dev tools for live web and company data.”
- [probe] “official MCP server documented at https://mcp.context.dev/mcp”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableBrowserbasenone0/10No evidence of versioning, review workflows, or rollback capabilities for automations; the docs cover session control, scraping, agent frameworks, and scheduling but nothing about version history or reverting changes to automations.