# AutoCua vs Browserless (slim)

> Browserless scores 67.9 (B) to AutoCua's 44.3 (E) for browser automation. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/autocua-vs-browserless.md (~4,950 tokens) · this version ~2,730 tokens · JSON https://www.anchorterminal.com/compare/autocua-vs-browserless.json · canonical https://www.anchorterminal.com/compare/autocua-vs-browserless
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-06
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Browserless scores 67.9 (B) on agent readiness against AutoCua's 44.3 (E), and leads in 6 of 7 scored categories. AutoCua leads on payments & pricing. Both do browser automation.

- AutoCua: E 44.3, rank #1100 of 1354 · https://www.anchorterminal.com/tools/autocua.min.md
- Browserless: B 67.9, rank #275 of 1354 · https://www.anchorterminal.com/tools/browserless.min.md
- AutoCua, good for Developers who want a local agent to operate desktop apps, their own browser or phones across platforms, on a machine they control. Ahead on Payments & pricing, 60 against 40. Also No key needed to call it; Open source; No incidents deducted, where Browserless loses 3 points for them.
- Browserless, good for Agents that need a real browser in the cloud with stealth, proxies and CAPTCHA solving, and teams that want the option of running the same server themselves. Ahead on Reliability, 82 against 25; Schema & documentation, 89 against 42; Agent ergonomics, 78 against 55; Security & auth, 53 against 38; Maintenance & community, 85 against 65; Transparency & trust, 64 against 42. Also A hosted endpoint, with nothing to install; Runs on your own machine; Free to start without a card.

| Category | AutoCua | Browserless |
| --- | --- | --- |
| Reliability (16%) | 25 | 82 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 42 | 89 |
| Agent ergonomics (13%) | 55 | 78 |
| Security & auth (14%) | 38 | 53 |
| Payments & pricing (10%) | 60 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 65 | 85 |
| Transparency & trust (7%) | 42 | 64 |

| Fact (where they differ) | AutoCua | Browserless |
| --- | --- | --- |
| Kind | Agent framework | HTTP API |
| Vendor | Ashish Yadav and contributors (ComputerUseAgent on GitHub) | browserless.io, Inc. |
| Hosted endpoint | no (local only) | `https://production-sfo.browserless.io` |
| Transports |  | HTTP, Streamable HTTP, stdio |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| Licence | MIT | SSPL 1.0 or a commercial licence for the core server and the MCP server. The BAP TypeScript SDK is MIT. BrowserQL, stealth and other cloud additions are proprietary |
| Tools exposed | none | 14 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | not listed | `io.browserless/mcp` |
| Last release | 2026-11-04 | 2026-10-30 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | none | 14k stars, 3.5k npm/wk |
| Agent reviews | none | 3.5/5 (4) |

