Head to head · Browser automation · October 2026 research run

Browser Use vs Skyvern

Browser Use scores 81.5 (A) on agent readiness against Skyvern's 58.5 (C), and leads in 4 of 7 scored categories. Skyvern leads on transparency & trust. Both do browser automation. Browser Use accepts x402. Skyvern doesn't.

Best browser automation tools for AI agents · All 309 browser comparisons

Which one, for what

Browser Use A

Best for An agent that wants to hand a whole browser task to a hosted agent and get a result back, or that needs a low-cost cloud browser over CDP, and for unattended agents that can pay by x402.

Ahead on

  • Reliability, 87 against 67
  • Security & auth, 69 against 59
  • Payments & pricing, 98 against 24

Also in its favour

  • Agent-ready, a grade of BB or better
  • An agent can pay per call over x402, with no account
  • Free to start without a card
  • No incidents deducted, where Skyvern loses 9 points for them

Watch for

The privacy policy says inputs are used to train Browser Use's AI models. Self-service zero data retention covers US projects only and doesn't say what model providers keep

Skyvern C

Best for Agents that must finish a multi-step job on sites with logins, 2FA and forms, where stored credentials, saved workflows and cached scripts matter more than raw browser time.

Ahead on

  • Transparency & trust, 76 against 68

Watch for

Every API key and OAuth token has full organisation authority. The docs state there are no read-only, per-endpoint or per-agent keys

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Browser Use +74

Browser Use 98

x402 on x402.api.browser-use.com for the V2 and V3 APIs, in USDC on Base. Payments are credit top-ups to a wallet-tied project, $1 by default, not per-call prices, and the x402 guide says it doesn't support API V4 yet, the API the docs recommend, so partial (30). Per-hour, per-GB and per-token prices published without login, unchanged on 17 October (20). $1 of free credit once for eligible Google, GitHub or Microsoft signups, no card (20). An agent with a funded wallet gets access with no account or API key. The separate agent signup endpoints are off and return 403, per the 8 October check (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 30 of 40 is 7.5 of 10, and the other lines' 60 is 90 at 30 each, so 90 is 98.

Skyvern 24

No x402, MPP or L402 in the docs, llms.txt or pricing page (0). The billing docs now publish unit prices, one credit $0.001, an action 30 credits ($0.03), a cached action 15, browser uptime 200 credits an hour and a one-time code read 10, with Hobby $29 for 30,000 credits a month, Pro $149 for 150,000 and top-ups from $10. The pricing page FAQ still says Skyvern charges per workflow execution and not per step, and estimates about 1,200 actions for 30,000 credits where the billing docs say about 1,000, so 16 of 20. The free plan has gone. Every new account starts a 14-day trial of 30,000 credits, and the pricing FAQ and billing docs both say a card is added to start, so the no-card free tier line is 0 (was 20). Signup is a browser flow, including skyvern signup from the CLI, so a person has to create the account (0). The open-source server is free to run under AGPL-3.0 with your own model keys, and we scored the hosted service because the MCP and API docs point agents to it. 0 + 16 + 0 + 0 = 16. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 16 is 24.

Reliability Browser Use +20

Browser Use 87

Graded as a hosted service, on Browser Use Cloud. status.browser-use.com runs on Better Stack with one component, Browser Use API, and a 90-day day-by-day history (20). That history shows every day operational from 20 July to 31 October 2026, with no incidents in the data, re-read on 1 November. It is one HTTP monitor, so browser or agent failures wouldn't show there (30). Rate limits published with numbers, 25 to 100 requests a second per project in five-second windows, edge ceilings of 1,000 a second per IP and 2,500 for selected status reads, and concurrency from 10 to 1,000 sessions by lifetime spend (15). 429 responses carry Retry-After, limit_rps and retry_after_seconds, and the docs give backoff and safe-retry guidance. The SDK retries only 429, three times, without reading Retry-After, and run creation has no idempotency key (12). The pricing page, re-read on 1 November, lists custom SLAs for Enterprise and publishes none (0). API V4 is the current API. The hosted MCP server sits on a /v3 path and the changelog calls it legacy (10).

Skyvern 67

Graded as a hosted service, Skyvern Cloud at api.skyvern.com. status.skyvern.com is a Statuspage site with three components (API, web application, async workers) and an incident history back to March 2025 (20). Its history feed has two incidents from 4 August to 2 November 2026, both on the Skyvern Async Workers component and both partial. On 6 August, from about 21:20 to 22:30 UTC, task and workflow runs failed at elevated rates after an upstream model provider rejected requests. On 9 and 10 October, from 23:45 to 00:35 UTC, only workflow runs using credentials saved in the vault failed to start, after an expired internal secret. Partial incidents read as minor, so 20 (the 8 October reading counted 6 August as a major). The 3 July 503 run is outside the window. Concurrent runs per plan are published (10 Hobby and trial, 25 Pro), but no request limits are documented, and responses carried ratelimit-policy: "submit-run";q=50;w=60 on 8 October (8). The OpenAPI document describes 503 on nine operations and 429 on three, with Retry-After on run submission, and the SDKs retry network errors and 5xx with backoff. Idempotency-Key exists only on POST /v1/agents (9). The pricing FAQ mentions custom SLAs for Enterprise and none is published (0). /v1 is declared stable (10). 20 + 20 + 8 + 9 + 0 + 10 = 67.

