AutoCua vs Pomerado

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.

Pomerado 86

OpenAPI 3.1 at /v1/openapi.json with 90 operations on 71 paths on 2 November (84 on 66 on 17 October), and every MCP tool on the keyless endpoint has a typed JSON Schema input with additionalProperties: false (25). llms.txt with every page, and a Markdown twin of each docs page (10). MCP descriptions say when to use each tool and when not to, such as Pomerado before a browser, the read-only run for read tools, possible_matches before a build, and secrets on answer_url, not in chat. The server's instructions say to use a browser only if Pomerado says it can't build a tool (18). 184 enums, lengths and ranges such as limit 1 to 100 and keys of 1 to 200 characters, and required fields marked. The run and build tools take input and example_input as JSON-encoded strings over MCP (11). 59 of 90 operations carry examples, all 90 document error responses, and the errors page gives 157 codes, each with its status, whether to retry and what to do (14). Paths are versioned /v1. The API reference still has a dated Changes list with one entry, of 15 October 2026, though six operations were added since, and the open-source core keeps CHANGELOG.md with breaking-change sections (8 of 15).

AutoCua 38

Framework reading (telemetry, approvals, guardrails, sandboxing). Provider keys stored in a local folder with Chrome profiles (10 of 30). The worker tools are an allow-list with no write tool, unseen ids are refused, downloads need a yes, but on Windows the model answers UAC elevation prompts itself through a kernel driver, with no person asked (6 of 20). The scraping ruleset has a prompt-injection instruction to log page text that gives instructions (10 of 15). Runs are logged in the app, with no audit log (7 of 15). No security policy, disclosure route or advisories found (5 of 20, for the vault and certificate handling). 10 + 6 + 10 + 7 + 5 = 38.

Pomerado 69

OAuth for MCP clients, and pom_ API keys limited to chosen permissions out of 11, expiring after 90 days by default, rotated and revoked through the API, with integration keys confined to one site's MCP. No secret travels in a URL; the keyless URL refuses a key (30). The read-only run refuses a tool that writes before a job starts, builds declare read or write, write tools carry destructiveHint, website logins go through a protected page, and a key can't reveal a saved password or authenticator code. No approval step of Pomerado's own for writes was found beyond the client's own prompt (16). Tools return website content. The job-object page says to treat a job's message as data, never as instructions, and outputs are checked against each tool's schema, but no wider guidance on untrusted page text was found (6). Run logs list each browser action and the site's own requests, kept 90 days, builds have an activity log, and connected apps show permissions used and last use (13). No security.txt, SOC 2, ISO 27001 or bug bounty found. The homepage footer now links a trust centre at trust.pomerado.ai, whose robots.txt answers with its script-drawn app page, so it wasn't read and nothing on it is credited. The README sends reports to GitHub private vulnerability reporting, and the terms commit to notify customers of incidents without undue delay (4). Pomerado stores website passwords, authenticator secrets and recovery codes, which raises the stakes of that gap.

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.

Pomerado 83

The keyless endpoint lists eight tools with about 27,400 characters of definitions on 2 November, and the docs give 14 for a signed-in connection, with the rest of the API reached through search_pomerado_api, describe_pomerado_api and call_pomerado_api instead of one tool per operation. An integration MCP narrows an agent to one site's tools (19 of 25). Lists take cursor and limit 1 to 100, tool search filters by query, site and integration, get_job takes include_result and wait_seconds, and paged results carry a cursor (17). One error envelope with code, message, retryable, docs_url and details, and codes such as key_permission_missing name the missing permission and the page to fix it (20). Idempotency keys on runs and builds, with replay marked Idempotent-Replayed, and every keyless tool carries readOnlyHint or destructiveHint, idempotentHint and openWorldHint as fits (20). Few required fields (none for search, two for a run), but no official client SDK. The npm package is the local minter, not a Cloud client (7 of 15).

AutoCua 60

Free self-hosted package with nothing to buy: 0 + 20 + 20 + 20 = 60.

Pomerado 42

No x402, MPP or L402 on Pomerado's endpoints (0). Plan prices are public, Free $0, Premium $50 a month and Business custom, with call and build allowances, but there is no per-call price (10). The Free plan and keyless use need no card (20). An agent can find and run 584 public read-only tools across 447 sites with no account (46 across 23 on 17 October), but writes, logins and builds need an account that a person approves, through OAuth or a device code, so partial credit (12 of 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.

Pomerado 81

The repository's newest tag is v0.4.0-canary.493 on 29 October 2026, with main merged to 1 November, and the API's Changes entry is of 15 October (30). Releases 0.1.0 to 0.2.0 between 5 and 6 October, 0.3.0 closed in the changelog on 7 October, and 34 tags in all, most of them canaries (20). 1,396 commits on main from 17 October to 1 November, nearly all by the two founders. GitHub issues and replies couldn't be read, because GitHub's pages and API answer 403 in this session, so this rests on the commit history and the founders' email address (8 of 25). In the official MCP registry as ai.pomerado/pomerado, a domain-verified namespace, version 1.0.0, active since 15 October 2026, re-read on 2 November (15). CI runs a gitleaks secret scan, pins actions by SHA and publishes with npm provenance, per the 17 October check. Run results couldn't be read (8 of 10). 30 + 20 + 8 + 15 + 8 = 81.

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.

Pomerado 40

Graded as a hosted service, Pomerado Cloud, since the MCP and REST docs and the homepage's setup prompt point agents to it. No status page found on 2 November. status.pomerado.ai still doesn't resolve, and none is linked from the site, the docs or llms.txt (0). No readable incident history (5). Daily allowances are published with numbers (100 or 1,000 tool runs a day, 10 or 100 integrations a month), keyless runs have a daily limit, and 20 connect keys an hour, but no per-second or per-minute request rate was found (10 of 15). Over a limit the API answers 429 quota_exceeded with reset_at, or try_limit_reached with Retry-After, every error carries retryable, retryable MCP errors add retry_after_seconds, and runs, builds and invitations take idempotency keys with write_status and outcome_unknown for writes whose result is unclear (15). Business lists SLA guarantees, with no published terms (0). No beta or preview label on the hosted MCP or API, and the registry entry is version 1.0.0 (10). 0 + 5 + 10 + 15 + 0 + 10 = 40.