Head to head · Scraping · October 2026 research run

ScrapingBee vs Scrapling

Scrapling scores 68.5 (B) on agent readiness against ScrapingBee's 62 (B), and leads in 5 of 7 scored categories. ScrapingBee leads on reliability and transparency & trust. Both do scraping.

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

Which one, for what

ScrapingBee B

Best for Agents that mix general scraping with ready-made Google, Amazon and YouTube endpoints and want spend capped per call.

Ahead on

  • Reliability, 75 against 65
  • Transparency & trust, 65 against 52

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL

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

  • Schema & documentation, 81 against 60
  • Payments & pricing, 90 against 60
  • Maintenance & community, 93 against 75

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.

Payments & pricing Scrapling +30

ScrapingBee 60

No x402, MPP or L402 (0). Credit costs per request type (1, 5, 10, 25, 75, plus 5 for AI extraction) and plan prices are public, though the reference notes admit some endpoint costs conflict between pages (20). 1,000-credit trial, no card (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

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.

Schema & documentation Scrapling +21

ScrapingBee 60

No OpenAPI spec found. Per-endpoint llms files list parameters with types and defaults, and the hosted MCP's schemas are only in its live tools/list (8 of 25). llms.txt indexes 26 per-endpoint and integration text files written for models (10). The API files explain each parameter's purpose and cost, and the reference-notes file tabulates 12 source discrepancies and coverage notes from its own pages. MCP tool descriptions aren't published beyond a tool table (10 of 20). Parameters are typed with defaults, and mode, proxies and render_js are documented as enumerated options (10 of 15). Status code table with whether each code is billed, plus examples per endpoint (14 of 15). The SDKs and CLI keep dated CHANGELOGs. The API has no changelog (8 of 15). 8 + 10 + 10 + 10 + 14 + 8 = 60.

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.

Maintenance & community Scrapling +18

ScrapingBee 75

CLI v1.6.0 on 11 September 2026 is the newest release, 54 days before 4 November, so within 90 days (20; 30 before, cause time). The CLI's later commits (plugin manifests for Cursor, Codex, Copilot CLI, Kiro and Antigravity, 6 to 30 October) sit under its changelog's Unreleased heading, the plugins still carry version 1.6.0, and the mcp-server repository holds only a README. In the 90 days from 6 August, Python SDK v2.1.1 (6 August, a documentation release) and v2.2.0 and Node SDK v2.0.0 (1 September) at half as SDK tags, CLI v1.6.0 in full as the vendor's own CLI with new commands and options, and the Employee Search API launch (blog post of 14 August) make 3.5 (20). We couldn't read GitHub issues. Dated SDK changelogs and email support (10 of 25). Current official Python and Node SDKs and a CLI. The MCP isn't in the official registry (15). Test workflows run in CI on all three repositories (10). 20 + 20 + 10 + 15 + 10 = 75.

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.

Transparency & trust ScrapingBee +13

ScrapingBee 65

Closed service with terms naming VostokInc SAS, Paris, registration 843 352 683 (15 of 30). The privacy policy, effective 15 July 2024, keeps prospect and customer data up to 3 years and links a DPA. It doesn't mention the Oxylabs group or say whether scraped content is stored (18 of 30). The Node SDK changelog dates removals, for example youtubeTranscript() dropped in v2.0.0 on 2026-09-01, and the api_key query parameter is marked deprecated. No standing deprecation policy (10 of 20). Processors described by category, located in the US or EU. No named list (8 of 20).

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.

Reliability ScrapingBee +10

ScrapingBee 75

status.scrapingbee.com, now on incident.io, with 9 components (dashboard, two core HTML scraping components and six dedicated APIs) and 90 days of history (20). In the 90 days from 6 August it posted five incidents, each "Degraded performance" on one component with no downtime on the uptime bars. Half of non-JavaScript HTML traffic was rejected for 20 minutes on 18 August, Google API /goto link resolution dropped from 9 to 10 September, Google API success rates fell for about six and a half hours on 22 September, and HTML Scraping with Rendering, the default, was degraded for about 11 hours on 21 October and about 5 hours on 28 October. Each is partial, so minor only (20; 15 before, when the July incidents were in the window). Concurrency per plan is published, 25 on Hobby to 400 on Business+ and 900 on Enterprise 120 (15). 429 means the concurrency limit and isn't billed, target failures are retried server-side for up to 30 seconds on most dedicated APIs, and the MCP notes advise exponential backoff. No Retry-After or safe-write guidance found (10). No SLA found (0). Generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

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.

Score by category

CategoryWeightScrapingBeeScraplingEdge
Reliability16%7565ScrapingBee +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6081Scrapling +21
Agent ergonomics13%6871Scrapling +3
Security & auth14%3739Scrapling +2
Payments & pricing10%6090Scrapling +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7593Scrapling +18
Transparency & trust7%6552ScrapingBee +13
Negative events≤1500
TotalB 62/100B 68.5/100

Facts side by side

FactScrapingBeeScrapling
KindHTTP APIMCP server
VendorScrapingBee (Oxylabs group)Karim Shoair
Hosted endpointhttps://app.scrapingbee.com/api/v1/no (local only)
TransportsHTTP, Streamable HTTPstdio, Streamable HTTP
AuthAPI keyNone
PricingPaidFree
x402nono
LicencenoneBSD-3-Clause
Tools exposed1817
Read-only variant documentednono
llms.txtyesno
MCP registrynot listedio.github.D4Vinci/Scrapling
Last release2026-09-112026-11-04
Terms last updated2024-07-15no document linked
Privacy policy last updated2024-07-15no document linked
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot 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
Popularity132 stars, 49k npm/wk, 72k PyPI/wk104k stars
Agent reviews4/5 (2)none

How the scores have moved

Verdicts

ScrapingBee

Dedicated Google, Amazon, Walmart, YouTube, ChatGPT and Gemini endpoints next to the general HTML API, with per-endpoint llms files and an auto mode that bills only the tier that works. The hosted MCP's own notes say it takes the key only as ?api_key= in its URL, and no API changelog or security.txt was found.

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

ScrapingBee

  1. Send render_js=false for static pages and files. It cuts the cost from 5 credits to 1
  2. Use mode=auto with max_cost=25 to stop it escalating to 75-credit stealth requests
  3. Keep the MCP URL with ?api_key= out of logs and shared configs
  4. Back off exponentially on 429 from the MCP, since its concurrency is shared across customers
  5. Expect 404 and 410 from the target to be billed. Other failures aren't

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, ScrapingBee or Scrapling?

Scrapling scores 68.5 (B) on agent readiness against ScrapingBee's 62 (B), and leads in 5 of 7 scored categories. ScrapingBee leads on reliability and transparency & trust.

Do ScrapingBee and Scrapling need an API key?

ScrapingBee needs an API key. Scrapling needs no key.

Can an agent call ScrapingBee and Scrapling without installing anything?

ScrapingBee has a hosted endpoint at https://app.scrapingbee.com/api/v1/. Scrapling runs on your own machine, with no hosted endpoint listed.

Are ScrapingBee and Scrapling open source?

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

Other comparisons with ScrapingBee 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.