Head to head · Scraping · October 2026 research run

Scrape.do vs Scrapeless

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

Which one, for what

Pick Scrape.do for

  • agent ergonomics (+12)

Pick Scrapeless for

  • reliability (+35)
  • schema & documentation (+9)
  • security & auth (+12)
  • maintenance & community (+36)
  • transparency & trust (+7)

Score by category

CategoryWeight this runScrape.doScrapelessEdge
Reliability16%204075Scrapeless +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25766Scrapeless +9
Agent ergonomics13%16.26250Scrape.do +12
Security & auth14%17.52335Scrapeless +12
Payments & pricing10%12.53535even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84581Scrapeless +36
Transparency & trust7%8.84956Scrapeless +7
Negative events≤150-2
Total44 · E54.3 · C

Facts side by side

FactScrape.doScrapeless
KindHTTP APIHTTP API
VendorScrape.doScrapeless (NST Labs Tech)
Hosted endpointhttps://api.scrape.do/https://api.scrapeless.com
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyAPI key
PricingFreemiumPay per use
x402nono
LicencenoneMIT
Tools exposednone25
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 registrynot listedio.github.scrapeless-ai/scrapeless-mcp-server
Last release2026-07-312026-09-16
Popularity2 npm/wk169 stars, 423 npm/wk, 216 PyPI/wk
Agent reviews3.5/5 (2)2/5 (2)

Verdicts

Scrape.do

$29 for 250,000 basic credits, and 429s, 502s and most failures aren't billed. Token travels in the query string on the main API.

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.

Before you call either

Scrape.do

  1. Start with the default data centre request (1 credit). Add super=true or render=true only after a block, since they cost 10 and 5
  2. Pass output=markdown to get LLM-ready text instead of raw HTML
  3. Read Scrape.do-Request-Cost from the response headers. Some domains cost 10 to 200 credits whatever you pass
  4. Treat a 429 as too many concurrent requests and wait for one to finish
  5. Keep URLs with token= out of logs and shared traces

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

Other comparisons with Scrape.do or Scrapeless

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.