Hyperbrowser vs Notte

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 to Notte
   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

   Notte~partialclaimed4/10

   Notte lets you script deterministic parts and generate/edit workflow code (notte-docs-2, notte-docs-26, notte-docs-30, notte-gh-2), which implies some cached/generated code can be replayed without re-prompting the LLM, but there is no explicit documentation of an action/result cache, deterministic replay guarantee, or cost/latency comparison for repeat runs. missing for 10: explicit caching mechanism for resolved actions, documentation of deterministic replay across runs, and cost/latency benchmarks comparing cached vs re-prompted execution.

   • [claimed-docs] “Deploy your scripts as API endpoints. Serverless automations you can invoke and schedule anywhere.”
   • [claimed-docs] “Functions are serverless deployments of your browser automations that can b”
   • [claimed-docs] “Generate it with the CLI first, then edit it.”
   • [github] “combines AI agents with traditional scripting for maximum efficiency - letting you script deterministic parts and use AI only when needed, c…”

   proof ↗⚑ flag

Dom

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

   weight 3 · round drawn
   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

   Notte~partialcommunity6/10

   Docs describe a genuine action-space abstraction (observe()/act() calls, 'no selectors, no maintenance', natural-language task execution) that maps directly to the described act/click/type primitives, and the CLI/MCP integrations reinforce this as a core product concept. However, there's no first-party benchmark or independent hands-on confirmation that these primitives specifically survive selector/layout changes, and community commentary raises skepticism about action-space reliability versus screenshot+HTML approaches without being a concrete contradiction. Missing for 10: independent reproducibility evidence of resilience across DOM changes, and a documented before/after example showing selector survival.

   • [claimed-docs] “Element IDs, selectors, and field mappings must come from a live `observe()` call, CLI `notte page observe` output, or generated workflow co…”
   • [claimed-docs] “Describe a task. Watch it happen. One prompt. No selectors, no maintenance.”
   • [github] “Give AI agents natural language tasks to complete on websites”
   • [github] “combines AI agents with traditional scripting for maximum efficiency - letting you script deterministic parts and use AI only when needed, c…”
   • [community] “why would an action space be more reliable than screenshots + html, this i don't get. I can think of many use cases it would fail”

   proof ↗⚑ flag

