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

   No evidence of caching resolved actions or generated code for deterministic, lower-cost replay; the product is LLM-driven agent automation with sessions/runs but nothing about caching or replay without re-invoking the model. missing for 10: any mention of action/code caching, deterministic replay mechanism, or cost/latency savings from skipping re-prompting.

   ⚑ 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
   Browser Use~partialcommunity6/10

   Browser Use's core agent is built around natural-language task instructions (e.g. "Find the top Hacker News story", "Fill in this job application") executed via an LLM-driven agent that perceives the DOM/page state and decides actions, which is the essence of DOM-understanding, layout-resilient automation — this is corroborated by GitHub task examples and community hands-on use (LinkedIn automation, resume filling). However, the evidence pack lacks explicit documentation of discrete act/click/type primitives with described-element targeting or any stated guarantee/mechanism for surviving selector/layout changes; it's inferred from the agent's general design rather than directly documented. missing for 10: explicit API/primitive-level documentation of click/type/act-on-described-element functions, and direct evidence/testing showing resilience to selector or layout changes rather than just general LLM-driven task completion.

   • [github] “Task: "Fill in this job application with my resume and information."”
   • [github] “Task: "Extract structured data about my followers and export it as a CSV."”
   • [community] “If you run it locally, you can connect it to your real browser and user profile where you are already logged in. This works for me for Linke…”
   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”

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

   Evidence shows live-preview URLs for human intervention during CAPTCHA/2FA and event polling for observability, but nothing about an explicit preview/plan step where candidate actions are surfaced for developer review before the agent commits to acting.

   • [claimed-docs] “If the challenge remains, open the [live preview](/cloud/browser/live-preview) for human control.”
   • [claimed-docs] “Ask the first run to stop at the 2FA screen, get its `live_view_url` from the [`browser.ready` event], and have the user enter the code. The…”
   • [claimed-docs] “Poll ordered V4 events to monitor a run or build a custom UI.”
   • [claimed-docs] “Ask the first run to stop at the 2FA screen, get its `live_view_url` from the [`browser.ready` event]”

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

   Browser Use's docs describe DOM-based agent actions, live preview/human handoff for CAPTCHA/2FA, and CDP-based control, but there is no evidence of a dedicated vision or computer-use mode that acts directly on screenshots for canvas/UI elements the DOM can't reach.

   ⚑ 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
   Browser Use✓fullprobed8/10

   Browser Use publishes a discoverable llms.txt at docs.browser-use.com/llms.txt confirmed live via probe (HTTP 200), which is exactly the agent-oriented docs entry point an AI-native user could point an agent at, and the broader docs site is structured/markdown-friendly for agent consumption. Missing for 10: no evidence of additional structured formats like llms-full.txt or explicit guidance encouraging agents to consume it, and no independent community confirmation of agents successfully using it.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.browser-use.com/llms.txt # Browser Use > Documentation for Browser Use Cloud Agent and Browser API…”

   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 to Notte
   Browser Use~partialclaimed6/10

   Browser Use ships both an open-source Python library and a cloud API (client.runs.create) that are inherently script/automatable, implying headless/CI use, and gh-3 explicitly pitches automating the web 'from your own code, and with any LLM.' However, there is no explicit documentation of headless mode flags, Docker images, or CI pipeline examples/integration guides. Missing for 10: explicit headless-mode configuration docs, CI/CD pipeline examples (e.g., GitHub Actions), and independent confirmation of running unattended in CI.

   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”
   • [github] “Want to automate the web at scale, from your own code, and with any LLM? Use the Python library”
   • [claimed-docs] “For a local agent, use the [open-source library](/open-source/quickstart).”
   • [claimed-docs] “Launch a browser, connect to its CDP URL, then stop it”

   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 userConnect an agent via an official MCP server

   weight 3 · round to Notte
   Browser Use!disputedcontradicted5/10

   Docs describe an official MCP server enabling Claude, Cursor, Windsurf or any MCP client to run Browser Use tasks (browser-use-docs-12, browser-use-probe-3), but a hands-on community report says the author had to switch tools because Browser Use 'doesn't support MCP integration' in Cursor (browser-use-comm-4), directly contradicting the documented claim. Missing for 10: independent corroboration that MCP connection actually works end-to-end, and resolution of the conflicting user report.

   • [claimed-docs] “Run browser automation tasks from your AI coding assistant. Connect to Claude, Cursor, Windsurf, or any MCP client.”
   • [probe] “official MCP server documented at https://docs.browser-use.com/cloud/guides/mcp-server”
   • [community] “I want to use browser-use in Cursor but I am using another option because it doesn't support MCP integration which is the common language th…”

   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

