# BrowserAct vs Scrape.do (slim)

> BrowserAct and Scrape.do score within a point of each other for scraping, 44.4 and 44 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/browseract-vs-scrape-do.md (~4,650 tokens) · this version ~2,080 tokens · JSON https://www.anchorterminal.com/compare/browseract-vs-scrape-do.json · canonical https://www.anchorterminal.com/compare/browseract-vs-scrape-do
- 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)

BrowserAct and Scrape.do score within a point of each other on agent readiness, 44.4 (E) and 44 (E). Scrape.do leads on reliability, agent ergonomics, payments & pricing and transparency & trust. Both do scraping.

- BrowserAct: E 44.4, rank #1204 of 1486 · https://www.anchorterminal.com/tools/browseract.min.md
- Scrape.do: E 44, rank #1219 of 1486 · https://www.anchorterminal.com/tools/scrape-do.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 57; Security & auth, 41 against 23; Maintenance & community, 61 against 45.
- Scrape.do, good for Cheap bulk fetching through rotating proxies when you call HTTP directly and keep the token server-side. Ahead on Reliability, 40 against 23; Agent ergonomics, 62 against 49; Payments & pricing, 35 against 25; Transparency & trust, 49 against 44. Also Free to start without a card.

| Category | BrowserAct | Scrape.do |
| --- | --- | --- |
| Reliability (16%) | 23 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 76 | 57 |
| Agent ergonomics (13%) | 49 | 62 |
| Security & auth (14%) | 41 | 23 |
| Payments & pricing (10%) | 25 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 61 | 45 |
| Transparency & trust (7%) | 44 | 49 |

| Fact (where they differ) | BrowserAct | Scrape.do |
| --- | --- | --- |
| Vendor | Hongkong Ziniao Technology Co., Limited | Scrape.do |
| Hosted endpoint | `https://mcp.browseract.com/mcp/` | `https://api.scrape.do/` |
| Transports | Streamable HTTP | HTTP |
| Last release | 2026-11-05 | 2026-07-31 |
| Terms last updated | 2025-05-15 | no date given |
| Privacy policy last updated | 2025-05-15 | no date given |
| Popularity | none | 2 npm/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Schema & documentation, BrowserAct +19: 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.); Scrape.do 57 (No OpenAPI file found (0 of 25). llms.txt at scrape.do/documentation/llms.txt with Markdown pages (10). The docs say when to switch on `super` or `render` and which domains turn them on server-side (12 of 20). Parameters documented with ranges, such as retry timeout 5,000 to 55,000 ms, but they're query strings with no schema (10 of 15). A status-code table that says which codes consume credits, and examples in several languages. The error body format isn't documented (13 of 15). Dated public changelog, no API versioning (12 of 15).)
- Security & auth, BrowserAct +18: BrowserAct 41 (One account-wide API key type, revocable and listed with last-used time, but without scopes or expiry (18). Confirmation Required mode holds purchases and asset creation or deletion for approval in the BrowserAct page (14). Scraped pages are untrusted, and no prompt-injection guidance was found (3). Keys show last use and runs keep logs (6). No security page, disclosure policy, certification or bug bounty found (0). 18 + 14 + 3 + 6 + 0 = 41.); Scrape.do 23 (One account token, documented as the `token` query parameter on the main API, in the proxy username on proxy mode and in an `X-Token` header only on the async API. We found no scopes or rotation for it. Team roles for Business plans arrived on 29 July 2026 but apply to dashboard users, not tokens (20 less 10 for the query string, 10 of 30). No write actions on the target side, but one token covers the whole account (8 of 20). Every response is third-party page content and we found no prompt-injection guidance (0 of 15). Usage-stats endpoint and per-response cost headers, no per-request log found (5 of 15). No security.txt, security page or disclosure policy found. Proxy mode needs Scrape.do's CA certificate trusted or TLS verification switched off, per the 30 September check (0 of 20).)
- Reliability, Scrape.do +17: 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.); Scrape.do 40 (No public status page. status.scrape.do returned 403 to our fetch again today, as it did on 30 September, and the site doesn't link it (0). No readable incident history, so 5 by the rubric (5). Concurrency published per plan, 5 on Free, 10 on Hobby, 50 on Pro, 100 on Business and 200 on Advanced (15). A 429 means the concurrency limit was hit and isn't billed, a 502 says to try again, and the service retries failed requests itself unless `disableRetry=true`, but there's no Retry-After or backoff guidance (10 of 15). No SLA on the pricing page, which claims a 99.98 per cent success rate instead (0). GA (10).)
- Maintenance & community, BrowserAct +16: 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.); Scrape.do 45 (Last changelog entry on 31 July 2026, a Gemini scraper API (20). Two dated entries since 3 July, 29 and 31 July, against the three the rubric asks for (10 of 20). Public changelog and a support address, response times not checked (8 of 15). The only official SDK, @scrape-do/client, hasn't shipped since 13 November 2024 (5 of 15). No public repository or CI to check (2 of 10).)
- Agent ergonomics, Scrape.do +13: 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.); Scrape.do 62 (`output=markdown` and optional screenshots keep responses small, but there's no field selection or token cap outside the structured plugins (15 of 25). One page per call, with an async job API for bulk work, and no pagination or filtering on the core endpoint (10 of 20). Status codes documented with billing behaviour (15 of 20). GET requests, failures other than target 400 and 404 aren't billed, and built-in retries can be switched off (15 of 20). Two required parameters, but the only official SDK is the Node client last released on 13 November 2024 (7 of 15).)
- Payments & pricing, Scrape.do +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.); Scrape.do 35 (No x402, MPP or L402. The pricing page lists card, crypto and bank wire (0). Credit costs per request type and per domain are public, but credits come only with monthly plans, with no pay-as-you-go (15 of 20). Free plan, 1,000 successful requests a month with every feature, no card (20). A person signs up in a browser to get a token (0).)