Observe

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

   weight 1 · round to Notte
   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

   Notte~partialprobed6/10

   Notte's docs explicitly describe an `observe()` call and CLI `notte page observe` command that returns element IDs/selectors before actions are executed, which is direct evidence of a preview/plan-before-act primitive. However, the evidence pack lacks a full worked example showing the observe→plan→act workflow end-to-end, independent confirmation of its reliability, or details on how proposed actions are presented/reviewed by a developer. missing for 10: a complete observe/plan-then-act workflow example, independent/hands-on verification that observe output is accurate and usable for gating actions, and documentation of any 'plan' abstraction distinct from observe.

   • [claimed-docs] “Element IDs, selectors, and field mappings must come from a live `observe()` call, CLI `notte page observe` output, or generated workflow co…”
   • [probe] “official CLI documented at https://docs.notte.cc/quickstart”
   • [claimed-docs] “The Notte CLI lets AI agents control browsers through simple shell commands.”

   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 Notte
   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

   Notte~partialcommunity5/10

   Notte's core action space is DOM/observe-based, but the docs include a dedicated integration guide for OpenAI's Computer Use Agent (CUA) that operates on screenshots atop Notte's browser infrastructure, showing a vision/computer-use path exists. However this is presented as an external integration rather than a first-class 'switch mode' toggle within Notte's own API, and community commentary explicitly questions the reliability of Notte's action-space approach versus screenshot-based methods. Missing for 10: native documented API/flag to toggle into vision mode, first-party examples of vision-based action execution, and independent hands-on confirmation that the CUA integration works reliably.

   • [claimed-docs] “This guide explains how to integrate OpenAI's Computer Use Agent (CUA) with Notte's browser infrastructure for automated web interactions.”
   • [claimed-docs] “Live View & Replays Screenshare & session playback”
   • [community] “why would an action space be more reliable than screenshots + html, this i don't get. I can think of many use cases it would fail”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to Notte
   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

   Notte✓fullprobed9/10

   Notte serves a verified llms.txt at docs.notte.cc/llms.txt with explicit 'Critical Instructions For AI Agents' directing agents to further docs, plus extensive agent-oriented docs (MCP server, CLI, integration guides for CrewAI, Vercel AI SDK, Claude Code) confirming a mature agentic-docs ecosystem. Missing for 10: independent third-party confirmation that agents actually consume llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.notte.cc/llms.txt # Notte ## Critical Instructions For AI Agents STOP. Read and follow https://do…”
   • [claimed-docs] “Give your AI agents access to the entire Notte ecosystem. Notte MCP lets it start cloud browser sessions, interact with the pages, fetch dat…”
   • [claimed-docs] “Notte MCP lets it start cloud browser sessions, interact with the pages, fetch data, build scripts, and more.”
   • [claimed-docs] “pointing it at the Notte MCP server hands your crew a real browser.”
   • [claimed-docs] “Point its MCP client at the Notte MCP server and your TypeScript agent gets a browser.”
   • [claimed-docs] “The Notte CLI lets AI agents control browsers through simple shell commands.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Notte✓fullprobed8/10

   Notte offers cloud/remote browser sessions, an API with Bearer token auth, serverless 'Functions' deployments that can be scheduled, and a CLI/SDK — all designed for headless, programmatic, CI-friendly automation without a local browser or UI. Community evidence corroborates real usage of the API/agent stack though with mixed reliability reports on task success. Missing for 10: no explicit CI pipeline example (e.g., GitHub Actions), no independent benchmark confirming headless stability at scale.

   • [claimed-docs] “Deploy your scripts as API endpoints. Serverless automations you can invoke and schedule anywhere.”
   • [claimed-docs] “All API requests require a Bearer token in the `Authorization` header.”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically.”
   • [claimed-docs] “Functions are serverless deployments of your browser automations that can b”
   • [claimed-docs] “Generate it with the CLI first, then edit it.”
   • [probe] “official CLI documented at https://docs.notte.cc/quickstart”
   • [community] “just tried to use it to extract data from hyatt.com completely failed. another hype but actually doesn't work browser agent.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Hyperbrowser—none0/10

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

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

   proof ↗⚑ flag

   Notte—none0/10

   All MCP-related evidence describes Notte exposing its own MCP server for external agents (Claude, CrewAI, Vercel AI SDK) to plug into and control Notte's browser tools — the reverse direction of this story. There is no evidence that Notte's own agents can consume or plug in external MCP servers to gain new tools.

   • [claimed-docs] “Give your AI agents access to the entire Notte ecosystem. Notte MCP lets it start cloud browser sessions, interact with the pages, fetch dat…”
   • [claimed-docs] “Notte MCP lets it start cloud browser sessions, interact with the pages, fetch data, build scripts, and more.”
   • [claimed-docs] “pointing it at the Notte MCP server hands your crew a real browser.”
   • [claimed-docs] “Point its MCP client at the Notte MCP server and your TypeScript agent gets a browser.”
   • [probe] “official MCP server documented at https://docs.notte.cc/mcp-server”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Notte✓fullprobed8/10

   Notte publishes a dedicated official MCP server (docs.notte.cc/mcp-server) that gives agents access to cloud browser sessions, page interaction, and data extraction, and this is corroborated across multiple integration guides (CrewAI, Vercel AI SDK) showing agents pointed at the Notte MCP server to get a real browser. Missing for 10: independent/hands-on third-party confirmation that the MCP server works reliably in practice (community evidence only covers the general product, not MCP specifically).

   • [claimed-docs] “Give your AI agents access to the entire Notte ecosystem. Notte MCP lets it start cloud browser sessions, interact with the pages, fetch dat…”
   • [claimed-docs] “Notte MCP lets it start cloud browser sessions, interact with the pages, fetch data, build scripts, and more.”
   • [claimed-docs] “pointing it at the Notte MCP server hands your crew a real browser.”
   • [claimed-docs] “Point its MCP client at the Notte MCP server and your TypeScript agent gets a browser.”
   • [probe] “official MCP server documented at https://docs.notte.cc/mcp-server”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Notte
   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

   Notte✓fullprobed8/10

   Notte documents an official CLI used to generate config, drive browsers, and produce observe/page output (notte-docs-30, notte-docs-31, notte-docs-9, notte-docs-8, notte-probe-4), explicitly positioned for AI agents to control browsers via shell commands. missing for 10: no independent/community hands-on validation of the CLI specifically (only vendor docs), and no detailed CLI command reference beyond scattered mentions.

   • [claimed-docs] “The Notte CLI lets AI agents control browsers through simple shell commands.”
   • [claimed-docs] “Generate it with the CLI first, then edit it.”
   • [claimed-docs] “give them the notte CLI and they can drive real browsers”
   • [claimed-docs] “Element IDs, selectors, and field mappings must come from a live `observe()` call, CLI `notte page observe` output, or generated workflow co…”
   • [probe] “official CLI documented at https://docs.notte.cc/quickstart”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Notte✓fullprobed8/10

   Notte documents a full public API with Bearer-token authentication, API reference pages (e.g., agent-start endpoint), SDKs, CLI, and MCP server for programmatic/agentic control of sessions, scraping, and functions, matching the ai-native/agenticness story well. missing for 10: no discoverable OpenAPI/swagger spec (404s on probe) and no independent third-party confirmation of API robustness beyond vendor docs.

   • [claimed-docs] “All API requests require a Bearer token in the `Authorization` header.”
   • [claimed-docs] “used to create cloud browser sessions, scrape webpages, and run web ai agents to act on your behalf on the internet”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically.”
   • [claimed-docs] “Functions are serverless deployments of your browser automations that can b”
   • [claimed-docs] “Give your AI agents access to the entire Notte ecosystem. Notte MCP lets it start cloud browser sessions, interact with the pages, fetch dat…”
   • [probe] “official MCP server documented at https://docs.notte.cc/mcp-server”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.notte.cc/openapi.json, https://docs.notte.cc/swagger.json, https://docs.notte.cc/api/op…”
   • [claimed-docs] “Generate it with the CLI first, then edit it.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Hyperbrowser—none0/10

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

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

   proof ↗⚑ flag

   Notte—none0/10

   Evidence shows only a single Bearer-token API authentication scheme (notte-docs-17) and a vault feature that hides stored web credentials from the LLM (notte-docs-14, notte-docs-27), but nothing about issuing scoped, role-limited, or least-privilege API keys specifically for agents. No mention of API key scopes, permission tiers, or per-agent credential restrictions.

   • [claimed-docs] “All API requests require a Bearer token in the `Authorization` header.”
   • [claimed-docs] “The significant security benefit of this approach is that the LLM never actually sees the actual credentials.”
   • [claimed-docs] “credentials are never exposed to LLMs or third-party services during agent execution”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Hyperbrowser
   Hyperbrowser✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Notte~partialprobed5/10

   Notte provides a documented REST API with Bearer-token auth, an official CLI, and an MCP server plus integration guides for frameworks like CrewAI, Vercel AI SDK, and OpenAI CUA, all of which support building AI-native automations programmatically. However, no evidence explicitly names or documents a first-party 'SDK' package (e.g., Python/TypeScript client library) and an OpenAPI spec probe returned 404s, suggesting the API surface may not be as formally packaged as a dedicated SDK. missing for 10: explicit official SDK package docs (Python/JS), a working OpenAPI/schema reference, independent developer confirmation of SDK usage.

   • [claimed-docs] “All API requests require a Bearer token in the `Authorization` header.”
   • [claimed-docs] “Generate it with the CLI first, then edit it.”
   • [probe] “official CLI documented at https://docs.notte.cc/quickstart”
   • [claimed-docs] “Give your AI agents access to the entire Notte ecosystem. Notte MCP lets it start cloud browser sessions, interact with the pages, fetch dat…”
   • [probe] “official MCP server documented at https://docs.notte.cc/mcp-server”
   • [claimed-docs] “pointing it at the Notte MCP server hands your crew a real browser.”
   • [claimed-docs] “Point its MCP client at the Notte MCP server and your TypeScript agent gets a browser.”
   • [claimed-docs] “This guide explains how to integrate OpenAI's Computer Use Agent (CUA) with Notte's browser infrastructure for automated web interactions.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.notte.cc/openapi.json, https://docs.notte.cc/swagger.json, https://docs.notte.cc/api/op…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Hyperbrowser—none0/10

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

   ⚑ flag

   Notte—none0/10

   No evidence pack item mentions webhooks or event subscription mechanisms; the product offers sessions, MCP, CLI, and API endpoints but nothing about push notifications or webhook callbacks. Missing for 10: any documentation of webhook subscription, event types, or delivery mechanism.

   ⚑ flag

