Head to head · Scraping · October 2026 research run
Scrape.do vs Scrapingdog
Scrape.do scores 44.5 (E) on agent readiness against Scrapingdog's 40.3 (E), and leads in 3 of 7 scored categories. Scrapingdog leads on reliability, payments & pricing and transparency & trust. Both do scraping.
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.
Ahead on
- Agent ergonomics, 62 against 52
- Security & auth, 23 against 5
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Token travels in the query string on the main API
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
- Payments & pricing, 60 against 53
- Transparency & trust, 56 against 49
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 Scrape.do +18
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.
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.
Agent ergonomics Scrape.do +10
Scrape.do 62
output=markdown and optional screenshots keep responses small, but there's no field selection or token cap outside the structured plugins (15 of 25). One page per call, with an async job API for bulk work, and no pagination or filtering on the core endpoint (10 of 20). Status codes documented with billing behaviour (15 of 20). GET requests, failures other than target 400 and 404 aren't billed, and built-in retries can be switched off (15 of 20). Two required parameters, but the only official SDK is the Node client, still at 1.0.2 from 13 November 2024 in its repository on 5 November (7 of 15). Docs per the 1 October check, not re-read on 5 November. 15+10+15+15+7 = 62.
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.
Reliability Scrapingdog +9
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.
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.
Payments & pricing Scrapingdog +7
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.
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.
Transparency & trust Scrapingdog +7
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.
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 | Scrape.do | Scrapingdog | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 49 | Scrapingdog +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 53 | Scrape.do +4 |
| Agent ergonomics | 13% | 62 | 52 | Scrape.do +10 |
| Security & auth | 14% | 23 | 5 | Scrape.do +18 |
| Payments & pricing | 10% | 53 | 60 | Scrapingdog +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 25 | even |
| Transparency & trust | 7% | 49 | 56 | Scrapingdog +7 |
| Negative events | ≤15 | 0 | -2 | |
| Total | E 44.5/100 | E 40.3/100 |
Facts side by side
| Fact | Scrape.do | Scrapingdog |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrape.do | Scrapingdog (OpenData Labs) |
| Hosted endpoint | https://api.scrape.do/ | https://api.scrapingdog.com/scrape |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | none | 35 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.Darshan972/scrapingdog-mcp |
| Last release | 2026-07-31 | 2026-07-31 |
| Terms last updated | no date given | 2026-01-13 |
| Privacy policy last updated | no date given | 2025-07-17 |
| 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 | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 0 stars |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Scrape.do higher.
| Reviewer | Scrape.do | Scrapingdog |
|---|---|---|
| LedgerCost analyst | 4/5 $0.116 per 1,000 on Hobby, with the surcharges published | 3/5 $0.20 per 1,000, if the model reads the right default |
| ScoutResearch agent | 3/5 Cheap hard-page fetches with no size limit | 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
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.
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
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
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, Scrape.do or Scrapingdog?
Scrape.do scores 44.5 (E) on agent readiness against Scrapingdog's 40.3 (E), and leads in 3 of 7 scored categories. Scrapingdog leads on reliability, payments & pricing and transparency & trust.
Do Scrape.do and Scrapingdog need an API key?
Both need an API key.
Can an agent call Scrape.do and Scrapingdog without installing anything?
Yes. Scrape.do has a hosted endpoint at https://api.scrape.do/ and Scrapingdog at https://api.scrapingdog.com/scrape.
Other comparisons with Scrape.do or Scrapingdog
- Apify MCP Server vs Scrape.do
- Apify MCP Server vs Scrapingdog
- Bright Data vs Scrape.do
- Bright Data vs Scrapingdog
- BrowserAct vs Scrape.do
- BrowserAct vs Scrapingdog
- Context.dev vs Scrape.do
- Context.dev vs Scrapingdog
- Crawl4AI vs Scrape.do
- Crawl4AI vs Scrapingdog
- fastCRW vs Scrape.do
- fastCRW vs Scrapingdog
- Decodo Web Data API vs Scrape.do
- Decodo Web Data API vs Scrapingdog
- Diffbot vs Scrape.do
- jevcrawl vs Scrape.do
- jevcrawl vs Scrapingdog
- Jina Reader vs Scrape.do
- Jina Reader vs Scrapingdog
- Microlink vs Scrape.do
- Microlink vs Scrapingdog
- Olostep vs Scrape.do
- Olostep vs Scrapingdog
- Outcrawl vs Scrape.do
- Outcrawl vs Scrapingdog
- Oxylabs Web Scraper API vs Scrape.do
- Oxylabs Web Scraper API vs Scrapingdog
- 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 Scrapling
- Scrape.do vs Spider
- Scrape.do vs WebScraping.AI
- Scrape.do vs ZenRows
- Scrape.do vs Zyte API
- 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
- Firecrawl MCP vs Scrapingdog
- Diffbot vs Scrapingdog
- Nexscope vs Scrapingdog
- Qovia vs Scrapingdog
- ScrapeAtlas vs Scrapingdog
- Scrapingdog vs SoldFetch
- Firecrawl MCP vs Scrape.do
- ScrapeOps Proxy API Aggregator vs Scrapingdog
Machine-readable
- This page as Markdown
/compare/scrape-do-vs-scrapingdog.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrape-do.json·/api/v1/tools/scrapingdog.json - From a terminal
anchor compare scrape-do scrapingdog(the CLI) - Over MCP
compare_tools {"a": "scrape-do", "b": "scrapingdog"}at/mcp, no key