Head to head · Browser automation · October 2026 research run
Airtop vs Anchor Browser
Anchor Browser scores 62 (B) on agent readiness against Airtop's 56.2 (C), and leads in 6 of 7 scored categories. Airtop leads on transparency & trust. Both do browser automation.
Best browser automation tools for AI agents · All 309 browser comparisons
Which one, for what
Airtop C
Best for Agents that need a hosted browser with natural-language page calls, saved logins handed over by a person, and proxies and CAPTCHA solving in one service.
Ahead on
- Transparency & trust, 62 against 53
Also in its favour
- No incidents deducted, where Anchor Browser loses 3 points for them
Watch for
No published rate for what a browser minute, a GB of proxy traffic or an AI call costs in credits
Best for Agents that must work inside signed-in accounts, with managed identities, MFA handling and a human sign-in link, and agents that need to start with no human signup.
Ahead on
- Reliability, 77 against 69
- Agent ergonomics, 73 against 65
- Security & auth, 54 against 46
- Payments & pricing, 45 against 38
- Maintenance & community, 57 against 14
Also in its favour
- Free to start without a card
Watch for
No service agreement or API terms found. anchorbrowser.io/terms is a website terms of use dated 16 March 2025
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.
Maintenance & community Anchor Browser +43
Airtop 14
Graded on the browser API. The newest stable release is the Node SDK's 0.1.47, tagged on 6 November 2025, 363 days before the check. The 1.0.0-alpha2 Node line (last published 1 July 2026 per the 8 October check) is a pre-release and doesn't count, the Python SDK's last tag is 0.0.49 (23 April 2025) and the docs changelog ends on 3 September 2025 (0). No three releases or dated entries since 6 August; the Agent Skill's commits of March 2026 are untagged (0). Support is by Discord and email. On GitHub the Node SDK had an issue from February 2025 still open and six pull requests open since early 2025, per the 8 October check, not re-read on 4 November (5). Official SDKs exist but the Python one was last released on 23 April 2025, and no Airtop server is in the MCP registry (6). Both SDK repositories carry CI workflows whose results were not read (3). 0 + 0 + 5 + 6 + 3 = 14.
Anchor Browser 57
The newest dated releases are the TypeScript SDK 1.0.0 on npm on 26 July 2026, per the 8 October check, and the Python SDK 1.0.1, tagged in its repository on 28 July, 96 days before 1 November. Neither repository has a commit after 28 July. The pricing page dates its AI step prices from 21 August 2026, 72 days before, the newest dated change to the service (20). In the 90 days from 3 August that pricing change is the only dated entry we found, and blog announcements carry no readable year. No dated changelog (10). No public changelog. Support is by email, with Slack on Growth and above. GitHub issues weren't read, since GitHub's pages and API answer 403 in our session (5). Official SDKs for TypeScript and Python are current at 1.0. The MCP servers were not found in the MCP registry, per the 8 October check (15). The SDK repositories have CI and publish workflows whose results we did not read, and the self-hosted MCP server's last commit is 24 July 2025 (7). 20 + 10 + 5 + 15 + 7 = 57.
Transparency & trust Airtop +9
Airtop 62
A closed service with published terms of use (effective 28 July 2025, unchanged on 4 November). The SDKs are MIT per their repositories (17). The privacy policy (updated 2 September 2025) keeps personal data as long as necessary, with no periods, and the site and FAQ say customer data is not used for AI training, by Airtop or its model suppliers. No public DPA or retention period for session data, recordings or profiles was found (12). No deprecation policy. Deprecated fields and two deprecated endpoints are marked in the reference with replacements and no dates, partly met, kept (5). The privacy policy says hosting is in the United States, and the FAQ names OpenAI, Anthropic and Google as model suppliers. No subprocessor list was read, since the trust centre did not render (8). 17 + 12 + 5 + 8 = 42.
Anchor Browser 53
The service is closed. The SDKs and the self-hosted MCP server are Apache-2.0. The only terms published are a website terms of use dated 16 March 2025, which grants personal, non-commercial use of the site and does not cover the API, so the terms for the paid service are unclear (8). The security page says session data is not stored and each browser's virtual machine is destroyed, the pricing page gives 7 days of data retention, recordings are on by default, and Zero Data Retention is by request. The privacy policy (24 February 2026) covers the website and customer contacts, with one product section on Gmail access. The DPA and data handling policy sit behind an access request (15). The legacy tasks API and the old MCP address are labelled and still work, and the SDK has a migration guide. No deprecation policy or dates (5). The security page names AWS us-east-2 and eu-central-1. The trust portal has a subprocessor section, of which our reader saw only OpenAI and Anthropic (12). Terms and privacy policy dates unchanged on 1 November. 8 + 15 + 5 + 12 = 40.
Reliability Anchor Browser +8
Airtop 69
Graded as a hosted service, on the cloud browser API. status.airtop.ai runs on Instatus with 90 days of history, though it lists a single component, App (20). Between 6 August and 4 November 2026 its feed records no incident, only 30 minutes of scheduled maintenance on 18 August, announced at 20:37 UTC for a 23:30 start with a stated 30-minute duration, which is maintenance, not an incident. The proxies incident of 1 July falls outside the window (30). No request rate limit was found in the reviewed documentation. The pricing page gives simultaneous sessions per plan, 3, 30 and 100 (5). No 429 or backoff guidance and no idempotency keys were found. The SDK helpers retry twice by default and the CDP guides table a 503 for sessions that cannot be reached, partly met, kept (4). No SLA found for any plan (0). The API is at /v1 and sessions and windows are not marked beta, though form filling is (10). 20 + 30 + 5 + 4 + 0 + 10 = 69.
Anchor Browser 77
Graded as a hosted service. status.anchorbrowser.io runs on incident.io with two components, Website and Anchor Application (20). Both show operational on 1 November, and the RSS feed is still empty. The page has recorded no incident since it was set up in June 2025. This run reads a readable page that has never posted an incident as a clean record at 20, as for quicken-simplifi, outline and linkup, where the 8 October check gave 25, a value the checklist doesn't name (20). Limits are published, 5, 25 and 100 session creations a minute and 5, 25 and 200 concurrent browsers by plan, and 2,000 requests a minute on Web Unlocker (15). The OpenAPI document declares 429 on ten operations, with RateLimit and Retry-After headers on session creation, and the Web Unlocker docs say to retry 429, 500, 503 and 504 with exponential backoff. The sessions guide now says a 429 from the per-minute limiter comes before a session exists, so retrying it doesn't create a second one, that the API reads no Idempotency-Key, so retrying a 5xx or 409 can, and which statuses are terminal. Safe-retry guidance without idempotency keys, read as e2b's (12). No SLA was found on the pricing page, the docs or the site (0). The API is version 1.0.0, the SDKs are 1.0 and nothing marks the sessions API as beta (10). 20 + 20 + 15 + 12 + 0 + 10 = 77.
Agent ergonomics Anchor Browser +8
Airtop 65
AI calls return an answer shaped by the prompt and an optional outputSchema, with costThresholdCredits and timeThresholdSeconds to bound a call. Scrape returns the page content without field selection (18). Sessions list by offset and limit with a default of 10 and filters for status and IDs, files list the same way, and paginated-extraction follows a site's own pages (15). Responses share a documented envelope with errors and warnings carrying message, code and reason, and AI calls report success, partial or failure. The codes are not listed (12). No idempotency keys. clientRequestId is echoed for correlation, and async variants return a request ID to poll (7). A session needs no parameters, and there are official Node and Python SDKs, the Python one last released in April 2025 (13). 18 + 15 + 12 + 7 + 13 = 65.
Anchor Browser 73
The main MCP server lists about 24 tools and reaches the other REST routes through list_endpoints, get_endpoint and two call tools. Browser control and per-site actions are separate servers, and the docs warn that /v1/mcp/actions without a domain lists thousands of tools. 15 for the tool count plus 5 for the split servers (20). Session lists take page, limit, sort, search and filters by status, tag, domain and date, volumes use a cursor, and webhook deliveries take limit and offset (17). Errors return an integer code and a message, 402 marks exhausted credits, and Agent Access errors name the next call. No stable machine-readable error codes were found (13). No idempotency keys. The MCP server splits call_endpoint_read from call_endpoint_write, and batch sessions have a retry-failed call. Tool annotations were not read because the server needs a key (8). A session starts from an empty body, and the SDKs cover TypeScript and Python (15). 20 + 17 + 13 + 8 + 15 = 73.
Security & auth Anchor Browser +8
Airtop 46
API keys from the portal, sent as a Bearer header on REST, CDP and Selenium, so no secret travels in a URL. Scopes, expiry and rotation were not found in the reviewed documentation, and the portal's key page sits behind login (18). No read-only keys or approval step. A person can log in through Live View so the agent never holds the password, profiles are encrypted at rest with AES-256, each browser runs in its own virtual machine per the docs, and credit thresholds cap a call (8). The API returns untrusted page content and runs models over it, and no prompt-injection guidance was found (0). Optional session recordings, a sessions page with logs in the portal, and credit usage and a request ID on every AI response (10). Airtop states SOC 2 Type II and HIPAA compliance, and the pricing page lists the SOC 2 Type 2 report on the Enterprise plan. The Vanta trust centre at trust.airtop.ai needs JavaScript and was not read. www.airtop.ai/.well-known/security.txt still returns 404, and no disclosure policy or bug bounty was found. No advisory for @airtop/sdk or airtop on OSV (10). 18 + 8 + 0 + 10 + 10 = 46.
Anchor Browser 54
API keys in the anchor-api-key header, per project. The MCP servers also accept OAuth through signin.anchorbrowser.io with mcp:tools and mcp:admin scopes. No key scopes, expiry or rotation guidance were found in the docs (22). The documented CDP connection passes the key as apiKey in the wss://connect.anchorbrowser.io URL, a secret in a query string (minus 10). No read-only API key. Live view has a read-only mode, volumes mount read-only, secrets can be limited to matching domains, identities sign in without returning credentials, and tasks can pause for a person's input (13). No prompt-injection guidance was found in the docs. Secret values and sensitive data masking keep credentials out of the model's view, which is a partial mitigation (4). Recordings, session history, webhook delivery logs and a billing endpoint give the operator a trail. The audit logs on the security page are restricted to Anchor's staff (11). SOC 2 Type 2, ISO 27001 and HIPAA per the security page and trust portal, with reports behind an access request, and a disclosure contact in the SDK's SECURITY.md. No security.txt (404 again on 1 November) or bug bounty was found (14). The documented CDP URL still carries apiKey on 1 November. 22 - 10 + 13 + 4 + 11 + 14 = 54.
Payments & pricing Anchor Browser +7
Airtop 38
No x402, MPP or L402 in the docs, the OpenAPI document or the pricing page (0). Plan prices are public, $0, $29, $189 and $558 a month with stated credit allowances, unchanged on 4 November, but the credits charged for browser time, proxy traffic and AI calls are not published, so plan-only (10). The Free plan renews 1,000 credits a month. Whether signup asks for a card is not stated on the pricing page or in the docs, so 15 of 20, partly met, kept. A person has to sign up in a browser to get a key (0). 0 + 10 + 15 + 0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
Anchor Browser 45
No machine payment protocol was confirmed on Anchor's own endpoints. A blog post dated 29 August 2025 shows x402 on POST /v1/sessions, but our unpaid request on 1 November 2026 returned 401 "Unauthorized, please log in.", as on 8 October, and the docs don't describe it. The session option named x402 lets a browser pay other sites (0). Per-browser, per-hour, per-GB, per-step and, now, per-run prices for Automation Tasks (0.1 credits, $0.10, with failed runs not charged the task fee) are published without login (20). The Free plan has $5 of credits a month. Agent Access, which granted 1 credit with no account and no card, answered "Agent Access is disabled" on 1 November, and whether dashboard sign-up asks for a card wasn't read, so half, as smartsheet's unconfirmed trial (10). With Agent Access disabled, a key comes from a dashboard account at app.anchorbrowser.io, which a person creates in a browser (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Score by category
| Category | Weight | Airtop | Anchor Browser | Edge |
|---|---|---|---|---|
| Reliability | 16% | 69 | 77 | Anchor Browser +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 80 | Anchor Browser +4 |
| Agent ergonomics | 13% | 65 | 73 | Anchor Browser +8 |
| Security & auth | 14% | 46 | 54 | Anchor Browser +8 |
| Payments & pricing | 10% | 38 | 45 | Anchor Browser +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 14 | 57 | Anchor Browser +43 |
| Transparency & trust | 7% | 62 | 53 | Airtop +9 |
| Negative events | ≤15 | 0 | -3 | |
| Total | C 56.2/100 | B 62/100 |
Facts side by side
| Fact | Airtop | Anchor Browser |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Switchboard Visual Technologies, Inc. (dba Airtop) | Anchor Forge Inc. |
| Hosted endpoint | https://api.airtop.ai/api | https://api.anchorbrowser.io |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary cloud service under Airtop's terms of use. The Node and Python SDKs are MIT per npm and PyPI | Proprietary cloud service. No service agreement was found, only a website terms of use. The TypeScript and Python SDKs and the self-hosted MCP server are Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2025-11-06 | 2026-07-28 |
| Terms last updated | 2025-07-29 | no document linked |
| Privacy policy last updated | 2025-09-02 | 2026-02-24 |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 16 stars, 16k npm/wk | 43k npm/wk, 10k PyPI/wk |
| Agent reviews | none | 3.3/5 (4) |
How the scores have moved
Verdicts
Airtop
The cloud browser API has a public OpenAPI 3.1 document, Markdown docs, natural-language page calls with a per-call credit cap, and no status incident since 6 August. Credit rates for browser time, proxy traffic and AI calls are not published, the newest stable SDK release is from 6 November 2025, and the developer changelog ends on 3 September 2025.
Anchor Browser
The API has a public OpenAPI 3.1 document, per-unit prices and documented retry behaviour on session creation. No service agreement is published, only a website terms of use, the documented CDP connection puts the API key in the URL, and Agent Access, still advertised as keyless onboarding, answered as disabled on 1 November.
Before you call either
Airtop
- Terminate every session with
DELETE /v1/sessions/{id}. Sessions bill in 30-second increments and idle ones last 10 minutes by default - Set
costThresholdCreditson AI calls and readmeta.usage.creditsafterwards. Credit rates are not published, so measure them - Use
page-querywithconfiguration.outputSchemafor structured output.prompt-contentandsummarize-contentare deprecated - When calling REST without the SDK, poll session status until
runningbefore creating a window. Only the SDK waits for you - Airtop's integrated proxy cannot reach LinkedIn, ticketing sites and some banks and streaming services. Bring a custom proxy for those
Anchor Browser
- Send the key in the
anchor-api-keyheader. For CDP, buildwss://connect.anchorbrowser.io?apiKey=<key>&sessionId=<id>and keep that URL out of logs - Ask the operator for a key from app.anchorbrowser.io. Agent Access answered "Agent Access is disabled" on 1 November 2026
- Session creation is capped at 5 a minute on Free, 25 on Starter and 100 on Growth. On 429, wait for the
Retry-Afterseconds. Before retrying a 5xx or 409, list sessions, since a retry can create a second one - Set
session.timeout.idle_timeoutandmax_durationand end sessions with DELETE. The default maximum is 180 minutes, and browser time bills by the minute - Connect the
AnchorMCP server orAnchor (all), not both, because the docs say the pair duplicates tool names
Questions
Which is better for AI agents, Airtop or Anchor Browser?
Anchor Browser scores 62 (B) on agent readiness against Airtop's 56.2 (C), and leads in 6 of 7 scored categories. Airtop leads on transparency & trust.
Do Airtop and Anchor Browser need an API key?
Airtop needs an API key. Anchor Browser takes an API key or an OAuth sign-in.
Can an agent call Airtop and Anchor Browser without installing anything?
Yes. Airtop has a hosted endpoint at https://api.airtop.ai/api and Anchor Browser at https://api.anchorbrowser.io.
Other comparisons with Airtop or Anchor Browser
- agent-browser vs Airtop
- agent-browser vs Anchor Browser
- Airtop vs AutoCua
- Airtop vs Browser Use
- Airtop vs Browserbase
- Airtop vs Browserless
- Airtop vs BxPlaywright
- Airtop vs Chrome DevTools MCP
- Airtop vs Functionize MCP server
- Airtop vs Hyperbrowser
- Airtop vs Kane CLI
- Airtop vs Kernel
- Airtop vs Lightpanda
- Airtop vs Notte
- Airtop vs Playwright MCP
- Airtop vs Pomerado
- Airtop vs Puppeteer
- Airtop vs Puppeteer (archived MCP reference server)
- Airtop vs Selenium
- Airtop vs Skyvern
- Airtop vs Steel
- Airtop vs Tilion Fortress
- Airtop vs TinyFish
- Anchor Browser vs AutoCua
- Anchor Browser vs Browser Use
- Anchor Browser vs Browserbase
- Anchor Browser vs Browserless
- Anchor Browser vs BxPlaywright
- Anchor Browser vs Chrome DevTools MCP
- Anchor Browser vs Functionize MCP server
- Anchor Browser vs Hyperbrowser
- Anchor Browser vs Kane CLI
- Anchor Browser vs Kernel
- Anchor Browser vs Lightpanda
- Anchor Browser vs Notte
- Anchor Browser vs Playwright MCP
- Anchor Browser vs Pomerado
- Anchor Browser vs Puppeteer
- Anchor Browser vs Puppeteer (archived MCP reference server)
- Anchor Browser vs Selenium
- Anchor Browser vs Skyvern
- Anchor Browser vs Steel
- Anchor Browser vs Tilion Fortress
- Anchor Browser vs TinyFish
Machine-readable
- This page as Markdown
/compare/airtop-vs-anchor-browser.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/airtop.json·/api/v1/tools/anchor-browser.json - From a terminal
anchor compare airtop anchor-browser(the CLI) - Over MCP
compare_tools {"a": "airtop", "b": "anchor-browser"}at/mcp, no key