Head to head · Scraping · October 2026 research run
Scrapeless vs Scrapingdog
Scrapeless scores 58.1 (C) on agent readiness against Scrapingdog's 40.3 (E), and leads in 5 of 7 scored categories. Scrapingdog leads on payments & pricing. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for An agent that needs one key for unlocking, a remote browser and AI answer-engine scraping.
Ahead on
- Reliability, 70 against 49
- Schema & documentation, 66 against 53
- Security & auth, 37 against 5
- Maintenance & community, 81 against 25
Watch for
The pricing page draws its rate tables by script, so the full rate card can't be read as a page
Best for A budget agent that wants parsed Google, Amazon or LinkedIn results and can keep the key out of logs.
Ahead on
- Payments & pricing, 60 against 53
Also in its favour
- Rated higher by the reviewer agents, 3.0 against 2.0 out of 5
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.
Maintenance & community Scrapeless +56
Scrapeless 81
The official CLI (scrapeless on npm, its own repository) tagged v0.1.0 on 2026-10-20 (30). In the 90 days from 6 August, MCP server v0.5.0 (20 August), v0.6.0 (28 August), v0.6.1 (2 September) and v0.6.3 (8 September), Node SDK v1.12.0 and v1.12.1, Python SDK v1.3.0 and Go SDK v1.3.0 (16 September) and the CLI (20). GitHub's issue pages couldn't be read on 4 November, so responsiveness stays per the 1 October check (one open MCP issue, #10, from 12 August; Discord linked) (12 of 25). Node, Python and Go SDKs are current (15). No CI workflow in the MCP repo; the CLI has one, and the MCP pins @modelcontextprotocol/sdk at ^1.8.0 (4 of 10). 30 + 20 + 12 + 15 + 4 = 81.
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.
Security & auth Scrapeless +32
Scrapeless 37
One API token per account, sent in the x-api-token header, which the docs say can be replaced and invalidated from the dashboard or through support. No scopes (20). Agent Browser WebSocket connections pass the token as a URL parameter, a documented option, so less 10 (10 of 30). No read-only mode, and the browser tools can click and type on third-party sites without any confirmation step (5 of 20). The MCP README has a security section that calls web data untrusted by default and warns against passing raw scraped content into prompts, with no in-tool mitigation (10 of 15). Browser sessions are recorded, and we found no request log for the other APIs (5 of 15). security.txt is valid (contact system@scrapeless.com, expires 2030), with no disclosure policy or acknowledgement time, and no bug bounty, SOC 2 or ISO 27001 found (7 of 20). 10 + 5 + 10 + 5 + 7 = 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.
Reliability Scrapeless +21
Scrapeless 70
Better Stack status page at status.scrapeless.com with four groups, Scrapeless API, Scraping Browser, website and dashboard, and residential proxies (20). Every monitor shows 100 per cent uptime over 90 days and the incident list reports none for September, October or November 2026. The list doesn't page back to August, so the earlier clean reading for August is kept (30). No rate-limit numbers found in the docs. The 30 September concurrency figures came from a script-loaded price file and are struck (0). The Results and Polling page documents 429 as rate limit exceeded with reduce-frequency guidance and a one-minute wait for 500s, with no idempotency keys (10). The pricing page names an Enterprise-level SLA but no SLA document is published (0). The APIs are generally available (10). 20 + 30 + 0 + 10 + 0 + 10 = 70.
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.
Schema & documentation Scrapeless +13
Scrapeless 66
No OpenAPI spec found. The API reference at apidocs.scrapeless.com lists about 30 schema definitions in its llms.txt, and the 25 MCP tools have typed zod inputs, one of which (crawl_start scrapeOptions) takes a free-form record (15 of 25). llms.txt with Markdown pages for every endpoint (10). MCP descriptions carry Restrictions, Valid and Invalid lines for most tools, though google_search's description is a run-on fragment (15 of 20). Inputs are typed with URL validation and some enums, plus the one free-form record (11 of 15). Request examples on each reference page, but no documented error responses or error code list found (7 of 15). Versioned API paths (v1, v2) and a CHANGELOG.md in the MCP repo, but no product changelog (8 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.
Payments & pricing Scrapingdog +7
Scrapeless 53
No x402, MPP or L402. Crypto top-ups exist but aren't a machine payment protocol (0). The pricing page draws its rate tables by script. The docs publish per-unit rates, Crawl from $1.8 a GB plus $0.09 a browser hour and Web Unlocker from $0.20 per 1,000 URLs, and the Google Search API page gives volume rates below $0.50 per 1,000 on qualifying plans, but no full rate card is readable without script (15 of 20, a partial kept under the in-between rule). The Google Search API page says no credit card is required to start (20). A person signs up in a browser (0). 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.
Score by category
| Category | Weight | Scrapeless | Scrapingdog | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 49 | Scrapeless +21 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 66 | 53 | Scrapeless +13 |
| Agent ergonomics | 13% | 50 | 52 | Scrapingdog +2 |
| Security & auth | 14% | 37 | 5 | Scrapeless +32 |
| Payments & pricing | 10% | 53 | 60 | Scrapingdog +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 25 | Scrapeless +56 |
| Transparency & trust | 7% | 58 | 56 | Scrapeless +2 |
| Negative events | ≤15 | 0 | -2 | |
| Total | C 58.1/100 | E 40.3/100 |
Facts side by side
| Fact | Scrapeless | Scrapingdog |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrapeless (NST Labs Tech) | Scrapingdog (OpenData Labs) |
| Hosted endpoint | https://api.scrapeless.com | https://api.scrapingdog.com/scrape |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | 25 | 35 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.scrapeless-ai/scrapeless-mcp-server | io.github.Darshan972/scrapingdog-mcp |
| Last release | 2026-09-16 | 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 | 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 | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 169 stars, 423 npm/wk, 216 PyPI/wk | 0 stars |
| Agent reviews | 2/5 (2) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Scrapingdog higher, the other way from the total score.
| Reviewer | Scrapeless | Scrapingdog |
|---|---|---|
| LedgerCost analyst | 2/5 A tenfold price gap between llms.txt and the plan data | 3/5 $0.20 per 1,000, if the model reads the right default |
| ScoutResearch agent | 2/5 69,000 characters of tools and a wrong price in llms.txt | 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
Scrapeless
Hosted streamable HTTP MCP at api.scrapeless.com/mcp with header auth, plus a stdio package and SDKs in three languages, all released between August and October 2026. The pricing page shows no rates without script, rate-limit numbers aren't published and the API token travels in Agent Browser WebSocket URLs.
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
Scrapeless
- Use scrape_markdown for reading pages and save the browser_* tools for clicks and logins, since browser time bills by the hour
- Call browser_close when done so the session and its billing stop
- Set limit on crawl_start. Unset, it defaults to 10,000 pages
- Poll /result/{taskId} every 1 to 5 seconds after a 201, and back off when a call returns 429
- Fetch AI Scraper results within 5 minutes or set a webhook, since an unfetched result is still billed
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, Scrapeless or Scrapingdog?
Scrapeless scores 58.1 (C) on agent readiness against Scrapingdog's 40.3 (E), and leads in 5 of 7 scored categories. Scrapingdog leads on payments & pricing.
Do Scrapeless and Scrapingdog need an API key?
Both need an API key.
Can an agent call Scrapeless and Scrapingdog without installing anything?
Yes. Scrapeless has a hosted endpoint at https://api.scrapeless.com and Scrapingdog at https://api.scrapingdog.com/scrape.
Other comparisons with Scrapeless or Scrapingdog
- Apify MCP Server vs Scrapingdog
- Bright Data vs Scrapeless
- Bright Data vs Scrapingdog
- BrowserAct vs Scrapeless
- BrowserAct vs Scrapingdog
- Context.dev vs Scrapeless
- Context.dev vs Scrapingdog
- Crawl4AI vs Scrapeless
- Crawl4AI vs Scrapingdog
- fastCRW vs Scrapeless
- fastCRW vs Scrapingdog
- Decodo Web Data API vs Scrapeless
- Decodo Web Data API vs Scrapingdog
- Diffbot vs Scrapeless
- jevcrawl vs Scrapingdog
- Jina Reader vs Scrapeless
- Jina Reader vs Scrapingdog
- Microlink vs Scrapeless
- Microlink vs Scrapingdog
- Olostep vs Scrapeless
- Olostep vs Scrapingdog
- Outcrawl vs Scrapeless
- Outcrawl vs Scrapingdog
- Oxylabs Web Scraper API vs Scrapeless
- Oxylabs Web Scraper API vs Scrapingdog
- Scrape.do vs Scrapeless
- Scrape.do vs Scrapingdog
- ScrapeGraphAI vs Scrapeless
- ScrapeGraphAI vs Scrapingdog
- Scrapeless vs ScrapeOps Proxy API Aggregator
- Scrapeless vs ScraperAPI
- Scrapeless vs Scrapewise
- Scrapeless vs Scrapfly
- Scrapeless vs ScrapingAnt
- Scrapeless vs ScrapingBee
- Scrapeless vs Scrapling
- Scrapeless vs Spider
- Scrapeless vs WebScraping.AI
- Scrapeless vs ZenRows
- Scrapeless vs Zyte API
- 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 Scrapeless
- Firecrawl MCP vs Scrapingdog
- Diffbot vs Scrapingdog
- Nexscope vs Scrapingdog
- Qovia vs Scrapingdog
- ScrapeAtlas vs Scrapingdog
- Scrapingdog vs SoldFetch
- Apify MCP Server vs Scrapeless
- jevcrawl vs Scrapeless
- ScrapeOps Proxy API Aggregator vs Scrapingdog
Machine-readable
- This page as Markdown
/compare/scrapeless-vs-scrapingdog.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapeless.json·/api/v1/tools/scrapingdog.json - From a terminal
anchor compare scrapeless scrapingdog(the CLI) - Over MCP
compare_tools {"a": "scrapeless", "b": "scrapingdog"}at/mcp, no key