# BrowserAct vs Scrapfly (slim)

> Scrapfly scores 74.5 (BB) 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-scrapfly.md (~5,450 tokens) · this version ~2,830 tokens · JSON https://www.anchorterminal.com/compare/browseract-vs-scrapfly.json · canonical https://www.anchorterminal.com/compare/browseract-vs-scrapfly
- 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)

Scrapfly scores 74.5 (BB) on agent readiness against BrowserAct's 44.4 (E), and leads in every scored category. Both do scraping.

- BrowserAct: E 44.4, rank #1204 of 1486 · https://www.anchorterminal.com/tools/browseract.min.md
- Scrapfly: BB 74.5, rank #84 of 1486 · https://www.anchorterminal.com/tools/scrapfly.min.md
- BrowserAct, good for Teams that want no-code, prompt-built scrapers an agent can rerun on a schedule. Also No incidents deducted, where Scrapfly loses 3 points for them.
- Scrapfly, good for An agent that needs scrape, screenshot, extraction, crawl and a hosted browser from one key, with errors it can branch on. Ahead on Reliability, 85 against 23; Schema & documentation, 95 against 76; Agent ergonomics, 80 against 49; Security & auth, 75 against 41; Payments & pricing, 40 against 25; Maintenance & community, 84 against 61; Transparency & trust, 75 against 44. Also Agent-ready, a grade of BB or better; Runs on your own machine; Free to start without a card.

| Category | BrowserAct | Scrapfly |
| --- | --- | --- |
| Reliability (16%) | 23 | 85 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 76 | 95 |
| Agent ergonomics (13%) | 49 | 80 |
| Security & auth (14%) | 41 | 75 |
| Payments & pricing (10%) | 25 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 61 | 84 |
| Transparency & trust (7%) | 44 | 75 |

| Fact (where they differ) | BrowserAct | Scrapfly |
| --- | --- | --- |
| Vendor | Hongkong Ziniao Technology Co., Limited | Scrapfly (Joam Intelligence, LLC) |
| Hosted endpoint | `https://mcp.browseract.com/mcp/` | `https://api.scrapfly.io/scrape` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Tools exposed | none | 62 |
| MCP registry | not listed | `io.scrapfly.mcp/mcp` |
| Last release | 2026-11-05 | 2026-10-15 |
| Terms last updated | 2025-05-15 | 2026-09-30 |
| Privacy policy last updated | 2025-05-15 | 2026-05-14 |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Popularity | none | 14 stars, 21k npm/wk |
| Agent reviews | none | 4/5 (2) |

