# BrowserAct vs Scrapeless (slim)

> Scrapeless scores 55.9 (C) to BrowserAct's 44.4 (E) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

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

Scrapeless scores 55.9 (C) on agent readiness against BrowserAct's 44.4 (E), and leads in 5 of 7 scored categories. BrowserAct leads on schema & documentation. Both do scraping.

- BrowserAct: E 44.4, rank #1204 of 1486 · https://www.anchorterminal.com/tools/browseract.min.md
- Scrapeless: C 55.9, rank #847 of 1486 · https://www.anchorterminal.com/tools/scrapeless.min.md
- BrowserAct, good for Teams that want no-code, prompt-built scrapers an agent can rerun on a schedule. Ahead on Schema & documentation, 76 against 66.
- Scrapeless, good for An agent that needs one key for unlocking, a remote browser and AI answer-engine scraping. Ahead on Reliability, 70 against 23; Payments & pricing, 35 against 25; Maintenance & community, 81 against 61; Transparency & trust, 58 against 44. Also Runs on your own machine; Free to start without a card.

| Category | BrowserAct | Scrapeless |
| --- | --- | --- |
| Reliability (16%) | 23 | 70 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 76 | 66 |
| Agent ergonomics (13%) | 49 | 50 |
| Security & auth (14%) | 41 | 37 |
| Payments & pricing (10%) | 25 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 61 | 81 |
| Transparency & trust (7%) | 44 | 58 |

| Fact (where they differ) | BrowserAct | Scrapeless |
| --- | --- | --- |
| Vendor | Hongkong Ziniao Technology Co., Limited | Scrapeless (NST Labs Tech) |
| Hosted endpoint | `https://mcp.browseract.com/mcp/` | `https://api.scrapeless.com` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Pricing | Freemium | Pay per use |
| Licence | none | MIT |
| Tools exposed | none | 25 |
| MCP registry | not listed | `io.github.scrapeless-ai/scrapeless-mcp-server` |
| Last release | 2026-11-05 | 2026-09-16 |
| Terms last updated | 2025-05-15 | no date given |
| Privacy policy last updated | 2025-05-15 | no date given |
| Terms restrict automated access | yes | not found in the text |
| Popularity | none | 169 stars, 423 npm/wk, 216 PyPI/wk |
| Agent reviews | none | 2/5 (2) |