Agentic features

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

   weight 2 · round to Notte
   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

   Notte✓fullcommunity7/10

   Notte supports deploying scripts/agents as serverless 'Functions' invocable via API and schedulable, plus persistent sessions, credential vaults, and cloud browser infrastructure that let automations run unattended in the background (notte-docs-2, notte-docs-26, notte-docs-24, notte-docs-4). This directly matches autonomous background automation for an AI-native user. Missing for 10: no independent/hands-on confirmation of scheduling reliability in production, and community feedback includes at least one report of a failed extraction task (notte-comm-1), so real-world robustness is unverified.

   • [claimed-docs] “Deploy your scripts as API endpoints. Serverless automations you can invoke and schedule anywhere.”
   • [claimed-docs] “Functions are serverless deployments of your browser automations that can b”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically.”
   • [claimed-docs] “Secure credential storage. Keep passwords, API keys, and sensitive data encrypted.”
   • [claimed-docs] “Persist cookies and login state across sessions.”
   • [community] “just tried to use it to extract data from hyatt.com completely failed. another hype but actually doesn't work browser agent.”

   proof ↗⚑ flag

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

   weight 3 · round to Hyperbrowser
   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

   Notte!disputedcontradicted5/10

   Notte's core offering is an AI web agent that accepts natural-language task descriptions and executes them autonomously on websites (notte-gh-1, notte-docs-18, notte-docs-37), which functions as a built-in AI assistant a user delegates tasks to. However, a hands-on community report describes a concrete failure ('tried to use it to extract data from hyatt.com completely failed... another hype but actually doesn't work browser agent' — notte-comm-1), and the founder himself admits only ~60% reliability on captcha-gated sites (notte-comm-7), directly contradicting the polished 'describe a task, watch it happen' framing. Missing for 10: independent verification of consistent task success, a true conversational/chat-based assistant UI (rather than API/CLI-driven task submission), and resolution of the documented failure case.

   • [github] “Give AI agents natural language tasks to complete on websites”
   • [claimed-docs] “Describe a task. Watch it happen. One prompt. No selectors, no maintenance.”
   • [claimed-docs] “used to create cloud browser sessions, scrape webpages, and run web ai agents to act on your behalf on the internet”
   • [community] “just tried to use it to extract data from hyatt.com completely failed. another hype but actually doesn't work browser agent.”
   • [community] “Founder: 'we can solve ~60% of providers right now (incl reCAPTCHA, Cloudflare, and main ones) and some others are still work in progress' r…”

   proof ↗⚑ flag

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

   weight 2 · round to Hyperbrowser
   Hyperbrowser✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Notte!disputedcontradicted5/10

   Notte's core value prop is natural-language task execution ('Describe a task. Watch it happen. One prompt', 'Give AI agents natural language tasks to complete on websites') backed by agent-start API and CLI/MCP integrations, so the capability is clearly built and documented. However, a hands-on community report describes a complete failure when trying to extract data from hyatt.com via the agent, and the founder himself admits captcha/anti-bot handling only works ~60% of the time, concretely undercutting reliability of the NL-driven approach. Missing for 10: independent reproducible success cases beyond vendor demos, and resolution of the documented hyatt.com failure.

   • [claimed-docs] “Describe a task. Watch it happen. One prompt. No selectors, no maintenance.”
   • [github] “Give AI agents natural language tasks to complete on websites”
   • [claimed-docs] “used to create cloud browser sessions, scrape webpages, and run web ai agents to act on your behalf on the internet”
   • [community] “just tried to use it to extract data from hyatt.com completely failed. another hype but actually doesn't work browser agent.”
   • [community] “Founder: 'we can solve ~60% of providers right now (incl reCAPTCHA, Cloudflare, and main ones) and some others are still work in progress' r…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Hyperbrowser
   Hyperbrowser~partialprobed3/10

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

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

   proof ↗⚑ flag

   Notte—none0/10

   Evidence shows only static API-reference pages (authentication, agent-start) and no OpenAPI/Swagger spec was found at any candidate path (probe-2 returned 404s), and nothing in the pack describes an interactive console or runnable code examples in the API docs.

   • [claimed-docs] “All API requests require a Bearer token in the `Authorization` header.”
   • [claimed-docs] “used to create cloud browser sessions, scrape webpages, and run web ai agents to act on your behalf on the internet”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.notte.cc/openapi.json, https://docs.notte.cc/swagger.json, https://docs.notte.cc/api/op…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Hyperbrowser—none0/10

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

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

   proof ↗⚑ flag

   Notte—none0/10

   The evidence shows Notte has human-readable API reference docs (auth, agent-start) but a direct probe for machine-readable spec files (openapi.json, swagger.json, etc.) returned 404 on all candidate paths, indicating no downloadable OpenAPI or equivalent spec is published.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.notte.cc/openapi.json, https://docs.notte.cc/swagger.json, https://docs.notte.cc/api/op…”
   • [claimed-docs] “All API requests require a Bearer token in the `Authorization` header.”
   • [claimed-docs] “used to create cloud browser sessions, scrape webpages, and run web ai agents to act on your behalf on the internet”

   proof ↗⚑ flag

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

   weight 1 · round to Hyperbrowser
   Hyperbrowser~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Notte~partialclaimed3/10

   Notte documents 'isolated browser instances running in the cloud' for each session and a free trial ('Try the full platform without a card'), which implies some session-level isolation from a user's own systems, but there is no explicit sandbox/production-data separation mode, staging environment, or test-data guarantee described anywhere in the docs. missing for 10: explicit sandbox vs production distinction, test-data isolation guarantees, hands-on confirmation that sandbox sessions never touch real production data.

   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically.”
   • [claimed-docs] “Try the full platform without a card.”
   • [claimed-docs] “Build, debug, and deploy production workflows with cloud browsers, web agents, scraping, serverless functions, credentials, and identities i…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Hyperbrowser—none0/10

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

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

   proof ↗⚑ flag

   Notte—none0/10

   There is evidence of an API with bearer token auth, but nothing about API versioning or a documented deprecation policy; OpenAPI probes even 404, suggesting no formal spec surfaced. missing for 10: versioning scheme, deprecation policy documentation, changelog entries about breaking changes.

   • [claimed-docs] “All API requests require a Bearer token in the `Authorization` header.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.notte.cc/openapi.json, https://docs.notte.cc/swagger.json, https://docs.notte.cc/api/op…”

   proof ↗⚑ flag

