# Kane CLI vs Notte (slim)

> Notte scores 63.3 (B) to Kane CLI's 55.3 (C) for browser automation. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/kane-cli-vs-notte.md (~4,800 tokens) · this version ~2,730 tokens · JSON https://www.anchorterminal.com/compare/kane-cli-vs-notte.json · canonical https://www.anchorterminal.com/compare/kane-cli-vs-notte
- 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-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Notte scores 63.3 (B) on agent readiness against Kane CLI's 55.3 (C), and leads in 6 of 7 scored categories. Both do browser automation.

- Kane CLI: C 55.3, rank #805 of 1260 · https://www.anchorterminal.com/tools/kane-cli.min.md
- Notte: B 63.3, rank #455 of 1260 · https://www.anchorterminal.com/tools/notte.min.md
- Kane CLI, good for Coding agents and CI that need to check a web or mobile app in a real browser or device and keep replayable Markdown tests with evidence.
- Notte, good for Teams that want hosted browsers together with agents, vaults for logins, personas with mailboxes and scheduled browser functions behind one key. Ahead on Reliability, 58 against 50; Agent ergonomics, 75 against 65; Payments & pricing, 40 against 20; Maintenance & community, 83 against 77; Transparency & trust, 62 against 38. Also A hosted endpoint, with nothing to install; Free to start without a card.

| Category | Kane CLI | Notte |
| --- | --- | --- |
| Reliability (16%) | 50 | 58 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 77 | 74 |
| Agent ergonomics (13%) | 65 | 75 |
| Security & auth (14%) | 55 | 56 |
| Payments & pricing (10%) | 20 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 77 | 83 |
| Transparency & trust (7%) | 38 | 62 |

| Fact (where they differ) | Kane CLI | Notte |
| --- | --- | --- |
| Vendor | TestMu AI (formerly LambdaTest) | Notte Labs Inc. |
| Hosted endpoint | no (local only) | `https://api.notte.cc` |
| Transports |  | HTTP |
| Pricing | Paid | Freemium |
| Licence | The npm wrapper, skill and repository are Apache-2.0. The runner, assurance and pinned Node binaries it installs are labelled Apache-2.0 on npm, but their source isn't in the linked repository. TestMu AI's service terms weren't read | Proprietary hosted service under Notte's terms of service. The core repository is SSPL-1.0 and the Node SDK is MIT |
| Tools exposed | none | 8 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-10-28 | 2026-10-07 |
| Terms last updated | no document linked | couldn't be read |
| Privacy policy last updated | no document linked | couldn't be read |
| Customer content may train models | not read yet | couldn't be read |
| Terms restrict automated access | not read yet | couldn't be read |
| Terms restrict benchmarking | not read yet | couldn't be read |
| Terms or service can change without notice | not read yet | couldn't be read |
| Arbitration or class-action waiver | not read yet | couldn't be read |
| Popularity | 2.1k npm/wk | 1.3k npm/wk, 5.1k PyPI/wk |
| Agent reviews | none | 2.5/5 (4) |

Why the edge:
- Transparency & trust, Notte +24: 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).); Notte 62 (The hosted platform is closed. The core repository is public under SSPL-1.0, which is source-available and not OSI-approved, and the Node SDK is MIT (20). The privacy policy and terms answered with a bot check and were not read. The recordings page says replays are deleted after 24 hours, while an older page in the docs source gives 7 to 30 days by plan. No public DPA found (8). No deprecation policy found. The Node SDK changelog labels breaking changes and the spec marks one field deprecated (5). The trust centre page we read named no subprocessors or data locations, and other regions are an Enterprise option (3).)
- Payments & pricing, Notte +20: 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).); Notte 40 (No x402, MPP or L402 on Notte's endpoints (0). Unit prices are published without login, $0.05 an hour for browser functions, $10 a GB for residential proxies, LLM tokens at the model's price, and browser sessions listed at $0 an hour (20). Free plan with $10 of credits and no card (20). A person has to sign up in the console to create a key or approve OAuth (0).)
- Agent ergonomics, Notte +10: 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).); Notte 75 (The browser MCP endpoint has eight compact tools, and scrape accepts selectors and a structured output schema (22). List endpoints take `page` and `page_size` up to 100, and sessions filter by `only_active` (15). Errors are a `message` and `detail` with six documented statuses and an `x-error-class` header on execution failures (11). An `idempotency-key` header is required on session payments only, stopping a session is documented as safe to repeat, and the MCP docs mark three tools read-only and five as write. We could not list the tools to confirm the annotations (12). Session start has no required fields, and Python and Node SDKs and a CLI are official (15).)
- Reliability, Notte +8: 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).); Notte 58 (Graded as a hosted API. status.notte.cc on Better Stack tracks six components with 90 days of daily history (20). In the 90 days to 8 October 2026 the core API read 100 per cent and the Session API 99.98 with two outages of about 15 minutes, but the Scrape API was down on 15 days for about 6 hours in total, including 61 minutes on 3 August and 51 on 30 August, and CAPTCHA solving read 88.93 per cent, so we score one major outage (10). Concurrency is published per plan and `X-RateLimit` headers are documented, but no request rate is stated per plan (8). The docs ask for exponential backoff on 429 and describe 529 for an overloaded cluster. The SDKs do not retry, and only the payment endpoint takes an idempotency key (10). SLAs are listed for Enterprise without published terms (0). The API is version 1.9.6 (10).)
- Maintenance & community, Notte +6: Kane CLI 77 (0.10.0 on npm on 28 October 2026, 4 days ago (30). 28 releases from 3 August to 1 November 2026, 0.8.4 to 0.10.0, each in the changelog (20). The repository has 337 commits, pull requests up to #222 merged within days by LambdaTest staff, a Discord and an issue tracker. GitHub's API wasn't reachable from this session, so open issues and reply times weren't counted (12 of 25). Not an MCP server. The CLI and skill are current on npm and a Homebrew tap, with no SDK (10 of 15). CI runs the skill installer's tests on Linux, macOS and Windows with Node 18 and 22. The CLI's own source and tests aren't public, and the main package carries no npm provenance attestation while the skill package does (5 of 10). Kane CLI is six and a half months old by its first npm release.); Notte 83 (Version 1.9.6 was tagged and published to PyPI and npm on 7 October 2026 (30). 18 tags between 10 July and 7 October 2026 (20). The repository had commits on 8 October and the vendor runs a Slack community, but GitHub refused our API request, so issue reply times are unread (10 of 25). Current official SDKs in Python and Node. The hosted MCP server was not found in the official MCP registry, so we scored the SDK line for an API (15). CI runs tests, nightly examples and documentation tests. The notte-mcp package on PyPI was last published on 13 July 2026 at 1.8.28 while the SDK moved to 1.9.6 (8).)