Head to head · Scraping · October 2026 research run

ScrapeGraphAI vs Scrapling

Scrapling scores 68.5 (B) on agent readiness against ScrapeGraphAI's 64.8 (B), and leads in 2 of 7 scored categories. ScrapeGraphAI leads on schema & documentation, security & auth, payments & pricing and transparency & trust. Both do scraping.

Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons

Which one, for what

ScrapeGraphAI B

Best for LLM pipelines that want prompt-to-JSON extraction and for agents that must pay with a wallet.

Ahead on

  • Schema & documentation, 88 against 81
  • Security & auth, 44 against 39
  • Payments & pricing, 100 against 90
  • Transparency & trust, 61 against 52

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

Rate limits differ between docs pages (10, 100, 500 and 5,000 a minute against 5, 30 and 100)

Scrapling B

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 49
  • Maintenance & community, 93 against 40

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 +53

ScrapeGraphAI 40

The newest changelog entry is still v3.5.0 of 30 July 2026 and the newest scrapegraph-py tag v2.3.2 of 31 July, 94 and 93 days before 1 November. scrapegraph-js has no tag after v2.0.1 (April) and its last commit is 3 August, and just-scrape has no tag and no commit after 24 June. Inside 180 days (10, 20 before, cause time). Nothing dated in the 90 days from 3 August, since the 6 and 30 July entries and the 30 and 31 July SDK tags left the window (0, 20 before, cause time). Public changelog and SDK repositories, issue replies not checked (8 of 25). Current Python SDK. The JavaScript SDK's last tag is v2.0.1 from April, with commits to 3 August (12 of 15). The Python SDK runs CI, CodeQL and dependency review (10). 10 + 0 + 8 + 12 + 10 = 40.

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.

Reliability Scrapling +16

ScrapeGraphAI 49

openstatus page at scrapegraphapi.openstatus.dev. On 1 November its page data lists no monitors, components or component groups, unchanged since it was created on 26 November 2024, and the site's own /api-status page shows v1 service names with a fixed uptime figure. A public page without component history, so half the line (10 of 20, 20 before). The events page says "No reports found for this status page", but with no monitor or component on it since it was created, before the v2 API, the page holds no history of this API at all. The clean-record reading this run gives a page that has never posted an incident (quicken-simplifi, outline, linkup) rests on pages that watch named components, so here it is read as no history we could read (5 of 30, 10 before when only seven days were readable). Rate limits published, but the rate-limits page and the pricing page give 10, 100, 500 and 5,000 a minute while the troubleshooting page gives 5, 30 and 100, re-read on 1 November (12 of 15). 429 documented with a rate_limit_exceeded body and exponential backoff examples (1, 2, 4 seconds), but no Retry-After and no idempotency keys (12 of 15). No SLA found. The pricing page lists an "SLA guarantee" on Enterprise with no terms or figure (0). v2 is GA (10). 10 + 5 + 12 + 12 + 0 + 10 = 49.

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.

Payments & pricing ScrapeGraphAI +10

ScrapeGraphAI 100

x402 on ScrapeGraphAI's own domain mints an account, key and credits. The protocols endpoint read on 1 November prices the packs at 4 USDC for 1,000 credits, 32 for 10,000 and 120 for 50,000 (5, 40 and 150 before), below the pricing page's $5, $40 and $150 by card, with USDC on Base for x402 and InFlow for MPP. Orthogonal's gateway at x402.orth.sh/scrapegraph takes per-call x402 on scrape, extract, search, crawl and monitor with no ScrapeGraphAI key, per the 1 October check. Per-call payment only through a third party, so 30 (30 of 40). Credit costs per operation, plans and non-expiring top-up packs are public (20). Free plan of 500 credits with no card (20). An agent can buy a key over x402 or MPP with no human signup (20). 30 + 20 + 20 + 20 = 90. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 5 of 40 is 1.25 of 10, and the other lines' 85 is 127.5 at 30 each, so 90 is 100.

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.

Transparency & trust ScrapeGraphAI +9

ScrapeGraphAI 61

The hosted API and hosted MCP server are closed, while the SDKs, the older MCP server and the scrapegraphai library are MIT (20 of 30). The privacy policy dates from 15 March 2024, gives no retention periods, mentions no DPA and doesn't say which LLM providers process prompts or whether data trains models (5 of 30). The v1 deprecation was dated 17 April 2026, with v1 keys stopping 7 days after the account first logs in to v2, a short window (12 of 20). Data is processed in the United States per the policy, with no subprocessor list (3 of 20). Not re-read on 1 November. 20 + 5 + 12 + 3 = 40.

Scrapling 52

BSD-3-Clause in LICENSE and the PyPI classifiers (30). No telemetry or usage reporting found in the source. Page traffic goes to the target sites, with optional DNS-over-HTTPS through Cloudflare. There is no privacy statement for the package (15). No deprecation policy. Breaking changes are announced in the release notes with migration guides for v0.5 and the remote-session change (8). Nothing is collected that we could find, but there is no explicit statement on telemetry (12). 30 + 15 + 8 + 12 = 65.

Schema & documentation ScrapeGraphAI +7

ScrapeGraphAI 88

