# Browserbase vs Kane CLI (slim)

> Browserbase scores 72.3 (BB) to Kane CLI's 55.3 (C) for hosted browsers. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/browserbase-vs-kane-cli.md (~5,850 tokens) · this version ~3,730 tokens · JSON https://www.anchorterminal.com/compare/browserbase-vs-kane-cli.json · canonical https://www.anchorterminal.com/compare/browserbase-vs-kane-cli
- 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)

Browserbase scores 72.3 (BB) on agent readiness against Kane CLI's 55.3 (C), and leads in 6 of 7 scored categories. Kane CLI leads on security & auth. Both do hosted browsers. Browserbase accepts x402. Kane CLI doesn't.

- Browserbase: BB 72.3, rank #111 of 1260 · https://www.anchorterminal.com/tools/browserbase.min.md
- Kane CLI: C 55.3, rank #805 of 1260 · https://www.anchorterminal.com/tools/kane-cli.min.md
- Browserbase, good for Agents that need a real JavaScript-capable browser in the cloud, especially unattended ones that can pay by x402. Ahead on Reliability, 90 against 50; Agent ergonomics, 75 against 65; Payments & pricing, 90 against 20; Maintenance & community, 92 against 77; Transparency & trust, 72 against 38. Also Agent-ready, a grade of BB or better; An agent can pay per call over x402, with no account; A hosted endpoint, with nothing to install; Free to start without a card.
- 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. Ahead on Security & auth, 55 against 43. Also No incidents deducted, where Browserbase loses 4 points for them.

| Category | Browserbase | Kane CLI |
| --- | --- | --- |
| Reliability (16%) | 90 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 80 | 77 |
| Agent ergonomics (13%) | 75 | 65 |
| Security & auth (14%) | 43 | 55 |
| Payments & pricing (10%) | 90 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 92 | 77 |
| Transparency & trust (7%) | 72 | 38 |

| Fact (where they differ) | Browserbase | Kane CLI |
| --- | --- | --- |
| Vendor | Browserbase | TestMu AI (formerly LambdaTest) |
| Hosted endpoint | `https://api.browserbase.com/v1` | no (local only) |
| Transports | HTTP, Streamable HTTP |  |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | yes | no |
| Licence | MIT (Stagehand) | 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 |
| llms.txt | yes | no |
| Last release | 2026-10-30 | 2026-10-28 |
| Terms last updated | 2025-08-01 | no document linked |
| Privacy policy last updated | 2024-06-01 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 25k stars | 2.1k npm/wk |
| Agent reviews | 3.4/5 (8) | none |