Compat

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

   weight 2 · round to Hyperbrowser
   Hyperbrowser✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Notte✓fullclaimed7/10

   Notte sessions explicitly expose a CDP endpoint documented to work with Playwright (notte-docs-11), which directly supports connecting existing Playwright/CDP automation code to Notte's cloud browsers rather than rewriting it. Puppeteer isn't explicitly named but CDP is the shared protocol underlying it, and sessions are described as programmatically controllable cloud instances (notte-docs-24). missing for 10: explicit Puppeteer example/docs, independent hands-on confirmation of the CDP/Playwright connection working at scale.

   • [claimed-docs] “Notte sessions expose a Chrome DevTools Protocol (CDP) endpoint that you can connect to with Playwright.”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically.”
   • [claimed-docs] “Viewing sessions: When you start a session, the output includes a `ViewerUrl` - open it to watch your browser live”

   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 Notte
   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

   Notte~partialclaimed7/10

   Notte's docs describe a credential vault where secrets are injected into the browser session but never exposed to the LLM, plus persistent cookies/login state and 'verified identities' (emails/phones) for sign-up and 2FA flows, directly matching the core of the story. However, there's no explicit walkthrough of a TOTP code being generated/entered by the agent, and no independent/hands-on confirmation that 2FA login flows work end-to-end in practice. Missing for 10: concrete TOTP-specific workflow documentation, independent verification of vault+2FA login success.

   • [claimed-docs] “Secure credential storage. Keep passwords, API keys, and sensitive data encrypted.”
   • [claimed-docs] “The significant security benefit of this approach is that the LLM never actually sees the actual credentials.”
   • [claimed-docs] “credentials are never exposed to LLMs or third-party services during agent execution”
   • [claimed-docs] “Persist cookies and login state across sessions.”
   • [claimed-docs] “Emails and phone numbers for sign-up and 2FA. Verified identities to interact across platforms.”
   • [claimed-docs] “Authenticated Profiles Browser profiles for each agent”

   proof ↗⚑ flag

