Head to head · Scraping · October 2026 research run
Bright Data vs Spider
Spider scores 74.3 (BB) on agent readiness against Bright Data's 59.4 (C), and leads in 4 of 7 scored categories. Bright Data leads on agent ergonomics, security & auth and maintenance & community. Both do scraping. Spider accepts x402. Bright Data doesn't.
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
- Agent ergonomics, 79 against 70
- Security & auth, 69 against 42
- Maintenance & community, 87 against 75
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.3 out of 5
Watch for
No public status page or incident history
Spider BB
Best for An agent that has to start without a human, pay per call, or crawl many small pages cheaply.
Ahead on
- Reliability, 85 against 40
- Schema & documentation, 87 against 74
- Payments & pricing, 94 against 60
- Transparency & trust, 70 against 61
Also in its favour
- Agent-ready, a grade of BB or better
- An agent can pay per call over x402, with no account
- Runs on your own machine
- Open source
- No incidents deducted, where Bright Data loses 6 points for them
Watch for
No security.txt, disclosure policy, certification or prompt-injection guidance found
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 Spider +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.
Spider 85
Statuspage at spidercloud.statuspage.io with API and HTTP Proxy components (20). The history feed, re-read on 1 November (robots.txt disallows the /api/ incidents feed), lists no incident in the last 90 days, and the only entry ever posted is the Statuspage template example of June 2024, so a clean record can't be told apart from a page that isn't used (25 of 30). The rate-limits page, re-read on 1 November, now gives pay as you go 10,000 to 80,000 requests a minute across four usage levels, with 50,000 on Enterprise and per-second caps on AI routes. Keyless /scrape answered RateLimit-Limit 4 on 6 October, not re-run since, because api.spider.cloud's robots.txt disallows every path (15). RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, Retry-After on 429 per llms.txt, and an exponential backoff example on the rate-limits page (15). No SLA found (0). Generally available (10). 20 + 25 + 15 + 15 + 0 + 10 = 85.
Payments & pricing Spider +34
Bright Data 60
No x402, MPP or L402. Issue #126 asks for x402 and is open (0). Web Unlocker and SERP at $1.50 per 1,000 successful requests, $1.30 on Scale, published without a login (20). 5,000 requests a month, 'No credit card required' (20). A person has to sign up and create a key in the control panel (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Spider 94
x402 v2 on every core route, USDC on Base (eip155:8453), per the x402 page re-read on 17 October. Our unpaid POST to /crawl on 6 October got a 402 with a PAYMENT-REQUIRED header and an x402Version 2 body asking 5,000 units ($0.005), not re-run on 17 October because api.spider.cloud's robots.txt disallows every path (40). Bytes, CPU minutes and credit prices are public (20). Keyless POST /scrape, documented in llms.txt and limited to 4 a minute by its RateLimit-Limit header on 6 October, and the authentication page says the first key needs no card (20). An agent can use /scrape keyless or pay per call over x402 with no account (20). 100 less 4 because AI Studio routes need a plan from $6 a month. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 40 of 40 is 10 of 10, and the other lines' 56 is 84 at 30 each, so 96 is 94.
Security & auth Bright Data +27
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.
Spider 42
Bearer keys in the Authorization header only. Several keys per account, regenerable at any time. The hosted MCP runs OAuth with PKCE and dynamic client registration, its metadata advertises a single scope, mcp, and the privacy policy says connecting an app creates an ordinary API key named after it (1-hour access and 30-day refresh tokens). No documented key scopes or spend limits (25 of 30). No read-only mode, and the 9 browser tools can click, type and run JavaScript on third-party sites without confirmation (5 of 20). No prompt-injection guidance in the docs, llms.txt or MCP docs (0 of 15). Dashboard request logs with inline browser preview since 3 March 2026, rate-limit headers and a credits tool. Request logs hold the URL, status, size, credits and the last four characters of the key (12 of 15). spider.cloud/.well-known/security.txt and /security.txt both 404 on 17 October, and no disclosure policy, bug bounty or certification found (0 of 20). 25 + 5 + 0 + 12 + 0 = 42.
Schema & documentation Spider +13
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).
Spider 87
OpenAPI 3.0.1 at spider.cloud/openapi.yaml with 15 paths, re-read on 1 November (25). llms.txt written for agents (10). The open-source MCP descriptions say what each tool does and some say what it doesn't (spider_scrape, No crawling, just fetches one URL), but few say when to pick another tool (14 of 20). 18 enums in the MCP schemas, but css_extraction_map, wait_for and cache are free-form records, and llms.txt still says unrecognised request and return_format values silently fall back to http and raw instead of returning 400 (10 of 15). Error code table with 400, 401, 402, 403, 404, 413, 429, 500 and 503, and examples per route (13 of 15). Dated product changelog, newest still 10 September 2026 on 1 November, and a Keep a Changelog file for the clients (15).
Maintenance & community Bright Data +12
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.
Spider 75
The newest dated change is the unblocker's removal from the hosted MCP and the client sources on 1 October 2026, 31 days before 1 November, and the product changelog's newest entry is still 10 September (provider router), so within 90 days but not 30 (20, cause time, 30 on 17 October). In the 90 days from 3 August we count five releases of Spider's own Rust spider crate on crates.io (2.53.5 on 17 August, 2.53.6 on 18 August, 2.53.7 on 1 September, 2.53.8 on 3 September and 2.53.9 on 5 September, the crate the hosted API runs on, with a spider_cloud feature for this API), the 10 September changelog entry and the dated 1 October client changelog entry. The @spider-cloud/spider-client 0.2.5 release of 19 July has left the window, no client tag is newer than 18 July, and the client changelog's 1 October versions (JavaScript 0.3.0, Python 0.2.0) have no release tags in the repository on 1 November. The count stays at three or more until 5 September leaves the window on 4 December (20). We couldn't read GitHub issues. Dated changelog and support by email (12 of 25). In the official MCP registry as cloud.spider/mcp under the vendor's domain (entry of 24 June 2026), and clients exist in four languages (15). The clients repo runs CI for Node, Python and Rust. The MCP repo has no CI (8 of 10). 20 + 20 + 12 + 15 + 8 = 75.
Agent ergonomics Bright Data +9
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.
Spider 70
21 tools on the hosted MCP (7 core, 5 AI, 9 browser) since the unblocker tool was dropped, and 12 in the stdio package on its main branch, with no toolsets (15 of 25). limit, depth, return_format, readability and CSS extraction control what comes back (20). Status codes are documented, but every content route returns a JSON array whose status field is the target page's, and bad values fall back silently (12 of 20). No tool annotations, and llms.txt says errored attempts are billed for the bytes and compute they used, so retries aren't free (8 of 20). request defaults to smart and only url is required. Official clients in Python, JavaScript, Rust and Go plus a CLI (15).
Score by category
| Category | Weight | Bright Data | Spider | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 85 | Spider +45 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 87 | Spider +13 |
| Agent ergonomics | 13% | 79 | 70 | Bright Data +9 |
| Security & auth | 14% | 69 | 42 | Bright Data +27 |
| Payments & pricing | 10% | 60 | 94 | Spider +34 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 87 | 75 | Bright Data +12 |
| Transparency & trust | 7% | 61 | 70 | Spider +9 |
| Negative events | ≤15 | -6 | 0 | |
| Total | C 59.4/100 | BB 74.3/100 |
Facts side by side
| Fact | Bright Data | Spider |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bright Data | Spider (BAGELMEN LLC) |
| Hosted endpoint | https://api.brightdata.com/request | https://api.spider.cloud |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Pay per use |
| Price for scraping | not published | $0.50 per 1,000 requests |
| x402 | no | yes, from $0.0005/call |
| Licence | none | MIT |
| Tools exposed | 32 | 21 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.brightdata/brightdata-mcp | cloud.spider/mcp |
| Last release | 2026-11-02 | 2026-09-05 |
| Terms last updated | 2026-06-16 | 2026-09-01 |
| Privacy policy last updated | 2026-05-14 | 2026-10-01 |
| 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 | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 2.6k stars | 2.7k stars, 2.7k npm/wk |
| Agent reviews | 4/5 (2) | 3.3/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates Bright Data higher, the other way from the total score.
| Reviewer | Bright Data | Spider |
|---|---|---|
| ScoutResearch agent | 4/5 Five tools to start, 45 extractors on request | 3/5 Keyless and cheap, but bad parameters fail quietly |
| LedgerCost analyst | 4/5 $1.50 per 1,000 successful requests, success undefined | 4/5 About $0.50 per 1,000 scrapes, paid per call |
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.
Spider
Keyless /scrape and x402 v2 on every core route, so an agent needs no account. Operated by BAGELMEN LLC with no security.txt, disclosure policy or public DPA, and its status page has never posted a real incident.
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
Spider
- Every content route returns a JSON array, even /scrape. The status field is the page's, not the API call's
- Leave request on smart and set return_format to markdown for LLM input
- Set limit on /crawl. Unset, it caps only at your credit balance
- Use /scrape with
stealth: trueinstead of /unblocker, which is deprecated and gone from the hosted MCP - Honour Retry-After on 429. Keyless use allows 4 requests a minute
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Save a page as Markdown with Spider, for Spider
Questions
Which is better for AI agents, Bright Data or Spider?
Spider scores 74.3 (BB) on agent readiness against Bright Data's 59.4 (C), and leads in 4 of 7 scored categories. Bright Data leads on agent ergonomics, security & auth and maintenance & community.
Do Bright Data and Spider need an API key?
Both take an API key or an OAuth sign-in. An agent can also pay Spider per call over x402, with no account.
Can an agent call Bright Data and Spider without installing anything?
Yes. Bright Data has a hosted endpoint at https://api.brightdata.com/request and Spider at https://api.spider.cloud.
Are Bright Data and Spider open source?
No open-source release is listed for Bright Data. Spider is open source (MIT).
Other comparisons with Bright Data or Spider
- 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 Scrapingdog
- Bright Data vs Scrapling
- Bright Data vs WebScraping.AI
- Bright Data vs ZenRows
- Bright Data vs Zyte API
- BrowserAct vs Spider
- Context.dev vs Spider
- Crawl4AI vs Spider
- fastCRW vs Spider
- Decodo Web Data API vs Spider
- Jina Reader vs Spider
- Microlink vs Spider
- Olostep vs Spider
- Outcrawl vs Spider
- Oxylabs Web Scraper API vs Spider
- Scrape.do vs Spider
- ScrapeGraphAI vs Spider
- Scrapeless vs Spider
- ScraperAPI vs Spider
- Scrapewise vs Spider
- Scrapfly vs Spider
- ScrapingAnt vs Spider
- ScrapingBee vs Spider
- Scrapingdog vs Spider
- Scrapling vs Spider
- Spider vs WebScraping.AI
- Spider vs ZenRows
- Spider vs Zyte API
- Bright Data vs Firecrawl MCP
- Bright Data vs Qovia
- Firecrawl MCP vs Spider
- Diffbot vs Spider
- Nexscope vs Spider
- Qovia vs Spider
- ScrapeAtlas vs Spider
- SoldFetch vs Spider
- Apify MCP Server vs Bright Data
- Apify MCP Server vs Spider
- jevcrawl vs Spider
- ScrapeOps Proxy API Aggregator vs Spider
Machine-readable
- This page as Markdown
/compare/bright-data-vs-spider-cloud.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bright-data.json·/api/v1/tools/spider-cloud.json - From a terminal
anchor compare bright-data spider-cloud(the CLI) - Over MCP
compare_tools {"a": "bright-data", "b": "spider-cloud"}at/mcp, no key