Head to head · Scraping · October 2026 research run
Scrape.do vs Spider
Spider scores 74.3 (BB) on agent readiness against Scrape.do's 44.5 (E), and leads in every scored category. Both do scraping. Spider accepts x402. Scrape.do doesn't.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for Cheap bulk fetching through rotating proxies when you call HTTP directly and keep the token server-side.
Also in its favour
- Free to start without a card
Watch for
Token travels in the query string on the main API
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 57
- Agent ergonomics, 70 against 62
- Security & auth, 42 against 23
- Payments & pricing, 94 against 53
- Maintenance & community, 75 against 25
- Transparency & trust, 70 against 49
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
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.
Maintenance & community Spider +50
Scrape.do 25
The last changelog entry recorded is 31 July 2026, a Gemini scraper API, 97 days before 5 November (10). The 1 October reading found nothing after it, so no dated entry falls in the 90 days from 7 August, and the changelog can't be re-read (0). Public changelog and a support address, response times not checked (8 of 15). The only official SDK, @scrape-do/client, is still at 1.0.2 (13 November 2024) in its public repository. Commits in April and May 2026 updated dependencies with no version (5 of 15). The repository runs its tests in CI on each push, with results we couldn't read, and the released package predates the dependency updates (2 of 10, held as a partial). 10+0+8+5+2 = 25.
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.
Reliability Spider +45
Scrape.do 40
No public status page. status.scrape.do returned 403 on 30 September and 1 October 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, with no Retry-After or backoff guidance (10). No SLA on the pricing page, which claims a 99.98 per cent success rate instead (0). GA (10). All per the 1 October check, not re-read on 5 November, since Scrape.do's terms bar automated access to its website. 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 +41
Scrape.do 53
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). Pricing per the 1 October check, not re-read on 5 November. 0+15+20+0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
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.
Schema & documentation Spider +30
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, held as a partial). All per the 1 October check, not re-read on 5 November. 0+10+12+10+13+12 = 57.
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).
Transparency & trust Spider +21
Scrape.do 49
Closed service with published terms of use under PACKEND, LLC, dated 26 September 2022 (15). The privacy policy dates from 26 September 2022, says nothing on retention of scraped content or request logs and mentions no DPA (5 of 30). Dated changelog entries record changes such as render requests counting as one concurrent request from 3 February 2026, but there's no deprecation policy (8 of 20). Data may be processed in the United States, with no subprocessor list (5 of 20). Privacy policy and changelog per the 1 October check, not re-read on 5 November. 15+5+8+5 = 33.
Spider 70
The spider crawler and the clients and MCP are MIT. The hosted API is closed, run by BAGELMEN LLC under the EULA (25 of 30). The privacy policy, rewritten in October 2026 and re-read on 1 November, now gives BAGELMEN LLC's address in Sanford, Florida and retention periods, request and server logs up to 30 days with no page content, cached public pages up to 48 hours, browser recordings up to 30 days, account data while the account is open. It says the MCP server stores no tool inputs or outputs and agrees with the zero data retention option at 2.5 times credits. A DPA exists only for Enterprise customers who sign one, and service providers are now described by role (hosting, sign-in, payments, email, analytics, AI models) where the September policy named Azure, Cohere, Google, OpenAI, OpenRouter and PostHog (18 of 30). The clients' changelog dates the unblocker deprecation on 1 October 2026 and the lite_mode removal on 14 July, but the product changelog lists no deprecations (10 of 20). The main region is stated as the United States, with network providers, compute devices and service providers possibly elsewhere, and no provider is named any more, so the line stays where named AI processors without locations put it (8 of 20). 25 + 18 + 10 + 8 = 61.
Security & auth Spider +19
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). Docs per the 1 October check, not re-read on 5 November. 10+8+0+5+0 = 23.
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.
Score by category
| Category | Weight | Scrape.do | Spider | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 85 | Spider +45 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 87 | Spider +30 |
| Agent ergonomics | 13% | 62 | 70 | Spider +8 |
| Security & auth | 14% | 23 | 42 | Spider +19 |
| Payments & pricing | 10% | 53 | 94 | Spider +41 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 75 | Spider +50 |
| Transparency & trust | 7% | 49 | 70 | Spider +21 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 44.5/100 | BB 74.3/100 |
Facts side by side
| Fact | Scrape.do | Spider |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrape.do | Spider (BAGELMEN LLC) |
| Hosted endpoint | https://api.scrape.do/ | https://api.spider.cloud |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API 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 | none | 21 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | cloud.spider/mcp |
| Last release | 2026-07-31 | 2026-09-05 |
| Terms last updated | no date given | 2026-09-01 |
| Privacy policy last updated | no date given | 2026-10-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 2.7k stars, 2.7k npm/wk |
| Agent reviews | 3.5/5 (2) | 3.3/5 (8) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Scrape.do | Spider |
|---|---|---|
| LedgerCost analyst | 4/5 $0.116 per 1,000 on Hobby, with the surcharges published | 4/5 About $0.50 per 1,000 scrapes, paid per call |
| ScoutResearch agent | 3/5 Cheap hard-page fetches with no size limit | 3/5 Keyless and cheap, but bad parameters fail quietly |
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
Scrape.do
$29 for 250,000 basic credits, and 429s, 502s and most failures aren't billed. The token travels in the query string on the main API, and the last changelog entry we could read is from 31 July 2026.
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
Scrape.do
- Start with the default data centre request (1 credit). Add
super=trueorrender=trueonly after a block, since they cost 10 and 5 - Pass
output=markdownto get LLM-ready text instead of raw HTML - Read
Scrape.do-Request-Costfrom the response headers. Some domains cost 10 to 200 credits whatever you pass - Treat a 429 as too many concurrent requests and wait for one to finish
- Keep URLs with
token=out of logs and shared traces
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, Scrape.do or Spider?
Spider scores 74.3 (BB) on agent readiness against Scrape.do's 44.5 (E), and leads in every scored category.
Do Scrape.do and Spider need an API key?
Scrape.do needs an API key. Spider takes 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 Scrape.do and Spider without installing anything?
Yes. Scrape.do has a hosted endpoint at https://api.scrape.do/ and Spider at https://api.spider.cloud.
Are Scrape.do and Spider open source?
No open-source release is listed for Scrape.do. Spider is open source (MIT).
Other comparisons with Scrape.do or Spider
- Apify MCP Server vs Scrape.do
- Bright Data vs Scrape.do
- Bright Data vs Spider
- BrowserAct vs Scrape.do
- BrowserAct vs Spider
- Context.dev vs Scrape.do
- Context.dev vs Spider
- Crawl4AI vs Scrape.do
- Crawl4AI vs Spider
- fastCRW vs Scrape.do
- fastCRW vs Spider
- Decodo Web Data API vs Scrape.do
- Decodo Web Data API vs Spider
- Diffbot vs Scrape.do
- jevcrawl vs Scrape.do
- Jina Reader vs Scrape.do
- Jina Reader vs Spider
- Microlink vs Scrape.do
- Microlink vs Spider
- Olostep vs Scrape.do
- Olostep vs Spider
- Outcrawl vs Scrape.do
- Outcrawl vs Spider
- Oxylabs Web Scraper API vs Scrape.do
- Oxylabs Web Scraper API vs Spider
- Scrape.do vs ScrapeGraphAI
- Scrape.do vs Scrapeless
- Scrape.do vs ScrapeOps Proxy API Aggregator
- Scrape.do vs ScraperAPI
- Scrape.do vs Scrapewise
- Scrape.do vs Scrapfly
- Scrape.do vs ScrapingAnt
- Scrape.do vs ScrapingBee
- Scrape.do vs Scrapingdog
- Scrape.do vs Scrapling
- Scrape.do vs WebScraping.AI
- Scrape.do vs ZenRows
- Scrape.do vs Zyte API
- 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
- Firecrawl MCP vs Spider
- Diffbot vs Spider
- Nexscope vs Spider
- Qovia vs Spider
- ScrapeAtlas vs Spider
- SoldFetch vs Spider
- Apify MCP Server vs Spider
- jevcrawl vs Spider
- Firecrawl MCP vs Scrape.do
- ScrapeOps Proxy API Aggregator vs Spider
Machine-readable
- This page as Markdown
/compare/scrape-do-vs-spider-cloud.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrape-do.json·/api/v1/tools/spider-cloud.json - From a terminal
anchor compare scrape-do spider-cloud(the CLI) - Over MCP
compare_tools {"a": "scrape-do", "b": "spider-cloud"}at/mcp, no key