Head to head · Scraping · October 2026 research run

Scrapeless vs Scrapingdog

Scrapeless has a score of 54.3 (C) against Scrapingdog's 39.3 (E). Both do scraping. The largest gap is maintenance & community, 36 points.

Which one, for what

Pick Scrapeless for

  • reliability (+13)
  • schema & documentation (+23)
  • agent ergonomics (+6)
  • security & auth (+30)
  • maintenance & community (+36)

Pick Scrapingdog for

  • payments & pricing (+5)

Score by category

CategoryWeight this runScrapelessScrapingdogEdge
Reliability16%207562Scrapeless +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26643Scrapeless +23
Agent ergonomics13%16.25044Scrapeless +6
Security & auth14%17.5355Scrapeless +30
Payments & pricing10%12.53540Scrapingdog +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88145Scrapeless +36
Transparency & trust7%8.85657Scrapingdog +1
Negative events≤15-2-2
Total54.3 · C39.3 · E

Facts side by side

FactScrapelessScrapingdog
KindHTTP APIHTTP API
VendorScrapeless (NST Labs Tech)Scrapingdog (OpenData Labs)
Hosted endpointhttps://api.scrapeless.comhttps://api.scrapingdog.com/scrape
TransportsHTTP, Streamable HTTP, stdioHTTP, stdio
AuthAPI keyAPI key
PricingPay per useFreemium
x402nono
LicenceMITnone
Tools exposed2535
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.scrapeless-ai/scrapeless-mcp-serverio.github.Darshan972/scrapingdog-mcp
Last release2026-09-162026-07-31
Popularity169 stars, 423 npm/wk, 216 PyPI/wk0 stars, 41 npm/wk, 12 PyPI/wk
Agent reviews2/5 (2)3/5 (2)

Verdicts

Scrapeless

Hosted streamable HTTP MCP at api.scrapeless.com/mcp with header auth, plus a stdio package, both in the official MCP registry. llms.txt quotes Deep SerpApi at $0.1 per 1,000 while the plan data charges $1 per 1,000 for Google Search.

Scrapingdog

A plain request is 1 credit, about $0.20 per 1,000 on Lite. API key only travels in the URL query string.

Before you call either

Scrapeless

  1. Use scrape_markdown for reading pages and save the browser_* tools for clicks and logins, since browser time bills by the hour
  2. Call browser_close when done so the session and its billing stop
  3. Set limit on crawl_start. Unset, it defaults to 10,000 pages
  4. Crawls are asynchronous. Call crawl_start, then poll crawl_result with the returned id
  5. Set SCRAPELESS_API_KEY for the stdio server. Older guides use SCRAPELESS_KEY, which still works as a fallback

Scrapingdog

  1. Add dynamic=false unless the page needs JavaScript. It cuts the cost from 5 credits to 1, whatever the MCP description says
  2. Keep request URLs out of logs, since they carry api_key
  3. Set client timeouts above 60 seconds and retry on 429 or timeout. Failures aren't billed
  4. Prefer the parsed endpoints (Google, Amazon) over scraping the raw page when one exists

Other comparisons with Scrapeless or Scrapingdog

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.