Why the edge:
- Reliability, Scrapfly +62: 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.); Scrapfly 85 (scrapfly.io/status answers with Statuspage's status JSON, which names its page as scrapfly.statuspage.io. That page has 25 components and incident history back to 2022, read through its history feed on 1 November. The 1 October check read only the overall state and found no history (20, was 10). The newest incident is a Scrapium rendering fault on 21 May 2026, so nothing is posted in the 90 days from 3 August (30, was 5). Concurrency per plan is published (5 on Discovery to 100 on Enterprise) and each project has a configurable per-minute throttle (15). The error catalogue marks every code retryable or not and has three ERR::THROTTLE codes, but we found no Retry-After header or backoff guidance on the errors or throttling pages (10 of 15). The terms disclaim uptime and no uptime SLA is published, and the pricing page's SLA mentions cover support response on Enterprise (0). The Scrape API is GA. Vault and alerting are beta, outside the main surface (10). 20+30+15+10+0+10 = 85.)
- Security & auth, Scrapfly +34: 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.); Scrapfly 75 (OAuth 2 on the hosted MCP with dashboard revocation, open to all plans. API keys are per project, live or test, and since 15 April 2026 can be restricted to products (30). The canonical API form puts the key in the key query parameter and the MCP also accepts ?key=, so less 10 (20 of 30). Product-restricted keys, confirm=true on every mutating vault and alert tool, info_api_key off in server-key mode, and the self-hosted HTTP server binds loopback by default. Since v1.4.0 Cloud Browser sessions are scoped to the API key that opened them (15 of 20). The source gates mutating vault tools behind a preview step because prompt injection can reach them and redacts keys from CDP URLs. We found no user-facing guidance on untrusted page content (8 of 15). Monitoring shows every call as a log with its error, credit cost line by line and Unblocker state, with replay, per the 24 October release notes, as well as per-domain metrics and alerting. The 1 October check couldn't confirm per-request logs (15, was 10). security.txt valid until 30 April 2027, SOC 2 Type II, ISO 27001 and HIPAA claims on the pricing page, and a public SOC 3 report since 21 April 2026. No bug bounty found (17 of 20). 20+15+8+15+17 = 75.)
- Agent ergonomics, Scrapfly +31: 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.); Scrapfly 80 (The open-source server registers 62 tools by default in v1.4.0 (5 web scraping, 2 account, 9 Cloud Browser sessions, 17 page interaction, 2 WebMCP, 15 credential vault, 12 alerts), all at once, and the docs list a smaller core. There's a code path to mount interaction tools per session, but registration is always-on for clients that don't refetch. On the API side, format=markdown and the extraction API keep responses small, and since v1.4.0 the scrape tools report `api_cost` and `cost_details` (10 of 25). Output format, extraction templates, crawler limits and 100-URL batches (15 of 20). Error codes an agent can branch on, with retryable and billed flags (20). Tools carry readOnlyHint, destructiveHint, idempotentHint and openWorldHint, and mutating vault and alert tools need confirm=true after a preview (20). web_get_page works with a URL alone, and official SDKs exist for Python, TypeScript, Go and Rust (15). 10+15+20+20+15 = 80.)
- Transparency & trust, Scrapfly +31: 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.); Scrapfly 75 (Closed service with terms updated 2026-09-30 under US law. SDKs are BSD 2-Clause, and the MCP source is public with no LICENSE file and ISC in package.json (15 of 30). Privacy policy updated 14 May 2026 with a published DPA and HIPAA BAA, but retention is as long as necessary, and the retention of scraped content isn't stated (18 of 30). Release notes date deprecations and removals, for example Scrapium v153 dropping legacy network interception on 11 September. No standing deprecation policy found (15 of 20). Stripe, Google Analytics, Google Ads and Google Cloud are named, with SCC and Data Privacy Framework transfers, but there's no full subprocessor list (10 of 20). The release notes still date each CDP removal, most recently `Storage.getRelatedWebsiteSets` in Scrapium v156 on 26 October. Not otherwise re-read on 1 November. 15+18+15+10 = 58.)
- Maintenance & community, Scrapfly +23: 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.); Scrapfly 84 (Scrapium v156 in the release notes on 26 October 2026 and MCP v1.4.0 on 15 October (30). MCP tags v1.3.1 to v1.3.3 (26 and 27 August), v1.3.4 (8 September) and v1.4.0 (15 October), SDKs 0.12.0 on 8 September, and dated release notes on 14, 24 and 26 August, 11, 23 and 25 September, 7, 24 and 26 October (20). Dated release notes most weeks and a support address. We couldn't read GitHub issues, since github.com refuses our reader (12 of 25). In the official MCP registry as io.scrapfly.mcp/mcp under the vendor's domain, though the entry still lists 1.0.0, and the SDKs are current (15). MCP moved to Go 1.27 on 23 October. Its CI runs only a reference check and the npm publish, while the TypeScript SDK runs tests in CI (7 of 10). 30+20+12+15+7 = 84.)
- Schema & documentation, Scrapfly +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.); Scrapfly 95 (A Swagger reference per the 30 September check, and the MCP server exposes it as a web_scraping_openapi_specification resource. Every MCP tool has JSON Schema inputs generated from typed Go structs (25). llms.txt and Markdown twins such as pricing.md per the 30 September check. robots.txt still disallows /docs/llms.txt and the .md twins for crawlers it doesn't name, so they weren't re-read on 1 November (10). Descriptions say when to use a tool and when to switch, for example web_get_page falls back to web_scrape for tuning and to cloud_browser_open for interaction. A few are long and steer the model's next step (17 of 20). Typed inputs with enums, for example the vault service discriminator, and required fields (13 of 15). Error catalogue of 100+ ERR:: codes, each with HTTP status, retryable and billed flags and its own doc link (15). Dated release notes, newest 26 October 2026 (15). 25+10+17+13+15+15 = 95.)