Why the edge:
- Reliability, Scrapeless +47: BrowserAct 23 (Hosted reading. No status page found (0) and no readable incident history (5). The docs say there are no rate limits, and give concurrency by plan (2 free, up to 20 for paid API users) and a 7-hour task cap (8). No 429 or retry guidance, and no idempotency keys on task creation (0). No SLA (0). No beta label on the API or MCP server (10). 0 + 5 + 8 + 0 + 0 + 10 = 23.); Scrapeless 70 (Better Stack status page at status.scrapeless.com with four groups, Scrapeless API, Scraping Browser, website and dashboard, and residential proxies (20). Every monitor shows 100 per cent uptime over 90 days and the incident list reports none for September, October or November 2026. The list doesn't page back to August, so the earlier clean reading for August is kept (30). No rate-limit numbers found in the docs. The 30 September concurrency figures came from a script-loaded price file and are struck (0). The Results and Polling page documents 429 as rate limit exceeded with reduce-frequency guidance and a one-minute wait for 500s, with no idempotency keys (10). The pricing page names an Enterprise-level SLA but no SLA document is published (0). The APIs are generally available (10). 20 + 30 + 0 + 10 + 0 + 10 = 70.)
- Maintenance & community, Scrapeless +20: BrowserAct 61 (browser-act-cli 1.6.2 on 5 November 2026, read from PyPI's release feed (30). Six CLI releases from 15 October to 5 November (20). A closed service with a support address, but no public changelog or issue tracker found (8). No official SDKs and no entry in the official MCP registry (0). The CLI package carries no licence or repository in its metadata (3). 30 + 20 + 8 + 0 + 3 = 61.); Scrapeless 81 (The official CLI (scrapeless on npm, its own repository) tagged v0.1.0 on 2026-10-20 (30). In the 90 days from 6 August, MCP server v0.5.0 (20 August), v0.6.0 (28 August), v0.6.1 (2 September) and v0.6.3 (8 September), Node SDK v1.12.0 and v1.12.1, Python SDK v1.3.0 and Go SDK v1.3.0 (16 September) and the CLI (20). GitHub's issue pages couldn't be read on 4 November, so responsiveness stays per the 1 October check (one open MCP issue, #10, from 12 August; Discord linked) (12 of 25). Node, Python and Go SDKs are current (15). No CI workflow in the MCP repo; the CLI has one, and the MCP pins @modelcontextprotocol/sdk at ^1.8.0 (4 of 10). 30 + 20 + 12 + 15 + 4 = 81.)
- Transparency & trust, Scrapeless +14: BrowserAct 44 (Closed service with published terms naming the operating company and governing law (15). The privacy policy of 15 May 2025 states retention by category and that crawled data is kept per plan and deletable by the user (15). No deprecation policy or notices found (0). No sub-processors or data locations named (3). 15 + 15 + 0 + 3 = 33.); Scrapeless 58 (The MCP server is open source but the LICENSE file says MIT while package.json says ISC. The API is closed, and the terms name NST LABS TECH LTD. with no address or governing law (15 of 30). The privacy policy gives no retention periods beyond tokens kept 24 hours. The Data Processing Agreement (v1.0, effective 7 August 2026, linked from the terms) covers sub-processor notice, SCCs for EEA transfers and deletion on termination, with no retention periods for scraped data (14 of 30). No deprecation policy or dated notices found (0). The DPA's Exhibit 2 names two sub-processors, Airwallex and Intercom, both in the United States, and no hosting location (10 of 20). 15 + 14 + 0 + 10 = 39.)
- Schema & documentation, BrowserAct +10: BrowserAct 76 (An OpenAPI 3.0.3 document behind the API reference (25). llms.txt on both the site and the docs, with Markdown pages (10). Endpoint descriptions explain the run flow (find a bot, read its input_schema, then run) and when to use the lighter status endpoint (14). Inputs are typed, but a run's input is an object shaped by each bot's own schema (10). Examples per endpoint and named error codes such as 10879 and 10127; no full error table found (10). The path carries v3, but no changelog was found (7). 25 + 10 + 14 + 10 + 10 + 7 = 76.); Scrapeless 66 (No OpenAPI spec found. The API reference at apidocs.scrapeless.com lists about 30 schema definitions in its llms.txt, and the 25 MCP tools have typed zod inputs, one of which (crawl_start scrapeOptions) takes a free-form record (15 of 25). llms.txt with Markdown pages for every endpoint (10). MCP descriptions carry Restrictions, Valid and Invalid lines for most tools, though google_search's description is a run-on fragment (15 of 20). Inputs are typed with URL validation and some enums, plus the one free-form record (11 of 15). Request examples on each reference page, but no documented error responses or error code list found (7 of 15). Versioned API paths (v1, v2) and a CHANGELOG.md in the MCP repo, but no product changelog (8 of 15).)
- Payments & pricing, Scrapeless +10: BrowserAct 25 (No x402, MPP or L402 (0). Plan prices and credit costs per bot build, run and workflow step are public, but there is no direct per-call price (15). A free plan with 200 credits; whether it needs a card isn't stated (10). A person signs up and creates the key in the dashboard (0). 0 + 15 + 10 + 0 = 25.); Scrapeless 35 (No x402, MPP or L402. Crypto top-ups exist but aren't a machine payment protocol (0). The pricing page draws its rate tables by script. The docs publish per-unit rates, Crawl from $1.8 a GB plus $0.09 a browser hour and Web Unlocker from $0.20 per 1,000 URLs, and the Google Search API page gives volume rates below $0.50 per 1,000 on qualifying plans, but no full rate card is readable without script (15 of 20, a partial kept under the in-between rule). The Google Search API page says no credit card is required to start (20). A person signs up in a browser (0). 0 + 15 + 20 + 0 = 35.)