Profiles

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

   weight 3 · round drawn
   Hyperbrowser✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Notte✓fullclaimed7/10

   Notte docs explicitly document persisting cookies/login state across sessions and 'Authenticated Profiles' as browser profiles per agent, alongside secure credential vaults so agents can skip re-authentication on subsequent runs. missing for 10: no independent/hands-on confirmation that persisted profiles actually skip login walls in practice, and no detail on profile reuse limits/expiry.

   • [claimed-docs] “Persist cookies and login state across sessions.”
   • [claimed-docs] “Authenticated Profiles Browser profiles for each agent”
   • [claimed-docs] “Secure credential storage. Keep passwords, API keys, and sensitive data encrypted.”
   • [claimed-docs] “The significant security benefit of this approach is that the LLM never actually sees the actual credentials.”
   • [claimed-docs] “credentials are never exposed to LLMs or third-party services during agent execution”

   proof ↗⚑ flag

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

   weight 2 · round to Hyperbrowser
   Hyperbrowser~partialcommunity6/10

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

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

   proof ↗⚑ flag

   Notte~partialclaimed4/10

   Notte offers scalable cloud browser sessions and serverless 'functions'/API endpoints that can be invoked and scheduled programmatically, which could in principle be used to run automation across many items, but there is no explicit documentation of a batch/bulk-processing feature (e.g., iterating over a list of URLs/records, parallel job queues, or bulk extraction outputs). missing for 10: explicit bulk/batch API or CLI examples, evidence of parallel multi-item execution, and any hands-on confirmation of running the same task across many inputs.

   • [claimed-docs] “Remote browser infrastructure. Fast, scalable browsers with anti-detection, proxies, and captcha solving.”
   • [claimed-docs] “Deploy your scripts as API endpoints. Serverless automations you can invoke and schedule anywhere.”
   • [claimed-docs] “Functions are serverless deployments of your browser automations that can b”
   • [claimed-docs] “Extract structured data with AI. Turn any website into structured data.”

   proof ↗⚑ flag

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

   weight 3 · round to Notte
   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

   Notte~partialclaimed3/10

   Notte supports scheduling serverless 'functions' (deploy scripts as API endpoints and 'schedule anywhere'), which gives some automation-trigger capability, but there is no evidence of a rules engine, webhooks, or event-based triggers (e.g., 'on page change, do X') as opposed to simple time-based scheduling/API invocation. Missing for 10: explicit event-trigger/webhook support, conditional rule definitions, and any UI/API for defining 'if event then action' automations.

   • [claimed-docs] “Deploy your scripts as API endpoints. Serverless automations you can invoke and schedule anywhere.”
   • [claimed-docs] “Functions are serverless deployments of your browser automations that can b”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Notte
   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

   Notte~partialclaimed5/10

   Notte's 'Functions' feature explicitly advertises serverless automations that can be 'invoked and scheduled anywhere' (notte-docs-2, notte-docs-26), directly supporting recurring job scheduling, and workflows can be deployed as API endpoints for automation pipelines. However, there is no documentation of a scheduling UI, cron syntax, or interval/trigger configuration, and no independent confirmation that scheduled jobs work reliably in practice. Missing for 10: concrete scheduling mechanism/API docs (cron expressions, triggers), example of a recurring job configured end-to-end, and independent verification that scheduled runs execute reliably.

   • [claimed-docs] “Deploy your scripts as API endpoints. Serverless automations you can invoke and schedule anywhere.”
   • [claimed-docs] “Functions are serverless deployments of your browser automations that can b”
   • [claimed-docs] “Build, debug, and deploy production workflows with cloud browsers, web agents, scraping, serverless functions, credentials, and identities i…”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   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

   Notte—none0/10

   No evidence of versioning, review workflows, diffs, or rollback capability for automations/workflows/functions; docs mention deploying, generating and editing scripts but nothing about version history or reverting changes.

   ⚑ flag

Local

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

   weight 2 · round drawn
   Hyperbrowser—none0/10

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

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

   proof ↗⚑ flag

   Notte—none0/10

   All evidence describes Notte as a cloud-hosted service — sessions are explicitly 'isolated browser instances running in the cloud,' access requires a Bearer API token, and pricing/credits are core to usage — with no documented option to run the agent against a local browser without a cloud account.

   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically.”
   • [claimed-docs] “All API requests require a Bearer token in the `Authorization` header.”
   • [claimed-docs] “Try the full platform without a card.”
   • [claimed-docs] “Remote browser infrastructure. Fast, scalable browsers with anti-detection, proxies, and captcha solving.”

   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 to Notte
   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

   Notte~partialprobed7/10

   Notte documents explicit integration guides for CrewAI (notte-docs-32), Vercel AI SDK (notte-docs-33), OpenAI CUA (notte-docs-34), and Claude-based agents via CLI/MCP (notte-docs-9, notte-docs-31), all pointing at its MCP server or CLI as the browser layer plug-in point. However, there is no documented LangChain adapter and no mention of 'Claude Agent SDK' specifically (only Claude Code/managed agents), so the story's exact framework list is only partially covered. Missing for 10: a LangChain-specific integration doc, explicit Claude Agent SDK adapter naming, and independent confirmation these adapters work hands-on.

   • [claimed-docs] “pointing it at the Notte MCP server hands your crew a real browser.”
   • [claimed-docs] “Point its MCP client at the Notte MCP server and your TypeScript agent gets a browser.”
   • [claimed-docs] “This guide explains how to integrate OpenAI's Computer Use Agent (CUA) with Notte's browser infrastructure for automated web interactions.”
   • [claimed-docs] “The Notte CLI lets AI agents control browsers through simple shell commands.”
   • [claimed-docs] “give them the notte CLI and they can drive real browsers”
   • [claimed-docs] “Give your AI agents access to the entire Notte ecosystem. Notte MCP lets it start cloud browser sessions, interact with the pages, fetch dat…”
   • [probe] “official MCP server documented at https://docs.notte.cc/mcp-server”

   proof ↗⚑ flag

