Hyperbrowser vs Smooth

Caching

1. developerCache resolved actions or generated code so repeat runs replay deterministically at lower cost and latency than re-prompting the LLM

   weight 2 · round drawn
   Hyperbrowser—none0/10

   No evidence of any caching mechanism for resolved actions or generated code; Hyperbrowser's docs cover agents, extraction, sessions, stealth, proxies, and sandboxes but nothing about replaying deterministic cached actions to avoid re-prompting the LLM.

   ⚑ flag

   Smooth—none0/10

   No evidence of caching resolved actions/generated code for deterministic, cheaper replay; docs mention persistent sessions (auth reuse), structured outputs, and cost efficiency via small models, but nothing about caching or replay of prior task executions to skip re-prompting the LLM. Missing for 10: any mention of action/result caching, replay mechanism, or cost/latency comparison for repeat runs.

   • [claimed-docs] “Log in once, then reuse that authentication for future tasks.”
   • [claimed-docs] “Structured outputs allow you to write deterministic code based on the agent's output. To activate structured outputs, set the `response_mode…”
   • [claimed-docs] “Smooth uses small and efficient AI models, making it 7x more affordable than browser-use.”

   proof ↗⚑ flag

Dom

1. developerDrive the page through DOM-understanding action primitives (act/click/type on described elements) that survive selector and layout changes

   weight 3 · round to Hyperbrowser
   Hyperbrowser~partialclaimed6/10

   HyperAgent's page.ai() lets developers issue natural-language commands (e.g., 'search for flights... select the cheapest option') instead of writing selectors, and docs explicitly say it lets you 'write natural language commands instead of complex selectors,' matching the DOM-understanding action-primitive story. However, evidence shows a single high-level task-execution call rather than discrete act/click/type primitives, and there's no independent/hands-on evidence confirming resilience to selector or layout changes. Missing for 10: granular primitive-level API docs (separate click/type/act calls), independent verification of survival across DOM/layout changes, and community confirmation of reliability.

   • [claimed-docs] “await page.ai("search for flights from Miami to LAX, select the cheapest option");”
   • [claimed-docs] “HyperAgent is our open-source tool that supercharges Playwright with AI.”
   • [claimed-docs] “HyperAgent is an open-source browser automation framework that extends Playwright with AI capabilities. Write natural language commands inst…”

   proof ↗⚑ flag

   Smooth~partialcommunity5/10

   Smooth's docs describe a 'Session Workflow' that lets you orchestrate smaller tasks, navigate to URLs, and extract data within a persistent session, and the whole product is framed as an AI browser agent that understands pages rather than relying on brittle selectors (smooth-docs-7, smooth-gh-1). However, there is no explicit documentation of discrete act/click/type primitives on described elements, nor any evidence/testing showing these survive selector or layout changes — community comments even note it doesn't fully close the gap versus Playwright-style tools (smooth-comm-8). Missing for 10: explicit act/click/type API reference, documented resilience testing against DOM/selector changes, independent verification of robustness claims.

   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [github] “The Smooth CLI is a browser for AI agents, enabling tools like Claude Code to navigate the web quickly, cheaply, and reliably.”
   • [community] “agent-browser helped a lot over playwright but doesn't completely close the gap.”

   proof ↗⚑ flag

Observe

1. developerPreview candidate actions on the current page (observe/plan) before committing the agent to act

   weight 1 · round drawn
   Hyperbrowser—none0/10

   Hyperbrowser's agent APIs (page.ai(), HyperAgent, MCP tools) execute actions directly via natural-language commands, and extract()/scrape() only pull data — there is no documented observe/plan primitive that lets a developer preview candidate actions before the agent commits to acting. missing for 10: an explicit plan/observe API or dry-run mode, evidence of returning candidate actions for approval, any UI or SDK method to inspect proposed steps prior to execution.

   • [claimed-docs] “await page.ai("search for flights from Miami to LAX, select the cheapest option");”
   • [claimed-docs] “HyperAgent is our open-source tool that supercharges Playwright with AI.”
   • [claimed-docs] “HyperAgent is an open-source browser automation framework that extends Playwright with AI capabilities. Write natural language commands inst…”
   • [claimed-docs] “The `page.extract()` method pulls structured data from web pages. Define what you want using natural language and optionally enforce a schem…”

   proof ↗⚑ flag

   Smooth—none0/10

   Smooth's docs describe live viewing of actions as they execute (live_url) and data extraction, but there is no evidence of a distinct observe/plan step that lets a developer preview candidate actions before committing the agent to act.

   ⚑ flag

Vision