4. ai-native userUse an official CLI

   weight 2 · round to Notte
   Browser Use—none0/10

   The evidence pack documents a Python SDK, cloud API, MCP server, and web dashboard, but never mentions an official standalone CLI tool for Browser Use. Since a browser-automation product could plausibly ship a CLI, absence of any such evidence means this axis is unmet.

   ⚑ 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

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

   weight 3 · round to Notte
   Browser Use~partialprobed7/10

   Browser Use documents a public Cloud API (client.runs.create, sessions, events polling, structured output, CDP connection) across multiple docs pages, indicating a real programmatic interface beyond the UI. However, probes for a formal OpenAPI/swagger spec returned 404s, so there's no machine-readable API contract, only prose docs and SDK examples. Missing for 10: a published OpenAPI/spec artifact, independent third-party confirmation of API usage beyond vendor docs.

   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”
   • [claimed-docs] “A **session** holds the agent’s conversation and can reuse its live browser. One session ID can contain multiple runs.”
   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”
   • [claimed-docs] “Poll ordered V4 events to monitor a run or build a custom UI.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.browser-use.com/openapi.json, https://docs.browser-use.com/swagger.json, https://docs.b…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.browser-use.com/llms.txt # Browser Use > Documentation for Browser Use Cloud Agent and Browser API…”

   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

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

   weight 2 · round drawn
   Browser Use—none0/10

   No evidence of scoped or least-privilege API key/credential issuance (e.g., role-based tokens, permission scopes) for agents; docs mention API keys implicitly via client usage but no mention of scoping, restricted permissions, or credential management features. Community/GitHub evidence also silent on this.

   ⚑ 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