Models

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

   weight 2 · round to Hyperbrowser
   Hyperbrowser✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Notte~partialclaimed5/10

   The pricing page lists 'Bring your own keys' as a feature (Yes for higher tiers), indicating some BYO-LLM-key support, and OpenAI CUA integration doc shows a specific model provider integration, but there is no documentation of broad model-agnostic architecture, no list of supported providers, and no explicit statement that any LLM can be swapped in across the framework. missing for 10: explicit multi-provider support documentation, list of supported LLM vendors, guidance on configuring custom/local models, independent confirmation of model-agnosticism.

   • [claimed-docs] “Bring your own keys No No Yes Yes”
   • [claimed-docs] “This guide explains how to integrate OpenAI's Computer Use Agent (CUA) with Notte's browser infrastructure for automated web interactions.”

   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 drawn
   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

   Notte~partialprobed6/10

   Notte offers a hosted HTTP API (Bearer-token auth, agent-start endpoint, cloud sessions, serverless 'functions' you can invoke and schedule) that let an agent submit a task without managing a browser itself, and sessions expose CDP/live-view for status. However there is no direct documentation of a polling endpoint or webhook callback mechanism for retrieving results, and no OpenAPI/swagger spec was found (404s), so completion-notification patterns are unclear. Missing for 10: explicit polling/webhook result-retrieval documentation, published OpenAPI schema, independent confirmation of end-to-end async task completion.

   • [claimed-docs] “All API requests require a Bearer token in the `Authorization` header.”
   • [claimed-docs] “used to create cloud browser sessions, scrape webpages, and run web ai agents to act on your behalf on the internet”
   • [claimed-docs] “Functions are serverless deployments of your browser automations that can b”
   • [claimed-docs] “Deploy your scripts as API endpoints. Serverless automations you can invoke and schedule anywhere.”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.notte.cc/openapi.json, https://docs.notte.cc/swagger.json, https://docs.notte.cc/api/op…”

   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
   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

   Notte!disputedcontradicted5/10

   Notte's docs and README explicitly market natural-language, multi-step web task execution (e.g. 'Give AI agents natural language tasks to complete on websites', 'Describe a task. Watch it happen. One prompt', and a worked example of logging into LinkedIn and extracting messages), backed by session/vault/proxy infrastructure. However, a hands-on community report describes a real attempt to use the agent to extract data from hyatt.com that 'completely failed,' directly contradicting the end-to-end reliability claim, and the founder himself admits captcha/anti-bot handling only works for ~60% of providers. Missing for 10: independent successful third-party demonstrations of complex multi-step flows, and resolution of the reported failure case.

   • [github] “Give AI agents natural language tasks to complete on websites”
   • [claimed-docs] “Describe a task. Watch it happen. One prompt. No selectors, no maintenance.”
   • [claimed-docs] “Got to linkedin.com, login with the credentials and extract the last 10 messages from my most recent conversation”
   • [claimed-docs] “used to create cloud browser sessions, scrape webpages, and run web ai agents to act on your behalf on the internet”
   • [community] “just tried to use it to extract data from hyatt.com completely failed. another hype but actually doesn't work browser agent.”
   • [community] “Founder: 'we can solve ~60% of providers right now (incl reCAPTCHA, Cloudflare, and main ones) and some others are still work in progress' r…”

   proof ↗⚑ flag

Workflows

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

   weight 2 · round to Notte
   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

   Notte~partialclaimed5/10

   Notte supports scripting deterministic automations and deploying them as serverless 'Functions'/API endpoints, and lets users generate workflow code via CLI then edit it, going beyond a single one-shot prompt (notte-docs-26, notte-docs-2, notte-docs-30, notte-gh-2). However there is no explicit documentation of workflow-level constructs like loops, conditionals, or parameterized templates. missing for 10: explicit docs on loop/conditional syntax in workflows, parameter binding across runs, independent confirmation of repeatable multi-step workflow composition.

   • [claimed-docs] “Functions are serverless deployments of your browser automations that can b”
   • [claimed-docs] “Deploy your scripts as API endpoints. Serverless automations you can invoke and schedule anywhere.”
   • [claimed-docs] “Generate it with the CLI first, then edit it.”
   • [github] “combines AI agents with traditional scripting for maximum efficiency - letting you script deterministic parts and use AI only when needed, c…”
   • [claimed-docs] “Start from ready-made browser automation templates for common workflo”

   proof ↗⚑ flag

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

   weight 2 · round to Hyperbrowser
   Hyperbrowser✓fullprobed7/10

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

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

   proof ↗⚑ flag

   Notte~partialprobed7/10

   Notte is built API/CLI/MCP-first: sessions, scraping, agents, functions, vaults, and even live session viewing are all exposed via API/CLI/MCP endpoints (notte-docs-2, -9, -17, -24, -37, -7/-29), suggesting broad UI/API parity for an API-native product. However there's no explicit vendor statement guaranteeing full feature parity, and a probe found no discoverable OpenAPI/swagger spec (404s across common paths), which weakens confidence that every UI capability (e.g. templates, dashboard-only settings) is fully API-exposed. Missing for 10: explicit parity documentation, a public OpenAPI spec, and independent confirmation that all UI-only features (templates, dashboard views) have API equivalents.

   • [claimed-docs] “Deploy your scripts as API endpoints. Serverless automations you can invoke and schedule anywhere.”
   • [claimed-docs] “The Notte CLI lets AI agents control browsers through simple shell commands.”
   • [claimed-docs] “All API requests require a Bearer token in the `Authorization` header.”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically.”
   • [claimed-docs] “used to create cloud browser sessions, scrape webpages, and run web ai agents to act on your behalf on the internet”
   • [claimed-docs] “Give your AI agents access to the entire Notte ecosystem. Notte MCP lets it start cloud browser sessions, interact with the pages, fetch dat…”
   • [claimed-docs] “Notte MCP lets it start cloud browser sessions, interact with the pages, fetch data, build scripts, and more.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.notte.cc/openapi.json, https://docs.notte.cc/swagger.json, https://docs.notte.cc/api/op…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Hyperbrowser—none0/10

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

   ⚑ flag

   Notte—none0/10

   No evidence of data export/portability features, open-format export of user data, or account deletion/data takeout mechanisms; the docs focus on browser automation, scraping outputs, and credential storage but nothing about exporting one's own account data in open formats. missing for 10: data export feature docs, open-format (e.g. JSON/CSV) account export, data portability/account deletion process, any independent confirmation of exportability.

   ⚑ flag

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

   weight 2 · round to Notte
   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

   Notte~partialcommunity3/10

   A public GitHub repository (nottelabs/notte) exists and is referenced in evidence, indicating the source code is at least publicly readable, but no evidence pack item specifies a license type (e.g., MIT/Apache) or confirms open-source licensing terms. A community comment even questions whether Notte is open source at all, suggesting ambiguity rather than confirmed openness. Missing for 10: explicit license file/badge evidence, confirmation of license terms, independent verification that the full product (not just parts) is open-licensed.

   • [github] “Give AI agents natural language tasks to complete on websites”
   • [github] “combines AI agents with traditional scripting for maximum efficiency - letting you script deterministic parts and use AI only when needed, c…”
   • [community] “Interesting but are there any open source products which can do the same too? This does feel something that I can trust more if it was open …”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Hyperbrowser—none0/10

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

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

   proof ↗⚑ flag

   Notte—none0/10

   All evidence describes Notte as a cloud/SaaS platform (remote browsers, cloud sessions, serverless functions, hosted API with Bearer auth) with no documented self-hosting or on-prem deployment path; a community comment even asks whether an open-source alternative exists, implying Notte itself isn't self-hostable.

   • [claimed-docs] “Remote browser infrastructure. Fast, scalable browsers with anti-detection, proxies, and captcha solving.”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically.”
   • [claimed-docs] “All API requests require a Bearer token in the `Authorization` header.”
   • [community] “Interesting but are there any open source products which can do the same too? This does feel something that I can trust more if it was open …”

   proof ↗⚑ flag