1. developerSwitch to a vision or computer-use action mode that operates on screenshots for canvases and UIs the DOM path can't handle

   weight 2 · round to Hyperbrowser
   Hyperbrowser~partialclaimed3/10

   Hyperbrowser documents 'built-in support for Claude, OpenAI, Gemini, Grok, and BrowserUse agents' (model-native agents) and can return screenshots via fetch/scrape APIs, hinting at vision-capable agent modes, but there is no explicit documentation of a dedicated 'vision' or 'computer-use' action mode that operates purely on screenshots for canvases/UIs the DOM can't reach. Missing for 10: explicit computer-use/vision mode docs, screenshot-based click/type action primitives, and any example of handling canvas/non-DOM UI elements.

   • [claimed-docs] “Built in support for Claude, OpenAI, Gemini, Grok, and BrowserUse agents.”
   • [claimed-docs] “Fetches a web page and returns the content in various formats (HTML, Markdown, JSON, screenshot, etc.)”
   • [github] “`scrape_webpage` - Extract formatted (markdown, screenshot etc) content from any webpage”

   proof ↗⚑ flag

   Smooth—none0/10

   The evidence pack covers Smooth's session workflows, extraction, custom tools, proxies, and CAPTCHA solving, but nowhere mentions a vision/computer-use mode operating on screenshots for canvases or non-DOM UI elements. This axis is plausible for a browser-automation agent, but no documentation or community report confirms such a capability exists.

   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [claimed-docs] “Extract structured data from the current page by providing a schema.”
   • [claimed-docs] “Custom tools allow you to give Smooth any arbitrary function as a tool.”
   • [github] “The Smooth CLI is a browser for AI agents, enabling tools like Claude Code to navigate the web quickly, cheaply, and reliably.”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Hyperbrowser✓fullprobed8/10

   Probe confirms a live, well-formed llms.txt at hyperbrowser.ai/llms.txt (HTTP 200) describing the product for agent consumption, and docs additionally expose an official MCP server that agents can connect to for structured access. missing for 10: no docs.md/full agent-oriented docs mirror (docs.md 404) and no OpenAPI spec discoverable, so agent-friendly docs coverage beyond llms.txt is incomplete.

   • [probe] “PROBE llms.txt: HTTP 200 at https://hyperbrowser.ai/llms.txt # Hyperbrowser > Hyperbrowser provides fast cloud browsers for AI agents and a…”
   • [probe] “PROBE docs-md: HTTP 404 at https://hyperbrowser.ai/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://hyperbrowser.ai/openapi.json, https://hyperbrowser.ai/swagger.json, https://hyperbrowser.ai/…”
   • [claimed-docs] “The Hyperbrowser MCP server provides a standardized interface for AI models to access powerful web automation capabilities like scraping, st…”
   • [probe] “official MCP server documented at https://hyperbrowser.ai/docs/integrations/model-context-protocol”

   proof ↗⚑ flag

   Smooth✓fullprobed8/10

   A direct probe confirms docs.smooth.sh/llms.txt returns HTTP 200 with a structured index of docs pages, and the docs themselves are mirrored as .md files (e.g. live-share.md, proxies.md) enabling agent-friendly consumption. One community comment notes the docs pages aren't fully token-efficient, a minor caveat. Missing for 10: independent verification that agents actually consume llms.txt effectively, and no evidence of additional agent-specific doc formats beyond the single llms.txt file.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.smooth.sh/llms.txt # Smooth ## Docs - [Introduction](https://docs.smooth.sh/index.md): Welcome to…”
   • [claimed-docs] “When running a task, you will receive a `live_url`, which can be used to view the agent actions live.”
   • [claimed-docs] “Log in once, then reuse that authentication for future tasks.”
   • [community] “Ironically, the landing page and docs pages of Smooth aren't all that token-efficient!”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Hyperbrowser
   Hyperbrowser✓fullclaimed8/10

   Hyperbrowser is fundamentally a headless, API/SDK/CLI-driven cloud browser service — sessions run in the cloud with no local browser needed, exposing WebSocket/CDP endpoints for Playwright/Puppeteer plus official SDKs and a CLI (`hx`), which is exactly the shape needed for CI/automation pipelines. Missing for 10: explicit CI pipeline examples (e.g., GitHub Actions docs) and independent hands-on confirmation of CI usage.

   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically. Each session gives you a WebSocket endpo…”
   • [claimed-docs] “Control Chrome browsers in the cloud using Puppeteer, Playwright, or our SDKs—no infrastructure management required.”
   • [claimed-docs] “Official SDKs for integrating Hyperbrowser into your applications”
   • [claimed-docs] “Set up the Hyperbrowser CLI (`hx`) and/or the SDKs to start working with sandboxes.”
   • [claimed-docs] “Connect your existing automation scripts to cloud browsers”
   • [claimed-docs] “The Scrape API allows you to get the data you want from web pages with a single call. You can scrape page content and capture its data in va…”
   • [claimed-docs] “The Crawl API allows you to crawl websites and get data from multiple pages in a single request. Starting from a URL, it can navigate throug…”

   proof ↗⚑ flag

   Smooth~partialprobed6/10

   Smooth is explicitly designed as an SDK/API and CLI for programmatic browser automation, with 'plug-and-play' 4-line-of-code task execution and custom tools/session workflows suited to unattended automation, and a documented CLI (smooth-gh-1, smooth-docs-1, smooth-probe-3). However there is no explicit documentation or example of running it inside a CI pipeline (e.g., GitHub Actions), headless flags, or exit-code/automation-specific guidance. Missing for 10: explicit CI/CD integration docs or examples, confirmation of non-interactive/headless auth flow for pipelines, independent confirmation of CI usage.

   • [claimed-docs] “Plug-and-play: Run a task in just 4 lines of code, making it easy to integrate into your workflow.”
   • [github] “The Smooth CLI is a browser for AI agents, enabling tools like Claude Code to navigate the web quickly, cheaply, and reliably.”
   • [probe] “official CLI documented at https://docs.smooth.sh/cli/overview”
   • [claimed-docs] “Custom tools allow you to give Smooth any arbitrary function as a tool.”
   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Hyperbrowser—none0/10

   Hyperbrowser documents itself as an MCP *server* that exposes its own scraping/automation tools to AI models (hyperbrowser-docs-8, hyperbrowser-gh-1, hyperbrowser-probe-4), but this is the opposite of the story, which asks whether Hyperbrowser (or its HyperAgent/browser-agent features) can act as an MCP *client* and plug in external MCP servers to use their tools. No evidence describes Hyperbrowser consuming or connecting to third-party MCP servers.

   • [claimed-docs] “The Hyperbrowser MCP server provides a standardized interface for AI models to access powerful web automation capabilities like scraping, st…”
   • [github] “`scrape_webpage` - Extract formatted (markdown, screenshot etc) content from any webpage”
   • [probe] “official MCP server documented at https://hyperbrowser.ai/docs/integrations/model-context-protocol”

   proof ↗⚑ flag

   Smooth—none0/10

   Smooth documents a 'custom tools' feature for arbitrary functions but there is no mention anywhere in docs, GitHub, or community discussion of MCP server support or integration, so this applicable capability is unevidenced.

   • [claimed-docs] “Custom tools allow you to give Smooth any arbitrary function as a tool.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.smooth.sh/llms.txt # Smooth ## Docs - [Introduction](https://docs.smooth.sh/index.md): Welcome to…”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Hyperbrowser
   Hyperbrowser✓fullprobed8/10

   Hyperbrowser ships an official MCP server (hyperbrowser.ai/docs/integrations/model-context-protocol) exposing tools like scrape_webpage, extraction, and crawling for AI agents to connect to, backed by a public GitHub repo listing the tool set. Missing for 10: independent/hands-on confirmation of the MCP server working with a real agent client and more detail on the full tool list/setup.

   • [claimed-docs] “The Hyperbrowser MCP server provides a standardized interface for AI models to access powerful web automation capabilities like scraping, st…”
   • [github] “`scrape_webpage` - Extract formatted (markdown, screenshot etc) content from any webpage”
   • [probe] “official MCP server documented at https://hyperbrowser.ai/docs/integrations/model-context-protocol”

   proof ↗⚑ flag

   Smooth—none0/10

   Smooth is a browser-automation SDK/CLI used by agents like Claude Code, but the evidence pack contains no mention of an official MCP server or MCP protocol integration anywhere in its docs, GitHub repo, or community discussion — only generic SDK/CLI methods and custom tool functions are documented.

   • [github] “The Smooth CLI is a browser for AI agents, enabling tools like Claude Code to navigate the web quickly, cheaply, and reliably.”
   • [claimed-docs] “Custom tools allow you to give Smooth any arbitrary function as a tool.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.smooth.sh/llms.txt # Smooth ## Docs - [Introduction](https://docs.smooth.sh/index.md): Welcome to…”
   • [probe] “official CLI documented at https://docs.smooth.sh/cli/overview”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Smooth
   Hyperbrowser~partialclaimed5/10

   Docs mention an official CLI called `hx` for setting up and working with sandboxes, confirming a first-party CLI exists, but the evidence pack gives no further detail on its command set, installation, or broader agentic workflow support beyond sandboxes. missing for 10: fuller CLI documentation (commands, usage examples), independent/hands-on confirmation, and evidence it covers more than just sandbox setup.

   • [claimed-docs] “Set up the Hyperbrowser CLI (`hx`) and/or the SDKs to start working with sandboxes.”

   proof ↗⚑ flag

   Smooth✓fullprobed7/10

   GitHub repo describes Smooth CLI explicitly as 'a browser for AI agents, enabling tools like Claude Code to navigate the web' and a docs probe confirms an official CLI overview page exists, showing a first-party CLI built for AI-agent workflows. Missing for 10: independent hands-on confirmation of the CLI's usage/reliability and more detailed CLI documentation content beyond the overview link.

   • [github] “The Smooth CLI is a browser for AI agents, enabling tools like Claude Code to navigate the web quickly, cheaply, and reliably.”
   • [probe] “official CLI documented at https://docs.smooth.sh/cli/overview”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to Hyperbrowser
   Hyperbrowser✓fullprobed8/10

   Hyperbrowser exposes a fully documented REST API (Scrape, Crawl, Extract, Sessions, Agents) plus official SDKs and a CLI, all covered in detailed first-party docs, and community comments confirm real developers have used the API/docs (even correcting a code sample). Missing for 10: a discoverable OpenAPI/swagger spec (probe found only 404s) and independent third-party validation of full API completeness.

   • [claimed-docs] “The Scrape API allows you to get the data you want from web pages with a single call. You can scrape page content and capture its data in va…”
   • [claimed-docs] “The Crawl API allows you to crawl websites and get data from multiple pages in a single request. Starting from a URL, it can navigate throug…”
   • [claimed-docs] “The Extract API allows you to extract structured data from web pages using AI. You can define a schema and prompt, and Hyperbrowser will ext…”
   • [claimed-docs] “Official SDKs for integrating Hyperbrowser into your applications”
   • [claimed-docs] “Control Chrome browsers in the cloud using Puppeteer, Playwright, or our SDKs—no infrastructure management required.”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically. Each session gives you a WebSocket endpo…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://hyperbrowser.ai/llms.txt # Hyperbrowser > Hyperbrowser provides fast cloud browsers for AI agents and a…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://hyperbrowser.ai/openapi.json, https://hyperbrowser.ai/swagger.json, https://hyperbrowser.ai/…”
   • [community] “one quick nit on your docs: https://docs.hyperbrowser.ai/guides/scrape-site ... should be [corrected code with 'let' instead of 'const']”

   proof ↗⚑ flag

   Smooth~partialprobed6/10

   Smooth provides documented SDK/API methods (task execution, session workflows, structured outputs, custom tools, proxies) and an llms.txt docs index plus a CLI, showing a documented programmatic interface for AI-native use. However, no formal OpenAPI/REST spec was found (404s on all standard paths), and there is no independent corroboration of API robustness beyond vendor docs. missing for 10: a discoverable OpenAPI/REST spec, independent/hands-on verification of API completeness and stability.

   • [claimed-docs] “Plug-and-play: Run a task in just 4 lines of code, making it easy to integrate into your workflow.”
   • [claimed-docs] “Custom tools allow you to give Smooth any arbitrary function as a tool.”
   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.smooth.sh/llms.txt # Smooth ## Docs - [Introduction](https://docs.smooth.sh/index.md): Welcome to…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.smooth.sh/openapi.json, https://docs.smooth.sh/swagger.json, https://docs.smooth.sh/api…”
   • [probe] “official CLI documented at https://docs.smooth.sh/cli/overview”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Hyperbrowser—none0/10

   No evidence of scoped or least-privilege API key/credential management for agents — only mentions of a generic 'credits' usage-tracking system, not permission-scoped API keys or role-based access controls. missing for 10: any API key scoping/permission model, docs on creating restricted-scope credentials, or agent-specific credential issuance.

   • [claimed-docs] “Hyperbrowser tracks your usage via `credits` which can be acquired through a subscription or through a direct purchase.”

   proof ↗⚑ flag

   Smooth—none0/10

   No evidence of scoped or least-privilege API credential issuance, API key scoping, or permission management for agents; docs cover task execution, sessions, proxies, and privacy features but nothing about credential scoping. missing for 10: scoped API key/token generation, permission/role controls, credential revocation or least-privilege access management.

   ⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Hyperbrowser
   Hyperbrowser✓fullclaimed8/10

   Hyperbrowser documents official SDKs (hyperbrowser-docs-18) alongside a dedicated SDK introduction page, plus consistent references throughout docs to using SDKs (or Puppeteer/Playwright) to integrate programmatically (hyperbrowser-docs-19, hyperbrowser-docs-9, hyperbrowser-docs-29). Missing for 10: independent/hands-on developer confirmation of SDK quality or completeness across languages, and no direct OpenAPI spec found (probe-3) which would reinforce SDK-generation credibility.

   • [claimed-docs] “Official SDKs for integrating Hyperbrowser into your applications”
   • [claimed-docs] “Control Chrome browsers in the cloud using Puppeteer, Playwright, or our SDKs—no infrastructure management required.”
   • [claimed-docs] “Connect your existing automation scripts to cloud browsers”
   • [claimed-docs] “Set up the Hyperbrowser CLI (`hx`) and/or the SDKs to start working with sandboxes.”

   proof ↗⚑ flag

   Smooth~partialprobed6/10

   Smooth documents SDK-style integration (4-line task execution, custom tools, structured outputs, session workflows) and a CLI positioned as "a browser for AI agents" usable with tools like Claude Code, indicating official first-party SDK/CLI support for AI-native workflows. However, there is no OpenAPI spec, no evidence of multi-language SDKs, and no independent/hands-on confirmation of SDK reliability beyond docs and a GitHub repo. missing for 10: OpenAPI/API spec availability, multi-language SDK coverage, independent developer corroboration of SDK usage/quality.

   • [claimed-docs] “Plug-and-play: Run a task in just 4 lines of code, making it easy to integrate into your workflow.”
   • [claimed-docs] “Custom tools allow you to give Smooth any arbitrary function as a tool.”
   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [github] “The Smooth CLI is a browser for AI agents, enabling tools like Claude Code to navigate the web quickly, cheaply, and reliably.”
   • [probe] “official CLI documented at https://docs.smooth.sh/cli/overview”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.smooth.sh/openapi.json, https://docs.smooth.sh/swagger.json, https://docs.smooth.sh/api…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Hyperbrowser—none0/10

   No evidence pack item mentions webhooks or event subscription mechanisms; the product docs cover sessions, agents, scraping, extraction, MCP, and sandboxes but nothing about webhook notifications for events like task completion or crawl status. missing for 10: any documentation of webhook subscription/callback endpoints, event types, or webhook configuration.

   ⚑ flag

   Smooth—none0/10

   No evidence pack item mentions webhooks or event subscriptions; Smooth's documented features (live_url, structured outputs, custom tools, sessions) do not include a webhook/event notification mechanism.

   ⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Smooth
   Hyperbrowser~partialclaimed4/10

   Hyperbrowser supports triggering agent tasks via API and cloud sessions, which could underlie automations, but there is no evidence of scheduling, triggers, or persistent background jobs that run autonomously without a caller invoking them each time. missing for 10: scheduled/triggered automation, background job orchestration, evidence of persistent autonomous runs, independent confirmation of unattended operation.

   • [claimed-docs] “Hyperbrowser lets you run powerful, AI-driven browser agents in managed cloud sessions... you can start tasks with a single API call and wat…”
   • [claimed-docs] “Hyperbrowser lets you run powerful, AI-driven browser agents in managed cloud sessions. Whether you prefer open-source frameworks or cutting…”
   • [claimed-docs] “Control Chrome browsers in the cloud using Puppeteer, Playwright, or our SDKs—no infrastructure management required.”
   • [claimed-docs] “Connect your existing automation scripts to cloud browsers”

   proof ↗⚑ flag

   Smooth~partialclaimed5/10

   Smooth lets users kick off browser-agent tasks programmatically that run autonomously (navigating, extracting data, solving CAPTCHAs) and provides a live_url to monitor progress, which supports hands-off execution once started. However there's no evidence of scheduling, triggers, webhooks, or persistent 'set it and forget it' background jobs that run without an explicit API call — the model shown is synchronous task invocation, not autonomous background automation setup. Missing for 10: scheduling/cron or event-trigger support, evidence of long-running unattended jobs, and independent confirmation of background execution beyond a single task call.

   • [claimed-docs] “Plug-and-play: Run a task in just 4 lines of code, making it easy to integrate into your workflow.”
   • [claimed-docs] “When running a task, you will receive a `live_url`, which can be used to view the agent actions live.”
   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [claimed-docs] “Auto-CAPTCHA solvers: Bypass CAPTCHA challenges automatically, allowing for uninterrupted task execution.”

   proof ↗⚑ flag

2. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Smooth
   Hyperbrowser✓fullclaimed7/10

   Hyperbrowser ships built-in AI agents (HyperAgent, page.ai(), browser agents) that let users delegate natural-language tasks like 'search for flights and select the cheapest option' with a single API call, and the agent executes multi-step browser actions autonomously. This is a first-party, well-documented delegation capability, not just a passive tool. missing for 10: independent hands-on evidence validating task delegation reliability/quality beyond vendor docs, and no in-product chat UI shown (delegation is via API/SDK only).

   • [claimed-docs] “Hyperbrowser lets you run powerful, AI-driven browser agents in managed cloud sessions... you can start tasks with a single API call and wat…”
   • [claimed-docs] “await page.ai("search for flights from Miami to LAX, select the cheapest option");”
   • [claimed-docs] “Hyperbrowser lets you run powerful, AI-driven browser agents in managed cloud sessions. Whether you prefer open-source frameworks or cutting…”
   • [claimed-docs] “HyperAgent is our open-source tool that supercharges Playwright with AI.”
   • [claimed-docs] “Built in support for Claude, OpenAI, Gemini, Grok, and BrowserUse agents.”

   proof ↗⚑ flag

   Smooth✓fullcommunity8/10

   Smooth's core product is a task-delegation interface: users hand off a task description (e.g., navigate, extract, multi-step session workflow) to Smooth's built-in AI/browser agent, which executes autonomously and returns live_url and structured outputs (smooth-docs-1, smooth-docs-7, smooth-docs-8, smooth-docs-5). Community hands-on feedback corroborates it executing complex prompts well (smooth-comm-2, smooth-comm-1), though it is agent-facing (tool for other agents like Claude Code) as well as human-facing. Missing for 10: independent/reproducible benchmarks of task success (raised unanswered in smooth-comm-14) and clearer human-only assistant UX beyond API/CLI task calls.

   • [claimed-docs] “Plug-and-play: Run a task in just 4 lines of code, making it easy to integrate into your workflow.”
   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [claimed-docs] “Extract structured data from the current page by providing a schema.”
   • [claimed-docs] “Structured outputs allow you to write deterministic code based on the agent's output. To activate structured outputs, set the `response_mode…”
   • [claimed-docs] “When running a task, you will receive a `live_url`, which can be used to view the agent actions live.”
   • [community] “Super impressive demo. Seems a lot faster than alternatives. How did you achieve that?”
   • [community] “I just wrote a complex prompt and it did a good job. How do you do evals or testing of your project?”

   proof ↗⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round to Hyperbrowser
   Hyperbrowser✓fullclaimed8/10

   Hyperbrowser explicitly supports natural-language commands via page.ai() and HyperAgent ('Write natural language commands instead of complex selectors'), plus natural-language driven extraction (page.extract()/Extract API) and an MCP server exposing these to AI models. missing for 10: independent hands-on verification that NL commands reliably succeed across varied tasks, and broader third-party corroboration beyond vendor docs.

   • [claimed-docs] “await page.ai("search for flights from Miami to LAX, select the cheapest option");”
   • [claimed-docs] “HyperAgent is an open-source browser automation framework that extends Playwright with AI capabilities. Write natural language commands inst…”
   • [claimed-docs] “The `page.extract()` method pulls structured data from web pages. Define what you want using natural language and optionally enforce a schem…”
   • [claimed-docs] “The Hyperbrowser MCP server provides a standardized interface for AI models to access powerful web automation capabilities like scraping, st…”

   proof ↗⚑ flag

   Smooth~partialclaimed6/10

   Smooth's core interaction model is task-based: you give it a task description that an agent executes in a browser (session workflow, extract, navigate), and it is explicitly positioned as "a browser for AI agents" usable by tools like Claude Code, implying natural-language task instructions. However, no evidence shows an explicit example of a natural-language prompt/command syntax or confirms this is exposed to end-users beyond agent-to-agent orchestration. Missing for 10: explicit example of a natural-language task string/command, confirmation of human-facing NL command interface, independent corroboration of NL usability.

   • [claimed-docs] “Plug-and-play: Run a task in just 4 lines of code, making it easy to integrate into your workflow.”
   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [github] “The Smooth CLI is a browser for AI agents, enabling tools like Claude Code to navigate the web quickly, cheaply, and reliably.”
   • [claimed-docs] “Extract structured data from the current page by providing a schema.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Hyperbrowser
   Hyperbrowser~partialprobed3/10

   Hyperbrowser's docs include an api-reference section with code snippets (e.g., fetch-a-web-page.md) and quickstart examples like page.ai()/page.extract(), showing static example code, but there's no evidence of an interactive, runnable API console — probes for openapi/swagger specs all returned 404s, indicating no auto-generated interactive reference. missing for 10: evidence of an actual interactive/try-it API explorer, runnable code sandboxes, or OpenAPI-based interactive docs.

   • [claimed-docs] “Fetches a web page and returns the content in various formats (HTML, Markdown, JSON, screenshot, etc.)”
   • [claimed-docs] “await page.ai("search for flights from Miami to LAX, select the cheapest option");”
   • [claimed-docs] “The `page.extract()` method pulls structured data from web pages. Define what you want using natural language and optionally enforce a schem…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://hyperbrowser.ai/openapi.json, https://hyperbrowser.ai/swagger.json, https://hyperbrowser.ai/…”

   proof ↗⚑ flag

   Smooth—none0/10

   The evidence pack shows only static markdown docs (llms.txt, feature pages) and explicitly shows the openapi.json/swagger endpoints returning 404, indicating no interactive API reference or runnable-example playground exists. No mention of a Swagger UI, Postman collection, or in-browser code runner is present anywhere in docs or community discussion.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.smooth.sh/llms.txt # Smooth ## Docs - [Introduction](https://docs.smooth.sh/index.md): Welcome to…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.smooth.sh/openapi.json, https://docs.smooth.sh/swagger.json, https://docs.smooth.sh/api…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Hyperbrowser—none0/10

   A direct probe for an OpenAPI/Swagger spec at all standard locations (openapi.json, swagger.json, etc.) returned 404s, and no docs page claims a downloadable machine-readable API spec exists — only human-readable API reference pages are present.

   • [probe] “PROBE openapi: all candidate paths 404 (https://hyperbrowser.ai/openapi.json, https://hyperbrowser.ai/swagger.json, https://hyperbrowser.ai/…”
   • [probe] “PROBE docs-md: HTTP 404 at https://hyperbrowser.ai/docs.md”
   • [claimed-docs] “Fetches a web page and returns the content in various formats (HTML, Markdown, JSON, screenshot, etc.)”

   proof ↗⚑ flag

   Smooth—none0/10

   A direct probe for OpenAPI/Swagger spec files at all standard paths returned 404, and no docs page references a downloadable machine-readable API spec; only an llms.txt (docs index) is available.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.smooth.sh/openapi.json, https://docs.smooth.sh/swagger.json, https://docs.smooth.sh/api…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.smooth.sh/llms.txt # Smooth ## Docs - [Introduction](https://docs.smooth.sh/index.md): Welcome to…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Hyperbrowser
   Hyperbrowser~partialclaimed6/10

   Hyperbrowser ships dedicated 'Sandboxes' (isolated exec environments with sub-50ms startup) and isolated cloud browser 'Sessions' that are separate from any user production environment, which aligns with testing in isolation. However, the docs never explicitly frame this as protecting 'production data' or describe production/staging separation guarantees, and there is no independent/hands-on confirmation of isolation guarantees. Missing for 10: explicit production-vs-sandbox data isolation claims, independent verification of sandbox isolation, and security/compliance detail on data leakage prevention.

   • [claimed-docs] “Hyperbrowser Sandboxes are the fastest sandboxes with less than 50ms startup time.”
   • [claimed-docs] “const result = await sandbox.exec("node -e 'console.log(\"hello world\")'");”
   • [claimed-docs] “Set up the Hyperbrowser CLI (`hx`) and/or the SDKs to start working with sandboxes.”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically. Each session gives you a WebSocket endpo…”

   proof ↗⚑ flag

   Smooth—none0/10

   Smooth's docs describe browser-automation features (live sessions, proxies, persistent auth, structured outputs) but nowhere mention a sandbox/staging mode or any mechanism to isolate test runs from production data or accounts. Community feedback even flags unresolved concerns about data handling and security, but no concrete sandbox capability is described or corroborated.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Hyperbrowser—none0/10

   No evidence of API versioning scheme or documented deprecation policy; OpenAPI/spec probes returned 404 and no changelog or versioning docs appear in the pack. missing for 10: versioned API endpoints/headers, changelog, explicit deprecation policy documentation.

   • [probe] “PROBE openapi: all candidate paths 404 (https://hyperbrowser.ai/openapi.json, https://hyperbrowser.ai/swagger.json, https://hyperbrowser.ai/…”
   • [probe] “PROBE docs-md: HTTP 404 at https://hyperbrowser.ai/docs.md”

   proof ↗⚑ flag

   Smooth—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; OpenAPI spec probe returned 404s and docs show no changelog/versioning references. missing for 10: versioned API scheme, deprecation policy documentation, changelog/migration guides.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.smooth.sh/openapi.json, https://docs.smooth.sh/swagger.json, https://docs.smooth.sh/api…”

   proof ↗⚑ flag

Compat

1. developerConnect my existing Playwright, Puppeteer, or CDP automation code to the product's browsers instead of rewriting it

   weight 2 · round to Hyperbrowser
   Hyperbrowser✓fullclaimed8/10

   Docs explicitly state sessions expose a WebSocket endpoint compatible with Playwright, Puppeteer, or any CDP-compatible tool, and the intro reiterates 'Control Chrome browsers in the cloud using Puppeteer, Playwright, or our SDKs.' This directly supports connecting existing automation code without rewriting it, plus profiles for persisting cookies/session state across sessions. Missing for 10: independent/hands-on developer confirmation of drop-in compatibility with existing large codebases and any noted friction points.

   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically. Each session gives you a WebSocket endpo…”
   • [claimed-docs] “Control Chrome browsers in the cloud using Puppeteer, Playwright, or our SDKs—no infrastructure management required.”
   • [claimed-docs] “Connect your existing automation scripts to cloud browsers”
   • [claimed-docs] “Profiles let you save and reuse browser state, which includes cookies, local storage, session storage, and cache, across multiple sessions.”

   proof ↗⚑ flag

   Smooth—none0/10

   Smooth's docs describe its own SDK/task API (structured outputs, sessions, custom tools) but there is no mention of a CDP endpoint, Playwright/Puppeteer connect() compatibility, or any way to point existing automation code at Smooth's browsers; one commenter even notes 'agent-browser helped a lot over playwright but doesn't completely close the gap,' underscoring the absence of such interoperability. Missing for 10: any CDP/WebSocket endpoint, official Playwright/Puppeteer connect examples, or documented browser-endpoint compatibility.

   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [claimed-docs] “Set to `"self"` to create a P2P tunnel through your machine, routing traffic via your IP and enabling access to localhost.”
   • [community] “agent-browser helped a lot over playwright but doesn't completely close the gap.”

   proof ↗⚑ flag

Credentials

1. automation-engineerStore credentials in a vault and have the agent complete logins including TOTP/2FA challenges without exposing secrets to the model

   weight 2 · round drawn
   Hyperbrowser—none0/10

   Evidence shows session/profile persistence (cookies, storage) and stealth/captcha features, but nothing about a credentials vault, secret injection into login forms, or TOTP/2FA handling without exposing secrets to the model.

   • [claimed-docs] “Profiles let you save and reuse browser state, which includes cookies, local storage, session storage, and cache, across multiple sessions.”

   proof ↗⚑ flag

   Smooth—none0/10

   The docs describe persistent sessions (log in once, reuse authentication) but there is no mention of a credential vault, secret injection to avoid model exposure, or TOTP/2FA handling anywhere in the evidence pack. This axis clearly applies to a browser-automation agent product, but no capability matching the story is documented.

   • [claimed-docs] “Log in once, then reuse that authentication for future tasks.”

   proof ↗⚑ flag

Profiles

1. developerPersist logged-in browser state in reusable profiles so agents skip the login wall on every subsequent run

   weight 3 · round drawn
   Hyperbrowser✓fullclaimed7/10

   Docs explicitly describe Profiles that persist cookies, local storage, session storage, and cache across multiple sessions, directly enabling agents to skip login walls on repeat runs. Missing for 10: no independent/hands-on confirmation that profile reuse actually bypasses login in practice, and no detail on profile lifecycle/management limits.

   • [claimed-docs] “Profiles let you save and reuse browser state, which includes cookies, local storage, session storage, and cache, across multiple sessions.”

   proof ↗⚑ flag

   Smooth✓fullclaimed7/10

   Smooth's docs explicitly describe a persistent-sessions feature ('Log in once, then reuse that authentication for future tasks') and a session workflow that maintains a persistent browser session across multi-step tasks, directly matching the story. However, there is no independent/hands-on corroboration of this specific feature working reliably, and no detail on profile management (multiple reusable profiles, storage/export). Missing for 10: independent verification of session persistence in practice, documentation on managing multiple reusable profiles.

   • [claimed-docs] “Log in once, then reuse that authentication for future tasks.”
   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Hyperbrowser
   Hyperbrowser~partialcommunity6/10

   Hyperbrowser's Crawl API can traverse and extract from many pages in one request, and the Extract/Scrape APIs support structured data pulls, with community evidence of higher concurrency limits enabling parallel bulk sessions. However there's no explicit documented 'batch job over an arbitrary list of items/URLs' endpoint, and no first-party proof of large-scale bulk-run examples or rate/queue management for bulk workloads. missing for 10: explicit bulk/batch API for arbitrary item lists, documented large-scale throughput examples, independent benchmarks of bulk operation reliability.

   • [claimed-docs] “The Crawl API allows you to crawl websites and get data from multiple pages in a single request. Starting from a URL, it can navigate throug…”
   • [claimed-docs] “The Scrape API allows you to get the data you want from web pages with a single call. You can scrape page content and capture its data in va…”
   • [claimed-docs] “The Extract API allows you to extract structured data from web pages using AI. You can define a schema and prompt, and Hyperbrowser will ext…”
   • [community] “Just did a pricing check, and you give twice as much concurrency/browsing/data-transfer as Browserbase. Nice!”

   proof ↗⚑ flag

   Smooth—none0/10

   Smooth's docs describe single-task execution, session workflows, and structured extraction, but nothing about running/orchestrating bulk operations across many items (e.g., batch task queues, parallel task fan-out) is documented or mentioned by users.

   • [claimed-docs] “Plug-and-play: Run a task in just 4 lines of code, making it easy to integrate into your workflow.”
   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [claimed-docs] “Extract structured data from the current page by providing a schema.”

   proof ↗⚑ flag

2. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Hyperbrowser—none0/10

   No evidence anywhere in the pack of scheduling, cron-like recurring jobs, or persistent workflow automation triggers; Hyperbrowser's docs cover on-demand sessions, agents, scraping, extraction, sandboxes and MCP integration but nothing about recurring/scheduled execution. Missing for 10: any scheduler/cron feature, recurring job API, or workflow trigger documentation.

   ⚑ flag

   Smooth—none0/10

   No evidence of scheduling, cron-like triggers, or recurring workflow orchestration; Smooth is documented as a task-execution/browser-automation tool (session workflows, extraction, structured output) with no mention of recurring/scheduled jobs. Missing for 10: any scheduling API, cron/trigger mechanism, or recurring workflow docs.

   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [claimed-docs] “Plug-and-play: Run a task in just 4 lines of code, making it easy to integrate into your workflow.”

   proof ↗⚑ flag

Local

1. developerRun the agent against a local browser on my own machine for development, without any cloud account

   weight 2 · round drawn
   Hyperbrowser—none0/10

   All evidence describes Hyperbrowser as a managed cloud-browser service — sessions are explicitly cloud-hosted with WebSocket/CDP endpoints, and control is via cloud sessions requiring credits/subscription, not local execution without a cloud account. No evidence of a local-browser dev mode or offline/no-account option exists.

   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically. Each session gives you a WebSocket endpo…”
   • [claimed-docs] “Control Chrome browsers in the cloud using Puppeteer, Playwright, or our SDKs—no infrastructure management required.”
   • [claimed-docs] “Hyperbrowser tracks your usage via `credits` which can be acquired through a subscription or through a direct purchase.”

   proof ↗⚑ flag

   Smooth—none0/10

   Smooth is documented as a cloud-hosted browser agent service (task execution via live_url, proxies, zero-data-retention as an 'enterprise' add-on), with no docs describing a local-browser/offline mode; a P2P tunnel feature only lets the cloud agent reach your localhost, not run without an account. Community feedback explicitly asks for self-hosting ('Make it self-hostable, the conversation can change'), confirming no local/no-account mode exists.

   • [claimed-docs] “Zero Data Retention is an enterprise feature that provides enhanced data privacy by allowing you to delete all data associated with complete…”
   • [claimed-docs] “Set to `"self"` to create a P2P tunnel through your machine, routing traffic via your IP and enabling access to localhost.”
   • [community] “I'm unwilling to send my data to a 3rd party that is so new on the scene... Make it self-hostable, the conversation can change”
   • [community] “Way too expensive, I'll wait for a free/open source browser optimized to be used by agents.”

   proof ↗⚑ flag

Frameworks

1. developerPlug the browser layer into agent frameworks (Claude Agent SDK, Vercel AI SDK, LangChain, CrewAI) through documented adapters

   weight 2 · round drawn
   Hyperbrowser—none0/10

   Evidence shows generic SDKs, an MCP server, and built-in support for AI models (Claude, OpenAI, Gemini, Grok, BrowserUse) plus Playwright/Puppeteer/CDP session control, but there is no documentation of adapters specifically for Claude Agent SDK, Vercel AI SDK, LangChain, or CrewAI framework integration as the story requires.

   • [claimed-docs] “Official SDKs for integrating Hyperbrowser into your applications”
   • [claimed-docs] “Built in support for Claude, OpenAI, Gemini, Grok, and BrowserUse agents.”
   • [claimed-docs] “The Hyperbrowser MCP server provides a standardized interface for AI models to access powerful web automation capabilities like scraping, st…”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically. Each session gives you a WebSocket endpo…”

   proof ↗⚑ flag

   Smooth—none0/10

   Evidence shows Smooth positions itself as a browser tool usable by agents like Claude Code, but there is no documentation of adapters for Claude Agent SDK, Vercel AI SDK, LangChain, or CrewAI specifically. Missing for 10: any documented integration guide or adapter package for these named frameworks.

   • [github] “The Smooth CLI is a browser for AI agents, enabling tools like Claude Code to navigate the web quickly, cheaply, and reliably.”
   • [claimed-docs] “Custom tools allow you to give Smooth any arbitrary function as a tool.”

   proof ↗⚑ flag

Models

1. developerBring my own LLM provider — the framework is model-agnostic rather than locked to one vendor's models

   weight 2 · round to Hyperbrowser
   Hyperbrowser✓fullclaimed7/10

   Hyperbrowser's docs explicitly state 'Built in support for Claude, OpenAI, Gemini, Grok, and BrowserUse agents,' indicating the agent framework is not locked to a single LLM vendor and can work with multiple providers. Missing for 10: independent/community confirmation of multi-provider use, and detailed docs on how to configure/swap providers or bring custom API keys.

   • [claimed-docs] “Built in support for Claude, OpenAI, Gemini, Grok, and BrowserUse agents.”
   • [claimed-docs] “HyperAgent is our open-source tool that supercharges Playwright with AI.”
   • [claimed-docs] “HyperAgent is an open-source browser automation framework that extends Playwright with AI capabilities. Write natural language commands inst…”

   proof ↗⚑ flag

   Smooth—none0/10

   Smooth's docs describe it as using its own internal 'small and efficient AI models' for browser-agent tasks, and none of the documentation, CLI, or API references mention any mechanism for developers to configure or swap in their own LLM provider (e.g., OpenAI, Anthropic, custom model endpoints). This suggests the opposite of model-agnosticism — the models are an implementation detail of the service, not a pluggable choice.

   • [claimed-docs] “Smooth uses small and efficient AI models, making it 7x more affordable than browser-use.”
   • [github] “The Smooth CLI is a browser for AI agents, enabling tools like Claude Code to navigate the web quickly, cheaply, and reliably.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.smooth.sh/llms.txt # Smooth ## Docs - [Introduction](https://docs.smooth.sh/index.md): Welcome to…”

   proof ↗⚑ flag

Tasks

1. ai agentSubmit a browser task over a hosted HTTP API and receive the result by polling or webhook, without managing any browser myself

   weight 2 · round to Hyperbrowser
   Hyperbrowser~partialprobed6/10

   Hyperbrowser's docs confirm a hosted HTTP API where AI agents can start browser tasks with a single API call and run them in managed cloud sessions (agents, scrape, crawl, extract), removing the need to manage a browser directly. However, the evidence pack never explicitly documents a polling endpoint or webhook callback mechanism for retrieving task results—only 'watch them execute live' and SDK/CDP connection details are mentioned. Missing for 10: explicit API documentation of a status/poll endpoint, explicit webhook/callback support, and independent confirmation of async result retrieval flow.

   • [claimed-docs] “Hyperbrowser lets you run powerful, AI-driven browser agents in managed cloud sessions... you can start tasks with a single API call and wat…”
   • [claimed-docs] “Hyperbrowser lets you run powerful, AI-driven browser agents in managed cloud sessions. Whether you prefer open-source frameworks or cutting…”
   • [claimed-docs] “Control Chrome browsers in the cloud using Puppeteer, Playwright, or our SDKs—no infrastructure management required.”
   • [claimed-docs] “Connect your existing automation scripts to cloud browsers”
   • [probe] “PROBE llms.txt: HTTP 200 at https://hyperbrowser.ai/llms.txt # Hyperbrowser > Hyperbrowser provides fast cloud browsers for AI agents and a…”

   proof ↗⚑ flag

   Smooth~partialprobed5/10

   Docs confirm a hosted task-submission model (4-line integration, live_url for tracking, persistent sessions, structured outputs) consistent with an agent submitting tasks without managing a browser, but no evidence pack item explicitly documents a polling endpoint or webhook delivery mechanism, and probes found no public OpenAPI/REST spec. missing for 10: explicit polling endpoint docs, explicit webhook/callback docs, confirmed REST API schema (openapi probe 404s).

   • [claimed-docs] “Plug-and-play: Run a task in just 4 lines of code, making it easy to integrate into your workflow.”
   • [claimed-docs] “When running a task, you will receive a `live_url`, which can be used to view the agent actions live.”
   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.smooth.sh/openapi.json, https://docs.smooth.sh/swagger.json, https://docs.smooth.sh/api…”
   • [probe] “official CLI documented at https://docs.smooth.sh/cli/overview”

   proof ↗⚑ flag

2. developerHand the product a natural-language goal and it completes a multi-step web task end to end — navigating, filling forms, and clicking through flows

   weight 3 · round drawn
   Hyperbrowser✓fullclaimed7/10

   Docs show HyperAgent's page.ai() executing natural-language multi-step goals (e.g., searching flights and selecting cheapest option) and a separate managed Agents API that starts autonomous browser-agent tasks with a single call, supporting navigation, clicking, and form interactions end-to-end. Missing for 10: independent/hands-on verification of complex multi-step task completion and success-rate data beyond first-party docs.

   • [claimed-docs] “await page.ai("search for flights from Miami to LAX, select the cheapest option");”
   • [claimed-docs] “Hyperbrowser lets you run powerful, AI-driven browser agents in managed cloud sessions... you can start tasks with a single API call and wat…”
   • [claimed-docs] “Hyperbrowser lets you run powerful, AI-driven browser agents in managed cloud sessions. Whether you prefer open-source frameworks or cutting…”
   • [claimed-docs] “HyperAgent is our open-source tool that supercharges Playwright with AI.”
   • [claimed-docs] “HyperAgent is an open-source browser automation framework that extends Playwright with AI capabilities. Write natural language commands inst…”
   • [claimed-docs] “Built in support for Claude, OpenAI, Gemini, Grok, and BrowserUse agents.”

   proof ↗⚑ flag

   Smooth✓fullcommunity7/10

   Docs describe exactly this capability: multi-step 'Session Workflow' that navigates URLs, orchestrates sub-tasks, and extracts data, plus a live_url to watch the agent act, and a community commenter confirms 'I just wrote a complex prompt and it did a good job.' This matches the natural-language, end-to-end web task story well. Missing for 10: independently reproducible benchmarks/evals (a commenter explicitly asks for third-party reproducible comparisons and gets no clear answer), and broader hands-on validation beyond a single anecdote.

   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [claimed-docs] “Extract structured data from the current page by providing a schema.”
   • [claimed-docs] “When running a task, you will receive a `live_url`, which can be used to view the agent actions live.”
   • [community] “I just wrote a complex prompt and it did a good job. How do you do evals or testing of your project?”
   • [community] “are your evals / comparisons publicly/3rd party reproducible? If it's 'trust me, I did a fair comparison', that's not going to fly today.”

   proof ↗⚑ flag

Workflows

1. automation-engineerCompose repeatable multi-step workflows with loops, conditionals, and parameters instead of one-shot prompts

   weight 2 · round to Smooth
   Hyperbrowser—none0/10

   Hyperbrowser's docs describe single-call agent tasks, scraping/extraction, and Playwright/Puppeteer session control, but nothing describes a workflow builder or orchestration layer with loops, conditionals, or parameterized multi-step flows—automation is either one-shot AI prompts (page.ai, Extract API) or raw code you write yourself against Playwright, not a documented workflow composition feature.

   • [claimed-docs] “await page.ai("search for flights from Miami to LAX, select the cheapest option");”
   • [claimed-docs] “HyperAgent is our open-source tool that supercharges Playwright with AI.”
   • [claimed-docs] “HyperAgent is an open-source browser automation framework that extends Playwright with AI capabilities. Write natural language commands inst…”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically. Each session gives you a WebSocket endpo…”

   proof ↗⚑ flag

   Smooth~partialclaimed4/10

   Smooth documents a 'Session Workflow' method for multi-step execution—orchestrating smaller tasks, navigating URLs, and extracting data within a persistent browser session—plus structured outputs and custom tools that let developers build deterministic logic around agent calls. However, there is no explicit documentation of native loop/conditional constructs or parameterized workflow templates; any control flow would rely on the surrounding SDK code rather than a built-in workflow engine. Missing for 10: explicit loop/conditional primitives, parameterization/templating of workflows, and independent evidence of repeatable multi-step automations beyond simple session chaining.

   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [claimed-docs] “Structured outputs allow you to write deterministic code based on the agent's output. To activate structured outputs, set the `response_mode…”
   • [claimed-docs] “Custom tools allow you to give Smooth any arbitrary function as a tool.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Hyperbrowser
   Hyperbrowser✓fullprobed7/10

   Hyperbrowser is API-first: sessions, scraping, crawling, extraction, agents, sandboxes, profiles, recordings, stealth/CAPTCHA solving are all exposed via API/SDK/CLI, and the dashboard is largely a viewer over the same session/agent primitives rather than a separate feature surface. missing for 10: no public OpenAPI spec was found (404s on probes), and no explicit statement confirming every dashboard-only setting (e.g., billing/team management) is API-controllable.

   • [claimed-docs] “Hyperbrowser lets you run powerful, AI-driven browser agents in managed cloud sessions... you can start tasks with a single API call and wat…”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically. Each session gives you a WebSocket endpo…”
   • [claimed-docs] “The Scrape API allows you to get the data you want from web pages with a single call. You can scrape page content and capture its data in va…”
   • [claimed-docs] “The Crawl API allows you to crawl websites and get data from multiple pages in a single request. Starting from a URL, it can navigate throug…”
   • [claimed-docs] “The Extract API allows you to extract structured data from web pages using AI. You can define a schema and prompt, and Hyperbrowser will ext…”
   • [claimed-docs] “Hyperbrowser Sandboxes are the fastest sandboxes with less than 50ms startup time.”
   • [claimed-docs] “Set up the Hyperbrowser CLI (`hx`) and/or the SDKs to start working with sandboxes.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://hyperbrowser.ai/openapi.json, https://hyperbrowser.ai/swagger.json, https://hyperbrowser.ai/…”

   proof ↗⚑ flag

   Smooth—none0/10

   The evidence pack shows Smooth as an API/CLI/SDK-first browser-automation tool with docs for tasks, sessions, proxies, custom tools, and a live_url for viewing agent actions, but there is no mention of a separate web dashboard/UI or any comparison of UI-only vs API-only capabilities. Without evidence of what a UI offers (or that all UI features are mirrored in the API), the parity claim can't be substantiated. Missing for 10: any documented web UI/dashboard, and an explicit statement or demonstration that all UI actions are also achievable via API.

   • [claimed-docs] “Plug-and-play: Run a task in just 4 lines of code, making it easy to integrate into your workflow.”
   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [probe] “official CLI documented at https://docs.smooth.sh/cli/overview”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Hyperbrowser—none0/10

   No evidence of a data export/portability feature for user data (sessions, profiles, recordings, extracted data) in open formats, nor any account-deletion/data-takeout mechanism; profiles and recordings are stored server-side with no documented export path.

   ⚑ flag

   Smooth—none0/10

   Smooth's docs mention Zero Data Retention (deletion of task data) but there is no evidence of a bulk data export feature or open-format export for users to take their data and leave — the closest related item is deletion, not portability. missing for 10: any documented export mechanism, open format specification, or user data portability tooling.

   • [claimed-docs] “Zero Data Retention is an enterprise feature that provides enhanced data privacy by allowing you to delete all data associated with complete…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Hyperbrowser—none0/10

   Hyperbrowser's core cloud service (sessions, scraping, sandboxes, MCP server) is presented purely as a closed commercial SaaS API/product with no license or public repo for the platform itself. The only open-source item mentioned, HyperAgent, is a separate client-side automation framework, not the Hyperbrowser product's own source code, so it doesn't satisfy this story.

   • [claimed-docs] “HyperAgent is our open-source tool that supercharges Playwright with AI.”
   • [claimed-docs] “HyperAgent is an open-source browser automation framework that extends Playwright with AI capabilities. Write natural language commands inst…”
   • [claimed-docs] “Hyperbrowser tracks your usage via `credits` which can be acquired through a subscription or through a direct purchase.”

   proof ↗⚑ flag

   Smooth—none0/10

   Smooth ships a GitHub repo for its SDK/CLI, but there is no evidence of an open-source license for the core product, and community comments explicitly request self-hosting/open-source alternatives ('Make it self-hostable, the conversation can change', 'I'll wait for a free/open source browser'), implying the core service is closed.

   • [github] “The Smooth CLI is a browser for AI agents, enabling tools like Claude Code to navigate the web quickly, cheaply, and reliably.”
   • [community] “I'm unwilling to send my data to a 3rd party that is so new on the scene... Make it self-hostable, the conversation can change”
   • [community] “Way too expensive, I'll wait for a free/open source browser optimized to be used by agents.”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Hyperbrowser—none0/10

   Hyperbrowser is presented entirely as a managed cloud service (cloud browser sessions, sandboxes, MCP server) with no evidence of a self-hostable core product, open-source repo of the main platform, or on-prem deployment option; only HyperAgent (a client-side automation library) is open source, not the underlying cloud infrastructure. missing for 10: any docs or repo for self-hosting the core browser/session infrastructure, deployment/Docker instructions, or license terms permitting self-hosting.

   • [claimed-docs] “Control Chrome browsers in the cloud using Puppeteer, Playwright, or our SDKs—no infrastructure management required.”
   • [claimed-docs] “Hyperbrowser Sandboxes are the fastest sandboxes with less than 50ms startup time.”
   • [claimed-docs] “HyperAgent is our open-source tool that supercharges Playwright with AI.”

   proof ↗⚑ flag

   Smooth—none0/10

   Smooth is offered only as a hosted cloud API/SaaS with no documented self-host option, and community feedback explicitly requests self-hosting as a missing capability ('Make it self-hostable, the conversation can change').

   • [community] “I'm unwilling to send my data to a 3rd party that is so new on the scene... Make it self-hostable, the conversation can change”
   • [community] “My first question was whether I could use this for sensitive tasks, given that it's not running on our machines. And after poking around for…”

   proof ↗⚑ flag

Pricing

1. developerSee transparent per-task or per-browser-hour pricing and documented rate/concurrency limits before committing

   weight 2 · round to Hyperbrowser
   Hyperbrowser!disputedcontradicted4/10

   Hyperbrowser docs mention a credit-based pricing model (hyperbrowser-docs-27) but provide no explicit per-task/per-browser-hour cost table or concurrency/rate-limit documentation in the evidence pack. Community feedback directly contradicts the transparency claim: users report confusion over credit costs versus competitors (hyperbrowser-comm-2) and one user states it appears 'not possible to follow robots.txt or limit RPS as a user of this service' (hyperbrowser-comm-9), indicating undocumented or absent rate-limiting behavior. missing for 10: a concrete pricing/rate-limit page with per-hour or per-task cost breakdown, explicit concurrency caps, and independent confirmation that documented limits match real usage.

   • [claimed-docs] “Hyperbrowser tracks your usage via `credits` which can be acquired through a subscription or through a direct purchase.”
   • [community] “Your pricing is too confusing... You charge $100 for 60K credits... In comparison it costs $249 for 3 million credits in ScrapingBee which e…”
   • [community] “So, amusingly, they seem to have added an 'ethical scraping' page to their docs in between me looking at this a few hours ago and now... as …”
   • [community] “This looks cool. I looked at the pricing. Is search included in the price - (you just pay credits/browser time?)”

   proof ↗⚑ flag

   Smooth—none0/10

   No evidence of documented per-task/per-browser-hour pricing tiers or rate/concurrency limits; only a vague claim of being '7x more affordable' with no actual pricing page or limits documented, and community comments call it 'too expensive' without citing specifics.

   • [claimed-docs] “Smooth uses small and efficient AI models, making it 7x more affordable than browser-use.”
   • [community] “Way too expensive, I'll wait for a free/open source browser optimized to be used by agents.”
   • [community] “I'm paying a fixed amount on Claude and other agents, so 'more tokens' is 'free' for me. There's a lot of niche tools out there but I think …”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Hyperbrowser—none0/10

   No evidence in the pack mentions data residency, region selection, or geographic storage location for Hyperbrowser sessions/data; proxy/geo-routing docs relate to traffic egress, not data storage location. Missing for 10: any mention of data residency options, region selection controls, or storage location guarantees.

   ⚑ flag

   Smooth—none0/10

   No evidence of data residency/region selection options; only Zero Data Retention (deletion) is mentioned, which is a different capability. Missing for 10: any mention of region choice, data center locations, or residency controls.

   • [claimed-docs] “Zero Data Retention is an enterprise feature that provides enhanced data privacy by allowing you to delete all data associated with complete…”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to Smooth
   Hyperbrowser—none0/10

   Hyperbrowser is a browser automation/scraping infrastructure product; no evidence anywhere in the pack addresses a data-training opt-out or any AI-model training data policy. Even the community threads about ethical scraping/robots.txt concern outbound scraping behavior, not whether Hyperbrowser uses customer data to train models. Absence of evidence for this applicable privacy-posture axis means none.

   ⚑ flag

   Smooth~partialcommunity4/10

   Smooth documents a 'Zero Data Retention' enterprise feature that lets customers delete all data tied to completed tasks, which is adjacent to preventing data reuse, but there is no explicit statement that data is excluded from model training, and this feature is gated to enterprise tier. Community feedback also notes an absence of any detailed security/privacy documentation despite marketing claims of 'enterprise-grade security', raising trust concerns without disputing the ZDR feature itself. missing for 10: explicit AI-training opt-out policy, default (non-enterprise) privacy guarantees, independent verification of data handling.

   • [claimed-docs] “Zero Data Retention is an enterprise feature that provides enhanced data privacy by allowing you to delete all data associated with complete…”
   • [community] “My first question was whether I could use this for sensitive tasks, given that it's not running on our machines. And after poking around for…”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Smooth
   Hyperbrowser—none0/10

   No evidence pack content addresses data retention policies, deletion controls, or privacy settings for stored session data, recordings, or profiles; community evidence even suggests scraping is done without regard to opt-out mechanisms like robots.txt, but this doesn't speak to retention/deletion controls directly. This is a fair axis for a cloud browser automation service handling user data (recordings, profiles, scraped data), so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Profiles let you save and reuse browser state, which includes cookies, local storage, session storage, and cache, across multiple sessions.”
   • [claimed-docs] “Hyperbrowser supports both web recordings (using rrweb) that capture DOM changes and interactions in a lightweight format, and traditional M…”
   • [community] “They do not respect robots.txt, and publish a doc page dedicated to circumventing scraping countermeasures. I pointed their scraper at a url…”
   • [community] “So, amusingly, they seem to have added an 'ethical scraping' page to their docs in between me looking at this a few hours ago and now... as …”

   proof ↗⚑ flag

   Smooth~partialcommunity5/10

   Docs confirm a 'Zero Data Retention' feature letting customers delete all data tied to completed tasks, directly addressing retention/deletion control, but it's explicitly gated as an 'enterprise feature' rather than a universal capability, and no detail is given on default retention periods, deletion APIs/CLI commands, or granular controls for non-enterprise users. Community feedback (e.g., concerns about sending data to a third party, no security details found) shows some skepticism but doesn't concretely contradict the ZDR claim itself. missing for 10: default/non-enterprise retention policy, self-serve deletion mechanism (API/CLI), independent verification of ZDR working in practice.

   • [claimed-docs] “Zero Data Retention is an enterprise feature that provides enhanced data privacy by allowing you to delete all data associated with complete…”
   • [community] “My first question was whether I could use this for sensitive tasks, given that it's not running on our machines. And after poking around for…”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Hyperbrowser—none0/10

   No evidence of any telemetry opt-out setting or privacy control; the only related mention is credit-based usage tracking for billing, which is a business metric, not telemetry, and no docs describe disabling analytics/tracking.

   • [claimed-docs] “Hyperbrowser tracks your usage via `credits` which can be acquired through a subscription or through a direct purchase.”

   proof ↗⚑ flag

   Smooth—none0/10

   No evidence describes a telemetry/usage-tracking opt-out control; the only related privacy feature is 'Zero Data Retention' for enterprise customers, which addresses data deletion after tasks rather than disabling telemetry/tracking. Community comments raise general privacy/security concerns but do not confirm or deny an opt-out mechanism.

   • [claimed-docs] “Zero Data Retention is an enterprise feature that provides enhanced data privacy by allowing you to delete all data associated with complete…”
   • [community] “My first question was whether I could use this for sensitive tasks, given that it's not running on our machines. And after poking around for…”

   proof ↗⚑ flag

Live

1. automation-engineerWatch a session live and take human control mid-run when the agent gets stuck

   weight 2 · round drawn
   Hyperbrowser~partialclaimed4/10

   Hyperbrowser docs confirm you can 'watch tasks execute live' and supports session recordings (rrweb/video) for later replay/debugging, but there is no evidence of a mechanism for a human to take control mid-run and intervene when the agent gets stuck — no live handoff, pause/resume, or manual takeover feature is documented. Missing for 10: documented live human takeover/intervention controls during an active agent run, and independent confirmation this works in practice.

   • [claimed-docs] “Hyperbrowser lets you run powerful, AI-driven browser agents in managed cloud sessions... you can start tasks with a single API call and wat…”
   • [claimed-docs] “Hyperbrowser lets you run powerful, AI-driven browser agents in managed cloud sessions. Whether you prefer open-source frameworks or cutting…”
   • [claimed-docs] “Hyperbrowser supports both web recordings (using rrweb) that capture DOM changes and interactions in a lightweight format, and traditional M…”
   • [claimed-docs] “Record and replay your browser sessions to debug failures, analyze behavior, and share reproducible bug reports.”

   proof ↗⚑ flag

   Smooth~partialclaimed4/10

   Docs confirm a live_url to watch agent actions in real time (smooth-docs-2), satisfying the 'watch a session live' half of the story, but there is no evidence of any mechanism for a human to intervene or take control mid-run when the agent gets stuck. missing for 10: documented human-takeover/control API or UI, evidence of pausing/resuming agent execution, hands-on confirmation of mid-run intervention.

   • [claimed-docs] “When running a task, you will receive a `live_url`, which can be used to view the agent actions live.”
   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”

   proof ↗⚑ flag

Replay

1. automation-engineerDebug a failed agent run from recorded replays — video, screenshots, step-by-step action timelines

   weight 2 · round to Hyperbrowser
   Hyperbrowser~partialclaimed5/10

   Hyperbrowser documents session recordings (rrweb DOM-level recordings and MP4 video) which support visual replay of a browser session, and MCP/scrape tools mention screenshot capture, but there is no evidence of a dedicated step-by-step action/timeline log for agent runs or a debugging UI tied to failed runs specifically. missing for 10: explicit step-by-step action timeline artifact, agent-run failure/debug UI, independent hands-on confirmation of replay-based debugging workflow.

   • [claimed-docs] “Hyperbrowser supports both web recordings (using rrweb) that capture DOM changes and interactions in a lightweight format, and traditional M…”
   • [claimed-docs] “Hyperbrowser lets you run powerful, AI-driven browser agents in managed cloud sessions... you can start tasks with a single API call and wat…”
   • [github] “`scrape_webpage` - Extract formatted (markdown, screenshot etc) content from any webpage”

   proof ↗⚑ flag

   Smooth~partialclaimed3/10

   Docs mention a `live_url` for viewing agent actions live during a run, but there is no evidence of persisted video recordings, screenshots, or a step-by-step action timeline that can be replayed after a run has finished and failed. Missing for 10: recorded video/screenshot artifacts, post-hoc replay viewer, structured action timeline, and any independent confirmation of replay-based debugging.

   • [claimed-docs] “When running a task, you will receive a `live_url`, which can be used to view the agent actions live.”

   proof ↗⚑ flag

Fleets

1. automation-engineerRun a fleet of concurrent browser sessions with documented concurrency limits and programmatic session management

   weight 2 · round to Hyperbrowser
   Hyperbrowser~partialcommunity6/10

   Hyperbrowser clearly supports programmatic, isolated cloud browser sessions controllable via Playwright/Puppeteer/SDKs (hyperbrowser-docs-10, hyperbrowser-docs-19), and community feedback indicates it offers more concurrency than competitors like Browserbase (hyperbrowser-comm-1), implying tiered concurrency limits exist. However, the evidence pack contains no first-party documentation page explicitly listing numeric concurrency limits per plan or fleet-scale orchestration guidance. Missing for 10: explicit documented concurrency-limit numbers/tiers, guidance on running many sessions in parallel, and independent verification of limits in practice.

   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically. Each session gives you a WebSocket endpo…”
   • [claimed-docs] “Control Chrome browsers in the cloud using Puppeteer, Playwright, or our SDKs—no infrastructure management required.”
   • [community] “Just did a pricing check, and you give twice as much concurrency/browsing/data-transfer as Browserbase. Nice!”
   • [claimed-docs] “Hyperbrowser tracks your usage via `credits` which can be acquired through a subscription or through a direct purchase.”

   proof ↗⚑ flag

   Smooth—none0/10

   The evidence pack covers single-session features (persistent sessions, live URL, proxies, structured output) but contains no documentation of concurrency limits, fleet/pool management, or APIs for running many sessions in parallel. Missing for 10: documented concurrency limits, fleet/pool orchestration APIs, rate-limit or scaling guidance, evidence of parallel session usage.

   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [claimed-docs] “Log in once, then reuse that authentication for future tasks.”
   • [claimed-docs] “When running a task, you will receive a `live_url`, which can be used to view the agent actions live.”

   proof ↗⚑ flag

Lifecycle

1. developerGet webhook notifications when tasks and sessions finish instead of polling for status

   weight 1 · round drawn
   Hyperbrowser—none0/10

   No evidence anywhere in the pack mentions webhooks, callbacks, or push notifications for task/session completion; all documented status mechanisms appear to be live/polling-based (watch execution live, sessions, recordings). Absence of evidence for this applicable capability yields none.

   ⚑ flag

   Smooth—none0/10

   No evidence pack item mentions webhooks, callback URLs, or event-driven notifications for task/session completion; the docs describe live_url viewing, structured outputs, and session workflows but nothing about push notifications versus polling.

   ⚑ flag

Captcha

1. automation-engineerRely on a documented captcha stance — automatic solving, human fallback, or explicit non-support — instead of silent task failures

   weight 2 · round to Smooth
   Hyperbrowser!disputedcontradicted5/10

   Hyperbrowser explicitly documents an automatic CAPTCHA-solving stance (enabled at session creation) alongside stealth mode for anti-bot detection, giving automation engineers a documented policy rather than silent failures. However, a hands-on community report describes being 'instantly blocked by cloudflare' in a real automation use case, contradicting the claimed automatic bypass/solving reliability in practice. missing for 10: independent verification that CAPTCHA solving works reliably across real sites, clarification of behavior when solving fails (human fallback vs silent failure), and resolution of the Cloudflare-blocking report.

   • [claimed-docs] “Hyperbrowser can automatically detect and solve CAPTCHAs when you enable it during session creation.”
   • [claimed-docs] “Stealth mode applies anti-detection techniques to help your automated browser sessions bypass bot detection.”
   • [community] “had usecase of keeping visa appointments slots and instantly blocked by cloudflare :sad:”

   proof ↗⚑ flag

   Smooth✓fullcommunity6/10

   Smooth explicitly documents an automatic captcha-solving stance ('Auto-CAPTCHA solvers: Bypass CAPTCHA challenges automatically, allowing for uninterrupted task execution'), giving automation engineers a clear documented behavior rather than silent failure. Community reaction (smooth-comm-3) criticizes the ethics/marketing of this feature but does not present a hands-on failure showing the solver doesn't work, so this remains a documented claim rather than a disputed one. Missing for 10: independent/hands-on verification that auto-solving actually succeeds in practice, and no documentation of fallback behavior (e.g., what happens if a captcha can't be auto-solved).

   • [claimed-docs] “Auto-CAPTCHA solvers: Bypass CAPTCHA challenges automatically, allowing for uninterrupted task execution.”
   • [community] “So you're shamelessly selling spambots? The marketing here is wild... "proxy rotation"... "auto-CAPTCHA solvers"”

   proof ↗⚑ flag

Posture

1. automation-engineerPoint to the vendor's published acceptable-use and anti-abuse posture governing what its stealth and automation features may be used for

   weight 1 · round to Hyperbrowser
   Hyperbrowser!disputedcontradicted4/10

   Hyperbrowser doesn't publish a clear acceptable-use/anti-abuse policy in its docs, and when community members pressed on robots.txt/rate-limit compliance, the company added an 'ethical scraping' page reactively — but a hands-on tester found it still doesn't actually support respecting robots.txt or limiting request rate, and Hyperbrowser's own docs promote circumventing bot-detection countermeasures (stealth/CAPTCHA-solving) rather than governing their limits. Missing for 10: an actual published acceptable-use policy document, terms defining permitted use of stealth/CAPTCHA features, and evidence of enforcement matching any stated ethical posture.

   • [community] “Is there support for robots.txt so service operators can opt out of your mass scraping?”
   • [community] “They do not respect robots.txt, and publish a doc page dedicated to circumventing scraping countermeasures. I pointed their scraper at a url…”
   • [community] “So, amusingly, they seem to have added an 'ethical scraping' page to their docs in between me looking at this a few hours ago and now... as …”
   • [claimed-docs] “Stealth mode applies anti-detection techniques to help your automated browser sessions bypass bot detection.”
   • [claimed-docs] “Hyperbrowser can automatically detect and solve CAPTCHAs when you enable it during session creation.”
   • [claimed-docs] “Ultra Stealth Mode - The most advanced stealth mode for extra evasion from bot detection.”

   proof ↗⚑ flag

   Smooth—none0/10

   No evidence anywhere in the pack of a published acceptable-use policy, anti-abuse terms, or guidance on permissible use of the stealth/CAPTCHA-bypass and automation features; docs only describe how to use auto-CAPTCHA and proxy features, not what usage is disallowed. Community commentary even calls out the lack of any such framing (e.g., accusing the marketing of enabling spambots), reinforcing the absence rather than disputing a claim.

   • [claimed-docs] “Auto-CAPTCHA solvers: Bypass CAPTCHA challenges automatically, allowing for uninterrupted task execution.”
   • [community] “So you're shamelessly selling spambots? The marketing here is wild... "proxy rotation"... "auto-CAPTCHA solvers"”

   proof ↗⚑ flag

Stealth

1. automation-engineerEnable stealth fingerprinting and residential or geo-targeted proxies so legitimate automations aren't blocked as bots

   weight 2 · round to Smooth
   Hyperbrowser!disputedcontradicted5/10

   Hyperbrowser explicitly documents Stealth Mode, an 'Ultra Stealth Mode', CAPTCHA solving, and proxy routing for geo-targeting/IP rotation, directly matching the story's anti-bot and geo-targeted proxy needs (hyperbrowser-docs-4, -12, -20, -5, -13). However, a first-hand community report describes being 'instantly blocked by cloudflare' despite using the service for an automation use case, and another user documents the scraper still exposing bot-like UA/IP patterns detectable by target sites, concretely contradicting the anti-detection claims in practice (hyperbrowser-comm-3, hyperbrowser-comm-8). missing for 10: independent benchmark showing stealth/proxy reliably evades modern bot defenses, explicit confirmation of 'residential' proxy type versus generic rotating proxies, and resolution of the Cloudflare-block report.

   • [claimed-docs] “Stealth mode applies anti-detection techniques to help your automated browser sessions bypass bot detection.”
   • [claimed-docs] “Stealth mode applies anti-detection techniques to help your automated browser sessions bypass bot detection. Use it when interacting with si…”
   • [claimed-docs] “Ultra Stealth Mode - The most advanced stealth mode for extra evasion from bot detection.”
   • [claimed-docs] “Hyperbrowser can automatically detect and solve CAPTCHAs when you enable it during session creation.”
   • [claimed-docs] “Route browser sessions through proxy servers to access geo-restricted content, rotate IPs, and distribute requests across different location…”
   • [community] “had usecase of keeping visa appointments slots and instantly blocked by cloudflare :sad:”
   • [community] “They do not respect robots.txt, and publish a doc page dedicated to circumventing scraping countermeasures. I pointed their scraper at a url…”

   proof ↗⚑ flag

   Smooth~partialcommunity5/10

   Docs confirm auto-CAPTCHA solving and configurable proxy server parameters plus persistent authenticated sessions, which support anti-bot automation goals, but there is no explicit mention of residential/geo-targeted proxy pools or stealth browser fingerprinting techniques. Missing for 10: explicit residential/geo-targeted proxy options, stealth fingerprinting details, and independent verification that bot-detection evasion actually works in practice.

   • [claimed-docs] “To use a proxy with Smooth, you need to specify the proxy server details in your task parameters.”
   • [claimed-docs] “Auto-CAPTCHA solvers: Bypass CAPTCHA challenges automatically, allowing for uninterrupted task execution.”
   • [claimed-docs] “Log in once, then reuse that authentication for future tasks.”
   • [community] “So you're shamelessly selling spambots? The marketing here is wild... "proxy rotation"... "auto-CAPTCHA solvers"”

   proof ↗⚑ flag

Extraction

1. developerExtract typed, schema-validated data (Zod/Pydantic-style) from pages the agent visits, not just raw text

   weight 3 · round drawn
   Hyperbrowser✓fullclaimed8/10

   Hyperbrowser documents both an Extract API and page.extract() method that support schema-based extraction with Zod, explicitly for type-safe structured results from visited pages, and this is available both in standalone scrape/crawl calls and agent workflows (HyperAgent). Missing for 10: no independent/hands-on verification of schema-validation correctness or Pydantic-specific support (docs only mention Zod), and no example showing enforcement failure/error handling.

   • [claimed-docs] “The `page.extract()` method pulls structured data from web pages. Define what you want using natural language and optionally enforce a schem…”
   • [claimed-docs] “The Extract API allows you to extract structured data from web pages using AI. You can define a schema and prompt, and Hyperbrowser will ext…”
   • [claimed-docs] “The `page.extract()` method pulls structured data from web pages. Define what you want using natural language and optionally”
   • [claimed-docs] “HyperAgent is our open-source tool that supercharges Playwright with AI.”

   proof ↗⚑ flag

   Smooth✓fullclaimed8/10

   Docs explicitly describe structured outputs via `response_model` for deterministic typed data and a dedicated `session-extract` method to extract structured data from a page by providing a schema, directly matching the story. Missing for 10: explicit Zod/Pydantic code examples and independent/hands-on confirmation that extraction validation works as documented.

   • [claimed-docs] “Structured outputs allow you to write deterministic code based on the agent's output. To activate structured outputs, set the `response_mode…”
   • [claimed-docs] “Extract structured data from the current page by providing a schema.”
   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”

   proof ↗⚑ flag

Files

1. developerMy agent can download files from and upload files to the sites it operates, with the artifacts retrievable afterwards

   weight 1 · round drawn
   Hyperbrowser—none0/10

   The evidence pack details scraping, extraction, session recording, and sandbox exec, but nowhere mentions file download/upload handling on target sites or artifact retrieval mechanisms for such files. Since Hyperbrowser exposes raw Playwright/Puppeteer CDP endpoints, this axis is plausible for the product category, but no documentation or community evidence confirms the capability.

   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically. Each session gives you a WebSocket endpo…”
   • [claimed-docs] “Control Chrome browsers in the cloud using Puppeteer, Playwright, or our SDKs—no infrastructure management required.”
   • [claimed-docs] “Hyperbrowser supports both web recordings (using rrweb) that capture DOM changes and interactions in a lightweight format, and traditional M…”

   proof ↗⚑ flag

   Smooth—none0/10

   The evidence pack describes Smooth's session workflows, structured extraction, live-view, proxies, and persistent auth, but nothing addresses file download/upload during a browser session or persisting artifacts for later retrieval. Since browser automation tools plausibly support file transfer (e.g., downloading a report from a site or uploading a document to a form), this axis applies but is unaddressed.

   • [claimed-docs] “Session Workflow — Multi-step execution where you can orchestrate smaller tasks, navigate to URLs, and extract data within a persistent brow…”
   • [claimed-docs] “Extract structured data from the current page by providing a schema.”
   • [claimed-docs] “When running a task, you will receive a `live_url`, which can be used to view the agent actions live.”

   proof ↗⚑ flag