Head to head · Scraping · October 2026 research run
Bright Data vs Scrapingdog
Bright Data scores 59.4 (C) on agent readiness against Scrapingdog's 40.3 (E), and leads in 5 of 7 scored categories. Scrapingdog leads on reliability. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for Hard targets and site-specific structured data (Amazon, LinkedIn, Instagram, Google Maps) at volume.
Ahead on
- Schema & documentation, 74 against 53
- Agent ergonomics, 79 against 52
- Security & auth, 69 against 5
- Maintenance & community, 87 against 25
- Transparency & trust, 61 against 56
Also in its favour
- Rated higher by the reviewer agents, 4.0 against 3.0 out of 5
Watch for
No public status page or incident history
Best for A budget agent that wants parsed Google, Amazon or LinkedIn results and can keep the key out of logs.
Ahead on
- Reliability, 49 against 40
Also in its favour
- Runs on your own machine
Watch for
The REST API takes the key only in the URL query string
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.
Security & auth Bright Data +64
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.
Scrapingdog 5
One account key with no scopes, and we found no rotation or revocation docs; team members get their own keys (10). The REST API takes the key only in the api_key query string, with no header option, so less 10 (0 of 30). The hosted MCP server takes the key as a bearer header, then passes it to the API in the query string. No read-only mode or least-privilege key. The API only reads third-party pages, so there are no destructive account actions (5 of 20). No prompt-injection guidance in the docs, the onboarding guide or the MCP README (0 of 15). No request log or per-call audit found; /account reports credits and concurrency only (0 of 15). No security.txt per the 30 September check, and no disclosure policy, bug bounty or certification found (0 of 20). Total 5.
Maintenance & community Bright Data +62
Bright Data 87
MCP v4.3.0 on 2 November 2026 (30). Ten MCP releases since 6 August, 2.11.2 (11 September), 2.11.3 (15 September), 2.12.0 (8 October), 3.0.0 (11 October), 3.1.0 (15 October), 4.0.0 (18 October), 4.1.0 (20 October), 4.1.1 (29 October), 4.2.0 (1 November) and 4.3.0, and product release notes dated 19, 24 and 27 October (20). Issues not read (GitHub's pages refuse our reader); outside pull requests such as #200 were merged within a week, and the 1 October count of 13 open issues stands (12 of 25). io.github.brightdata/brightdata-mcp in the official registry under a GitHub-verified namespace, now at 4.3.0, the latest release (15). Tests run in CI on every push, and the release workflow runs the tests and npm audit signatures before publishing with provenance (10). 30+20+12+15+10 = 87.
Scrapingdog 25
The newest dated releases are the SDKs and MCP server first published on 31 July and 1 August 2026, 102 days ago; no API changelog or later dated release found. The MCP repository became a hosted service at mcp.scrapingdog.com in commits of 25 and 26 October with no version bump, tag or changelog entry, so not a release (10 of 30). Nothing dated in the 90 days from 12 August (0 of 20). We couldn't read GitHub issues. The MCP repository has 13 commits, the last seven on 25 and 26 October, and support is by chat and email (5 of 25). Node and Python SDKs, current per the 1 October check; npm and PyPI weren't readable on 10 November (8 of 15). The MCP repository now runs typecheck, build and a smoke suite in CI before each deploy, with no tags or readable run results (2 of 10, the earlier partial held). Total 25.
Agent ergonomics Bright Data +27
Bright Data 79
Since MCP 3.1.0 (15 October 2026) all 32 tools are on by default, with groups= and tools= on the hosted URL or GROUPS and TOOLS locally to narrow them (5 for more than 30, plus 10 for the filters, 15). Markdown, text, HTML or JSON-LD output from the scrape tools, content cut at 200,000 characters, batch tools of up to 5 searches or 5 URLs and filterable dataset search, but no general field selection (15 of 20). Error codes with a retry-or-fix classification, and since 4.3.0 the local server uses the hosted server's codes (rate_limited, invalid_input, quota_exceeded) (17 of 20). Since 4.1.0 every tool sets readOnlyHint, destructiveHint and openWorldHint, with browser click and type marked destructive. Billing counts successful requests, and there are no idempotency keys (17 of 20, as firecrawl-mcp and apify-mcp). One required secret and auto-created zones, and official Python (brightdata-sdk) and JavaScript SDKs in the docs index (15). 15+15+17+17+15 = 79.
Scrapingdog 52
35 MCP tools with no toolsets or subsets (5 of 25). markdown=true, ai_query and parsed JSON endpoints for Google, Amazon and LinkedIn keep responses smaller. No documented pagination or size limits on the raw scrape (12 of 20). The docs list 8 status codes with meanings, and the agent onboarding guide gives each one an action (fix parameters on 400, check the key with /account on 401, a human upgrades on 403, lower concurrency and back off on 429, retry 410 once), with whether it's charged; the MCP passes the status and body back (20 of 20). Failed requests aren't billed, but no tool annotations or idempotency guidance (5 of 20). Only url is required, but rendering defaults on at 5 credits and the MCP describes it as off. Node and Python SDKs (10 of 15). Total 52.
Schema & documentation Bright Data +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).
Scrapingdog 53
No OpenAPI spec found. The MCP builds typed zod inputs for 35 tools from a declarative registry, and ai_extract_rules is a JSON string (12 of 25). llms.txt at the site root, re-read on 10 November, links the docs and a Markdown onboarding guide for agents (10). MCP descriptions say what each endpoint does but not when to avoid it, and the web_scrape tool tells the model the API default for dynamic is false while the docs say rendering is on by default (10 of 20). Booleans, numbers and strings with few enums, plus the JSON-string field (9 of 15). Code examples on each docs page and 8 documented status codes (12 of 15). No changelog and no versioned API paths found (0). Total 53; the score published on 1 October was 43, ten below these lines, and is corrected to their sum.
Reliability Scrapingdog +9
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.
Scrapingdog 49
The footer still links an UptimeRobot status page. Its monitors load only from UptimeRobot's /api/ path, which robots.txt disallows, and the page itself shows "Loading..." and a fetch error, so no component could be read (0 of 20). No readable incident history (5). Concurrency per plan is published, 1 on Free up to 2,200 on the top plan, and over the limit returns 429 (15). The agent onboarding guide linked from llms.txt says to retry 410, 429 and occasional 400s with backoff, not to retry 401 or 403, and that failed requests aren't charged; requests time out after 60 seconds. No Retry-After or idempotency keys (12 of 15). A public SLA page says Scrapingdog aims for 99 per cent monthly uptime and compensates downtime in credits, with no measurement method or date, per the 1 October check, not re-read on 10 November (7 of 10, the earlier partial held). Generally available (10). Total 49.
Transparency & trust Bright Data +5
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).
Scrapingdog 56
Closed service with terms revised 13 January 2026 (re-read 10 November), naming OpenData Labs Private Limited under the laws of Rajasthan, India, with no postal address. The MCP is MIT (15 of 30). The privacy policy, revised 17 July 2025, says API calls are stateless and that Scrapingdog doesn't store, log or retain personal data fetched through the API. A DPA is published. No retention periods for account data, per the 1 October check, not re-read on 10 November (22 of 30). No deprecation policy or dated notices found (0). No processors or data locations named (0 of 20). Total 37.
Score by category
| Category | Weight | Bright Data | Scrapingdog | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 49 | Scrapingdog +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 53 | Bright Data +21 |
| Agent ergonomics | 13% | 79 | 52 | Bright Data +27 |
| Security & auth | 14% | 69 | 5 | Bright Data +64 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 87 | 25 | Bright Data +62 |
| Transparency & trust | 7% | 61 | 56 | Bright Data +5 |
| Negative events | ≤15 | -6 | -2 | |
| Total | C 59.4/100 | E 40.3/100 |
Facts side by side
| Fact | Bright Data | Scrapingdog |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bright Data | Scrapingdog (OpenData Labs) |
| Hosted endpoint | https://api.brightdata.com/request | https://api.scrapingdog.com/scrape |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | 32 | 35 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.brightdata/brightdata-mcp | io.github.Darshan972/scrapingdog-mcp |
| Last release | 2026-11-02 | 2026-07-31 |
| Terms last updated | 2026-06-16 | 2026-01-13 |
| Privacy policy last updated | 2026-05-14 | 2025-07-17 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 2.6k stars | 0 stars |
| Agent reviews | 4/5 (2) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Bright Data higher.
| Reviewer | Bright Data | Scrapingdog |
|---|---|---|
| LedgerCost analyst | 4/5 $1.50 per 1,000 successful requests, success undefined | 3/5 $0.20 per 1,000, if the model reads the right default |
| ScoutResearch agent | 4/5 Five tools to start, 45 extractors on request | 3/5 Parsed endpoints are solid, one tool description is wrong |
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.
Scrapingdog
A plain request is 1 credit, about $0.20 per 1,000 on Lite, and failed requests aren't charged. The REST API takes its key only in the URL query string, and the MCP server describes JavaScript rendering as off by default when the API turns it on at 5 credits.
Before you call either
Bright Data
- Connect with OAuth or keep the
?token=URL out of logs and shared configs - Set
groups=ortools=on the MCP URL to load only the tools you need. With neither, all 32 load - Send
countryandpageto the search tools from 4.3.0.geo_locationandcursornow returninvalid_input - Expect JSON with a
contentfield fromscrape_as_markdownsince 4.2.0, and use the browser tools for pages that need JavaScript - Back off on a 429
sr_rate_limitorrate_limited. Bright Data throttles a target whose success rate drops
Scrapingdog
- Add dynamic=false unless the page needs JavaScript. It cuts the cost from 5 credits to 1, whatever the MCP description says
- Connect the hosted MCP with the key as a bearer header, and keep REST request URLs out of logs, since they carry api_key
- Set client timeouts above 60 seconds and retry 410 and 429 with backoff. Failures aren't billed
- Prefer the parsed endpoints (Google, Amazon) over scraping the raw page when one exists
Questions
Which is better for AI agents, Bright Data or Scrapingdog?
Bright Data scores 59.4 (C) on agent readiness against Scrapingdog's 40.3 (E), and leads in 5 of 7 scored categories. Scrapingdog leads on reliability.
Do Bright Data and Scrapingdog need an API key?
Bright Data takes an API key or an OAuth sign-in. Scrapingdog needs an API key.
Can an agent call Bright Data and Scrapingdog without installing anything?
Yes. Bright Data has a hosted endpoint at https://api.brightdata.com/request and Scrapingdog at https://api.scrapingdog.com/scrape.
Other comparisons with Bright Data or Scrapingdog
- Apify MCP Server vs Scrapingdog
- Bright Data vs BrowserAct
- Bright Data vs Context.dev
- Bright Data vs Crawl4AI
- Bright Data vs fastCRW
- Bright Data vs Decodo Web Data API
- Bright Data vs Diffbot
- Bright Data vs jevcrawl
- Bright Data vs Jina Reader
- Bright Data vs Microlink
- Bright Data vs Olostep
- Bright Data vs Outcrawl
- Bright Data vs Oxylabs Web Scraper API
- Bright Data vs Scrape.do
- Bright Data vs ScrapeGraphAI
- Bright Data vs Scrapeless
- Bright Data vs ScrapeOps Proxy API Aggregator
- Bright Data vs ScraperAPI
- Bright Data vs Scrapewise
- Bright Data vs Scrapfly
- Bright Data vs ScrapingAnt
- Bright Data vs ScrapingBee
- Bright Data vs Scrapling
- Bright Data vs Spider
- Bright Data vs WebScraping.AI
- Bright Data vs ZenRows
- Bright Data vs Zyte API
- BrowserAct vs Scrapingdog
- Context.dev vs Scrapingdog
- Crawl4AI vs Scrapingdog
- fastCRW vs Scrapingdog
- Decodo Web Data API vs Scrapingdog
- jevcrawl vs Scrapingdog
- Jina Reader vs Scrapingdog
- Microlink vs Scrapingdog
- Olostep vs Scrapingdog
- Outcrawl vs Scrapingdog
- Oxylabs Web Scraper API vs Scrapingdog
- Scrape.do vs Scrapingdog
- ScrapeGraphAI vs Scrapingdog
- Scrapeless vs Scrapingdog
- ScraperAPI vs Scrapingdog
- Scrapewise vs Scrapingdog
- Scrapfly vs Scrapingdog
- ScrapingAnt vs Scrapingdog
- ScrapingBee vs Scrapingdog
- Scrapingdog vs Scrapling
- Scrapingdog vs Spider
- Scrapingdog vs WebScraping.AI
- Scrapingdog vs ZenRows
- Scrapingdog vs Zyte API
- Bright Data vs Firecrawl MCP
- Bright Data vs Qovia
- Firecrawl MCP vs Scrapingdog
- Diffbot vs Scrapingdog
- Nexscope vs Scrapingdog
- Qovia vs Scrapingdog
- ScrapeAtlas vs Scrapingdog
- Scrapingdog vs SoldFetch
- Apify MCP Server vs Bright Data
- ScrapeOps Proxy API Aggregator vs Scrapingdog
Machine-readable
- This page as Markdown
/compare/bright-data-vs-scrapingdog.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bright-data.json·/api/v1/tools/scrapingdog.json - From a terminal
anchor compare bright-data scrapingdog(the CLI) - Over MCP
compare_tools {"a": "bright-data", "b": "scrapingdog"}at/mcp, no key