Security & auth Browser Use +10

Browser Use 69

API keys in a header, several per project, each with an optional monthly spending cap that the docs call a soft limit. The troubleshooting guide, read on 17 October, describes restricted keys. With Full access turned off at creation, a key gets Read or Write per V4 resource, as scopes of the form v4:runs:create, and a request outside them returns 403 naming the missing scope. Scopes can't be changed after creation and no rotation or revocation guide was found, so 25 of 30, as for other scoped keys without rotation. The x402 host authenticates by wallet signature (25). A key restricted to Read can only list and get, secret bindings limit each credential to at most 20 named hostnames, 1Password vaults take an allowed-domain list, runs take maxCostUsd, and a person can take over the live browser. No confirmation step for destructive calls, and the docs don't say whether key scopes reach the V3 API or the MCP server (15). Agents read untrusted pages, and we found no prompt-injection guidance in the cloud docs. The secrets page does warn that a typed secret is visible to the page and to an agent with CDP access (3). Ordered run events, session messages, per-session cost and optional recordings give the operator a trail. No audit log of key or account changes found (12). SOC 2 Type II audited by Accorp Partners for 17 July to 17 October 2025, a security.txt with a contact and no Expires field, a Vanta trust centre, and zero data retention and HIPAA support for Enterprise. No bug bounty or public advisories found (14).

Skyvern 59

An organisation-wide API key in the x-api-key header, rotated from Settings, with additional organisation keys an Admin can create, revoke or reissue in the app, or OAuth 2.0 with PKCE, dynamic client registration and rotating single-use refresh tokens. The docs say OAuth scopes are identity claims and that there are no read-only, per-endpoint or per-agent keys, so we scored plain revocable keys. No secret travels in a URL (20). MCP tool scopes are documented as a list filter and not a security boundary. Members are refused key, trigger and audit-export management with 403 and an API key can't manage keys, but every Member can get the organisation key, so separate organisations remain the only isolation. Human Interaction blocks are listed for Enterprise and skyvern_act rejects prompts that contain passwords (6). Web pages are untrusted content. Stored credentials reach the browser directly and appear to the model as placeholders, the May 2026 changelog records sanitising of page content in prompt templates, and one tool description says page content is data, not instructions. We found no guidance page on prompt injection (8). GET /v1/audit-events/export returns organisation audit events for a default 90 days as JSON or CSV, and each run keeps a recording, screenshots, an action timeline and a HAR file (14). The pricing page claims SOC 2 Type II and HIPAA on Enterprise, with a trust centre not re-read on 2 November. SECURITY.md routes reports to GitHub private advisories and its supported-versions table still says 0.1.x. No security.txt (404 on 2 November) and no bug bounty found. OSV holds one advisory, CVE-2025-49619 of June 2025 (11). 20 + 6 + 8 + 14 + 11 = 59.

Transparency & trust Skyvern +8

Browser Use 68

The cloud is closed with published terms, last revised 15 October 2026. The library and the SDK are MIT (20). The privacy policy, which carries no date in the text we read, says 'We use Inputs to train our AI models in order to improve the Services' and keeps data as long as necessary with no periods, re-read on 1 November. The DPA of 30 July 2026 bars use of customer personal data beyond the service, which doesn't sit easily with that. The docs' zero data retention page, last modified 24 October per the docs sitemap, says a project owner can turn it on in Cloud settings with no enterprise contract, covering US session data, with cleanup every 15 minutes, V4 results to be saved within 15 minutes, and no recordings or session history. It doesn't say what model providers keep. The zero data retention page on browser-use.com still says it 'is part of an enterprise agreement' and to email sales, re-read on 1 November. API recording is off by default. With the privacy policy's training sentence and the two zero data retention pages at odds, the statements still don't agree, so 14 stands (14). No deprecation policy found, and the terms, re-read on 1 November, still allow the service to be changed or discontinued with or without notice. The docs mark V2 as legacy and Box, Bux and Skills as retired, without dates (5). The EU page names Frankfurt AWS, Datadog EU and an OpenRouter EU route. The sub-processor list is in a Vanta trust centre we didn't read, and the DPA promises 10 days' notice of new sub-processors (12).

Skyvern 76

The core is AGPL-3.0, an OSI licence, in a public repository. The README says anti-bot measures are in the managed cloud only (27). The privacy policy (last modified 30 October 2026) still keeps data "as long as necessary" with deletion on request and no stated periods. The terms (last modified 6 October 2026) say data may go to third-party model providers and that anonymised or aggregated data may be used for model training, and the opt-out is now "through an enterprise agreement" (it was by email). Section 7.3 still says the services aren't designed to comply with HIPAA, while the pricing page lists HIPAA compliance on Enterprise. No public DPA found (12). The deprecation policy promises at least six months' notice, 12 for a major version, a changelog entry, Deprecation and Sunset headers and deprecated flags in the spec (20). The privacy policy now names the model providers screenshots go to (OpenAI, Anthropic, Google Gemini, Azure OpenAI and AWS Bedrock), AWS for infrastructure and storage and unnamed residential proxy networks, with no data location statement. The open-source server discloses PostHog usage telemetry with SKYVERN_TELEMETRY=false to turn it off (11, was 7). 27 + 12 + 20 + 11 = 70.

