Head to head · Scraping · October 2026 research run

Bright Data vs Scrapfly

Scrapfly scores 77 (BB) on agent readiness against Bright Data's 59.4 (C), and leads in 5 of 7 scored categories. Both do scraping.

Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons

Which one, for what

Bright Data C

Best for Hard targets and site-specific structured data (Amazon, LinkedIn, Instagram, Google Maps) at volume.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No public status page or incident history

Scrapfly BB

Best 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 40
  • Schema & documentation, 95 against 74
  • Security & auth, 75 against 69
  • Transparency & trust, 75 against 61

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine

Watch for

The open-source MCP server registers 62 tools at once, a heavy tools/list

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Scrapfly +45

Bright Data 40

No public status page found. status.brightdata.com doesn't resolve and the docs index and security overview link none (0). No readable incident history, so 5 by the rubric (5). The SERP API fair-use page gives 1,000 requests a minute for unfunded accounts with HTTP 429 above it and a header that reads the account's limit, paid Web Unlocker plans state unlimited concurrency, and the free tier is 5,000 requests a month (15). The Web Unlocker error catalogue documents a 429 sr_rate_limit when Bright Data throttles a target with a low success rate, and says which errors are worth retrying, but there's no Retry-After or backoff guidance (10 of 15). The pricing page names a Premium SLA for Enterprise and claims 99.99 per cent uptime, with no SLA terms published (0). GA (10). 0+5+15+10+0+10 = 40.

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.

Schema & documentation Scrapfly +21

Bright Data 74

No OpenAPI file found for the API. The MCP server has zod schemas on every tool, so partial credit (15 of 25). llms.txt at docs.brightdata.com with Markdown pages (10). MCP descriptions say what each tool returns, and the dataset tools say when to use them instead of run_scraper (14 of 20). Typed inputs with enums such as engine (bing or google), time_range and format (12 of 15). Per-product error catalogues for Web Unlocker, Browser API and scrapers, and curl examples (13 of 15). Release notes, now dated to 27 October 2026, and an MCP CHANGELOG with a gap between 2.6.0 and 2.10.0, per the 1 October reading (10 of 15).

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.

Transparency & trust Scrapfly +14

Bright Data 61

The API is closed under the Bright Data licence, and the MCP server is MIT, so we gave 20 between the closed and open bands (20 of 30). The privacy policy, last reviewed 14 May 2026, gives no retention periods and doesn't mention a DPA, and the licence lets Bright Data keep collected data per the 26 September check (10 of 30). Release notes carry dated deprecations, such as the Google Maps start and num parameters deprecated on 15 December 2025, but we found no policy (10 of 20). No subprocessor list. The policy says only that recipients outside the EEA are in countries the European Commission approves (3 of 20).

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.

Security & auth Scrapfly +6

Bright Data 69

API keys carry one of five roles (Admin, Finance, Ops, Limit, User), can be given an expiry, and are revoked or refreshed in the control panel, and the hosted MCP also takes OAuth 2.1 with PKCE and one mcp scope (30). The README's default hosted setup still puts the key in the URL as ?token=, a documented option, so less 10 (20). User-role keys can't change configuration, tools load by group, and tools carry readOnlyHint and destructiveHint, but browser tools can fill forms and click with no confirmation step from the server (14 of 20). Since 3.1.0 results from search, scrape, scraper, dataset and browser tools are wrapped as untrusted web content with a per-call marker, and since 2.12.0 a content gate, documented in the README and on by default, asks the user through MCP elicitation before returning page text that looks like instructions to change the MCP configuration (12 of 15). The MCP session_stats tool reports calls in a session. We didn't find a per-request log for operators (5 of 15). ISO 27001, 27017 and 27018, SOC 2 Type II under NDA, a public SOC 3, a managed private bug bounty and security fixes in the MCP changelog per the 1 October check. No security.txt (404 on 4 November). OSV holds no advisory for @brightdata/mcp (18 of 20). 20+14+12+5+18 = 69.

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.

Score by category

CategoryWeightBright DataScrapflyEdge
Reliability16%4085Scrapfly +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7495Scrapfly +21
Agent ergonomics13%7980Scrapfly +1
Security & auth14%6975Scrapfly +6
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8784Bright Data +3
Transparency & trust7%6175Scrapfly +14
Negative events≤15-6-3
TotalC 59.4/100BB 77/100

Facts side by side

FactBright DataScrapfly
KindHTTP APIHTTP API
VendorBright DataScrapfly (Joam Intelligence, LLC)
Hosted endpointhttps://api.brightdata.com/requesthttps://api.scrapfly.io/scrape
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
Tools exposed3262
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.brightdata/brightdata-mcpio.scrapfly.mcp/mcp
Last release2026-11-022026-10-15
Terms last updated2026-06-162026-09-30
Privacy policy last updated2026-05-142026-05-14
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity2.6k stars14 stars, 21k npm/wk
Agent reviews4/5 (2)4/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Bright Data

Bright Data bills only successful requests, $1.50 per 1,000 on Web Unlocker and SERP, and its MCP server now wraps scraped content as untrusted. There's no public status page or incident history, and MCP 4.2.0 and 4.3.0 changed tool inputs and outputs in minor releases without notice.

Scrapfly

The error catalogue documents HTTP status, retry behaviour and billing for over 100 codes, and the Statuspage history shows no incident since May 2026. The MCP server loads 62 tools at once, and the API's canonical form puts the key in the URL.

Before you call either

Bright Data

  1. Connect with OAuth or keep the ?token= URL out of logs and shared configs
  2. Set groups= or tools= on the MCP URL to load only the tools you need. With neither, all 32 load
  3. Send country and page to the search tools from 4.3.0. geo_location and cursor now return invalid_input
  4. Expect JSON with a content field from scrape_as_markdown since 4.2.0, and use the browser tools for pages that need JavaScript
  5. Back off on a 429 sr_rate_limit or rate_limited. Bright Data throttles a target whose success rate drops

Scrapfly

  1. Send X-Scrapfly-Api-Key as a header rather than key= so the key stays out of logs
  2. Pass unblocker=false to the MCP web_scrape tool for plain pages, since it's on when omitted. asp is the deprecated alias
  3. Set cost_budget on each scrape so an Unblocker upgrade can't blow through credits
  4. Check retryable in the error body before retrying, and stop on ERR::THROTTLE::MAX_API_CREDIT_BUDGET_EXCEEDED
  5. Use web_get_page for a simple fetch and save cloud_browser_open for pages that need clicks

Questions

Which is better for AI agents, Bright Data or Scrapfly?

Scrapfly scores 77 (BB) on agent readiness against Bright Data's 59.4 (C), and leads in 5 of 7 scored categories.

Do Bright Data and Scrapfly need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Bright Data and Scrapfly without installing anything?

Yes. Bright Data has a hosted endpoint at https://api.brightdata.com/request and Scrapfly at https://api.scrapfly.io/scrape.

Other comparisons with Bright Data or Scrapfly

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.