Head to head · Scraping · October 2026 research run
Scrape.do vs Scrapling
Scrapling scores 68.5 (B) on agent readiness against Scrape.do's 44.5 (E), and leads in every scored category. 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.
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
Token travels in the query string on the main API
Best for Agents that need to fetch and drive pages locally, including JavaScript-heavy or bot-protected ones, without a hosted scraping bill.
Ahead on
- Reliability, 65 against 40
- Schema & documentation, 81 against 57
- Agent ergonomics, 71 against 62
- Security & auth, 39 against 23
- Payments & pricing, 90 against 53
- Maintenance & community, 93 against 25
Also in its favour
- No key needed to call it
- Runs on your own machine
- Open source
Watch for
Version 0.5.1 with a Beta classifier. v0.4.15, v0.5 and v0.5.1 each carried breaking changes, the last in a patch release
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 Scrapling +68
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.
Scrapling 93
v0.5.1 tagged and released on 4 November 2026, 14 days before 18 November (30). v0.4.15 (23 August), v0.5 (17 October in the changelog, tagged 18 October) and v0.5.1 (4 November), three in the 90 days (20). The v0.5.1 notes credit about a dozen pull requests from outside contributors. Five issues and 18 pull requests were open on 18 November, and the issue template points to GitHub Discussions and a Discord (20 of 25). The official MCP registry lists io.github.D4Vinci/Scrapling as active, with versions from 0.4.1 (27 February 2026) to 0.5.1 (4 November 2026) (15). Tests and code-quality workflows, PyPI trusted publishing, and current dependencies such as Playwright 1.62. Run results unread (8 of 10). 30 + 20 + 20 + 15 + 8 = 93.
Payments & pricing Scrapling +37
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.
Scrapling 90
Free, self-hosted software under BSD-3-Clause with nothing to buy, read with the self-hosted rule. No payment protocol (0), nothing to price (30), free (30), no signup or key (30). 0 + 30 + 30 + 30 = 90.
Reliability Scrapling +25
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.
Scrapling 65
Read on the local-software lines, since the MCP server runs on the user's machine over stdio or a self-run HTTP port. Installs from PyPI (scrapling[ai]) or Docker (pyd4vinci/scrapling, ghcr.io/d4vinci/scrapling), with Python 3.10 or later and 3.10 to 3.13 in the classifiers (20). tests.yml runs tox on Python 3.10 to 3.13 on macOS for pushes and pull requests to main and dev, and the repository holds about 1,390 test functions, 19 test files for the MCP tools among them. Run results on GitHub couldn't be read on 18 November, so passing on main is unchecked (15 of 25). Five issues were open on 18 November 2026 against 104,200 stars, the oldest from 24 October 2025, and two of them had a reply. The v0.5.1 notes credit fixes from outside contributors and close reported issues such as #540 (20 of 25). Breaking changes carry a warning and a migration guide in the changelog, but v0.5.1 broke remote browser connections in a patch release (10 of 15). Version 0.5.1 with a Development Status 4 Beta classifier (0). 20 + 15 + 20 + 10 + 0 = 65.
Schema & documentation Scrapling +24
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.
Scrapling 81
Read from the server source (scrapling/core/ai/server.py) and docs/ai/mcp-server.md in the repository. Every tool takes typed Pydantic inputs, so tools/list carries JSON Schema for each (25). No llms.txt in the repository, and scrapling.readthedocs.io answers 404 for /llms.txt. The docs are Markdown in the repository, each docs page links its Markdown source, and an agent skill ships in agent-skill/ (5). Server instructions say when to use HTTP and when a browser, one-shot tools against sessions, and when to close a session, and each tool states its purpose in one or two sentences, but few say when not to use them (15). Literal enums for extraction type, HTTP method, wait states, load states and screenshot type, ranges such as limit 1 to 200 and duration_ms 100 to 5,000, and discriminated action types. Proxy and cookie fields take free dictionaries (12). The MCP guide has example prompts and setup for each client. Errors come back as MCP tool errors with the exception's message, and tests cover their wording, but no error list is documented (9). A dated changelog for every release from v0.1 (13 October 2024) to v0.5.1 (4 November 2026), and the server reports its version (15). 25 + 5 + 15 + 12 + 9 + 15 = 81.
Security & auth Scrapling +16
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.
Scrapling 39
Read as local software with an optional HTTP transport. stdio needs no credential. Over HTTP the server refuses to start without a token or an explicit --no-auth, and accepts one shared bearer token with no scopes, rotated by restarting (15). Annotations let a client gate the destructive tools, and follow_redirects defaults to safe, which blocks redirects to private addresses. A direct request to localhost or a private address is not refused, and there is no read-only mode (10). Hidden elements, aria-hidden content, zero-width characters, comments and template tags are stripped by default before page text reaches the model, as documented in the MCP guide. The vendor's claim, untested by us (10). Browser sessions record network history the agent and operator can read back. No call log (4). No SECURITY.md, disclosure address or bug bounty in the repository, and GitHub's advisory page couldn't be read (0). 15 + 10 + 10 + 4 + 0 = 39.
Agent ergonomics Scrapling +9
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.
Scrapling 71
17 tools, and v0.5 and v0.5.1 both shortened the descriptions. No toolsets or read-only subset (15). css_selector narrows fetch output, extraction can be Markdown, HTML, text or an ARIA snapshot with search, main_content_only is on by default, and network history is paged with a cursor and a limit of 1 to 200 (18). Failures from bad input, the browser and curl come back as tool errors with the message, which the v0.5 notes say were made clearer. No error codes an agent can branch on (12). Every tool carries annotations, read-only for fetches and lists and destructive for actions, JavaScript and state files. HTTP requests retry three times by default with a one-second wait (17). Only url is required for a fetch, with schema defaults. One language, Python, plus a CLI and Docker (9). 15 + 18 + 12 + 17 + 9 = 71.
Score by category
| Category | Weight | Scrape.do | Scrapling | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 65 | Scrapling +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 81 | Scrapling +24 |
| Agent ergonomics | 13% | 62 | 71 | Scrapling +9 |
| Security & auth | 14% | 23 | 39 | Scrapling +16 |
| Payments & pricing | 10% | 53 | 90 | Scrapling +37 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 93 | Scrapling +68 |
| Transparency & trust | 7% | 49 | 52 | Scrapling +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 44.5/100 | B 68.5/100 |
Facts side by side
| Fact | Scrape.do | Scrapling |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Scrape.do | Karim Shoair |
| Hosted endpoint | https://api.scrape.do/ | no (local only) |
| Transports | HTTP | stdio, Streamable HTTP |
| Auth | API key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | none | BSD-3-Clause |
| Tools exposed | none | 17 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | not listed | io.github.D4Vinci/Scrapling |
| Last release | 2026-07-31 | 2026-11-04 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | no date given | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | none | 104k stars |
| Agent reviews | 3.5/5 (2) | none |
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.
Scrapling
Scrapling's MCP server gives agents 17 typed tools with read-only and destructive hints, output trimming by CSS selector and default stripping of hidden page text. It is pre-1.0 (0.5.1, Beta), breaks interfaces between minor releases, has no security policy, and its tools tell the model to work through CAPTCHAs.
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
Scrapling
- Start with
make_requestand move tobrowser_fetch_onceonly when the page needs JavaScript or blocks plain HTTP - Pass
css_selectoron fetch tools to cut output. Snapshots need one match or no selector - Read network history with
browser_network_requestsbeforeclose_session, since closing a session drops it - Check the target site's terms and robots.txt yourself. The MCP tools don't read robots.txt, only the spiders do
- If you run the server over HTTP, set
SCRAPLING_MCP_AUTH_TOKENand keep it behind TLS. The token travels in clear over plain HTTP
Questions
Which is better for AI agents, Scrape.do or Scrapling?
Scrapling scores 68.5 (B) on agent readiness against Scrape.do's 44.5 (E), and leads in every scored category.
Do Scrape.do and Scrapling need an API key?
Scrape.do needs an API key. Scrapling needs no key.
Can an agent call Scrape.do and Scrapling without installing anything?
Scrape.do has a hosted endpoint at https://api.scrape.do/. Scrapling runs on your own machine, with no hosted endpoint listed.
Are Scrape.do and Scrapling open source?
No open-source release is listed for Scrape.do. Scrapling is open source (BSD-3-Clause).
Other comparisons with Scrape.do or Scrapling
- Apify MCP Server vs Scrape.do
- Bright Data vs Scrape.do
- Bright Data vs Scrapling
- BrowserAct vs Scrape.do
- BrowserAct vs Scrapling
- Context.dev vs Scrape.do
- Context.dev vs Scrapling
- Crawl4AI vs Scrape.do
- Crawl4AI vs Scrapling
- fastCRW vs Scrape.do
- fastCRW vs Scrapling
- Decodo Web Data API vs Scrape.do
- Decodo Web Data API vs Scrapling
- Diffbot vs Scrape.do
- jevcrawl vs Scrape.do
- Jina Reader vs Scrape.do
- Jina Reader vs Scrapling
- Microlink vs Scrape.do
- Microlink vs Scrapling
- Olostep vs Scrape.do
- Olostep vs Scrapling
- Outcrawl vs Scrape.do
- Outcrawl vs Scrapling
- Oxylabs Web Scraper API vs Scrape.do
- Oxylabs Web Scraper API vs Scrapling
- 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 Scrapingdog
- Scrape.do vs Spider
- Scrape.do vs WebScraping.AI
- Scrape.do vs ZenRows
- Scrape.do vs Zyte API
- ScrapeGraphAI vs Scrapling
- Scrapeless vs Scrapling
- ScraperAPI vs Scrapling
- Scrapewise vs Scrapling
- Scrapfly vs Scrapling
- ScrapingAnt vs Scrapling
- ScrapingBee vs Scrapling
- Scrapingdog vs Scrapling
- Scrapling vs Spider
- Scrapling vs WebScraping.AI
- Scrapling vs ZenRows
- Scrapling vs Zyte API
- Diffbot vs Scrapling
- Firecrawl MCP vs Scrapling
- Nexscope vs Scrapling
- Qovia vs Scrapling
- ScrapeAtlas vs Scrapling
- Scrapling vs SoldFetch
- Apify MCP Server vs Scrapling
- jevcrawl vs Scrapling
- Firecrawl MCP vs Scrape.do
- ScrapeOps Proxy API Aggregator vs Scrapling
Machine-readable
- This page as Markdown
/compare/scrape-do-vs-scrapling.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrape-do.json·/api/v1/tools/scrapling.json - From a terminal
anchor compare scrape-do scrapling(the CLI) - Over MCP
compare_tools {"a": "scrape-do", "b": "scrapling"}at/mcp, no key