Pricing

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

   weight 2 · round to Hyperbrowser
   Hyperbrowser!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

   Notte!disputedcontradicted3/10

   Notte does have a public pricing page and free-trial claim (notte-docs-22, notte-docs-23), but there is no documentation of concrete per-task/per-browser-hour rates or rate/concurrency limits, and community feedback directly contradicts the transparency claim: users on HN explicitly ask what a 'credit' actually buys and report the pricing page doesn't explain it, calling the credit-based scheme 'broken' and unpredictable (notte-comm-2, notte-comm-3, notte-comm-4). missing for 10: explicit per-task/per-hour rate tables, documented concurrency/rate limits, and resolution of the community complaints about opaque credit meaning.

   • [claimed-docs] “Try the full platform without a card.”
   • [claimed-docs] “Bring your own keys No No Yes Yes”
   • [community] “The pricing page mentions how many credits you get but not what a credit does or gets you. Could you elaborate on that?”
   • [community] “Credit based pricing is broken. No way u produce shiy then user get out of credit to get nothing done.”
   • [community] “You missed the point. What i mean, is your pricing scheme is a scam because u never know if your bot response would solve customer issue. St…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Hyperbrowser—none0/10

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

   ⚑ flag

   Notte—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location choices for Notte's cloud infrastructure; only general security/credential features are documented.

   ⚑ flag

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

   weight 3 · round drawn
   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

   Notte—none0/10

   No evidence in the pack addresses opting out of AI training data usage, data retention policies for model training, or any privacy commitment regarding customer data not being used to train models. Notte's docs cover security of credentials, sessions, stealth mode, and infrastructure, but nothing about AI-training data usage policy.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   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

   Notte—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or user-facing options to purge stored data/sessions/credentials; docs mention credential encryption and cookie persistence but nothing about retention windows or deletion mechanisms.

   ⚑ flag

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

   weight 2 · round drawn
   Hyperbrowser—none0/10

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

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

   proof ↗⚑ flag

   Notte—none0/10

   No evidence pack item mentions telemetry, analytics opt-out, or usage-tracking controls for Notte; missing for 10: any privacy policy or docs section on telemetry collection, opt-out mechanism/flag, or data retention settings.

   ⚑ flag

Live

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

   weight 2 · round to Notte
   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

   Notte~partialclaimed5/10

   Notte clearly supports live session viewing via ViewerUrl and a 'Live View & Replays' screenshare feature, and sessions expose a CDP endpoint connectable via Playwright which could in principle allow manual intervention. However, there is no explicit documentation of a human-takeover/pause-and-control workflow mid-run when an agent gets stuck. Missing for 10: explicit human-in-the-loop takeover mechanism, documentation of pausing agent execution to hand control to a human, and independent confirmation this works in practice.

   • [claimed-docs] “Viewing sessions: When you start a session, the output includes a `ViewerUrl` - open it to watch your browser live”
   • [claimed-docs] “Live View & Replays Screenshare & session playback”
   • [claimed-docs] “Notte sessions expose a Chrome DevTools Protocol (CDP) endpoint that you can connect to with Playwright.”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically.”

   proof ↗⚑ flag

Replay

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

   weight 2 · round drawn
   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

   Notte~partialclaimed5/10

   Notte docs confirm 'Live View & Replays' with screenshare and session playback, plus a live ViewerUrl to watch sessions and CDP/Playwright hooks for programmatic inspection, giving some replay-debugging capability. However, there is no explicit documentation of step-by-step action timelines or a dedicated debugging UI for failed runs, and no independent/hands-on confirmation this replay feature works reliably. missing for 10: documented step-by-step action timeline/debugging tool, independent verification of replay/video debugging in practice.

   • [claimed-docs] “Live View & Replays Screenshare & session playback”
   • [claimed-docs] “Viewing sessions: When you start a session, the output includes a `ViewerUrl` - open it to watch your browser live”
   • [claimed-docs] “Notte sessions expose a Chrome DevTools Protocol (CDP) endpoint that you can connect to with Playwright.”
   • [claimed-docs] “Build, debug, and deploy production workflows with cloud browsers, web agents, scraping, serverless functions, credentials, and identities i…”

   proof ↗⚑ flag

