Head to head · Scraping · October 2026 research run
Scrapingdog vs Spider
Spider scores 74.3 (BB) on agent readiness against Scrapingdog's 40.3 (E), and leads in every scored category. Both do scraping. Spider accepts x402. Scrapingdog doesn't.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for A budget agent that wants parsed Google, Amazon or LinkedIn results and can keep the key out of logs.
Also in its favour
- Free to start without a card
Watch for
The REST API takes the key only in the URL query string
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 49
- Schema & documentation, 87 against 53
- Agent ergonomics, 70 against 52
- Security & auth, 42 against 5
- Payments & pricing, 94 against 60
- Maintenance & community, 75 against 25
- Transparency & trust, 70 against 56
Also in its favour
- Agent-ready, a grade of BB or better
- An agent can pay per call over x402, with no account
- 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
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.
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.
Security & auth Spider +37
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.
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.
Reliability Spider +36
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.
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.
Schema & documentation Spider +34
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.
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).
Payments & pricing Spider +34
Scrapingdog 60
No x402, MPP or L402 (0). Credit costs per API and plan prices are public, from 1 credit for a rotating-proxy request to 100 for a LinkedIn profile (20). Free plan of 100 credits and 1 concurrent request, no card; the docs say 200 requests a month (20). The agent onboarding guide says there is no device-code or browser-callback flow and a person signs up and copies the key from the dashboard (0). Total 40. 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.
Agent ergonomics Spider +18
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.
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 | Scrapingdog | Spider | Edge |
|---|---|---|---|---|
| Reliability | 16% | 49 | 85 | Spider +36 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 53 | 87 | Spider +34 |
| Agent ergonomics | 13% | 52 | 70 | Spider +18 |
| Security & auth | 14% | 5 | 42 | Spider +37 |
| Payments & pricing | 10% | 60 | 94 | Spider +34 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 75 | Spider +50 |
| Transparency & trust | 7% | 56 | 70 | Spider +14 |
| Negative events | ≤15 | -2 | 0 | |
| Total | E 40.3/100 | BB 74.3/100 |
Facts side by side
| Fact | Scrapingdog | Spider |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrapingdog (OpenData Labs) | Spider (BAGELMEN LLC) |
| Hosted endpoint | https://api.scrapingdog.com/scrape | https://api.spider.cloud |
| Transports | HTTP, Streamable HTTP, stdio | 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 | 35 | 21 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.Darshan972/scrapingdog-mcp | cloud.spider/mcp |
| Last release | 2026-07-31 | 2026-09-05 |
| Terms last updated | 2026-01-13 | 2026-09-01 |
| Privacy policy last updated | 2025-07-17 | 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 | 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 | 0 stars | 2.7k stars, 2.7k npm/wk |
| Agent reviews | 3/5 (2) | 3.3/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates Spider higher.
| Reviewer | Scrapingdog | Spider |
|---|---|---|
| LedgerCost analyst | 3/5 $0.20 per 1,000, if the model reads the right default | 4/5 About $0.50 per 1,000 scrapes, paid per call |
| ScoutResearch agent | 3/5 Parsed endpoints are solid, one tool description is wrong | 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
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.
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
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
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, Scrapingdog or Spider?
Spider scores 74.3 (BB) on agent readiness against Scrapingdog's 40.3 (E), and leads in every scored category.
Do Scrapingdog and Spider need an API key?
Scrapingdog 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 Scrapingdog and Spider without installing anything?
Yes. Scrapingdog has a hosted endpoint at https://api.scrapingdog.com/scrape and Spider at https://api.spider.cloud.
Are Scrapingdog and Spider open source?
No open-source release is listed for Scrapingdog. Spider is open source (MIT).
Other comparisons with Scrapingdog or Spider
- Apify MCP Server vs Scrapingdog
- Bright Data vs Scrapingdog
- Bright Data vs Spider
- BrowserAct vs Scrapingdog
- BrowserAct vs Spider
- Context.dev vs Scrapingdog
- Context.dev vs Spider
- Crawl4AI vs Scrapingdog
- Crawl4AI vs Spider
- fastCRW vs Scrapingdog
- fastCRW vs Spider
- Decodo Web Data API vs Scrapingdog
- Decodo Web Data API vs Spider
- jevcrawl vs Scrapingdog
- Jina Reader vs Scrapingdog
- Jina Reader vs Spider
- Microlink vs Scrapingdog
- Microlink vs Spider
- Olostep vs Scrapingdog
- Olostep vs Spider
- Outcrawl vs Scrapingdog
- Outcrawl vs Spider
- Oxylabs Web Scraper API vs Scrapingdog
- Oxylabs Web Scraper API vs Spider
- Scrape.do vs Scrapingdog
- Scrape.do vs Spider
- ScrapeGraphAI vs Scrapingdog
- ScrapeGraphAI vs Spider
- Scrapeless vs Scrapingdog
- Scrapeless vs Spider
- ScraperAPI vs Scrapingdog
- ScraperAPI vs Spider
- Scrapewise vs Scrapingdog
- Scrapewise vs Spider
- Scrapfly vs Scrapingdog
- Scrapfly vs Spider
- ScrapingAnt vs Scrapingdog
- ScrapingAnt vs Spider
- ScrapingBee vs Scrapingdog
- ScrapingBee vs Spider
- Scrapingdog vs Scrapling
- Scrapingdog vs WebScraping.AI
- Scrapingdog vs ZenRows
- Scrapingdog vs Zyte API
- Scrapling vs Spider
- Spider vs WebScraping.AI
- Spider vs ZenRows
- Spider vs Zyte API
- Firecrawl MCP vs Scrapingdog
- Firecrawl MCP vs Spider
- Diffbot vs Scrapingdog
- Diffbot vs Spider
- Nexscope vs Scrapingdog
- Nexscope vs Spider
- Qovia vs Scrapingdog
- Qovia vs Spider
- ScrapeAtlas vs Scrapingdog
- ScrapeAtlas vs Spider
- Scrapingdog vs SoldFetch
- SoldFetch vs Spider
- Apify MCP Server vs Spider
- jevcrawl vs Spider
- ScrapeOps Proxy API Aggregator vs Scrapingdog
- ScrapeOps Proxy API Aggregator vs Spider
Machine-readable
- This page as Markdown
/compare/scrapingdog-vs-spider-cloud.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapingdog.json·/api/v1/tools/spider-cloud.json - From a terminal
anchor compare scrapingdog spider-cloud(the CLI) - Over MCP
compare_tools {"a": "scrapingdog", "b": "spider-cloud"}at/mcp, no key