Head to head · Scraping · October 2026 research run

Scrapewise vs Scrapling

Scrapling scores 68.5 (B) on agent readiness against Scrapewise's 62.5 (B), and leads in 4 of 7 scored categories. Scrapewise leads on security & auth. Both do scraping.

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

Which one, for what

Scrapewise B

Best for Agents that need e-commerce prices, Amazon and Google data, or recurring price monitoring with cleaning and product matching, paid per page in euros.

Ahead on

  • Security & auth, 56 against 39

Also in its favour

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

Watch for

No status page, SLA, security.txt, disclosure policy or certification found

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 45
  • Payments & pricing, 90 against 60
  • Maintenance & community, 93 against 79

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

Scrapewise 60

No machine payment protocol (0). Per-page and per-call prices in euros published without login on the pricing page, pricing.md and each data API page (20). 5 free requests with no card (20). Signup is a browser flow with email or Google, keys are minted in the portal, and top-ups go through Stripe Checkout, so a person is needed (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.

Reliability Scrapling +20

Scrapewise 45

Read with the hosted lines. No status page found on scrapewise.ai, the docs, llms.txt or agents.md on 2 November 2026 (0). No readable incident history (5). Rate limits documented with numbers, per account per second and per day by plan (30 a second and 50,000 a day on STARTER up to 1,000 and 100,000,000 on BUSINESS, 2 a second unauthenticated), and 30 requests a second per key on the MCP gateway, plus an hourly cost ceiling there (15). 429 carries Retry-After and X-RateLimit-Remaining, Idempotency-Key is supported on scraper create and run, and paid MCP tools take an idempotency_key remembered for 24 hours (15). No SLA found (0). The API and MCP server are not marked beta, though AI control is in a test phase (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.

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.

Security & auth Scrapewise +17

Scrapewise 56

Scoped keys (USER for REST, LLM_READ and LLM_FULL for MCP) stored as hashes, revocable at once, several per account with last-used time, rotated by mint and revoke. No expiry and no finer scopes (26 of 30). LLM_READ cannot run paid tools or write, and deletes need a preview token committed within 5 minutes. Since 22 October the setup and destructive tools are no longer opt-in for a Full key, and LLM_FULL has no per-tool consent (16 of 20). A documented prompt-injection contract and guidance, but it rests on a type: "scraped" content block that the MCP specification of 25 November 2025 does not define, and the docs' statement that Anthropic's clients honour it by default was not confirmed (8 of 15). Every call is logged with a correlation id and key prefix and the wallet ledger itemises charges, but the operator sees logs only through support (6 of 15). No security.txt, disclosure policy, bug bounty or certification found, security.txt still 404 on 2 November (0 of 20).

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.

Maintenance & community Scrapling +14

Scrapewise 79

Read as a closed service. Changelog items dated 18, 20, 21, 22 and 23 October 2026 (30). At least three dated changes in 90 days, the September entry and the October items among them (20). A public changelog, a support address and site chat. Two outside issues on the MCP repository from 11 and 15 October had no reply per the 15 October check; GitHub's issue pages couldn't be read on 2 November (8 of 15). Verified namespace in the official MCP registry, version 0.1.1 still the latest on 2 November (15). The Python SDK has CI and trusted publishing at version 0.1.0, Beta, with no commit since 7 October (6 of 10). 30 + 20 + 8 + 15 + 6 = 79.

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.

Score by category

CategoryWeightScrapewiseScraplingEdge
Reliability16%4565Scrapling +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7981Scrapling +2
Agent ergonomics13%7271Scrapewise +1
Security & auth14%5639Scrapewise +17
Payments & pricing10%6090Scrapling +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7993Scrapling +14
Transparency & trust7%5452Scrapewise +2
Negative events≤1500
TotalB 62.5/100B 68.5/100

Facts side by side

FactScrapewiseScrapling
KindHTTP APIMCP server
VendorBEBOTECH OÜKarim Shoair
Hosted endpointhttps://mcp.scrapewise.ai/mcpno (local only)
TransportsStreamable HTTPstdio, Streamable HTTP
AuthAPI keyNone
PricingPay per useFree
x402nono
LicencenoneBSD-3-Clause
Tools exposed11317
Read-only variant documentednono
llms.txtyesno
MCP registryai.scrapewise/scrapewiseio.github.D4Vinci/Scrapling
Last release2026-10-232026-11-04
Terms last updated2025-10-29no document linked
Privacy policy last updated2025-10-29no 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
Popularity1 stars, 30 PyPI/wk104k stars
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

Scrapewise

Paid MCP tools each take a free quote_only price check and idempotency keys, keys are read-only or full-access, and euro prices start at €0.15 per 1,000 plain pages. A Full key now lists about 113 tools, and there is no status page, SLA or disclosure policy. The terms claim ownership of all scraped data.

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

Scrapewise

  1. Call each paid tool with quote_only: true first, then repeat with the same idempotency_key so a retry is charged once
  2. Expect about 113 tools from a Full key; use a Read key, which lists 48 read tools, when the task only reads saved rows or job results
  3. Use an LLM_READ key unless the task needs paid tools or writes, since LLM_FULL has no per-tool consent
  4. Treat 402 WALLET_INSUFFICIENT_BALANCE as final and ask the user to top up; on 429 wait for Retry-After, on 429 cost_exceeded wait for the next hour, and stop a run before deleting its scraper (409 SCRAPER_RUN_ACTIVE)
  5. Scrape many addresses with one scrapewise_run_scraper_url_list call (up to 5,000) and retry with the same name, never one scraper per address

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

Scrapling scores 68.5 (B) on agent readiness against Scrapewise's 62.5 (B), and leads in 4 of 7 scored categories. Scrapewise leads on security & auth.

Do Scrapewise and Scrapling need an API key?

Scrapewise needs an API key. Scrapling needs no key.

Can an agent call Scrapewise and Scrapling without installing anything?

Scrapewise has a hosted endpoint at https://mcp.scrapewise.ai/mcp. Scrapling runs on your own machine, with no hosted endpoint listed.

Are Scrapewise and Scrapling open source?

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

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