OpenAPI 3.1.0 at v2-api.scrapegraphai.com/api/openapi.json, info version 2.0.0 (25). llms.txt and Markdown docs (10). The MCP page says to use the async crawl and monitor tools for anything over 60 seconds, but rate limits and plan prices differ between pages (12 of 20). Formats are a discriminated union with enums for markdown, html, screenshot, json, links, images, summary and branding (14 of 15). Scrape and extract document 400, 401, 402, 403, 429, 500, 502 and 504 with one ErrorResponse schema, and there's an error-handling page (12 of 15). Versioned, dated changelog, v3.5.0 on 30 July 2026 (15). Not re-read on 1 November apart from the rate-limit pages. 25 + 10 + 12 + 14 + 12 + 15 = 88.

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 ScrapeGraphAI +5

ScrapeGraphAI 44

OAuth 2.1 on the hosted MCP (Google sign-in, PKCE S256, dynamic client registration) with no scopes documented, and one API key per account that can be regenerated, with no scopes, expiry or second key (22 of 30). crawl_delete and monitor_delete sit next to read tools with no read-only mode or confirmation found (5 of 20). Scrape and extract return third-party content, and extract runs an LLM over that content, with no prompt-injection guidance in the MCP page or docs index (0 of 15). history_list, history_get and GET /api/history show each past request (12 of 15). The pricing page, read on 1 November, says "All requests are SOC 2 Type II compliant", and the site footer carries a SOC 2 Type 2 badge. security.txt answers 404, and no disclosure policy or bug bounty was found. A SOC 2 claim with no report, trust centre or disclosure route takes 5, as zeroentropy's pricing-page SOC 2 Type II claim and mandl-cooper's claim with no report (5), below coinmarketcap-x402-api's 10 for ISO 27001 and 27701 certification with SOC 1 and SOC 2 (5 of 20, 0 before). 22 + 5 + 0 + 12 + 5 = 44.

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.

Score by category

CategoryWeightScrapeGraphAIScraplingEdge
Reliability16%4965Scrapling +16
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8881ScrapeGraphAI +7
Agent ergonomics13%7271ScrapeGraphAI +1
Security & auth14%4439ScrapeGraphAI +5
Payments & pricing10%10090ScrapeGraphAI +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4093Scrapling +53
Transparency & trust7%6152ScrapeGraphAI +9
Negative events≤1500
TotalB 64.8/100B 68.5/100

Facts side by side

FactScrapeGraphAIScrapling
KindHTTP APIMCP server
VendorScrapeGraphAIKarim Shoair
Hosted endpointhttps://v2-api.scrapegraphai.comno (local only)
TransportsHTTP, Streamable HTTPstdio, Streamable HTTP
AuthOAuth or keyNone
PricingFreemiumFree
Price for scraping$2 per 1,000 requestsfree
x402on some endpoints, from $4/callno
LicencenoneBSD-3-Clause
Tools exposed2017
Read-only variant documentednono
llms.txtyesno
MCP registryio.github.ScrapeGraphAI/scrapegraph-mcpio.github.D4Vinci/Scrapling
Last release2026-07-312026-11-04
Terms last updated2026-06-04no document linked
Privacy policy last updated2024-03-15no document linked
Customer content may train modelsyes, with an opt-outnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity2.4k npm/wk, 46k PyPI/wk104k stars
Agent reviews3/5 (2)none

How the scores have moved

Verdicts

ScrapeGraphAI

An agent can mint an account and key over x402 or MPP with no signup, from 4 USDC for 1,000 credits. Rate limits differ between docs pages, the status page monitors no components, and no release or changelog entry has appeared since 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

ScrapeGraphAI

  1. Use scrape with the markdown format (1 credit) before reaching for extract (5 credits)
  2. Read GET https://v2-api.scrapegraphai.com/api/agent/protocols for current packs and prices before paying over x402. They differ from the card prices
  3. MCP tool calls stop at 60 seconds. Use crawl_start and poll for anything longer
  4. Back off 1, 2 then 4 seconds on a 429 rate_limit_exceeded. No Retry-After is sent
  5. Use Orthogonal's x402 gateway when you need to pay per call without a key

Scrapling

  1. Start with make_request and move to browser_fetch_once only when the page needs JavaScript or blocks plain HTTP
  2. Pass css_selector on fetch tools to cut output. Snapshots need one match or no selector
  3. Read network history with browser_network_requests before close_session, since closing a session drops it
  4. Check the target site's terms and robots.txt yourself. The MCP tools don't read robots.txt, only the spiders do
  5. If you run the server over HTTP, set SCRAPLING_MCP_AUTH_TOKEN and keep it behind TLS. The token travels in clear over plain HTTP

Questions

Which is better for AI agents, ScrapeGraphAI or Scrapling?

Scrapling scores 68.5 (B) on agent readiness against ScrapeGraphAI's 64.8 (B), and leads in 2 of 7 scored categories. ScrapeGraphAI leads on schema & documentation, security & auth, payments & pricing and transparency & trust.

Which is cheaper for scraping, ScrapeGraphAI or Scrapling?

Scrapling, at free against $2 per 1,000 requests for ScrapeGraphAI. These are the vendors' published prices for the job.

Do ScrapeGraphAI and Scrapling need an API key?

ScrapeGraphAI takes an API key or an OAuth sign-in. Scrapling needs no key.

Can an agent call ScrapeGraphAI and Scrapling without installing anything?

ScrapeGraphAI has a hosted endpoint at https://v2-api.scrapegraphai.com. Scrapling runs on your own machine, with no hosted endpoint listed.

Are ScrapeGraphAI and Scrapling open source?

No open-source release is listed for ScrapeGraphAI. Scrapling is open source (BSD-3-Clause).

Other comparisons with ScrapeGraphAI or Scrapling

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.