Fleets

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

   weight 2 · round to Hyperbrowser
   Hyperbrowser~partialcommunity6/10

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

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

   proof ↗⚑ flag

   Notte~partialcommunity4/10

   Notte documents cloud-based, isolated, programmatically controllable sessions (notte-docs-24), API/CLI/SDK control (notte-docs-17, notte-docs-37, notte-probe-4), and serverless scaling claims (notte-docs-1, notte-docs-26), supporting the 'programmatic session management' half of the story. However, no evidence anywhere specifies actual concurrency limits, quotas, or fleet-scale numbers for running many sessions in parallel — pricing/credit pages are mentioned only vaguely by community members (notte-comm-2) without concurrency specifics. missing for 10: documented concurrency/rate limits per plan, explicit multi-session fleet management API/dashboard evidence, independent benchmarks of parallel session throughput.

   • [claimed-docs] “Remote browser infrastructure. Fast, scalable browsers with anti-detection, proxies, and captcha solving.”
   • [claimed-docs] “Sessions are isolated browser instances running in the cloud that you can control programmatically.”
   • [claimed-docs] “All API requests require a Bearer token in the `Authorization` header.”
   • [claimed-docs] “Functions are serverless deployments of your browser automations that can b”
   • [claimed-docs] “used to create cloud browser sessions, scrape webpages, and run web ai agents to act on your behalf on the internet”
   • [community] “The pricing page mentions how many credits you get but not what a credit does or gets you. Could you elaborate on that?”

   proof ↗⚑ flag

Lifecycle

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

   weight 1 · round drawn
   Hyperbrowser—none0/10

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

   ⚑ flag

   Notte—none0/10

   No evidence pack item mentions webhooks, callback URLs, or event-driven notifications for task/session completion; the docs describe sessions, viewer URLs, CDP endpoints and API auth but nothing about push notifications, forcing polling-based status checks instead.

   ⚑ 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 Hyperbrowser
   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

   Notte!disputedcontradicted4/10

   Notte's docs advertise 'captcha solving' as a built-in feature of its browser infrastructure (notte-docs-1), suggesting automatic handling, but there is no documented policy for what happens when solving fails (no human fallback or explicit non-support statement). Concrete contradicting evidence comes from the founder himself in community discussion, admitting captcha solving only works for ~60% of providers and some are 'still work in progress' (notte-comm-7), directly undercutting the blanket 'captcha solving' claim and leaving automation engineers without clarity on failure behavior. missing for 10: documented success-rate/coverage table, explicit fallback or escalation behavior on captcha failure, and independent verification of solve rates beyond the founder's informal comment.

   • [claimed-docs] “Remote browser infrastructure. Fast, scalable browsers with anti-detection, proxies, and captcha solving.”
   • [community] “Founder: 'we can solve ~60% of providers right now (incl reCAPTCHA, Cloudflare, and main ones) and some others are still work in progress' r…”

   proof ↗⚑ flag

Posture

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

   weight 1 · round to Hyperbrowser
   Hyperbrowser!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

   Notte—none0/10

   No evidence pack item shows Notte publishing an acceptable-use policy, terms governing stealth/captcha-bypass usage, or an anti-abuse stance; docs only describe stealth/proxy/captcha features themselves. A community comment even accuses Notte of 'disrespecting robots.txt' and enabling spam, but this is criticism, not a vendor-published policy to compare against.

   • [claimed-docs] “All Notte sessions automatically include: **Clean browser fingerprints** - Realistic browser signatures”
   • [claimed-docs] “Combine stealth mode with residential proxies for maximum anonymity”
   • [claimed-docs] “Notte sessions include built-in stealth features to help your automations avoid detection by anti-bot systems.”
   • [community] “Avoiding captchas and disrespecting robots.txt. How does it feel to advertise your spam service? Are you proud?”

   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 Notte
   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

   Notte✓fullclaimed7/10

   Notte's docs explicitly describe stealth mode with clean/realistic browser fingerprints, built-in anti-bot detection avoidance, and residential proxies with a global network including fixed IPs and BYO options, directly matching the story's ask for fingerprinting and geo/residential proxy control. missing for 10: independent hands-on verification that stealth+proxy combo actually evades sophisticated bot detection in practice, and finer detail on geo-targeting granularity beyond 'global network'.

   • [claimed-docs] “All Notte sessions automatically include: **Clean browser fingerprints** - Realistic browser signatures”
   • [claimed-docs] “Combine stealth mode with residential proxies for maximum anonymity”
   • [claimed-docs] “Residential Proxies Global network, fixed IPs & BYO”
   • [claimed-docs] “Notte sessions include built-in stealth features to help your automations avoid detection by anti-bot systems.”
   • [claimed-docs] “Remote browser infrastructure. Fast, scalable browsers with anti-detection, proxies, and captcha solving.”

   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
   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

   Notte!disputedcontradicted5/10

   Docs show Pydantic-style schema extraction (BaseModel classes) and structured/markdown output via 'fetch' and scraping concepts (notte-docs-15, notte-docs-3, notte-docs-25), which directly matches the story. However, a hands-on community report states extraction 'completely failed' on a real site (hyatt.com), directly contradicting the reliability of the extraction pipeline in practice. Missing for 10: Zod/TypeScript schema examples (only Python/Pydantic shown), independent corroboration of successful schema-validated extraction, and resolution of the reported failure case.

   • [claimed-docs] “Extract structured data from a page: ... class HackerNewsFeed(BaseModel):”
   • [claimed-docs] “Extract structured data with AI. Turn any website into structured data.”
   • [claimed-docs] “Fetch extracts web page content as markdown or structured data using LLM-powered extraction.”
   • [community] “just tried to use it to extract data from hyatt.com completely failed. another hype but actually doesn't work browser agent.”

   proof ↗⚑ flag

Files

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

   weight 1 · round drawn
   Hyperbrowser—none0/10

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

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

   proof ↗⚑ flag

   Notte—none0/10

   The evidence pack covers browser sessions, scraping/extraction, credentials, and CDP/Playwright access, but no documentation mentions file upload/download handling or artifact retrieval from agent-operated sites. This is a plausible capability for a browser-automation platform, so absence of evidence yields 'none' rather than 'na'.

   ⚑ flag