7. ai-native userBuild against official SDKs

   weight 2 · round to Browser Use
   Browser Use✓fullprobed7/10

   Browser Use ships an official open-source Python library (github, docs-19) and a cloud client SDK with documented usage patterns (client.runs.create, sessions, events polling) shown in docs-1/4/5/14, giving AI-native devs a concrete first-party SDK to build against. Missing for 10: evidence of SDKs beyond Python (e.g. JS/TS), and no OpenAPI spec was found (probe-2 all 404) or independent third-party corroboration of SDK usage.

   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”
   • [claimed-docs] “A **session** holds the agent’s conversation and can reuse its live browser. One session ID can contain multiple runs.”
   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”
   • [claimed-docs] “For a local agent, use the [open-source library](/open-source/quickstart).”
   • [github] “Want to automate the web at scale, from your own code, and with any LLM? Use the Python library”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.browser-use.com/openapi.json, https://docs.browser-use.com/swagger.json, https://docs.b…”

   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

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Browser Use—none0/10

   The docs describe an event system based on polling `runs.events()` with a cursor, not webhook subscriptions; no evidence anywhere in the pack mentions webhooks, callback URLs, or push notifications.

   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”
   • [claimed-docs] “Poll ordered V4 events to monitor a run or build a custom UI.”

   proof ↗⚑ 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 userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Browser Use
   Browser Use~partialclaimed4/10

   Browser Use's agent can extract and return structured data/results from web tasks (e.g., extracting follower data to CSV, structured JSON output), which counts as AI-generated output from data it gathers, but there is no evidence of proactive 'insights and suggestions' generated from a user's own stored data inside a product dashboard — it's task-driven extraction, not analytics-style suggestion generation. missing for 10: dedicated insights/suggestions surface, evidence of proactive recommendations, analysis of user's own historical data corpus rather than ad-hoc scraped web data.

   • [github] “Task: "Extract structured data about my followers and export it as a CSV."”
   • [claimed-docs] “V4 returns `run.result` as a string. Ask for JSON only, then validate it client-side”
   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”

   proof ↗⚑ flag

   Notte—none0/10

   Notte's evidence covers AI-driven data extraction, browser agents, and automation infrastructure, but nothing shows the product itself analyzing a user's own data to proactively surface insights or suggestions inside a dashboard/UI — extraction is task-driven ('extract the last 10 messages'), not autonomous insight generation. Missing for 10: any documented insights/analytics dashboard, proactive suggestion feature, or evidence of the product surfacing patterns/recommendations from a user's stored data.

   • [claimed-docs] “Extract structured data with AI. Turn any website into structured data.”
   • [claimed-docs] “Extract structured data from a page: ... class HackerNewsFeed(BaseModel):”
   • [claimed-docs] “Fetch extracts web page content as markdown or structured data using LLM-powered extraction.”
   • [claimed-docs] “Got to linkedin.com, login with the credentials and extract the last 10 messages from my most recent conversation”

   proof ↗⚑ flag

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

   weight 2 · round to Notte
   Browser Use~partialclaimed5/10

   Browser Use Cloud lets users kick off agent runs via API (client.runs.create) that execute asynchronously in a hosted browser, with session reuse and event polling to monitor progress without keeping a local process open, which supports a form of unattended background execution. However there is no documented scheduling, cron-like triggers, or webhook-based automation setup for recurring/background jobs, so it's unclear whether truly hands-off recurring automations are supported. Missing for 10: explicit scheduling/trigger mechanism, evidence of long-running unattended jobs beyond single API-invoked runs, and independent confirmation of background reliability.

   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”
   • [claimed-docs] “A **session** holds the agent’s conversation and can reuse its live browser. One session ID can contain multiple runs.”
   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”
   • [claimed-docs] “Poll ordered V4 events to monitor a run or build a custom UI.”

   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

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

   weight 2 · round to Browser Use
   Browser Use✓fullcommunity8/10

   Browser Use is fundamentally natural-language driven: tasks are issued as plain-English strings like "Find the top Hacker News story" or "Fill in this job application with my resume and information", with the agent interpreting and executing them autonomously, corroborated by GitHub examples and community hands-on use for LinkedIn automation. missing for 10: independent benchmark of instruction-following accuracy, and clearer docs on limits/failure modes of natural-language parsing.

   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”
   • [github] “Task: "Fill in this job application with my resume and information."”
   • [github] “Task: "Extract structured data about my followers and export it as a CSV."”
   • [community] “If you run it locally, you can connect it to your real browser and user profile where you are already logged in. This works for me for Linke…”

   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 drawn
   Browser Use—none0/10

   Docs show static code snippets (e.g., client.runs.create examples) but no evidence of an interactive, runnable API console/reference; explicit probes for OpenAPI/Swagger specs at standard paths all returned 404, indicating no interactive API explorer exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.browser-use.com/openapi.json, https://docs.browser-use.com/swagger.json, https://docs.b…”
   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.browser-use.com/llms.txt # Browser Use > Documentation for Browser Use Cloud Agent and Browser API…”

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

   A direct probe for OpenAPI/swagger spec files returned 404 on all candidate paths, and no documentation references a downloadable machine-readable API spec despite having a REST/cloud API.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.browser-use.com/openapi.json, https://docs.browser-use.com/swagger.json, https://docs.b…”

   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 Notte
   Browser Use—none0/10

   The evidence describes cloud browser sessions, live preview, and CDP connections, but nothing indicates a dedicated sandbox/staging mode that isolates test runs from production data or real accounts. Users are shown reusing real logged-in profiles (browser-use-comm-5) rather than isolated test environments, and no docs mention a sandbox distinct from production.

   • [claimed-docs] “A **session** holds the agent’s conversation and can reuse its live browser. One session ID can contain multiple runs.”
   • [claimed-docs] “Log in once, save the profile, then reuse it to start future browsers already logged in.”
   • [community] “If you run it locally, you can connect it to your real browser and user profile where you are already logged in. This works for me for Linke…”

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

   Evidence shows an API version label ("V4") in docs, but there is no documented deprecation policy, versioning changelog, or API stability guarantees anywhere in the pack; the OpenAPI spec probe also 404s, indicating no formal API contract is published.

   • [claimed-docs] “V4 returns `run.result` as a string. Ask for JSON only, then validate it client-side”
   • [claimed-docs] “Automatic CAPTCHA solving is enabled by default for API V4 Agent runs and standalone Cloud Browser sessions.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.browser-use.com/openapi.json, https://docs.browser-use.com/swagger.json, https://docs.b…”

   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 drawn
   Browser Use✓fullcommunity7/10

   Docs explicitly describe connecting existing Playwright/Puppeteer/CDP code to Browser Use's browsers via CDP URL, with a documented choice between Browser Use driving or the developer's own code connecting directly over CDP (docs-2, docs-18), and community reports confirm connecting to a real local Chrome profile via CDP for existing automation. missing for 10: independent hands-on validation specifically with Playwright/Puppeteer libraries (not just CDP raw), and more detail on session/auth persistence when using external code.

   • [claimed-docs] “Launch a browser, connect to its CDP URL, then stop it”
   • [claimed-docs] “Choose whether Browser Use drives the browser or your Playwright/Puppeteer code connects directly over CDP.”
   • [claimed-docs] “A **session** holds the agent’s conversation and can reuse its live browser. One session ID can contain multiple runs.”
   • [community] “If you run it locally, you can connect it to your real browser and user profile where you are already logged in. This works for me for Linke…”

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

   Browser Use supports saved/reused login profiles (docs-10) and a documented 2FA workflow where the run pauses at the challenge and a human enters the code via live view (docs-11/16), but there is no vault/secrets-manager integration for storing credentials and injecting them without model exposure, and TOTP is handled via human-in-the-loop rather than automated secret injection. missing for 10: a credential vault/secrets-manager integration, evidence that passwords/TOTP secrets are injected without ever passing through the model context, fully automated TOTP handling without human intervention, independent confirmation of the 2FA flow working in practice.

   • [claimed-docs] “Log in once, save the profile, then reuse it to start future browsers already logged in.”
   • [claimed-docs] “Ask the first run to stop at the 2FA screen, get its `live_view_url` from the [`browser.ready` event], and have the user enter the code. The…”
   • [claimed-docs] “Ask the first run to stop at the 2FA screen, get its `live_view_url` from the [`browser.ready` event]”

   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 to Browser Use
   Browser Use✓fullcommunity8/10

   Docs explicitly describe saving a login profile once and reusing it to start future browsers already logged in, plus a 2FA guide for handling the initial login flow, and community evidence confirms local profile reuse works for logged-in automation (e.g., LinkedIn). missing for 10: independent/hands-on corroboration specifically of the cloud profile-reuse feature (only local profile reuse is community-validated) and no detail on profile storage/security guarantees.

   • [claimed-docs] “Log in once, save the profile, then reuse it to start future browsers already logged in.”
   • [claimed-docs] “Ask the first run to stop at the 2FA screen, get its `live_view_url` from the [`browser.ready` event], and have the user enter the code. The…”
   • [claimed-docs] “Ask the first run to stop at the 2FA screen, get its `live_view_url` from the [`browser.ready` event]”
   • [community] “If you run it locally, you can connect it to your real browser and user profile where you are already logged in. This works for me for Linke…”

   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 Notte
   Browser Use~partialclaimed3/10

   The library is pitched for automating the web 'at scale' from custom code (gh-3) and cloud sessions can hold multiple runs, hinting at multi-task orchestration, but there is no explicit documentation of a batch/bulk API, parallel run submission, or looping over many items as a first-class feature. Missing for 10: dedicated bulk/batch endpoint or SDK pattern, concurrency limits/guidance, and hands-on evidence of running many items in one operation.

   • [github] “Want to automate the web at scale, from your own code, and with any LLM? Use the Python library”
   • [claimed-docs] “A **session** holds the agent’s conversation and can reuse its live browser. One session ID can contain multiple runs.”
   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”

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

   Browser Use's evidence covers on-demand task runs, sessions, observability polling, CAPTCHA/stealth, and MCP integration, but nothing describes user-defined rules or triggers that fire actions automatically on external events (e.g., webhooks, schedules, conditional triggers). The product is presented as an agent you invoke to perform a task, not an event-driven automation/rules engine.

   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”
   • [claimed-docs] “A **session** holds the agent’s conversation and can reuse its live browser. One session ID can contain multiple runs.”
   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”
   • [claimed-docs] “Run browser automation tasks from your AI coding assistant. Connect to Claude, Cursor, Windsurf, or any MCP client.”
   • [github] “Want to automate the web at scale, from your own code, and with any LLM? Use the Python library”

   proof ↗⚑ 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
   Browser Use—none0/10

   The evidence pack covers runs, sessions, observability, stealth/proxy/CAPTCHA handling, auth profiles, and MCP integration, but nowhere mentions cron-like scheduling, recurring triggers, or workflow automation over time. No docs or community evidence describe a scheduler or recurring-job feature.

   ⚑ 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
   Browser Use—none0/10

   Browser Use documents runs, sessions, event polling, and observability, but there is no evidence of versioning automation definitions, reviewing changes, or rolling back to prior versions of a task/automation. Missing for 10: version history/diffing of automations, review/approval workflow, rollback mechanism.

   • [claimed-docs] “A **session** holds the agent’s conversation and can reuse its live browser. One session ID can contain multiple runs.”
   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”
   • [claimed-docs] “Poll ordered V4 events to monitor a run or build a custom UI.”

   proof ↗⚑ 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 to Browser Use
   Browser Use✓fullcommunity8/10

   Browser Use ships an open-source Python library explicitly positioned for local, code-driven automation ('For a local agent, use the open-source library'; 'automate the web at scale, from your own code, and with any LLM'), and community reports confirm running it locally against a real local Chrome browser/profile without a cloud account. missing for 10: no explicit walkthrough showing zero network/account calls during local runs, and no independent benchmark of purely offline/local operation.

   • [claimed-docs] “For a local agent, use the [open-source library](/open-source/quickstart).”
   • [github] “Want to automate the web at scale, from your own code, and with any LLM? Use the Python library”
   • [community] “If you run it locally, you can connect it to your real browser and user profile where you are already logged in. This works for me for Linke…”
   • [claimed-docs] “Launch a browser, connect to its CDP URL, then stop it”

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

   Evidence documents an MCP server for connecting to Claude, Cursor, or Windsurf, and a Python library for custom code, but there is no mention of documented adapters for Claude Agent SDK, Vercel AI SDK, LangChain, or CrewAI specifically.

   • [claimed-docs] “Run browser automation tasks from your AI coding assistant. Connect to Claude, Cursor, Windsurf, or any MCP client.”
   • [probe] “official MCP server documented at https://docs.browser-use.com/cloud/guides/mcp-server”
   • [github] “Want to automate the web at scale, from your own code, and with any LLM? Use the Python library”

   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 Browser Use
   Browser Use✓fullcommunity8/10

   GitHub docs explicitly market the library as usable with any LLM ('Use the Python library ... with any LLM'), and independent community testing corroborates this by reporting successful use with Gemini models rather than being locked to one vendor. Missing for 10: a dedicated docs page enumerating specific supported providers/configuration examples and broader independent confirmation across multiple providers beyond Gemini.

   • [github] “Want to automate the web at scale, from your own code, and with any LLM? Use the Python library”
   • [community] “From the first glance, browser-use is compatible with more models, and has (much) more github stars. Coincidentally I played with it over th…”

   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 to Browser Use
   Browser Use✓fullprobed8/10

   Docs show a hosted Cloud API (client.runs.create) that creates runs, supports polling via runs.events() with cursors, and returns structured results without the caller managing browser infrastructure (stealth, proxies, CAPTCHA solving handled server-side). Missing for 10: no explicit webhook callback mechanism is documented (only polling is shown), and no public OpenAPI spec was found to confirm full REST surface.

   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”
   • [claimed-docs] “V4 returns `run.result` as a string. Ask for JSON only, then validate it client-side”
   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”
   • [claimed-docs] “Poll ordered V4 events to monitor a run or build a custom UI.”
   • [claimed-docs] “Every cloud browser session runs in a hardened Chromium fork with stealth enabled by default — no configuration needed.”
   • [claimed-docs] “Residential proxies are enabled by default across 195+ countries.”
   • [claimed-docs] “Every Browser Use Cloud browser enables automatic CAPTCHA solving.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.browser-use.com/openapi.json, https://docs.browser-use.com/swagger.json, https://docs.b…”

   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 Browser Use
   Browser Use✓fullcommunity8/10

   Docs and GitHub examples show natural-language goals (e.g., "Find the top Hacker News story", "Fill in this job application") driving an agent that navigates, logs in, handles 2FA/CAPTCHA, and completes multi-step flows end-to-end via both cloud API and open-source library; community reports corroborate real-world use (e.g., LinkedIn automation). Missing for 10: independent third-party benchmark of complex multi-step task success rates and more robust evidence of reliability at scale beyond anecdotal community reports.

   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”
   • [github] “Task: "Fill in this job application with my resume and information."”
   • [github] “Task: "Extract structured data about my followers and export it as a CSV."”
   • [claimed-docs] “Log in once, save the profile, then reuse it to start future browsers already logged in.”
   • [claimed-docs] “Ask the first run to stop at the 2FA screen, get its `live_view_url` from the [`browser.ready` event], and have the user enter the code. The…”
   • [claimed-docs] “Every Browser Use Cloud browser enables automatic CAPTCHA solving.”
   • [community] “If you run it locally, you can connect it to your real browser and user profile where you are already logged in. This works for me for Linke…”
   • [github] “Want to automate the web at scale, from your own code, and with any LLM? Use the Python library”

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

   Evidence shows Browser Use runs are essentially single natural-language task strings within a session/run model (create run, poll events, reuse session) with no documented constructs for loops, conditionals, or parameterized workflow templates; the Python library is described as scriptable but no workflow-composition API (branching, iteration, variables) is shown.

   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”
   • [claimed-docs] “A **session** holds the agent’s conversation and can reuse its live browser. One session ID can contain multiple runs.”
   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”
   • [github] “Want to automate the web at scale, from your own code, and with any LLM? Use the Python library”

   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 Notte
   Browser Use~partialprobed6/10

   Docs show the API (client.runs.create, sessions, events polling, structured output, live_view_url for 2FA/CAPTCHA handoff, stealth/proxy defaults) mirrors most cloud UI capabilities, and there's an official MCP server for coding-agent access, suggesting broad but not explicitly confirmed feature parity with the dashboard/UI. However there's no discoverable OpenAPI/formal API spec (404s on all candidate paths) and no explicit vendor statement that 100% of UI functionality is API-reachable; missing for 10: a canonical API reference/OpenAPI spec, and explicit parity documentation confirming every UI action (e.g., live preview manual takeover) is independently scriptable via API rather than requiring the UI.

   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”
   • [claimed-docs] “A **session** holds the agent’s conversation and can reuse its live browser. One session ID can contain multiple runs.”
   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”
   • [claimed-docs] “If the challenge remains, open the [live preview](/cloud/browser/live-preview) for human control.”
   • [claimed-docs] “Ask the first run to stop at the 2FA screen, get its `live_view_url` from the [`browser.ready` event], and have the user enter the code. The…”
   • [claimed-docs] “Run browser automation tasks from your AI coding assistant. Connect to Claude, Cursor, Windsurf, or any MCP client.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.browser-use.com/openapi.json, https://docs.browser-use.com/swagger.json, https://docs.b…”
   • [probe] “official MCP server documented at https://docs.browser-use.com/cloud/guides/mcp-server”

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

   The evidence pack describes agent runs, sessions, CAPTCHA handling, and pricing, but nothing documents an account/data export feature (e.g., downloading all run history, sessions, or stored data in an open format) that would let a user leave the platform with their data intact; the open-source library allows self-hosting but that's a separate capability from exporting existing cloud account data.

   ⚑ 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 Browser Use
   Browser Use~partialprobed5/10

   The GitHub repo (browser-use/browser-use) and docs reference an 'open-source library' with a public quickstart, indicating the core Python library's source is publicly viewable, but no evidence explicitly states an open-source license (e.g., MIT/Apache) or shows license text. missing for 10: explicit license file/declaration, confirmation of license type, evidence of full source (vs. cloud API) being open.

   • [github] “Want to automate the web at scale, from your own code, and with any LLM? Use the Python library”
   • [claimed-docs] “For a local agent, use the [open-source library](/open-source/quickstart).”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.browser-use.com/llms.txt # Browser Use > Documentation for Browser Use Cloud Agent and Browser API…”

   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 to Browser Use
   Browser Use✓fullprobed7/10

   Browser Use ships an open-source Python library (github.com/browser-use/browser-use) that runs locally and independently of the Cloud API, explicitly positioned as the option for self-hosted/local agents ("For a local agent, use the open-source library"), and community reports confirm running it locally connected to a real browser/profile. missing for 10: no first-party self-hosting guide covering infra/deployment (e.g. Docker, scaling), and no independent audit of parity between self-hosted and cloud feature sets (stealth, CAPTCHA solving, proxies are cloud-only per docs).

   • [claimed-docs] “For a local agent, use the [open-source library](/open-source/quickstart).”
   • [github] “Want to automate the web at scale, from your own code, and with any LLM? Use the Python library”
   • [community] “If you run it locally, you can connect it to your real browser and user profile where you are already logged in. This works for me for Linke…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.browser-use.com/llms.txt # Browser Use > Documentation for Browser Use Cloud Agent and Browser API…”

   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 Browser Use
   Browser Use~partialclaimed4/10

   Pricing page shows credits-based model ($5+ credits, no subscription, one-time $15 signup credit) but there is no documented per-task or per-browser-hour cost breakdown, and no documented rate/concurrency limits anywhere in the evidence. missing for 10: explicit per-task/per-browser-hour cost figures, documented rate limits, documented concurrency limits, any independent confirmation of pricing transparency.

   • [claimed-docs] “One-time $15 credit for eligible Google, GitHub or Microsoft signups ... No card required”
   • [claimed-docs] “Credits from $5. No subscription. No expiry.”

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

   No evidence pack material addresses data residency, region selection, or storage location controls for cloud runs/sessions; the open-source library option avoids the cloud entirely but that's not the same as choosable region/residency within the product. missing for 10: any mention of data center regions, residency options, or storage location controls.

   ⚑ 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
   Browser Use—none0/10

   No evidence in the pack addresses data usage for AI model training, opt-out policies, or privacy/data-retention commitments for Browser Use Cloud or the open-source library.

   ⚑ 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
   Browser Use—none0/10

   No evidence of data retention controls, deletion APIs, or privacy/data-lifecycle policy documentation anywhere in the pack; only session/profile reuse and credit pricing are mentioned. missing for 10: retention policy documentation, data deletion API/UI, export/erasure controls, any privacy compliance statement.

   ⚑ 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
   Browser Use—none0/10

   No evidence in the pack mentions telemetry, usage data collection, or any opt-out/privacy setting for Browser Use; the documentation and community items cover unrelated features like stealth browsing, CAPTCHA solving, and MCP integration.

   ⚑ 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 Browser Use
   Browser Use~partialclaimed6/10

   Docs describe a live_view_url/live preview that lets a human take control mid-run for cases like CAPTCHAs or 2FA, and events can be polled to monitor a run, which supports live-watch-and-intervene workflows. However, this is scoped to specific triggers (CAPTCHA/2FA) rather than a general 'agent gets stuck, operator takes over anytime' workflow, and there's no independent/hands-on evidence confirming smooth mid-run handoff in practice. missing for 10: general-purpose stuck-detection/handoff beyond CAPTCHA/2FA scenarios, independent hands-on confirmation of live takeover working reliably, clear UI/replay-debugging tooling details.

   • [claimed-docs] “If the challenge remains, open the [live preview](/cloud/browser/live-preview) for human control.”
   • [claimed-docs] “Ask the first run to stop at the 2FA screen, get its `live_view_url` from the [`browser.ready` event], and have the user enter the code. The…”
   • [claimed-docs] “Ask the first run to stop at the 2FA screen, get its `live_view_url` from the [`browser.ready` event]”
   • [claimed-docs] “Poll ordered V4 events to monitor a run or build a custom UI.”
   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”

   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 to Notte
   Browser Use~partialclaimed4/10

   Docs describe an observability/events stream (runs.events()) for monitoring a run and a live_view_url for real-time human intervention, which could support building a step timeline, but there is no explicit mention of recorded video or screenshot capture for post-hoc replay debugging of failed runs. Missing for 10: documented video recording of sessions, screenshot capture per action, and a dedicated replay/timeline UI for past runs.

   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”
   • [claimed-docs] “Poll ordered V4 events to monitor a run or build a custom UI.”
   • [claimed-docs] “Ask the first run to stop at the 2FA screen, get its `live_view_url` from the [`browser.ready` event], and have the user enter the code. The…”
   • [claimed-docs] “Ask the first run to stop at the 2FA screen, get its `live_view_url` from the [`browser.ready` event]”

   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 drawn
   Browser Use~partialclaimed4/10

   Docs show programmatic session/run creation (client.runs.create, session IDs holding multiple runs) and event polling for observability, implying some ability to manage sessions programmatically, but there is no documented concurrency limit, no fleet/parallel-session guidance, and no scaling architecture described. missing for 10: documented concurrency limits, guidance/examples for running multiple concurrent sessions at scale, rate-limit or quota specs, and independent evidence of parallel session management working in practice.

   • [claimed-docs] “run = client.runs.create("Find the top Hacker News story")”
   • [claimed-docs] “A **session** holds the agent’s conversation and can reuse its live browser. One session ID can contain multiple runs.”
   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”
   • [claimed-docs] “Poll ordered V4 events to monitor a run or build a custom UI.”
   • [github] “Want to automate the web at scale, from your own code, and with any LLM? Use the Python library”

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

   Docs explicitly describe polling patterns for run status (runs.events() with cursor, polling ordered V4 events) but no webhook or callback-based notification mechanism is mentioned anywhere in the evidence pack.

   • [claimed-docs] “Poll `runs.events()` with the previous cursor to receive only new events”
   • [claimed-docs] “Poll ordered V4 events to monitor a run or build a custom UI.”

   proof ↗⚑ 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 Browser Use
   Browser Use✓fullclaimed8/10

   Browser Use documents a clear captcha stance: automatic CAPTCHA solving is enabled by default for cloud Agent runs and standalone Cloud Browser sessions, with an explicit human-fallback path via the live preview if the challenge persists. This directly matches the story's requirement of a documented stance rather than silent failure. Missing for 10: independent/hands-on verification of captcha-solving success rates and explicit behavior/limits for the self-hosted open-source library (docs focus on Cloud).

   • [claimed-docs] “Every Browser Use Cloud browser enables automatic CAPTCHA solving.”
   • [claimed-docs] “If the challenge remains, open the [live preview](/cloud/browser/live-preview) for human control.”
   • [claimed-docs] “Automatic CAPTCHA solving is enabled by default for API V4 Agent runs and standalone Cloud Browser sessions.”

   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 drawn
   Browser Use—none0/10

   The evidence pack documents stealth, proxy, and CAPTCHA-solving features in detail, but there is no published acceptable-use policy, terms of service, or anti-abuse statement governing what these stealth/automation features may or may not be used for; community discussion even raises security/abuse concerns without any vendor policy response cited.

   ⚑ 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 drawn
   Browser Use✓fullclaimed7/10

   Docs explicitly state cloud browsers run in a hardened Chromium fork with stealth enabled by default and residential proxies across 195+ countries, directly matching the story's stealth+proxy ask, with automatic CAPTCHA solving as a complementary layer. Missing for 10: explicit control/documentation for selecting a specific geo-target rather than automatic 195+ country rotation, and independent/hands-on evidence confirming bot-detection evasion actually works in practice.

   • [claimed-docs] “Every cloud browser session runs in a hardened Chromium fork with stealth enabled by default — no configuration needed.”
   • [claimed-docs] “Residential proxies are enabled by default across 195+ countries.”
   • [claimed-docs] “Every Browser Use Cloud browser enables automatic CAPTCHA solving.”
   • [claimed-docs] “Automatic CAPTCHA solving is enabled by default for API V4 Agent runs and standalone Cloud Browser sessions.”

   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 Browser Use
   Browser Use~partialclaimed4/10

   Docs mention structured output but V4 returns `run.result` as a plain string with a recommendation to 'ask for JSON only, then validate it client-side' — there's no native Zod/Pydantic schema binding or first-party typed-schema extraction feature shown. This is a workaround rather than a built-in schema-validated extraction pipeline. missing for 10: no evidence of a documented schema/type-binding API (e.g., passing a Pydantic/Zod schema directly to the agent), no SDK-level validation helpers, no independent/hands-on confirmation that structured JSON output reliably conforms to a given schema.

   • [claimed-docs] “V4 returns `run.result` as a string. Ask for JSON only, then validate it client-side”
   • [github] “Task: "Extract structured data about my followers and export it as a CSV."”

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

   The evidence pack has no documentation of file upload/download handling or of artifacts being stored and retrievable after a run — GH task examples merely reference a resume being filled in and CSV export, but no confirmation these are handled as retrievable files via any API or session mechanism. Missing for 10: explicit file upload API/tooling, download/save-to-cloud-storage feature, and an artifact retrieval endpoint or docs section.

   • [github] “Task: "Fill in this job application with my resume and information."”
   • [github] “Task: "Extract structured data about my followers and export it as a CSV."”

   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