Skyvern vs Hyperbrowser

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
   Skyvern—none0/10

   No evidence of caching resolved actions or generated code for deterministic, cheaper replay; Skyvern's model is per-run AI-driven navigation via LLM+vision, and community feedback even complains about cost/latency of repeated LLM calls with no mention of a caching mechanism to mitigate this.

   • [community] “I tried it out and it's pretty pricey. My OpenAI API bill is $3.20 after using this on a few different pages to test it out... this is alway…”
   • [community] “This is an impressive tool. I especially like the observability around the workflow and the steps it takes to achieve the outcome. We are po…”
   • [claimed-docs] “It navigates websites it has never seen before, filling forms, extracting data, and completing multi-step tasks via a simple API.”

   proof ↗⚑ flag

   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

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
   Skyvern!disputedcontradicted5/10

   Skyvern's docs describe exactly this: natural-language act/click/type primitives with vision+DOM understanding that operate on sites 'never seen before' and fall back to selectors only if needed (skyvern-docs-19, skyvern-gh-1, skyvern-docs-17), positioned explicitly as a replacement for brittle Selenium scripts (skyvern-docs-13). However, a hands-on community test found it worked on the happy path but concretely failed to interact with a layout element (a popup) and struggled to hit a tab on a real site (skyvern-comm-2), contradicting the claim that it robustly survives arbitrary layout changes. Missing for 10: independent benchmark data on selector/layout-change robustness, broader corroboration beyond one hands-on report, and resolution of the observed failure mode.

   • [claimed-docs] “Drop-in AI commands on top of Playwright. Use natural language to act, extract, and validate — or fall back to selectors.”
   • [github] “Skyvern can operate on websites it's never seen before, as it's able to map visual elements to actions necessary to complete a workflow, wit…”
   • [claimed-docs] “It navigates websites it has never seen before, filling forms, extracting data, and completing multi-step tasks via a simple API.”
   • [claimed-docs] “You're replacing brittle Selenium scripts, integrating browser automation via API, or building workflows into your product.”
   • [community] “I played with the Geico example, and it seems to do a good job on the happy path. But I tried costcotravel.com... it struggled to hit the 'r…”

   proof ↗⚑ flag

   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

Observe

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

   weight 1 · round to Skyvern
   Skyvern~partialcommunity3/10

   Skyvern's docs mention human-in-the-loop pausing for approval between steps and a VNC stream to watch/take control, which offers some ability to intervene before the agent proceeds, but there is no documented explicit 'plan/preview candidate actions' step (e.g., a dry-run or action list shown before execution). A community comment even notes the absence of assertion/verification-style controls compared to Playwright, suggesting no built-in preview mechanism for validating steps before they run. Missing for 10: an explicit plan/preview UI or API that lists candidate actions before execution, and independent confirmation that the pause-for-approval flow shows planned actions rather than just pausing mid-run.

   • [claimed-docs] “Human-in-the-loop flows: pause for approval between steps without losing browser state. The VNC stream lets you watch or take control at any…”
   • [community] “I can't see that option in Skyvern which would have me worrying that process changes would be overlooked and we would unknowingly start ente…”

   proof ↗⚑ flag

   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

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 Skyvern
   Skyvern✓fullclaimed7/10

   Skyvern's core action loop is vision-based: it maps visual elements to actions on pages it has never seen, without custom DOM-specific code (skyvern-gh-1), and separately uses its vision model to detect and solve CAPTCHAs, which are canvas-like elements the DOM can't parse (skyvern-docs-9, skyvern-docs-27). Docs also mention falling back to selectors when useful (skyvern-docs-19), implying vision-first with DOM as a secondary path rather than a purely DOM-based tool needing a special switch. missing for 10: explicit documentation of a discrete 'vision/computer-use mode' toggle, dedicated canvas/non-DOM UI examples (e.g., canvas-drawn widgets, non-HTML apps), and independent benchmarking confirming success on such UIs.

   • [github] “Skyvern can operate on websites it's never seen before, as it's able to map visual elements to actions necessary to complete a workflow, wit…”
   • [claimed-docs] “Skyvern detects CAPTCHAs using its vision model and solves them automatically. This works for reCAPTCHA v2/v3, hCaptcha, Cloudflare Turnstil…”
   • [claimed-docs] “Skyvern detects CAPTCHAs using its vision model and solves them automatically.”
   • [claimed-docs] “Drop-in AI commands on top of Playwright. Use natural language to act, extract, and validate — or fall back to selectors.”

   proof ↗⚑ flag

   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