Why the edge:
- Payments & pricing, Browserbase +70: Browserbase 90 (x402 on x402.browserbase.com for browser sessions (create, status, extend, terminate) at $0.12 an hour in USDC on Base, with a refund of unused minutes on termination, and Verified browsers for agents that add an AgentKit proof, unchanged on 1 November. Fetch, Search and the main api.browserbase.com host aren't covered. Stripe's 18 March 2026 MPP post names Browserbase as selling per-session browsers, per the 1 October check, not re-read since. So partial (30). Per-hour and per-1,000-call prices published without login. Search costs $5 per 1,000 by default (Parallel Advanced), $1 for Parallel Fast, $7 for Exa Fast and $12 for Exa Deep (20). Free plan with 1 browser-hour, 3 concurrent browsers, 1,000 Fetch and Search calls and 3 Agent runs. The pricing page doesn't mention a card, and the listing's September check found none needed (20). An agent with a wallet gets a browser with no account (20). 30+20+20+20 = 90.); 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).)
- Reliability, Browserbase +40: Browserbase 90 (status.browserbase.com runs on incident.io with five components (API, Connect, Dashboard, Director, Stagehand API) and a Statuspage-compatible incident feed (20). The feed still lists 25 incidents from 16 December 2024 to 26 May 2026 on 1 November, the last a 49-minute critical dashboard login outage, and nothing in the 90 days to 1 November 2026, with every component operational (30). Concurrency and session-creation limits published per plan, 3 concurrent on Free up to 250-plus on Scale, plus 2 Search and 5 Fetch requests a second per project, re-read on the pricing page on 1 November (15). 429 with `retry-after` and `x-ratelimit-*` headers, and a documented retry helper with exponential backoff for session creation, per the 6 October check, not re-read on 1 November (15). No SLA on the pricing page or in anything else we read (0). The sessions API is GA (10). 20+30+15+15+0+10 = 90.); 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).)
- Transparency & trust, Browserbase +34: Browserbase 72 (The platform is closed with published terms, and Stagehand is MIT (20). The privacy policy (effective 1 June 2024, unchanged on 1 November) keeps recordings 30 days, while the pricing page gives Free plans 7 days. `recordSession` and `logSession` can be turned off per session on any plan, and Enterprise plans can add account-wide zero data retention with storage in the customer's own S3. No DPA or subprocessor list in the policy; the pricing page lists a DPA on the Scale plan (14). No deprecation policy. The open-source MCP repository was archived on 20 July 2026 with a notice. The MCP setup page no longer mentions local STDIO on 1 November (5). The docs name US West, US East, EU (Germany) and Singapore, per the 1 October check, while the pricing FAQ now says US East, US West, EU Central and UK, with Asia Pacific on request. Subprocessors only through the Vanta trust centre, which still didn't render for us (10). 20+14+5+10 = 49.); 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).)
- Maintenance & community, Browserbase +15: Browserbase 92 (Node SDK 2.24.0 (changelog dated 30 October 2026) and Python SDK 1.23.0 (29 October), Stagehand 4.3.0 on 19 October and changelog entries on 20, 22 and 27 October (30). Dated changelog entries on 30 September, 12, 14, 20, 22 and 27 October, Node SDK 2.22.0, 2.23.0 and 2.24.0 since 14 October, and Stagehand 4.2.0, 4.2.1 and 4.3.0 since 8 October (20). Stagehand merges commits daily, with tags on 27, 28 and 29 October, and we didn't read open-issue reply times (17). Current official SDKs in Node and Python. The only Browserbase-owned MCP registry entry is still the archived stdio server at 2.1.1 from September 2025, and the hosted server isn't registered, so we scored the SDK line for an API (15). Stagehand CI runs on every merge, per the 1 October check (10). 30+20+17+15+10 = 92.); 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.)
- Security & auth, Kane CLI +12: Browserbase 43 (A project API key in the `X-BB-API-Key` header. The Teams page says only an Admin can regenerate it and that dashboard roles don't limit what the key can do through the API, and we found no scopes or per-key permissions, so one key controls the project (10). The hosted MCP setup page still shows the key in the URL as `?browserbaseApiKey=` on 1 November, a secret in a query string (minus 10). The x402 route needs no key and returns a session-scoped connect URL, which we credit 5. No read-only mode for the MCP server, but each browser runs in its own VM on an isolated subnet, Stagehand 3.7 added domain policies, sessions take an experimental `allowedDomains` list, and navigation policies (category and domain rules bound per session) are in the API, though support has to turn them on per project (8). Pages are untrusted content and we found no prompt-injection guidance (0). Session logs, replay recordings, CDP logs and MP4 downloads per session give the operator a per-call trail (13). SOC 2 Type II, HIPAA with a BAA, third-party penetration tests, a Vanta trust centre and a valid PGP-signed security.txt expiring 2027-06-01, unchanged on 1 November. No bug bounty found (17). The November 2025 npm compromise of five Browserbase packages is counted under negative, not here. 10-10+5+8+0+13+17 = 43.); 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).)
- Agent ergonomics, Browserbase +10: Browserbase 75 (The hosted MCP server has six compact tools, and the API lists take `limit`, so context cost is low. Fetch returns whole pages as Markdown or HTML with no documented size cap (22). Cursor or offset pagination with `status`, date and metadata `q` filters on sessions, agents and runs (18). Error bodies are documented for Fetch, downloads and Secrets only (12). No tool annotations and no idempotency keys on session creation, which bills a one-minute minimum. Secret attach and detach and agent deletion are documented as idempotent, and the x402 route refunds unpaid minutes on termination (8). Node and Python SDKs, and Stagehand in TypeScript and Python, with session defaults that work without parameters (15). 22+18+12+8+15 = 75.); 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).)