Kane CLI vs Pomerado

Kane CLI 20

No x402, MPP or L402 (0). Plan prices are public per the listing check of 1 November 2026 (Starter $17 a month billed annually, Pro $89), and run_end reports credits per run, but the credit price per run isn't published, so plan-only pricing (10). The release says "free to start" and the check found a 10,000-credit, 30-day trial; whether it needs a card couldn't be read today. Judgement call (10 of 20). A person signs up and approves OAuth in a browser, or copies an access key from the dashboard, before any run (0).

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 46 public read-only tools with no account, but writes, logins and builds need an account that a person approves, through OAuth or a device code, so partial credit (12 of 20).

Kane CLI 65

Graded on the CLI as an agent drives it. run_end carries summary, one_liner and only the values asked for with "store as" in final_state, and --max-steps and --timeout bound a run. The skill an agent loads is about 40 KB with 25 reference files (15 of 25). testrun selects by paths, --match and --tags, explore list and explore sessions filter by run, and --json on design and review commands; few size controls beyond that (14 of 20). Exit codes separate pass, fail, setup error and timeout, failure reasons are named, and refusals name the command to run next (18 of 20). Replays of saved tests come from cache, reconcile resumes rather than re-billing, and Exploration allows one run at a time. A one-shot run has no idempotency key and Exploration's default can change data (10 of 20). One required argument for run; Exploration's mutating default isn't a safe one; no SDKs, only the CLI from npm, Homebrew and a shell script (8 of 15).

Pomerado 83

The keyless endpoint lists eight tools with about 24,000 characters of definitions, 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).

Kane CLI 38

The editorial half. The wrapper, skill and docs are Apache-2.0. The runner, assurance and pinned Node binaries are labelled Apache-2.0 on npm with no source in the linked repository, and the service terms couldn't be read (12 of 30). The repository says what leaves the machine. Every run uploads to Test Manager with screenshots and an evidence pack recording the user's name and email, secrets are masked, credentials are stored with mode 0600, and the evidence viewer reads packs locally. The privacy policy, DPA and retention periods are on testmuai.com and weren't read (10 of 30). The changelog calls out breaking changes, such as the removal of the bare-objective shortcut in 0.4.1, but there's no deprecation policy or dated notice period (5 of 20). The changelog describes telemetry (a remote log, support ids, errors spooled and sent at exit) and a daily npm update check. The opt-out KANE_TELEMETRY=0 appears only in a skill reference, not the user guide (8 of 20).

Pomerado 53

The hosted service is closed with clear terms (Common Paper Cloud Service Agreement 2.1, last updated 4 October 2026), and the complete minting core is MIT on GitHub, which the README says the Cloud runs (24). The privacy policy is an iubenda embed whose path iubenda's robots.txt disallows, so it was not read. The homepage FAQ says results are erased once read or within 60 minutes, credentials are kept only if saved, and hashes of sign-in identifiers are retained, and the API docs keep run logs for 90 days. No public DPA found (10 of 30). No deprecation policy found. The tool docs promise that a repair never removes or loosens an output field unless the site stopped showing it and the person confirms, and the terms give 30 days' notice of price changes (7). No subprocessor list or data location found. The open-source README says builds use OpenAI models (2).

Kane CLI 55

Two credential routes. OAuth with browser consent and token revocation on logout, scopes not documented; or the account's username and access key, which the docs say lets anyone holding it run tests on the account, passed as a command-line flag in CI. Not in a URL. 20 of 30 for revocable credentials without documented scopes. Exploration's read_only policy blocks write requests to any host and never presses Delete, Sign out or Pay, with --deny, --allow-domain and --allow-post, and the first mutating run in a project asks once on a terminal. The default is mutating, with no confirmation in agent mode (12 of 20). Results include text from the page under test. The 0.10.0 content fence masks secrets before they leave the worker, but no prompt-injection guidance was found (2 of 15). Every run lands in Test Manager with screenshots, evidence packs record steps and logs, and Exploration findings keep a history naming who changed what (13 of 15). SECURITY.md with security@testmuai.com, signed and notarised binaries per the README, npm registry signatures. No bug bounty, certification or security.txt could be checked, since testmuai.com wasn't readable, and SECURITY.md's supported versions list only 0.1.x (8 of 20).

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

Kane CLI 50

Graded with the hosted lines, because every run, exploration and design job goes through TestMu AI's service and spends credits, and Exploration runs on HyperExecute. status.lambdatest.io (Statusfy) lists Kane CLI and KaneAI as their own components with incident history and an Atom feed (20). From 3 August to 1 November 2026 no incident names Kane CLI or KaneAI. The platform under it had test creation timeouts from 09:00 to 13:30 UTC on 28 September with slow Automation and HyperExecute starts, six hours of partial macOS HyperExecute degradation on 25 September, and real-device partial outages on 21 August and 22 October (57 minutes). Judgement call, 10 for multi-hour degradation of the service runs depend on. No request rate limit is published; the only numbers are Exploration's built-in limits (an hour, 400 actions or 800 model calls), 20 cloud browsers and a 15-minute real-device queue (5 of 15). No 429 or Retry-After guidance. maintain reconcile is documented as idempotent, Exploration refuses a second run with RUN_ACTIVE, and the skill says never to rerun a paid command just to get a support id (5 of 15). No SLA found; the terms weren't readable (0). Nothing in the repository labels Kane CLI or Exploration beta or preview (10).

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. status.pomerado.ai has no DNS record and none is linked from the site or docs (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). The service is 12 days old by its first npm release.

Kane CLI 77

No OpenAPI or JSON Schema file. The NDJSON events are documented in typed Markdown tables, run_end is declared stable across versions, and each command family has its event list (10 of 25). Markdown docs in the repository, an agent skill and a context7.json for agents. The agents.md guide on testmuai.com wasn't readable and no llms.txt was checked (10). The user guide and skill say when to use run, testmd, testrun, assurance or Exploration, and when not (Exploration when there are no written requirements, read_only for data you care about) (17 of 20). Flag tables give defaults and allowed values for --mode, --target, --policy and --bug-detection; --variables and --session-context take free-form JSON (12 of 15). Examples throughout, exit-code tables and troubleshooting tables with named failures such as failed:setup_failed and RUN_ACTIVE. The README's run_end example names credits while the skill names credits_consumed (13 of 15). Semantic versions with a dated Keep a Changelog file and git tags (15).

Pomerado 86

OpenAPI 3.1 at /v1/openapi.json with 84 operations on 66 paths, 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). 159 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). 58 of 84 operations carry examples, all 84 document error responses, and the errors page gives 132 codes, each with its status, whether to retry and what to do (14). Paths are versioned /v1. The API reference has a dated Changes list with one entry, of 15 October 2026, and the open-source core keeps CHANGELOG.md with breaking-change sections (8 of 15).