Agent access

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

   weight 2 · round drawn
   Skyvern✓fullprobed8/10

   A probe confirms llms.txt is live and returns a structured summary of Skyvern for agent consumption, and skyvern.com/llms provides an agent-oriented docs page listing features in a scannable format. This directly satisfies pointing an agent at llms.txt or agent-oriented docs. Missing for 10: a docs.md/markdown-mirrored docs endpoint (404) and an accessible OpenAPI spec, which would round out machine-readable documentation.

   • [probe] “PROBE llms.txt: HTTP 200 at https://skyvern.com/llms.txt # Skyvern > Skyvern is an open-source, AI-powered browser automation platform. It …”
   • [claimed-docs] “Visual workflow builder for non-developers — drag-and-drop, no code required”
   • [claimed-docs] “Browser recorder that converts manual actions into reusable automations”
   • [claimed-docs] “SOP upload — describe a process in plain English and Skyvern builds the workflow”
   • [claimed-docs] “Copilot chat for building and debugging workflows interactively”
   • [probe] “PROBE docs-md: HTTP 404 at https://skyvern.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://skyvern.com/openapi.json, https://skyvern.com/swagger.json, https://skyvern.com/api/openapi.…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Hyperbrowser
   Skyvern✓fullclaimed7/10

   Skyvern ships a code-first SDK/REST API (Python/TypeScript) that connects to a cloud or self-hosted Chromium instance, explicitly positioned as replacing brittle Selenium scripts and integrating browser automation via API into other products, and can run entirely on your own infrastructure with your own LLM keys, supporting headless/scriptable use suitable for CI. missing for 10: explicit CI/CD pipeline documentation or example (e.g. GitHub Actions integration), and independent confirmation of headless execution in automated environments

   • [claimed-docs] “Integrate browser automation into your product with Python, TypeScript, or REST.”
   • [claimed-docs] “Run Skyvern on your own infrastructure with your own LLM keys.”
   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”
   • [claimed-docs] “Self-hosted Skyvern runs entirely on your infrastructure: your servers, your browsers, your LLM API keys.”
   • [claimed-docs] “You're replacing brittle Selenium scripts, integrating browser automation via API, or building workflows into your product.”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Skyvern—none0/10

   Evidence only shows Skyvern exposing an MCP *server* so external AI assistants (Claude, Cursor, etc.) can control Skyvern's browser — the reverse of the story, which asks whether Skyvern can consume external MCP servers' tools as a client. No documentation or community evidence shows Skyvern importing or connecting to third-party MCP servers to extend its own toolset.

   • [claimed-docs] “The Skyvern MCP server lets AI assistants like Claude Desktop, Claude Code, Codex, Cursor, and Windsurf control a browser.”
   • [probe] “official MCP server documented at https://skyvern.com/docs/developers/getting-started/mcp”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Skyvern✓fullprobed8/10

   Skyvern documents an official MCP server (skyvern-docs-7, skyvern-probe-4) that lets AI assistants like Claude Desktop, Claude Code, Codex, Cursor, and Windsurf control a browser via Skyvern, directly matching the story. Missing for 10: independent/hands-on community verification of the MCP server specifically (community evidence covers other features, not MCP usage) and a clear setup/config example beyond the single doc page.

   • [claimed-docs] “The Skyvern MCP server lets AI assistants like Claude Desktop, Claude Code, Codex, Cursor, and Windsurf control a browser.”
   • [probe] “official MCP server documented at https://skyvern.com/docs/developers/getting-started/mcp”

   proof ↗⚑ flag

   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

5. ai-native userUse an official CLI

   weight 2 · round to Hyperbrowser
   Skyvern—none0/10

   Evidence covers Skyvern's Python/TypeScript SDKs, REST API, MCP server, and visual dashboard, but nowhere mentions an official CLI tool for AI-native workflows. missing for 10: any documented CLI command, npm/pip CLI package, or terminal-based interface.

   • [claimed-docs] “Integrate browser automation into your product with Python, TypeScript, or REST.”
   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”
   • [claimed-docs] “The Skyvern MCP server lets AI assistants like Claude Desktop, Claude Code, Codex, Cursor, and Windsurf control a browser.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Hyperbrowser
   Skyvern✓fullprobed7/10

   Skyvern documents a public API/SDK surface (Python, TypeScript, REST) for creating tasks, running multi-step browser automations, and extracting structured data via JSON schema, matching the ai-native 'drive via documented API' story; it also ships an MCP server for agent control. Missing for 10: a discoverable OpenAPI/swagger spec (probe found 404s for all candidate paths) and independent/hands-on confirmation of API robustness beyond first-party docs.

   • [claimed-docs] “Integrate browser automation into your product with Python, TypeScript, or REST.”
   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”
   • [claimed-docs] “It navigates websites it has never seen before, filling forms, extracting data, and completing multi-step tasks via a simple API.”
   • [claimed-docs] “You provide a natural-language prompt describing the goal, a starting URL, and optionally a JSON schema for structured output.”
   • [claimed-docs] “you can extract structured data from any page using `page.extract` with a JSON schema, or by passing a `data_extraction_schema` to `page.age…”
   • [claimed-docs] “The Skyvern MCP server lets AI assistants like Claude Desktop, Claude Code, Codex, Cursor, and Windsurf control a browser.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://skyvern.com/openapi.json, https://skyvern.com/swagger.json, https://skyvern.com/api/openapi.…”
   • [probe] “official MCP server documented at https://skyvern.com/docs/developers/getting-started/mcp”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Skyvern—none0/10

   No evidence of scoped or least-privilege API credential issuance for agents; docs mention API keys and self-hosted LLM keys but nothing about credential scoping, permissions, or restricting agent access levels. Community comments even raise concerns about handling sensitive credentials in plain text with no mitigation shown. Missing for 10: any documentation of scoped API tokens, role-based access control, or least-privilege credential management for agents.

   • [claimed-docs] “Run Skyvern on your own infrastructure with your own LLM keys.”
   • [claimed-docs] “Self-hosted Skyvern runs entirely on your infrastructure: your servers, your browsers, your LLM API keys.”
   • [community] “you are expecting them to pass over their website login credentials and apparently their credit card details too, in plain text. You had bet…”

   proof ↗⚑ flag

   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

8. ai-native userBuild against official SDKs

   weight 2 · round to Hyperbrowser
   Skyvern✓fullprobed7/10

   Skyvern explicitly documents official Python and TypeScript SDKs plus a REST API for integrating browser automation, with SDK-level primitives like page.extract and data_extraction_schema shown in docs (skyvern-docs-1, skyvern-docs-5, skyvern-docs-19, skyvern-docs-4). Missing for 10: independent/hands-on developer corroboration of SDK usage and a public API reference (OpenAPI spec probe returned 404s, skyvern-probe-3), so quality is capped below full confidence in completeness.

   • [claimed-docs] “Integrate browser automation into your product with Python, TypeScript, or REST.”
   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”
   • [claimed-docs] “Drop-in AI commands on top of Playwright. Use natural language to act, extract, and validate — or fall back to selectors.”
   • [claimed-docs] “you can extract structured data from any page using `page.extract` with a JSON schema, or by passing a `data_extraction_schema` to `page.age…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://skyvern.com/openapi.json, https://skyvern.com/swagger.json, https://skyvern.com/api/openapi.…”

   proof ↗⚑ flag

   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

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Skyvern—none0/10

   No evidence in the pack mentions webhooks or event subscriptions of any kind; Skyvern's documented integration surfaces are REST/SDK APIs, Zapier, and an MCP server, none of which constitute a webhook subscription mechanism.

   ⚑ flag

   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

