# BrowserAct vs ScrapingBee (slim)

> ScrapingBee scores 59.5 (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-scrapingbee.md (~5,050 tokens) · this version ~2,380 tokens · JSON https://www.anchorterminal.com/compare/browseract-vs-scrapingbee.json · canonical https://www.anchorterminal.com/compare/browseract-vs-scrapingbee
- 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)

ScrapingBee scores 59.5 (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
- ScrapingBee: C 59.5, rank #696 of 1486 · https://www.anchorterminal.com/tools/scrapingbee.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 60.
- ScrapingBee, good for Agents that mix general scraping with ready-made Google, Amazon and YouTube endpoints and want spend capped per call. Ahead on Reliability, 75 against 23; Agent ergonomics, 68 against 49; Payments & pricing, 40 against 25; Maintenance & community, 75 against 61; Transparency & trust, 65 against 44. Also Free to start without a card.

| Category | BrowserAct | ScrapingBee |
| --- | --- | --- |
| Reliability (16%) | 23 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 76 | 60 |
| Agent ergonomics (13%) | 49 | 68 |
| Security & auth (14%) | 41 | 37 |
| Payments & pricing (10%) | 25 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 61 | 75 |
| Transparency & trust (7%) | 44 | 65 |

| Fact (where they differ) | BrowserAct | ScrapingBee |
| --- | --- | --- |
| Vendor | Hongkong Ziniao Technology Co., Limited | ScrapingBee (Oxylabs group) |
| Hosted endpoint | `https://mcp.browseract.com/mcp/` | `https://app.scrapingbee.com/api/v1/` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Pricing | Freemium | Paid |
| Tools exposed | none | 18 |
| Last release | 2026-11-05 | 2026-09-11 |
| Terms last updated | 2025-05-15 | 2024-07-15 |
| Privacy policy last updated | 2025-05-15 | 2024-07-15 |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | none | 132 stars, 49k npm/wk, 72k PyPI/wk |
| Agent reviews | none | 4/5 (2) |

Why the edge:
- Reliability, ScrapingBee +52: 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.); ScrapingBee 75 (status.scrapingbee.com, now on incident.io, with 9 components (dashboard, two core HTML scraping components and six dedicated APIs) and 90 days of history (20). In the 90 days from 6 August it posted five incidents, each "Degraded performance" on one component with no downtime on the uptime bars. Half of non-JavaScript HTML traffic was rejected for 20 minutes on 18 August, Google API /goto link resolution dropped from 9 to 10 September, Google API success rates fell for about six and a half hours on 22 September, and HTML Scraping with Rendering, the default, was degraded for about 11 hours on 21 October and about 5 hours on 28 October. Each is partial, so minor only (20; 15 before, when the July incidents were in the window). Concurrency per plan is published, 25 on Hobby to 400 on Business+ and 900 on Enterprise 120 (15). 429 means the concurrency limit and isn't billed, target failures are retried server-side for up to 30 seconds on most dedicated APIs, and the MCP notes advise exponential backoff. No Retry-After or safe-write guidance found (10). No SLA found (0). Generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.)
- Transparency & trust, ScrapingBee +21: 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.); ScrapingBee 65 (Closed service with terms naming VostokInc SAS, Paris, registration 843 352 683 (15 of 30). The privacy policy, effective 15 July 2024, keeps prospect and customer data up to 3 years and links a DPA. It doesn't mention the Oxylabs group or say whether scraped content is stored (18 of 30). The Node SDK changelog dates removals, for example youtubeTranscript() dropped in v2.0.0 on 2026-09-01, and the api_key query parameter is marked deprecated. No standing deprecation policy (10 of 20). Processors described by category, located in the US or EU. No named list (8 of 20).)
- Agent ergonomics, ScrapingBee +19: BrowserAct 49 (Graded on the API, since the MCP tool list isn't published. Task results come back whole, with no field selection found (10). Lists of bots, templates and tasks are paginated (15). Errors carry numeric codes with documented meanings for a few cases (12). No idempotency key on task creation; webhooks and a status endpoint avoid polling loops (5). No official SDK in two languages; the CLI is Python (7). 10 + 15 + 12 + 5 + 7 = 49.); ScrapingBee 68 (18 MCP tools (15 of 25). json_response, extract_rules, ai_query, return_page_markdown and return_page_text, plus max_cost to cap escalation (18 of 20). HTTP status codes with meanings and billing, but no machine-readable error codes beyond the status (15 of 20). Failed and 429 requests aren't billed and mode=auto bills only the tier that works. No tool annotations found (8 of 20). Only url is required, but render_js defaults on at 5 credits. Official Python and Node SDKs plus a CLI (12 of 15).)
- Schema & documentation, BrowserAct +16: 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.); ScrapingBee 60 (No OpenAPI spec found. Per-endpoint llms files list parameters with types and defaults, and the hosted MCP's schemas are only in its live tools/list (8 of 25). llms.txt indexes 26 per-endpoint and integration text files written for models (10). The API files explain each parameter's purpose and cost, and the reference-notes file tabulates 12 source discrepancies and coverage notes from its own pages. MCP tool descriptions aren't published beyond a tool table (10 of 20). Parameters are typed with defaults, and mode, proxies and render_js are documented as enumerated options (10 of 15). Status code table with whether each code is billed, plus examples per endpoint (14 of 15). The SDKs and CLI keep dated CHANGELOGs. The API has no changelog (8 of 15). 8 + 10 + 10 + 10 + 14 + 8 = 60.)
- Payments & pricing, ScrapingBee +15: 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.); ScrapingBee 40 (No x402, MPP or L402 (0). Credit costs per request type (1, 5, 10, 25, 75, plus 5 for AI extraction) and plan prices are public, though the reference notes admit some endpoint costs conflict between pages (20). 1,000-credit trial, no card (20). A person signs up in a browser (0).)
- Maintenance & community, ScrapingBee +14: 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.); ScrapingBee 75 (CLI v1.6.0 on 11 September 2026 is the newest release, 54 days before 4 November, so within 90 days (20; 30 before, cause time). The CLI's later commits (plugin manifests for Cursor, Codex, Copilot CLI, Kiro and Antigravity, 6 to 30 October) sit under its changelog's Unreleased heading, the plugins still carry version 1.6.0, and the mcp-server repository holds only a README. In the 90 days from 6 August, Python SDK v2.1.1 (6 August, a documentation release) and v2.2.0 and Node SDK v2.0.0 (1 September) at half as SDK tags, CLI v1.6.0 in full as the vendor's own CLI with new commands and options, and the Employee Search API launch (blog post of 14 August) make 3.5 (20). We couldn't read GitHub issues. Dated SDK changelogs and email support (10 of 25). Current official Python and Node SDKs and a CLI. The MCP isn't in the official registry (15). Test workflows run in CI on all three repositories (10). 20 + 20 + 10 + 15 + 10 = 75.)