# Browserless > Browserless runs hosted headless browsers that agents drive over CDP, Playwright, REST endpoints, BrowserQL or its official MCP server. The same software can be self-hosted from a Docker image. - Canonical: https://www.anchorterminal.com/tools/browserless - Markdown: https://www.anchorterminal.com/tools/browserless.md (~8,150 tokens) - Slim: https://www.anchorterminal.com/tools/browserless.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/browserless.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade BB · 70.4/100 · rank #128 of 629 · #4 in Browser automation · agent-ready · confidence medium** ## Assessment An OpenAPI document, llms.txt and a 14-tool MCP server with annotations on every tool make the service easy for an agent to read, and the free plan needs no card. The API token travels in the URL query string by default, cloud tokens carry no scopes, and no machine payment route exists. ## Facts | Field | Value | | --- | --- | | Vendor | browserless.io, Inc. (https://www.browserless.io) | | Kind | HTTP API | | Category | Browser automation (https://www.anchorterminal.com/categories/browser) | | Transport | HTTP, Streamable HTTP, stdio | | Endpoint | `https://production-sfo.browserless.io` | | Auth | OAuth or key · Self-serve API token from the account dashboard after signing up in a browser. REST, BrowserQL and WebSocket routes take it as `?token=` in the URL. The hosted MCP server accepts OAuth sign-in with a Browserless account, an `Authorization: Bearer` header, or `?token=` for URL-only clients. An account holds up to 20 named tokens, each shown once and revocable on its own. Cloud tokens have no scopes. The admin, developer and viewer token roles apply to self-hosted Enterprise containers only. | | Pricing | Freemium ($0.002 / credit) · Free with 1,000 units a month, 2 concurrent browsers and 2-minute sessions, no card. A unit is up to 30 seconds of browser time. Prototyping is $35 a month ($25 billed annually) with 20,000 units, then $0.0020 a unit. Starter is $200 ($140) with 180,000 units, then $0.0017. Scale is $500 ($350) with 500,000 units, then $0.0015. Enterprise and self-hosting licences are priced by sales. An agent can start on the free plan once a person has signed up (https://www.browserless.io/pricing, checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the docs (llms-full.txt), the OpenAPI document or the pricing page (checked 2026-10-08). The Stripe Link checkout tools are for an agent paying a merchant, not for paying Browserless. | | Licence | SSPL 1.0 or a commercial licence for the core server and the MCP server. The BAP TypeScript SDK is MIT. BrowserQL, stealth and other cloud additions are proprietary | | Tools exposed | 14 | | Packages | npm: `@browserless.io/mcp`; npm: `@browserless.io/bap-ts`; npm: `@browserless.io/browserless` | | Source | https://github.com/browserless/browserless | | Docs | https://docs.browserless.io | | llms.txt | https://docs.browserless.io/llms.txt | | Last release | 2026-10-05 | | GitHub stars | 13,786 (as of 2026-10-08) | | npm downloads / week | 3,484 | | Surfaces | REST endpoints (/screenshot, /pdf, /content, /scrape, /smart-scrape, /search, /map, /crawl, /agent/run), BrowserQL over GraphQL, CDP and Playwright WebSockets, and the MCP server. Graded here as the hosted cloud API with its hosted MCP server | | MCP server | Official, hosted at https://mcp.browserless.io/mcp (Streamable HTTP only) and on npm as @browserless.io/mcp 1.36.0 for stdio, Node.js 24 or newer. 14 documented tools, one stateful browser agent, eight stateless tools and five read-only account tools | | Free tier | 1,000 units a month, 2 concurrent browsers, 2-minute sessions, 1 day of replay storage, no card | | Limits | Concurrent browsers 2 on Free, 5 on Prototyping, 30 on Starter and 80 on Scale when billed monthly (10, 40 and 100 billed annually). Session length 2, 15, 30 and 60 minutes. No hourly or daily unit limit. 429 when concurrency and the queue are full | | Regions | San Francisco (production-sfo), London (production-lon) and Amsterdam (production-ams). Stored data stays in the United States on the shared fleet | | Billing rules | Requests rejected before a browser starts, such as a 429, cost nothing. A run that fails midway is charged for the browser time and proxy traffic used. An overage spend cap can be set in account settings | | Self-hosting | Docker images at ghcr.io/browserless for Chromium, Chrome, Firefox, WebKit and Edge under SSPL 1.0 or a commercial licence. Enterprise images add BrowserQL, stealth and session recording | | Machine payment | None. No x402, MPP or L402 found | | Capabilities | browser.control, browser.hosted, browser.debug, scraping.js-render, scraping.anti-bot, scraping.proxies, web.scrape, web.crawl, web.search, pdf.generate | | Tags | official, hosted, self-hosted, freemium, free-tier, no-card, mcp, oauth, openapi, llms-txt, typescript, source-available, commercial-licence, proxies, status-page, soc2 | | JSON | https://www.anchorterminal.com/api/v1/tools/browserless.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 82 | 16.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 89 | 14.5 | | Agent ergonomics | 13% | 16.2 | 78 | 12.7 | | Security & auth | 14% | 17.5 | 53 | 9.3 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 82 | 7.2 | | Transparency & trust (editorial 47, provenance 77) | 7% | 8.8 | 62 | 5.4 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **70.4 → BB** | ### Why each score - Reliability 82: Graded as a hosted service, on the cloud API and its hosted MCP server. status.browserless.io runs on Better Stack with eight monitored components and 90 days of daily history (20). The page lists no incident reports for August to October 2026. Its monitors record 129 minutes of downtime on Unit and Usage Services on 11 September 2026, 45 minutes on the Account API on 5 September, and 3 minutes on US East, with US West, London and Amsterdam at 100 per cent, so minor only (20). Concurrency and session-length limits are published per plan, 2 to 100 browsers and 2 to 60 minutes, and the docs say there is no hourly or daily unit limit (15). 429 is documented as a full concurrency slot or queue, with a retry and exponential backoff guide and advice to retry only operations that are safe to run twice. No Retry-After header or idempotency key was found in the reviewed documentation (12). One docs page claims a 99.9% uptime SLA and the site lists SLAs under Enterprise, but no SLA terms are published (5). The REST, WebSocket and MCP surfaces are generally available, with the MCP server at 1.36.0 (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 89: OpenAPI 3.0.0 at www.browserless.io/swagger.json with 87 paths and 100 operations, and Zod-typed inputs on every MCP tool in the source (25). llms.txt, llms-full.txt, a Markdown twin of every docs page, an API catalogue and an MCP server card under /.well-known (10). MCP descriptions state purpose and point to the right neighbour, for example `browserless_smartscraper` sends multi-page work to `browserless_crawl`. The agent tool's description is a long operating prompt (16). Inputs use enums and limits, but `browserless_function` takes free-form Puppeteer code and `browserless_agent` advertises a slimmed schema that the server re-validates at run time (12). Every OpenAPI operation lists 400, 401, 403, 404, 408, 429, 500 and 503, the docs carry an error table with fixes, and examples come in cURL, JavaScript and Python (13). A monthly product changelog and semver changelogs for the core (2.57.0) and MCP (1.36.0) repositories. REST paths carry no version (13). - Agent ergonomics 78: The full MCP server documents 14 tools (15), and a separate connector endpoint exposes five. The `browserless_agent` description is long, so we added back 5 of a possible 10 (20). `browserless_logs` pages by cursor, search, crawl and profiles take `limit`, crawl output is truncated per page, and Smart Scrape returns only the formats asked for (17). Errors come with a documented table of causes and fixes, a `requestId` that can be looked up in request logs, and `x-response-code` headers for the target site's status (16). Every MCP tool in the source carries `readOnlyHint` and `destructiveHint`, and account tools add `idempotentHint`. No idempotency keys, and the docs warn that a retried mutation can repeat a click or form submission (15). Few required parameters and existing Puppeteer or Playwright scripts connect by changing the endpoint, but the only published SDK is TypeScript. The docs say the Python SDK is not on PyPI yet (10). - Security & auth 53: An account holds up to 20 named API tokens, each shown once and revocable on its own, with a rotation guide. The hosted MCP server also accepts OAuth sign-in with PKCE. Cloud tokens have no scopes, and token roles apply only to self-hosted Enterprise containers (22). The docs give `?token=` in the URL as the standard way to authenticate REST and WebSocket calls and as an option for MCP, a secret in a query string (minus 10). The connector endpoint limits an assistant to five tools, account tools are read-only, the agent prompt tells the model to confirm controls marked destructive, and the draft Stripe Link checkout needs the buyer's approval for each purchase up to $50. No read-only token (10). Pages are untrusted content. Saved logins and card details are kept out of the model's context, but no prompt-injection guidance was found in the docs or the MCP agent prompt (3). Request logs record every request with endpoint, region, duration, error and cost, filterable by API key, and sessions can be replayed (13). SOC 2 Type II, third-party penetration tests and a disclosure policy with a 72-hour acknowledgement target on the trust centre. No security.txt and no bug bounty found (15). - Payments & pricing 40: No x402, MPP or L402 on any endpoint. The Stripe Link checkout tools let an agent pay a merchant and are not a way to pay Browserless (0). Plan prices, included units and per-unit overage rates of $0.0015 to $0.0020 are published without login, with the unit defined as up to 30 seconds of browser time (20). Free plan with 1,000 units a month, and the pricing page says no card is required (20). A person has to sign up in a browser to get a token or complete OAuth (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 82: @browserless.io/mcp 1.36.0 was published on 5 October 2026 and the core server 2.57.0 on 30 September (30). npm lists 32 stable MCP releases and 14 core releases since 10 July 2026, and the product changelog has an entry for each month from March to October 2026 (20). Both repositories show commits on 6 and 7 October 2026 and use release automation. GitHub's API refused our requests, so issue reply times went unread, and we scored the public changelogs and the support email only (12). The MCP server and the BAP TypeScript SDK (2.0.0) are current on npm, the Python SDK is unpublished, and the official MCP registry holds only a third-party entry for Browserless, so we scored the SDK line for an API (12). Test, lint, CodeQL and dependency-update workflows are in the repositories. We did not read their run results (8). - Transparency & trust 62: The core server and MCP server are source-available under SSPL 1.0, which is not an OSI licence, or a commercial licence, and the cloud additions are closed under published terms (18). The privacy policy says Browserless does not store page content and keeps only an email address, and names Stripe, SendGrid, DigitalOcean and Fathom. The trust centre, updated 11 September 2026, says request logs, session replays, saved profiles and crawl results are stored in the United States on AWS, DigitalOcean and Supabase, and the pricing page gives replay storage of 1 to 90 days. The two do not agree, the policy is undated, and a DPA is on Enterprise plans only (12). No deprecation policy. The terms allow the service to be changed or discontinued without notice, though the docs flag the v1 API and the chrome.browserless.io endpoint as deprecated (5). Execution regions and storage locations are stated in detail. The subprocessor list is on request by email (12). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/browserless.md (JSON https://www.anchorterminal.com/fixes/browserless.json) ### What we couldn't check - unchecked: GitHub issue counts and reply times. GitHub's API refused our requests for the rate limit, and the issues page did not give a count to our reader - unchecked: published security advisories for browserless/browserless. The advisories page did not render its list for our reader - unchecked: whether CI passes on the default branches. We read the workflow files, not their results - unchecked: the subprocessor list, which the trust centre says is available on request by email - No SLA terms were found. One docs page claims a 99.9% uptime SLA and the site lists SLAs under Enterprise - No Retry-After header, request-rate limit or idempotency key was found in the reviewed documentation - The status page lists no incident reports, though its monitors recorded downtime on 5 and 11 September 2026. We did not establish what those outages affected for customers - The source registers two Stripe Link tools beyond the 14 documented. The docs say they are a draft preview not yet enabled on the hosted fleet, so toolCount is 14 ### Sources - docs index for agents: (seen 2026-10-08) - full docs in one file: (seen 2026-10-08) - pricing: (seen 2026-10-08) - unit consumption: (seen 2026-10-08) - API token management: (seen 2026-10-08) - MCP server setup and tools: (seen 2026-10-08) - MCP connector endpoint: (seen 2026-10-08) - agentic checkout: (seen 2026-10-08) - retry and backoff guide: (seen 2026-10-08) - token roles, self-hosted: (seen 2026-10-08) - OpenAPI document: (seen 2026-10-08) - MCP server card: (seen 2026-10-08) - OAuth protected resource metadata: (seen 2026-10-08) - status page: (seen 2026-10-08) - status history feed: (seen 2026-10-08) - incident history: (seen 2026-10-08) - trust centre: (seen 2026-10-08) - terms of service: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - product changelog: (seen 2026-10-08) - MCP server source, tool definitions and changelog: (seen 2026-10-08) - core server source and changelog: (seen 2026-10-08) - npm, MCP server: (seen 2026-10-08) - npm, core server: (seen 2026-10-08) - npm weekly downloads: (seen 2026-10-08) - MCP registry search: (seen 2026-10-08) - security.txt, 404: (seen 2026-10-08) - RDAP record: (seen 2026-10-08) ## Who's behind it (provenance 77/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | browserless.io, Inc. | 20/20 | | Domain age | browserless.io, registered 2017-09-06 (9 years) | 11/15 | | Endpoint on the vendor's domain | production-sfo.browserless.io | 15/15 | | Terms of service | read, states 5 of the 7 things a reader expects, and has 2 clauses that cost points | 4.3/10 | | Privacy policy | read, states 3 of the 8 things a reader expects | 6.3/10 | | Status page | status.browserless.io | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The terms of service name browserless.io, Inc., 23207 NE 192nd Ct, Battle Ground, WA 98604, United States. Neither the terms nor the privacy policy carries a date. www.browserless.io/.well-known/security.txt and docs.browserless.io/.well-known/security.txt both return 404. The trust centre sends vulnerability reports to security@browserless.io. RDAP for browserless.io gives a registration date of 2017-09-06. The API answers at production-sfo, production-lon and production-ams.browserless.io and the MCP server at mcp.browserless.io. The OAuth metadata at data.browserless.io names a supabase.co issuer. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.browserless.io/terms-of-service), read 2026-10-08, gives no date, states 5 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "(i) to spam, phish, pharm, pretext, spider, crawl, or scrape;" - To know. Says the terms or the service can change without notice (costs points). "We reserve the right at any time to modify or discontinue the Service (or any part or content thereof) without notice at any time." - To know. Says access can be ended without notice or for any reason. "You agree that from time to time we may remove the service for indefinite periods of time or cancel the service at any time, without notice to you." - Not found in the text. Gives the date it was last updated. - States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence. - Says how changes to the terms are announced. Changes are posted, with no other notice named. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Customer content other than credit card information may be transferred unencrypted across networks. "You understand that your content (not including credit card information), may be transferred unencrypted and involve (a) transmissions over various networks; and (b) changes to conform and adapt to technical requirements of connecting networks or devices." - Also in the text (2026-10-08). Prices can change without notice, and Browserless accepts no liability for a price change. "Prices for our products are subject to change without notice." **Privacy policy** (https://www.browserless.io/privacy-policy), read 2026-10-08, gives no date, states 3 of the 8 things a reader expects. - Not found in the text. Gives the date it was last updated. - Not found in the text. Says how long data is kept. - Not found in the text. Says what rights people have over their data. - Not found in the text. Gives a privacy contact. - Not found in the text. Says where data is transferred or stored. - Also in the text (2026-10-08). The policy says Browserless does not monitor, store, retain or resell the content of pages visited in sessions, and keeps session metrics only for a short time. "Browserless does not monitor, store, retain, or resell the content of the pages you visit or the detailed nature of your sessions." - Also in the text (2026-10-08). The stored email address is destroyed automatically once the account is cancelled and the billing period has expired. "When you cancel your account, and the billing period expires, we automatically destroy this information so it isn't kept around." ## Live (updated 2026-10-08 17:36 UTC) - Right now: up, HTTP 401, 448 ms, checked 2026-10-08 17:36 UTC (get on `https://production-sfo.browserless.io`, asks for auth) - Uptime 24h 100.0% (25 probes) · 30 days 100.0% (25 probes) · p50 444 ms · p95 507 ms - Vendor status page: unknown, no machine-readable status found - github `browserless/browserless` v2.57.0, released 2026-09-30 - npm `@browserless.io/bap-ts` 2.0.0 - npm `@browserless.io/browserless` 2.57.0 - npm `@browserless.io/mcp` 1.36.0 - security.txt: none - Always current: https://www.anchorterminal.com/api/v1/live/browserless.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Unit overage, Prototyping plan | $0.002 | per credit | One unit is up to 30 seconds of browser time | | Unit overage, Starter plan | $0.0017 | per credit | | | Unit overage, Scale plan | $0.0015 | per credit | | | Browser time at the overage rate, Prototyping plan | $0.24 | per browser-hour | Our arithmetic, 120 units at $0.0020 | | Browser time at the overage rate, Starter plan | $0.204 | per browser-hour | Our arithmetic, 120 units at $0.0017 | | Browser time at the overage rate, Scale plan | $0.18 | per browser-hour | Our arithmetic, 120 units at $0.0015 | | Prototyping plan | $35 | per month (plan) | 20,000 units, $25 a month billed annually | | Starter plan | $200 | per month (plan) | 180,000 units, $140 a month billed annually | | Scale plan | $500 | per month (plan) | 500,000 units, $350 a month billed annually | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - OpenAPI 3.0.0 document with 87 paths, llms.txt, llms-full.txt and Markdown twins of the docs - Hosted MCP server at mcp.browserless.io with 14 documented tools, each carrying read-only and destructive annotations - Free plan with 1,000 units a month and no card, with per-unit overage prices published for paid plans - Up to 20 named API tokens per account, each revocable on its own, plus request logs filterable by key - MCP server released 32 times between 10 July and 5 October 2026, with a dated changelog in the repository ## Weaknesses - REST and WebSocket routes take the API token as `?token=` in the URL, which the docs give as the standard method - Cloud tokens have no scopes or roles. Token roles exist only on self-hosted Enterprise containers - No x402, MPP or L402, and an account needs a person to sign up in a browser - No prompt-injection guidance found in the docs or in the MCP agent prompt - The terms allow the service to be changed or discontinued without notice, and the subprocessor list is on request only ## Before you call it (notes for agents) 1. Send the token as `Authorization: Bearer` to the MCP server. On REST and WebSocket routes it goes in `?token=`, so keep those URLs out of logs 2. Close sessions as soon as the work is done. Browser time bills one unit per 30 seconds, rounded up, idle or not 3. For multi-step work with `browserless_agent`, set `keepSessionAlive: true` on the first call and pass the returned `sessionId` after that. Sessions are one-shot by default since server 1.33.0 4. On 429, back off and retry. It means the plan's concurrency limit or queue is full, usually from sessions left open 5. Match the path to the protocol. Use `/chromium` for CDP clients and `/chromium/playwright` only for `playwright.connect()` ## Connect Install: ```bash npx -y @browserless.io/mcp ``` First request: ```bash curl -X POST "https://production-sfo.browserless.io/screenshot?token=YOUR_API_TOKEN_HERE" -H "Content-Type: application/json" -d '{"url": "https://scraping-sandbox.netlify.app/dashboard"}' -o response.png ``` Claude Code: ```bash claude mcp add --transport http browserless https://mcp.browserless.io/mcp --header "Authorization: Bearer YOUR_API_TOKEN_HERE" ``` MCP client configuration: ```json { "mcpServers": { "browserless": { "headers": { "Authorization": "Bearer YOUR_API_TOKEN_HERE" }, "type": "http", "url": "https://mcp.browserless.io/mcp" } } } ``` Through letme (picks today, calling later): https://letme.dev/browserless (letme picks it for pdf.generate, the top-graded tool for the job). letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Spider | BB | 74.1 | 64 | web.scrape, web.crawl, web.search, browser.hosted, scraping.proxies, scraping.js-render, scraping.anti-bot | yes | https://www.anchorterminal.com/tools/spider-cloud.md | | Steel | BB | 70.4 | 129 | browser.control, browser.hosted, browser.debug, web.scrape, scraping.proxies, scraping.anti-bot, pdf.generate | yes | https://www.anchorterminal.com/tools/steel.md | | Anchor Browser | B | 67.3 | 196 | browser.control, browser.hosted, browser.debug, web.scrape, scraping.proxies, scraping.anti-bot, pdf.generate | no | https://www.anchorterminal.com/tools/anchor-browser.md | | Scrapeless | C | 54.1 | 472 | web.scrape, web.crawl, web.search, browser.hosted, scraping.proxies, scraping.js-render, scraping.anti-bot | no | https://www.anchorterminal.com/tools/scrapeless.md | | Scrapfly | B | 69.6 | 143 | web.scrape, web.crawl, browser.hosted, scraping.proxies, scraping.js-render, scraping.anti-bot | no | https://www.anchorterminal.com/tools/scrapfly.md | | ScrapeGraphAI | B | 68.3 | 175 | web.scrape, web.crawl, web.search, scraping.proxies, scraping.js-render, scraping.anti-bot | no | https://www.anchorterminal.com/tools/scrapegraphai.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Official MCP server, hosted at https://mcp.browserless.io/mcp over Streamable HTTP and published as @browserless.io/mcp for stdio, with OAuth sign-in or a Bearer token (source: ) - A second MCP endpoint, https://mcp.browserless.io/mcp/connector, exposes five tools for assistant directories (source: ) - A unit is up to 30 seconds of browser time. Residential proxy traffic costs 6 units a MB, datacentre proxy 2 units a MB and a solved CAPTCHA 10 units (source: ) - The core server and the MCP server are published on GitHub under SSPL 1.0 or a commercial licence. BrowserQL, stealth and CAPTCHA solving are in the cloud and Enterprise builds only (source: ) - Agentic Checkout with Stripe Link is a draft preview that the docs say is not yet enabled on the hosted fleet. Purchases are capped at $50 and each needs the buyer's approval (source: ) - The trust centre, last updated 11 September 2026, says stored data such as request logs, session replays and saved profiles stays in the United States whichever regional endpoint is used (source: ) - Discovery files are published at /.well-known/api-catalog, /.well-known/mcp/server-card.json and /.well-known/agent-skills/index.json (source: ) ## Compare - [Airtop vs Browserless](https://www.anchorterminal.com/compare/airtop-vs-browserless.md): C 55.3 vs BB 70.4 - [Anchor Browser vs Browserless](https://www.anchorterminal.com/compare/anchor-browser-vs-browserless.md): B 67.3 vs BB 70.4 - [Browser Use vs Browserless](https://www.anchorterminal.com/compare/browser-use-vs-browserless.md): BB 77.9 vs BB 70.4 - [Browserless vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/browserless-vs-chrome-devtools-mcp.md): BB 70.4 vs BB 77 - [Browserless vs Hyperbrowser](https://www.anchorterminal.com/compare/browserless-vs-hyperbrowser.md): BB 70.4 vs B 66.9 - [Browserless vs Notte](https://www.anchorterminal.com/compare/browserless-vs-notte.md): BB 70.4 vs B 63.2 - [Browserless vs Playwright MCP](https://www.anchorterminal.com/compare/browserless-vs-playwright-mcp.md): BB 70.4 vs B 67.6 - [Browserless vs Puppeteer (archived MCP reference server)](https://www.anchorterminal.com/compare/browserless-vs-puppeteer-reference-server-archived.md): BB 70.4 vs F 30.6 - [Browserless vs Skyvern](https://www.anchorterminal.com/compare/browserless-vs-skyvern.md): BB 70.4 vs B 63.1 - [Browserless vs Steel](https://www.anchorterminal.com/compare/browserless-vs-steel.md): BB 70.4 vs BB 70.4 - [Browserbase vs Browserless](https://www.anchorterminal.com/compare/browserbase-vs-browserless.md): BB 76.2 vs BB 70.4 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on browserless.io or one of its subdomains, or the README of github.com/browserless/browserless. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "browserless", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Browserless on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Browserless on Anchor Terminal](https://www.anchorterminal.com/badges/browserless.svg)](https://www.anchorterminal.com/tools/browserless) ``` Plain link: ```html Browserless on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Browserless is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/browserless-dark.png - Light: https://www.anchorterminal.com/assets/share/browserless-light.png