Agentic features

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

   weight 2 · round to Skyvern
   Skyvern~partialcommunity7/10

   Skyvern's docs show multi-step, code-first and no-code workflows that run via API or cloud UI, persist browser state, and can pause for human approval while capturing recordings/artifacts — all indicative of autonomous background execution (skyvern-docs-5,6,10,11,21). Zapier integration and API-driven triggering (skyvern-docs-16, skyvern-docs-28) supports running without manual intervention, but there's no explicit documentation of a scheduler, cron-like triggers, or continuous monitoring dashboard for unattended runs. Missing for 10: explicit scheduling/trigger docs, evidence of long-running unattended background jobs, and independent confirmation of reliability at scale (community notes some brittleness, e.g. skyvern-comm-2).

   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”
   • [claimed-docs] “Build multi-step automations visually in the Cloud UI with drag-and-drop blocks. No code required. Share templates across your team.”
   • [claimed-docs] “Human-in-the-loop flows: pause for approval between steps without losing browser state. The VNC stream lets you watch or take control at any…”
   • [claimed-docs] “Every run automatically captures what happened: recordings of the browser session, screenshots at each step, the AI's reasoning, and network…”
   • [claimed-docs] “Cookies, local storage, open tabs, and the current page all persist, so later operations pick up exactly where the previous one stopped.”
   • [claimed-docs] “Connect to Zapier”
   • [claimed-docs] “Skyvern automates browser-based workflows across these platforms — no API keys or custom connectors required.”
   • [community] “I played with the Geico example, and it seems to do a good job on the happy path. But I tried costcotravel.com... it struggled to hit the 'r…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Skyvern✓fullclaimed7/10

   Skyvern's core product IS an AI agent you delegate to via natural-language prompts to complete multi-step browser tasks (skyvern-docs-17, skyvern-docs-18), and it also ships a 'Copilot chat for building and debugging workflows interactively' inside the platform (skyvern-docs-25), plus SOP-to-workflow generation from plain English (skyvern-docs-24). This matches an AI-native user delegating tasks to a built-in assistant. Missing for 10: independent/hands-on validation of the copilot chat feature specifically (community evidence focuses on task execution quality, not the assistant/copilot UX), and no detail on assistant's conversational scope beyond workflow authoring.

   • [claimed-docs] “It navigates websites it has never seen before, filling forms, extracting data, and completing multi-step tasks via a simple API.”
   • [claimed-docs] “You provide a natural-language prompt describing the goal, a starting URL, and optionally a JSON schema for structured output.”
   • [claimed-docs] “SOP upload — describe a process in plain English and Skyvern builds the workflow”
   • [claimed-docs] “Copilot chat for building and debugging workflows interactively”
   • [github] “Skyvern can operate on websites it's never seen before, as it's able to map visual elements to actions necessary to complete a workflow, wit…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Hyperbrowser
   Skyvern✓fullcommunity7/10

   Skyvern's core interaction model is natural-language: users provide a prompt describing the goal (docs-18), SOPs in plain English are converted to workflows (docs-24), and a Copilot chat and MCP server let AI assistants/users direct browser actions in natural language (docs-25, docs-7, docs-19). This is corroborated by community reports of using it via prompts on real sites, though with mixed reliability on complex flows. missing for 10: independent benchmarking or hands-on confirmation that natural-language commands reliably handle complex multi-step tasks, and clearer evidence of NL-driven success rates beyond anecdotal HN reports.

   • [claimed-docs] “You provide a natural-language prompt describing the goal, a starting URL, and optionally a JSON schema for structured output.”
   • [claimed-docs] “SOP upload — describe a process in plain English and Skyvern builds the workflow”
   • [claimed-docs] “Copilot chat for building and debugging workflows interactively”
   • [claimed-docs] “The Skyvern MCP server lets AI assistants like Claude Desktop, Claude Code, Codex, Cursor, and Windsurf control a browser.”
   • [claimed-docs] “Drop-in AI commands on top of Playwright. Use natural language to act, extract, and validate — or fall back to selectors.”
   • [community] “I played with the Geico example, and it seems to do a good job on the happy path. But I tried costcotravel.com... it struggled to hit the 'r…”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round to Hyperbrowser
   Skyvern—none0/10

   Evidence shows only static docs describing SDKs and REST usage, with no interactive API reference or runnable-example explorer; probes explicitly found no OpenAPI/Swagger spec at any candidate path (404s), indicating no interactive reference exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://skyvern.com/openapi.json, https://skyvern.com/swagger.json, https://skyvern.com/api/openapi.…”
   • [probe] “PROBE docs-md: HTTP 404 at https://skyvern.com/docs.md”
   • [claimed-docs] “Integrate browser automation into your product with Python, TypeScript, or REST.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Skyvern—none0/10

   Skyvern offers a REST API (skyvern-docs-1) but a direct probe for OpenAPI/swagger specs at standard paths returned 404 across all candidates, and no docs mention a downloadable machine-readable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://skyvern.com/openapi.json, https://skyvern.com/swagger.json, https://skyvern.com/api/openapi.…”
   • [probe] “PROBE docs-md: HTTP 404 at https://skyvern.com/docs.md”
   • [claimed-docs] “Integrate browser automation into your product with Python, TypeScript, or REST.”

   proof ↗⚑ flag

   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

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

   weight 1 · round to Hyperbrowser
   Skyvern—none0/10

   Skyvern's docs describe cloud or self-hosted execution, credential handling, and observability, but nothing describes a dedicated sandbox/staging mode isolated from production data or systems — missing for 10: any mention of a sandbox environment, test/staging mode, or data isolation guarantees.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Skyvern—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; OpenAPI/spec probes all returned 404 and no changelog or versioning docs appear in the pack. Missing for 10: versioned API endpoints (e.g., /v1/), a published deprecation/support policy, and changelog documentation.

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

   proof ↗⚑ flag

   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

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
   Skyvern~partialclaimed5/10

   Docs show Skyvern's own SDK connects to a cloud Chromium instance over CDP and layers Playwright on top, and describe 'drop-in AI commands on top of Playwright' with fallback to raw selectors, implying some interoperability with existing Playwright code. However there is no explicit guidance or example showing a developer pointing an existing Playwright/Puppeteer/CDP script at Skyvern's managed browser instead of rewriting into Skyvern's task/workflow API, and no independent confirmation of this specific reuse pattern. Missing for 10: explicit BYO-script CDP endpoint docs, Puppeteer-specific support, and hands-on/community verification of dropping in existing automation code unchanged.

   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”
   • [claimed-docs] “Drop-in AI commands on top of Playwright. Use natural language to act, extract, and validate — or fall back to selectors.”
   • [claimed-docs] “you can extract structured data from any page using `page.extract` with a JSON schema, or by passing a `data_extraction_schema` to `page.age…”

   proof ↗⚑ flag

   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

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 to Skyvern
   Skyvern✓fullcommunity7/10

   Skyvern's docs explicitly describe storing credentials via password-manager vault integrations (Bitwarden, 1Password, Azure Key Vault) and automatically handling TOTP/2FA, email, and SMS verification during login flows, matching the story closely [skyvern-docs-8][skyvern-docs-26]. However, there's no independent/hands-on verification that secrets are never exposed to the LLM, and a community comment raises concern about credentials being handled in plain text, so missing for 10: independent security audit or hands-on confirmation of secret-masking from the model, and clarification addressing the community's plaintext-handling concern.

   • [claimed-docs] “Skyvern handles logins with stored credentials, TOTP/authenticator codes, email and SMS verification, magic links, and password manager inte…”
   • [claimed-docs] “Skyvern handles authentication end-to-end, from simple passwords to multi-factor flows with TOTP codes, email verification, and magic links.”
   • [community] “you are expecting them to pass over their website login credentials and apparently their credit card details too, in plain text. You had bet…”

   proof ↗⚑ flag

   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

Profiles

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

   weight 3 · round to Hyperbrowser
   Skyvern~partialclaimed6/10

   Skyvern's browser-sessions feature explicitly persists cookies, local storage, and open tabs across operations so 'later operations pick up exactly where the previous one stopped,' and pauses preserve browser state — this directly supports skipping repeated logins. However, the docs don't clearly describe a named 'profile' abstraction, how long sessions persist across truly separate future runs, or how these persisted sessions are managed/reused across different agents or teams. missing for 10: explicit reusable-profile management docs, long-term persistence guarantees across independent runs, independent/hands-on confirmation of skip-login behavior.

   • [claimed-docs] “Cookies, local storage, open tabs, and the current page all persist, so later operations pick up exactly where the previous one stopped.”
   • [claimed-docs] “Human-in-the-loop flows: pause for approval between steps without losing browser state. The VNC stream lets you watch or take control at any…”
   • [claimed-docs] “Skyvern handles logins with stored credentials, TOTP/authenticator codes, email and SMS verification, magic links, and password manager inte…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Hyperbrowser
   Skyvern—none0/10

   No evidence describes a bulk-operation feature (e.g., running the same task across a list/CSV of items, batch triggering, or concurrent multi-item processing) — the docs focus on single-task API calls, visual workflows, and MCP integration rather than batch/bulk execution.

   ⚑ flag

   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

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Skyvern
   Skyvern~partialclaimed3/10

   Skyvern documents a Zapier integration, which could allow external events to trigger Skyvern workflows, but there is no evidence of a native rule/trigger engine, webhooks, or scheduled/event-based automation within Skyvern itself. Missing for 10: documented native event triggers or webhook listeners, schedule-based triggers, and any conditional rule engine inside Skyvern's workflow builder.

   • [claimed-docs] “Connect to Zapier”
   • [claimed-docs] “Build multi-step automations visually in the Cloud UI with drag-and-drop blocks. No code required. Share templates across your team.”

   proof ↗⚑ flag

   Hyperbrowser—none0/10

   Hyperbrowser provides on-demand browser automation, scraping, extraction, and agent APIs, but there is no evidence of an event-driven rules/trigger engine (e.g., webhooks on page changes, scheduled triggers, condition-based automation) that would let a user define 'if X happens, do Y' automation. All capabilities described are invoked synchronously via API calls, not autonomously triggered by events. Missing for 10: rule/trigger definition mechanism, event listeners or webhooks, scheduling/condition-based automation execution.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Skyvern—none0/10

   The evidence pack describes Skyvern's workflow builder, API/SDK, MCP integration, and automation features extensively, but contains no mention of scheduling, cron triggers, or recurring job execution anywhere in the docs, GitHub description, or community discussion. Since Skyvern is a workflow/automation platform, scheduling recurring runs is a fair capability to expect, but it's simply absent from the provided evidence.

   ⚑ flag

   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

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Skyvern—none0/10

   No evidence in the pack describes version history, change review, or rollback capabilities for Skyvern workflows/automations — only building, running, sharing templates, and artifact capture (recordings/screenshots) are documented. Missing for 10: workflow version history, diff/review UI, rollback-to-previous-version mechanism, any changelog or audit trail for automation edits.

   ⚑ flag

   Hyperbrowser—none0/10

   Hyperbrowser is a cloud browser/automation infrastructure product with sessions, recordings, and agents, but there is no evidence of version control, review workflows, or rollback capabilities for automations themselves. Session recordings enable debugging replay but not versioning/review/rollback of automation scripts or flows. Missing for 10: any versioning system, diff/review interface, or rollback mechanism for automations.

   ⚑ flag

Local

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

   weight 2 · round to Skyvern
   Skyvern~partialclaimed6/10

   Skyvern is open-source and its self-hosted docs explicitly state it 'runs entirely on your infrastructure: your servers, your browsers, your LLM API keys' (skyvern-docs-12, skyvern-docs-2), which supports running without a cloud account. However, the core SDK/browser-automation flow described elsewhere connects to a 'cloud Chromium instance over CDP' (skyvern-docs-5), suggesting the default path is cloud-based, and no local-machine dev setup details (docker/local browser config, install steps) are shown. Missing for 10: explicit local-browser dev walkthrough, confirmation that the local-first SDK path bypasses cloud Chromium, and independent hands-on confirmation of local-only operation.

   • [claimed-docs] “Self-hosted Skyvern runs entirely on your infrastructure: your servers, your browsers, your LLM API keys.”
   • [claimed-docs] “Run Skyvern on your own infrastructure with your own LLM keys.”
   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”

   proof ↗⚑ flag

   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

Frameworks

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

   weight 2 · round drawn
   Skyvern—none0/10

   Skyvern documents a Python/TypeScript/REST SDK and an MCP server that plugs into Claude Desktop, Claude Code, Codex, Cursor, and Windsurf, but there is no evidence of documented adapters for Claude Agent SDK, Vercel AI SDK, LangChain, or CrewAI. missing for 10: any documented integration guide or adapter for LangChain, CrewAI, Vercel AI SDK, or Claude Agent SDK specifically.

   • [claimed-docs] “Integrate browser automation into your product with Python, TypeScript, or REST.”
   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”
   • [claimed-docs] “The Skyvern MCP server lets AI assistants like Claude Desktop, Claude Code, Codex, Cursor, and Windsurf control a browser.”

   proof ↗⚑ flag

   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

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
   Skyvern~partialclaimed6/10

   Docs state self-hosted Skyvern runs with 'your own LLM API keys' on your own infrastructure, implying model-agnosticism rather than lock-in to a single vendor, but there is no explicit list of supported providers/models or first-party guide on swapping LLM backends, and no independent confirmation of multi-provider support. Missing for 10: an explicit supported-providers list/config docs, and community/hands-on evidence of using non-default LLMs.

   • [claimed-docs] “Run Skyvern on your own infrastructure with your own LLM keys.”
   • [claimed-docs] “Self-hosted Skyvern runs entirely on your infrastructure: your servers, your browsers, your LLM API keys.”

   proof ↗⚑ flag

   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

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
   Skyvern~partialprobed5/10

   Docs confirm a hosted REST/SDK API where you submit a prompt+URL (optionally a JSON schema) and Skyvern runs the task on cloud Chromium without the caller managing a browser (skyvern-docs-1, skyvern-docs-5, skyvern-docs-18, skyvern-docs-17). However, there is no explicit documentation of a polling endpoint or webhook callback mechanism, and probes found no discoverable OpenAPI spec, so the exact result-retrieval mechanism described in the story is unconfirmed. Missing for 10: explicit webhook/callback docs, explicit polling endpoint docs, and an accessible API reference confirming these mechanics.

   • [claimed-docs] “Integrate browser automation into your product with Python, TypeScript, or REST.”
   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”
   • [claimed-docs] “You provide a natural-language prompt describing the goal, a starting URL, and optionally a JSON schema for structured output.”
   • [claimed-docs] “It navigates websites it has never seen before, filling forms, extracting data, and completing multi-step tasks via a simple API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://skyvern.com/openapi.json, https://skyvern.com/swagger.json, https://skyvern.com/api/openapi.…”

   proof ↗⚑ flag

   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

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 to Hyperbrowser
   Skyvern!disputedcontradicted5/10

   Skyvern's docs and GitHub strongly claim natural-language goal execution across novel, multi-step web flows (forms, logins, CAPTCHAs) via a single prompt/API (skyvern-docs-17, skyvern-docs-18, skyvern-gh-1), but a hands-on community test found it succeeded only on the 'happy path' and concretely failed on a real multi-step flow (costcotravel.com), struggling to hit a tab and failing to click a popup (skyvern-comm-2). This is a specific documented counter-example contradicting the 'completes multi-step task end to end' claim, not just general skepticism. Missing for 10: independent benchmark results, more hands-on trials showing consistent success on complex/unseen sites, and resolution of the reported failure case.

   • [claimed-docs] “It navigates websites it has never seen before, filling forms, extracting data, and completing multi-step tasks via a simple API.”
   • [claimed-docs] “You provide a natural-language prompt describing the goal, a starting URL, and optionally a JSON schema for structured output.”
   • [github] “Skyvern can operate on websites it's never seen before, as it's able to map visual elements to actions necessary to complete a workflow, wit…”
   • [community] “I played with the Geico example, and it seems to do a good job on the happy path. But I tried costcotravel.com... it struggled to hit the 'r…”

   proof ↗⚑ flag

   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

Workflows

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

   weight 2 · round to Skyvern
   Skyvern~partialclaimed5/10

   Skyvern clearly supports multi-step, repeatable workflows via both a code-first SDK and a visual no-code drag-and-drop builder (skyvern-docs-5, skyvern-docs-6, skyvern-docs-22), plus SOP-to-workflow generation and a browser recorder for building reusable automations (skyvern-docs-23, skyvern-docs-24). However, the evidence never explicitly documents loop constructs, conditional branching, or parameterized workflow inputs as first-class workflow-builder features. Missing for 10: explicit documentation of loop/iteration blocks, conditional/branching logic, and named/typed workflow parameters in the workflow builder.

   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”
   • [claimed-docs] “Build multi-step automations visually in the Cloud UI with drag-and-drop blocks. No code required. Share templates across your team.”
   • [claimed-docs] “Visual workflow builder for non-developers — drag-and-drop, no code required”
   • [claimed-docs] “Browser recorder that converts manual actions into reusable automations”
   • [claimed-docs] “SOP upload — describe a process in plain English and Skyvern builds the workflow”
   • [github] “a no-code workflow builder to help both technical and non-technical users automate manual workflows on any website, replacing brittle or unr…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Hyperbrowser
   Skyvern~partialprobed6/10

   Skyvern's docs show a strong code-first path (Python/TS/REST SDKs, page.extract, workflow creation via API) that covers most core automation tasks also available in the dashboard, and MCP/REST access is documented. However, several UI-only tooling features (drag-and-drop visual builder, browser recorder, SOP upload, copilot chat) are described only as dashboard capabilities with no documented API equivalent, and no public OpenAPI/swagger spec was discoverable to confirm full API-UI parity. Missing for 10: documented API equivalents for recorder/SOP-upload/copilot-chat features, and a discoverable OpenAPI reference confirming complete parity.

   • [claimed-docs] “Integrate browser automation into your product with Python, TypeScript, or REST.”
   • [claimed-docs] “Use the dashboard to run tasks and build agents visually.”
   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”
   • [claimed-docs] “Build multi-step automations visually in the Cloud UI with drag-and-drop blocks. No code required. Share templates across your team.”
   • [claimed-docs] “Visual workflow builder for non-developers — drag-and-drop, no code required”
   • [claimed-docs] “Browser recorder that converts manual actions into reusable automations”
   • [claimed-docs] “SOP upload — describe a process in plain English and Skyvern builds the workflow”
   • [claimed-docs] “Copilot chat for building and debugging workflows interactively”
   • [probe] “PROBE openapi: all candidate paths 404 (https://skyvern.com/openapi.json, https://skyvern.com/swagger.json, https://skyvern.com/api/openapi.…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Skyvern
   Skyvern~partialclaimed3/10

   Skyvern is open-source and self-hostable, meaning your data (artifacts, recordings, screenshots, network traffic) stays on your own infrastructure rather than being locked in a vendor's cloud, which implicitly supports data portability. However, there is no explicit documentation of a data export feature, standard open-format export (e.g., JSON/CSV bulk export of run history), or a stated 'leave with your data' workflow. Missing for 10: explicit export functionality/documentation, named open data formats, and any independent confirmation of successful data migration out of the platform.

   • [claimed-docs] “Self-hosted Skyvern runs entirely on your infrastructure: your servers, your browsers, your LLM API keys.”
   • [claimed-docs] “Every run automatically captures what happened: recordings of the browser session, screenshots at each step, the AI's reasoning, and network…”
   • [claimed-docs] “Run Skyvern on your own infrastructure with your own LLM keys.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Skyvern
   Skyvern!disputedcontradicted4/10

   Skyvern is described as open-source with a GitHub repo, and probe evidence confirms it self-identifies as 'open-source' (skyvern-probe-1), but community evidence directly contradicts full open-license access, noting the project is AGPL3 licensed, which is a legally open license but is called out as a practical non-starter/restrictive for many users (skyvern-comm-3). missing for 10: explicit statement of license terms in docs, confirmation of what percentage of the product (cloud vs self-hosted) is actually open-sourced, and independent corroboration that the full source is readable without restriction.

   • [github] “Skyvern can operate on websites it's never seen before, as it's able to map visual elements to actions necessary to complete a workflow, wit…”
   • [github] “a no-code workflow builder to help both technical and non-technical users automate manual workflows on any website, replacing brittle or unr…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://skyvern.com/llms.txt # Skyvern > Skyvern is an open-source, AI-powered browser automation platform. It …”
   • [community] “Exciting stuff, my employer would be interested but it's AGPL3 licensed so it's a non-starter for them.”

   proof ↗⚑ flag

   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

4. ai-native userSelf-host the core product

   weight 3 · round to Skyvern
   Skyvern✓fullprobed8/10

   Skyvern has a dedicated self-hosted docs page stating it 'runs entirely on your infrastructure: your servers, your browsers, your LLM API keys' (skyvern-docs-12, skyvern-docs-2), and community evidence confirms it is genuinely open-source (AGPL3) rather than just marketing language (skyvern-comm-3). Missing for 10: independent hands-on confirmation of a successful self-host deployment and clarity on how AGPL licensing affects commercial self-hosting use.

   • [claimed-docs] “Self-hosted Skyvern runs entirely on your infrastructure: your servers, your browsers, your LLM API keys.”
   • [claimed-docs] “Run Skyvern on your own infrastructure with your own LLM keys.”
   • [community] “Exciting stuff, my employer would be interested but it's AGPL3 licensed so it's a non-starter for them.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://skyvern.com/llms.txt # Skyvern > Skyvern is an open-source, AI-powered browser automation platform. It …”

   proof ↗⚑ flag

   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

Pricing

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

   weight 2 · round to Hyperbrowser
   Skyvern—none0/10

   The pricing page is referenced only for its target-audience blurb (skyvern-docs-13); no evidence pack item shows actual per-task or per-browser-hour rates, tiers, or documented rate/concurrency limits. Community comments only express general cost concerns ('pretty pricey', wanting cost down 'at scale') without citing concrete published pricing or limits.

   • [claimed-docs] “You're replacing brittle Selenium scripts, integrating browser automation via API, or building workflows into your product.”
   • [community] “I tried it out and it's pretty pricey. My OpenAI API bill is $3.20 after using this on a few different pages to test it out... this is alway…”
   • [community] “This is an impressive tool. I especially like the observability around the workflow and the steps it takes to achieve the outcome. We are po…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Skyvern
   Skyvern~partialclaimed5/10

   Skyvern offers a self-hosted deployment mode where 'your servers, your browsers, your LLM API keys' run entirely on the user's own infrastructure, which lets an AI-native user control where data resides by choosing their hosting region themselves — but this is achieved only by self-hosting, not via an explicit region/residency selector in the managed cloud product. Missing for 10: documented data residency/region options in the hosted Skyvern Cloud offering, compliance certifications, or explicit multi-region storage controls.

   • [claimed-docs] “Run Skyvern on your own infrastructure with your own LLM keys.”
   • [claimed-docs] “Self-hosted Skyvern runs entirely on your infrastructure: your servers, your browsers, your LLM API keys.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Skyvern
   Skyvern~partialclaimed4/10

   Skyvern offers self-hosted deployment using your own infrastructure and your own LLM API keys, which implicitly lets users avoid sending data to Skyvern-controlled models/training pipelines, but there is no explicit privacy policy, data-retention statement, or 'we do not train on your data' commitment in the evidence for the hosted/cloud offering. Missing for 10: explicit no-training/data-use policy documentation, opt-out mechanism for the cloud product, and independent confirmation of data handling practices.

   • [claimed-docs] “Run Skyvern on your own infrastructure with your own LLM keys.”
   • [claimed-docs] “Self-hosted Skyvern runs entirely on your infrastructure: your servers, your browsers, your LLM API keys.”

   proof ↗⚑ flag

   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

3. ai-native userControl data retention and deletion

   weight 2 · round to Skyvern
   Skyvern~partialcommunity4/10

   Skyvern offers self-hosting (docs-2, docs-12) which gives infrastructure-level control over where data lives, and it captures artifacts (recordings, screenshots, network traffic) per run (docs-11), implying some data exists to manage, but there is no documented retention policy, data deletion API/UI, or export/purge controls for the cloud/hosted product. missing for 10: explicit data retention policy, user-facing deletion/export controls, documentation on how long artifacts/credentials are stored in cloud mode, and independent confirmation that self-hosting actually eliminates vendor-side data retention.

   • [claimed-docs] “Run Skyvern on your own infrastructure with your own LLM keys.”
   • [claimed-docs] “Self-hosted Skyvern runs entirely on your infrastructure: your servers, your browsers, your LLM API keys.”
   • [claimed-docs] “Every run automatically captures what happened: recordings of the browser session, screenshots at each step, the AI's reasoning, and network…”
   • [community] “you are expecting them to pass over their website login credentials and apparently their credit card details too, in plain text. You had bet…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Skyvern—none0/10

   No evidence pack item discusses telemetry, usage tracking, or an opt-out mechanism; while self-hosting exists, there is no explicit statement about data collection or opt-out controls for the cloud/hosted product. missing for 10: any mention of telemetry collection, privacy policy on usage data, or an opt-out setting/flag.

   ⚑ flag

   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

Live

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

   weight 2 · round to Skyvern
   Skyvern✓fullclaimed8/10

   Docs explicitly state a VNC stream lets you watch a live session and take control at any point, plus pause-for-approval human-in-the-loop flows that preserve browser state — directly matching the story. missing for 10: independent/hands-on confirmation of the live takeover UX and details on how control handoff works mid-run beyond the docs description.

   • [claimed-docs] “Human-in-the-loop flows: pause for approval between steps without losing browser state. The VNC stream lets you watch or take control at any…”
   • [claimed-docs] “Cookies, local storage, open tabs, and the current page all persist, so later operations pick up exactly where the previous one stopped.”

   proof ↗⚑ flag

   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

Replay

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

   weight 2 · round to Skyvern
   Skyvern✓fullcommunity8/10

   Skyvern docs explicitly state every run captures session recordings, per-step screenshots, AI reasoning traces, and network traffic for debugging, and community feedback corroborates strong observability into workflow steps. missing for 10: independent hands-on verification of the video/timeline UI itself, and no mention of a true step-by-step interactive timeline scrubber beyond artifact capture.

   • [claimed-docs] “Every run automatically captures what happened: recordings of the browser session, screenshots at each step, the AI's reasoning, and network…”
   • [community] “This is an impressive tool. I especially like the observability around the workflow and the steps it takes to achieve the outcome. We are po…”

   proof ↗⚑ flag

   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

Fleets

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

   weight 2 · round to Hyperbrowser
   Skyvern—none0/10

   Evidence covers session persistence, VNC control, self-hosting, and SDK/API access, but nowhere documents concurrency limits, fleet-level session orchestration, or programmatic management of multiple simultaneous browser sessions. Missing for 10: documented concurrency limits, APIs for spinning up/managing many parallel sessions, and any scaling/throughput guidance.

   • [claimed-docs] “Human-in-the-loop flows: pause for approval between steps without losing browser state. The VNC stream lets you watch or take control at any…”
   • [claimed-docs] “Cookies, local storage, open tabs, and the current page all persist, so later operations pick up exactly where the previous one stopped.”
   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”
   • [claimed-docs] “Self-hosted Skyvern runs entirely on your infrastructure: your servers, your browsers, your LLM API keys.”

   proof ↗⚑ flag

   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

Lifecycle

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

   weight 1 · round drawn
   Skyvern—none0/10

   No evidence pack item mentions webhooks, callback URLs, or push notifications for task/session completion; the docs discuss artifacts, VNC streaming, and human-in-the-loop review but nothing about event-driven notification instead of polling. missing for 10: any documentation of webhook/callback support, event subscription API, or notification configuration.

   ⚑ flag

   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

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 Skyvern
   Skyvern✓fullclaimed8/10

   Skyvern's docs give an explicit, detailed captcha stance: automatic detection and solving via its vision model for reCAPTCHA v2/v3, hCaptcha, Cloudflare Turnstile, FunCaptcha, MTCaptcha, and text/image captchas, avoiding silent failure ambiguity. Missing for 10: independent/hands-on confirmation that captcha solving works reliably in practice (community evidence discusses pricing, mobile UX, and credential handling but not captcha outcomes specifically), and no documented fallback/human-in-the-loop behavior specifically tied to captcha failures.

   • [claimed-docs] “Skyvern detects CAPTCHAs using its vision model and solves them automatically. This works for reCAPTCHA v2/v3, hCaptcha, Cloudflare Turnstil…”
   • [claimed-docs] “Skyvern detects CAPTCHAs using its vision model and solves them automatically.”

   proof ↗⚑ flag

   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

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
   Skyvern—none0/10

   No evidence in the pack of any published acceptable-use policy, terms of service, or anti-abuse statement covering CAPTCHA-solving/stealth automation features; docs describe capabilities (CAPTCHA bypass, bot bypass) but no governance/AUP language is cited. missing for 10: a published acceptable-use policy, anti-abuse terms, or statement on permitted use of stealth/CAPTCHA-bypass features.

   ⚑ flag

   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

Stealth

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

   weight 2 · round to Hyperbrowser
   Skyvern—none0/10

   Evidence covers CAPTCHA solving and authentication/2FA handling, but there is no mention anywhere of stealth fingerprinting, browser fingerprint spoofing, or residential/geo-targeted proxy support. Missing for 10: any documentation of proxy configuration, geo-targeting, or anti-fingerprinting/stealth mode features.

   • [claimed-docs] “Skyvern detects CAPTCHAs using its vision model and solves them automatically. This works for reCAPTCHA v2/v3, hCaptcha, Cloudflare Turnstil…”
   • [claimed-docs] “Skyvern detects CAPTCHAs using its vision model and solves them automatically.”

   proof ↗⚑ flag

   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

Extraction

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

   weight 3 · round to Hyperbrowser
   Skyvern✓fullclaimed7/10

   Skyvern's docs explicitly support structured, schema-based extraction via `page.extract` with a JSON schema or `data_extraction_schema` param, matching the developer's need for typed output rather than raw text (skyvern-docs-4, skyvern-docs-20, skyvern-docs-18). However, evidence only shows JSON-schema validation, not native Zod/Pydantic model binding, and there's no independent/hands-on confirmation of this specific feature. missing for 10: explicit Zod/Pydantic model integration examples, independent verification of extraction accuracy/schema enforcement.

   • [claimed-docs] “you can extract structured data from any page using `page.extract` with a JSON schema, or by passing a `data_extraction_schema` to `page.age…”
   • [claimed-docs] “you can extract structured data from any page using page.extract with a JSON schema”
   • [claimed-docs] “You provide a natural-language prompt describing the goal, a starting URL, and optionally a JSON schema for structured output.”
   • [claimed-docs] “Browser Automation is the code-first way to build multi-step automations. The Skyvern SDK connects to a cloud Chromium instance over CDP, la…”

   proof ↗⚑ flag

   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

Files

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

   weight 1 · round to Skyvern
   Skyvern~partialclaimed5/10

   Docs show Skyvern can log into vendor portals and download PDFs (skyvern-docs-15) and captures per-run artifacts like recordings, screenshots, and network traffic retrievable afterward (skyvern-docs-11), implying file download support, but there is no explicit documentation of file upload capability to sites, nor of a dedicated API/UI for retrieving downloaded artifacts as opposed to just run/debug artifacts. missing for 10: explicit upload-to-site capability documentation, a documented file-download/artifact storage API distinct from debugging screenshots, and independent/hands-on confirmation of file transfer working in practice.

   • [claimed-docs] “Log into vendor portals, find invoices, download PDFs.”
   • [claimed-docs] “Every run automatically captures what happened: recordings of the browser session, screenshots at each step, the AI's reasoning, and network…”
   • [claimed-docs] “Auto-fill and submit applications on Lever, Greenhouse, and more.”

   proof ↗⚑ flag

   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