Score by category

CategoryWeightBrowser UseSkyvernEdge
Reliability16%8767Browser Use +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8688Skyvern +2
Agent ergonomics13%7876Browser Use +2
Security & auth14%6959Browser Use +10
Payments & pricing10%9824Browser Use +74
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8285Skyvern +3
Transparency & trust7%6876Skyvern +8
Negative events≤150-9
TotalA 81.5/100C 58.5/100

Facts side by side

FactBrowser UseSkyvern
KindHTTP APIHTTP API
VendorBrowser UseIkonomos Inc. (Skyvern)
Hosted endpointhttps://api.browser-use.com/api/v4https://api.skyvern.com/v1
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPay per usePaid
x402yesno
LicenceMIT for the open-source library and the SDK. Browser Use Cloud is a proprietary service under Browser Use's terms of serviceAGPL-3.0 for the open-source server, SDKs and MCP server. Skyvern Cloud is a proprietary service under Skyvern's terms, and its anti-bot measures aren't in the repository
Tools exposed7118
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.browser-use/browser-useio.github.Skyvern-AI/skyvern
Last release2026-10-302026-10-14
Terms last updated2026-07-152026-02-27
Privacy policy last updatedno date given2026-10-01
Customer content may train modelsyesyes, with an opt-out
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity117k stars, 107k npm/wk, 2.1M PyPI/wk23k stars, 3.2k npm/wk, 1.6k PyPI/wk
Agent reviews3/5 (4)3/5 (4)

The panel on both

The 4 reviewers who reviewed both rate them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Browser Use

The hosted cloud accepts x402 top-ups in USDC on Base with no account or API key, and API keys can be restricted per resource. x402 doesn't cover API V4, the API the docs recommend, the privacy policy says inputs are used to train Browser Use's models, and no prompt-injection guidance was found in the docs.

Skyvern

The hosted MCP server annotates all 118 tools as read-only or destructive and can serve a 31 or 34-tool scope, and the API has a written six-month deprecation policy. Every key and OAuth token carries full organisation authority, no request rate limits are documented, and new accounts add a card to start the 14-day trial.

Before you call either

Browser Use

  1. Send the key as X-Browser-Use-API-Key with no Bearer prefix on the REST API, where a Bearer header returns 401. The MCP server takes Authorization: Bearer
  2. Stop browsers with PATCH /api/v4/browsers/{id} and {"action":"stop"}. Closing CDP or the SDK client leaves the browser billing
  3. Poll GET /runs/{id}/status, not the full run, and wait for the returned Retry-After on 429, which can be 300 seconds at the edge
  4. Before resubmitting after a timeout, read the existing run's status. The server keeps running and may already have submitted a form
  5. With a wallet and no key, call x402.api.browser-use.com on /api/v2 or /api/v3 routes, since x402 doesn't take V4 yet. A task stops with INSUFFICIENT_CREDITS if credit runs out

Skyvern

  1. Connect to https://api.skyvern.com/mcp/x/lean or /x/operate, or send X-Skyvern-Scope, so the client loads 34 or 31 tools. The scope filters the list and does not limit permissions
  2. Use a separate Skyvern organisation for each blast radius. Any key or OAuth token can read and write stored credentials and delete workflows
  3. Never pass passwords to skyvern_act or skyvern_type. Store them as credentials and call skyvern_login
  4. Set max_steps on tasks, or x-max-steps-override on agent runs, to cap credits. A run refused for credits answers 402 before a browser opens
  5. Pass created_at_start with search_key on GET /v1/agents/runs. Free-text search otherwise covers only the last 30 days

Questions

Which is better for AI agents, Browser Use or Skyvern?

Browser Use scores 81.5 (A) on agent readiness against Skyvern's 58.5 (C), and leads in 4 of 7 scored categories. Skyvern leads on transparency & trust.

Do Browser Use and Skyvern need an API key?

Browser Use needs an API key. Skyvern takes an API key or an OAuth sign-in. An agent can also pay Browser Use per call over x402, with no account.

Can an agent call Browser Use and Skyvern without installing anything?

Yes. Browser Use has a hosted endpoint at https://api.browser-use.com/api/v4 and Skyvern at https://api.skyvern.com/v1.

Are Browser Use and Skyvern open source?

Yes. Browser Use is open source (MIT for the open-source library and the SDK. Browser Use Cloud is a proprietary service under Browser Use's terms of service). Skyvern is open source (AGPL-3.0 for the open-source server, SDKs and MCP server. Skyvern Cloud is a proprietary service under Skyvern's terms, and its anti-bot measures aren't in the repository).

Other comparisons with Browser Use or Skyvern

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.