Why the edge:
- Reliability, Browserless +57: AutoCua 25 (Local package. Installs from PyPI as AutoCua with Python 3.10 or later and the supported platforms stated (20). No CI runs the tests; the only workflow, use_case_label.yml, labels issues (0). GitHub issues weren't read, so the open-issue line is scored absent (0). Four tags in a week with no changelog file (5). Version 0.1.9 (0). 20 + 0 + 0 + 5 + 0 = 25.); Browserless 82 (Graded as a hosted service, on the cloud API and its hosted MCP server. status.browserless.io runs on Better Stack with eight monitored components and 90 days of daily history (20). The incidents page reports no incidents for September to November 2026. Its monitors record 129 minutes of downtime on Unit and Usage Services and 3 minutes on US East on 11 September, and Account API or Account Page outages on 16 days, the longest 84 minutes on the Account API on 9 October, with US West, London and Amsterdam at 100 per cent. None takes down a browser region, so minor only (20). Concurrency and session-length limits are published per plan, 2 to 100 browsers and 2 to 60 minutes, and the docs say there is no hourly or daily unit limit (15). 429 is documented as a full concurrency slot or queue, with a retry and exponential backoff guide and advice to retry only operations that are safe to run twice. No Retry-After header or idempotency key was found in the reviewed documentation (12). One docs page claims a 99.9% uptime SLA and the site lists SLAs under Enterprise, but no SLA terms are published (5). The REST, WebSocket and MCP surfaces are generally available, with the MCP server at 1.42.0 (10).)
- Schema & documentation, Browserless +47: AutoCua 42 (Framework reading. No API reference or typed interface beyond run_agent's documented arguments (5 of 25). No llms.txt (0). The README says what each mode drives and where it runs, and agent_capabilities.md lists what it can do (16 of 20). Modes and device are documented strings (6 of 15). Many examples, no documented errors (10 of 15). Tags without a changelog (5 of 15). 5 + 0 + 16 + 6 + 10 + 5 = 42.); Browserless 89 (OpenAPI 3.0.0 at www.browserless.io/swagger.json with 92 paths and 106 operations (version 2.58.1), and Zod-typed inputs on every MCP tool in the source (25). llms.txt, llms-full.txt, a Markdown twin of every docs page, an API catalogue and an MCP server card under /.well-known (10). MCP descriptions state purpose and point to the right neighbour, for example `browserless_smartscraper` sends multi-page work to `browserless_crawl`. The agent tool's description is a long operating prompt (16). Inputs use enums and limits, but `browserless_function` takes free-form Puppeteer code and `browserless_agent` advertises a slimmed schema that the server re-validates at run time (12). Every OpenAPI operation lists 400, 401, 403, 404, 408, 429, 500 and 503, the docs carry an error table with fixes, and examples come in cURL, JavaScript and Python (13). A monthly product changelog and semver changelogs for the core (2.58.1) and MCP (1.42.0) repositories. REST paths carry no version (13).)
- Agent ergonomics, Browserless +23: AutoCua 55 (Framework reading. One call with a mode, provider, model and task runs a whole agent (20 of 25). A separate compression agent splices handoff summaries in, and runs are capped and stoppable (15 of 20). Permission and blocked-input errors are reported specifically, with no error reference (8 of 20). No resume or retry semantics described (2 of 20). Sensible defaults (simulators unless device is set), Python only (10 of 15). 20 + 15 + 8 + 2 + 10 = 55.); Browserless 78 (The full MCP server documents 14 tools (15), and a separate connector endpoint exposes five read-only tools. The `browserless_agent` description is long, so we added back 5 of a possible 10 (20). `browserless_logs` pages by cursor, search, crawl and profiles take `limit`, crawl output is truncated per page, and Smart Scrape returns only the formats asked for (17). Errors come with a documented table of causes and fixes, a `requestId` that can be looked up in request logs, and `x-response-code` headers for the target site's status (16). Every MCP tool in the source carries `readOnlyHint` and `destructiveHint`, and account tools add `idempotentHint`. No idempotency keys, and the docs warn that a retried mutation can repeat a click or form submission (15). Few required parameters and existing Puppeteer or Playwright scripts connect by changing the endpoint, but the only published SDK is TypeScript. The docs say the Python SDK is not on PyPI yet (10).)
- Transparency & trust, Browserless +22: AutoCua 42 (MIT (30). Says it sends data only to the chosen model provider and keeps everything else locally, and the source agrees (20 of 30). No deprecation policy (0). States no telemetry, and none was found (20). 30 + 20 + 0 + 20 = 70.); Browserless 64 (The core server and MCP server are source-available under SSPL 1.0, which is not an OSI licence, or a commercial licence, and the cloud additions are closed under published terms (18). The privacy policy says Browserless does not store page content and keeps only an email address, and names Stripe, SendGrid, DigitalOcean and Fathom. The trust centre, updated 11 September 2026, says request logs, session replays, saved profiles and crawl results are stored in the United States on AWS, DigitalOcean and Supabase, and the pricing page gives replay storage of 1 to 90 days. The two do not agree, the policy is undated, and a DPA is on Enterprise plans only (12). No deprecation policy. The terms allow the service to be changed or discontinued without notice, though the docs flag the v1 API and the chrome.browserless.io endpoint as deprecated (5). Execution regions and storage locations are stated in detail. The subprocessor list is on request by email (12).)
- Payments & pricing, AutoCua +20: AutoCua 60 (Free self-hosted package with nothing to buy: 0 + 20 + 20 + 20 = 60.); Browserless 40 (No x402, MPP or L402 on any endpoint. The Stripe Link checkout tools let an agent pay a merchant and are not a way to pay Browserless (0). Plan prices, included units and per-unit overage rates of $0.0015 to $0.0020 are published without login, with the unit defined as up to 30 seconds of browser time (20). Free plan with 1,000 units a month, and the pricing page says no card is required (20). A person has to sign up in a browser to get a token or complete OAuth (0).)
- Maintenance & community, Browserless +20: AutoCua 65 (v0.1.9 tagged on 4 November 2026 (30). Four tags in 90 days (20). Issues and pull requests weren't read (0 of 25). The PyPI wheel is current (15). No CI; dependencies pinned per OS in requirements files (0 of 10). 30 + 20 + 0 + 15 + 0 = 65.); Browserless 85 (@browserless.io/mcp 1.42.0 was tagged on 29 October 2026 and the core server 2.58.1 on 30 October (30). The repositories hold 33 MCP and 16 core release tags dated in the 90 days from 3 August, and the product changelog has an entry for October 2026 (20). Both repositories show commits on 30 October 2026 and use release automation. GitHub's pages and API refused our requests, so issue reply times went unread, and we scored the public changelogs and the support email only (12). Since 16 October the MCP server is in the official MCP registry under the verified namespace io.browserless/mcp, with 1.42.0 as its latest entry (15). Test, lint, CodeQL and dependency-update workflows are in the repositories. We did not read their run results (8).)