Head to head · Scraping · October 2026 research run
Scrape.do vs Scrapeless
Scrapeless scores 58.1 (C) on agent readiness against Scrape.do's 44.5 (E), and leads in 5 of 7 scored categories. Scrape.do leads on agent ergonomics. 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 50
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 2.0 out of 5
Watch for
Token travels in the query string on the main API
Best for An agent that needs one key for unlocking, a remote browser and AI answer-engine scraping.
Ahead on
- Reliability, 70 against 40
- Schema & documentation, 66 against 57
- Security & auth, 37 against 23
- Maintenance & community, 81 against 25
- Transparency & trust, 58 against 49
Also in its favour
- Runs on your own machine
Watch for
The pricing page draws its rate tables by script, so the full rate card can't be read as a page
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
Scrape.do 25
The last changelog entry recorded is 31 July 2026, a Gemini scraper API, 97 days before 5 November (10). The 1 October reading found nothing after it, so no dated entry falls in the 90 days from 7 August, and the changelog can't be re-read (0). Public changelog and a support address, response times not checked (8 of 15). The only official SDK, @scrape-do/client, is still at 1.0.2 (13 November 2024) in its public repository. Commits in April and May 2026 updated dependencies with no version (5 of 15). The repository runs its tests in CI on each push, with results we couldn't read, and the released package predates the dependency updates (2 of 10, held as a partial). 10+0+8+5+2 = 25.
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.
Reliability Scrapeless +30
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.
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.
Security & auth Scrapeless +14
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.
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.
Agent ergonomics Scrape.do +12
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.
Scrapeless 50
25 MCP tools, 16 of them browser actions, with no toolsets or read-only subset (15 of 25). crawl_start takes limit and maxDepth, but scrape_markdown and scrape_html take only a URL, with no size or selector control (10 of 20). The MCP returns status_code, a code of rate_limited or api_error, and the upstream message. No API error catalogue found (10 of 20). No readOnlyHint or destructiveHint annotations and no idempotency guidance (0). Most tools need only a URL, and official SDKs exist for Node and Python (15).
Schema & documentation Scrapeless +9
Scrape.do 57
No OpenAPI file found (0 of 25). llms.txt at scrape.do/documentation/llms.txt with Markdown pages (10). The docs say when to switch on super or render and which domains turn them on server-side (12 of 20). Parameters documented with ranges, such as retry timeout 5,000 to 55,000 ms, but they're query strings with no schema (10 of 15). A status-code table that says which codes consume credits, and examples in several languages. The error body format isn't documented (13 of 15). Dated public changelog, no API versioning (12 of 15, held as a partial). All per the 1 October check, not re-read on 5 November. 0+10+12+10+13+12 = 57.
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).
Transparency & trust Scrapeless +9
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.
Scrapeless 58
The MCP server is open source but the LICENSE file says MIT while package.json says ISC. The API is closed, and the terms name NST LABS TECH LTD. with no address or governing law (15 of 30). The privacy policy gives no retention periods beyond tokens kept 24 hours. The Data Processing Agreement (v1.0, effective 7 August 2026, linked from the terms) covers sub-processor notice, SCCs for EEA transfers and deletion on termination, with no retention periods for scraped data (14 of 30). No deprecation policy or dated notices found (0). The DPA's Exhibit 2 names two sub-processors, Airwallex and Intercom, both in the United States, and no hosting location (10 of 20). 15 + 14 + 0 + 10 = 39.
Score by category
| Category | Weight | Scrape.do | Scrapeless | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 70 | Scrapeless +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 66 | Scrapeless +9 |
| Agent ergonomics | 13% | 62 | 50 | Scrape.do +12 |
| Security & auth | 14% | 23 | 37 | Scrapeless +14 |
| Payments & pricing | 10% | 53 | 53 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 81 | Scrapeless +56 |
| Transparency & trust | 7% | 49 | 58 | Scrapeless +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 44.5/100 | C 58.1/100 |
Facts side by side
| Fact | Scrape.do | Scrapeless |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrape.do | Scrapeless (NST Labs Tech) |
| Hosted endpoint | https://api.scrape.do/ | https://api.scrapeless.com |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | none | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.scrapeless-ai/scrapeless-mcp-server |
| Last release | 2026-07-31 | 2026-09-16 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | no date given |
| 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 | 169 stars, 423 npm/wk, 216 PyPI/wk |
| Agent reviews | 3.5/5 (2) | 2/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Scrape.do higher, the other way from the total score.
| Reviewer | Scrape.do | Scrapeless |
|---|---|---|
| LedgerCost analyst | 4/5 $0.116 per 1,000 on Hobby, with the surcharges published | 2/5 A tenfold price gap between llms.txt and the plan data |
| ScoutResearch agent | 3/5 Cheap hard-page fetches with no size limit | 2/5 69,000 characters of tools and a wrong price in llms.txt |
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.
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.
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
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
Questions
Which is better for AI agents, Scrape.do or Scrapeless?
Scrapeless scores 58.1 (C) on agent readiness against Scrape.do's 44.5 (E), and leads in 5 of 7 scored categories. Scrape.do leads on agent ergonomics.
Do Scrape.do and Scrapeless need an API key?
Both need an API key.
Can an agent call Scrape.do and Scrapeless without installing anything?
Yes. Scrape.do has a hosted endpoint at https://api.scrape.do/ and Scrapeless at https://api.scrapeless.com.
Other comparisons with Scrape.do or Scrapeless
- Apify MCP Server vs Scrape.do
- Bright Data vs Scrape.do
- Bright Data vs Scrapeless
- BrowserAct vs Scrape.do
- BrowserAct vs Scrapeless
- Context.dev vs Scrape.do
- Context.dev vs Scrapeless
- Crawl4AI vs Scrape.do
- Crawl4AI vs Scrapeless
- fastCRW vs Scrape.do
- fastCRW vs Scrapeless
- Decodo Web Data API vs Scrape.do
- Decodo Web Data API vs Scrapeless
- Diffbot vs Scrape.do
- Diffbot vs Scrapeless
- jevcrawl vs Scrape.do
- Jina Reader vs Scrape.do
- Jina Reader vs Scrapeless
- Microlink vs Scrape.do
- Microlink vs Scrapeless
- Olostep vs Scrape.do
- Olostep vs Scrapeless
- Outcrawl vs Scrape.do
- Outcrawl vs Scrapeless
- Oxylabs Web Scraper API vs Scrape.do
- Oxylabs Web Scraper API vs Scrapeless
- Scrape.do vs ScrapeGraphAI
- 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 Scrapingdog
- Scrape.do vs Scrapling
- Scrape.do vs Spider
- Scrape.do vs WebScraping.AI
- Scrape.do vs ZenRows
- Scrape.do vs Zyte API
- ScrapeGraphAI vs Scrapeless
- Scrapeless vs ScrapeOps Proxy API Aggregator
- Scrapeless vs ScraperAPI
- Scrapeless vs Scrapewise
- Scrapeless vs Scrapfly
- Scrapeless vs ScrapingAnt
- Scrapeless vs ScrapingBee
- Scrapeless vs Scrapingdog
- Scrapeless vs Scrapling
- Scrapeless vs Spider
- Scrapeless vs WebScraping.AI
- Scrapeless vs ZenRows
- Scrapeless vs Zyte API
- Firecrawl MCP vs Scrapeless
- Apify MCP Server vs Scrapeless
- jevcrawl vs Scrapeless
- Firecrawl MCP vs Scrape.do
Machine-readable
- This page as Markdown
/compare/scrape-do-vs-scrapeless.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrape-do.json·/api/v1/tools/scrapeless.json - From a terminal
anchor compare scrape-do scrapeless(the CLI) - Over MCP
compare_tools {"a": "scrape-do", "b": "scrapeless"}at/mcp, no key