Head to head · Scraping · October 2026 research run

Context.dev vs Scrapling

Context.dev scores 78.8 (A) on agent readiness against Scrapling's 68.5 (B), and leads in 5 of 7 scored categories. Scrapling leads on payments & pricing and maintenance & community. Both do scraping.

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

Which one, for what

Context.dev A

Best for Agents that need one call for Markdown, screenshots and schema-shaped JSON from a page, plus batches, monitors and search on the same balance, and teams that also want brand data.

Ahead on

  • Schema & documentation, 96 against 81
  • Agent ergonomics, 90 against 71
  • Security & auth, 83 against 39
  • Transparency & trust, 78 against 52

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

The terms let Context.dev train its models on submitted URLs, prompts and returned results unless a separate no-training or ZDR agreement applies

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

  • Payments & pricing, 90 against 75
  • Maintenance & community, 93 against 85

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • Open source
  • No incidents deducted, where Context.dev loses 3 points for them

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.

Security & auth Context.dev +44

Context.dev 83

Restricted keys scoped to data calls, logs, monitors, batches and, since 28 October, access policies on every plan, revocable, with a documented rotation process, and OAuth with PKCE on the MCP server. The docs say never to put a key in a URL and no query-string option was found (30). Read-only scopes for logs, monitors and batches, and the MCP guide, re-read on 1 November, asks clients to keep approvals on for tools that start work or change state. Access policies (28 October) can limit which domains requests reach, per key or account, but are enabled per organisation on request. MCP tool annotations couldn't be checked (15 of 20). The MCP guide, agent quickstart and agent-context guide say to treat page content as untrusted data that can't authorise tool calls. No filter or classifier found (10 of 15). Request logs with retained input and response for up to a year, a Logs API, per-key usage and X-Credits-Used (15). SOC 2 Type II since 18 September 2026 per the changelog, and the trust centre on 1 November shows SOC 2 Type 2 and Type 1 as compliant, and a valid security.txt to 26 September 2027 that points to the support address. No disclosure policy or bug bounty found (13 of 20). 30 + 15 + 10 + 15 + 13 = 83.

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.

Transparency & trust Context.dev +26

Context.dev 78

Closed service. SDKs and CLI are Apache-2.0, the MCP server is closed. Terms last updated 26 October 2026 under Delaware law now say automated access is expected, that software calling the API is never by itself a violation, and that benchmarking is allowed, so the bar on bots and scripts that cost 2 points on 17 October is gone (15 of 30, up from 13). Privacy policy (31 October 2026) and terms agree that requests and results may be used to train models unless a request uses zero data retention or another agreement applies. The docs keep request logs up to a year and batch results 180 days, the DPA (29 October 2026) returns or deletes data within 10 business days of the end of service, but the privacy policy keeps API request logs as long as needed and gives no fixed periods (18 of 30). A stated 90-day minimum for deprecated surfaces and dated changelog notices (20). The website sub-processor list, last updated 31 October 2026, names 15 with each location and purpose and promises 14 days' notice of changes, and it now agrees with the trust centre, which also lists 15 and names Cloudflare among them, where on 17 October the two lists disagreed (20, up from 14). 15 + 18 + 20 + 20 = 73.

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.

Agent ergonomics Context.dev +19

Context.dev 90

formats selects outputs, and mainContentOnly, include and exclude selectors and Highlights with maxCharacters shrink responses. The MCP server registers 42 tools by the vendor's count with no toolsets found, and caps responses at 40,000 characters with a truncation flag, re-read on 1 November (20 of 25). Map and Crawl filter by path, subdomain, count and, since 19 October, an exclude pattern, crawls take page, depth and time limits, and logs, batches, news and People Search paginate (20). Every failed output returns an error_code and a message with the next step, 403 names the missing permission, and since 18 October credit exhaustion returns 402 with error_data saying how to refill (20). Batch submission is idempotent, reads are safe to retry and unbilled on 408, 429 and 5xx. MCP readOnly and destructive hints couldn't be checked (15 of 20). Two required fields, and SDKs in five languages (15). 20 + 20 + 20 + 15 + 15 = 90.

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.

Schema & documentation Context.dev +15

Context.dev 96

Public OpenAPI 3.1 at www.context.dev/openapi.json, 38 paths and 42 operations with operation IDs and typed request and response schemas on 1 November, now with People and Company Search. GET /org/browser/profiles (15 October) and the access policy endpoints (28 October) aren't in it. The MCP tool definitions are behind OAuth and weren't read (25). llms.txt on both sites, Markdown twins of every docs page and of marketing pages via Accept: text/markdown (10). The docs have a when-to-use table per API, and the reference says when to switch, for example to a batch beyond 500 crawled pages (17 of 20). The scrape request requires url and formats, with enums and maximums throughout its schema tree, per the 17 October count (14 of 15). Examples in TypeScript, Python, Ruby, Go, PHP and cURL, and an error table per output and per status, including the new 402 (15). /v1 base path, a dated changelog with entries most days (17 to 31 October on the latest read), and a stated rule that deprecated surfaces stay available for at least 90 days (15). 25 + 10 + 17 + 14 + 15 + 15 = 96.

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.

Payments & pricing Scrapling +15

Context.dev 75

No x402, MPP or L402 in llms.txt, the pricing page or the OpenAPI file on 1 November (0). Credit costs per operation and overage per 1,000 credits are public (20). Free plan of 1,000 credits a month, "no credit card required" (20). auth.md, re-read on 1 November, lets an agent start registration and poll for a key, but the person completes the claim in a browser, and the docs MCP route also needs a browser sign-in (10 of 20). 0 + 20 + 20 + 10 = 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

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.

Maintenance & community Scrapling +8

Context.dev 85

TypeScript SDK 3.21.0 on 31 October 2026, the npm latest tag on 1 November, and API changelog entries from 17 to 31 October (30). 19 TypeScript SDK releases from 3.9.0 on 18 October to 3.21.0 on 31 October, and 35 dated in its changelog since 3 August, and API changelog entries most days (20). Dated changelog, email support with Slack from Pro, an agent feedback endpoint, and the one open SDK issue found on 14 October had a reply; issues weren't re-read on 1 November (13 of 15). Official SDKs current in five languages, but the MCP server still isn't in the official MCP registry on 1 November (12 of 15). SDK repositories run CI and release-please (10). 30 + 20 + 13 + 12 + 10 = 85.

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

CategoryWeightContext.devScraplingEdge
Reliability16%6765Context.dev +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9681Context.dev +15
Agent ergonomics13%9071Context.dev +19
Security & auth14%8339Context.dev +44
Payments & pricing10%7590Scrapling +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8593Scrapling +8
Transparency & trust7%7852Context.dev +26
Negative events≤15-30
TotalA 78.8/100B 68.5/100

Facts side by side

FactContext.devScrapling
KindHTTP APIMCP server
VendorContext Dev Inc.Karim Shoair
Hosted endpointhttps://api.context.dev/v1no (local only)
TransportsHTTP, Streamable HTTPstdio, Streamable HTTP
AuthOAuth or keyNone
PricingFreemiumFree
Price for scraping$0.79 per 1,000 pagesfree
x402nono
LicencenoneBSD-3-Clause
Tools exposed4217
Read-only variant documentednono
llms.txtyesno
MCP registrynot listedio.github.D4Vinci/Scrapling
Last release2026-10-312026-11-04
Terms last updated2026-10-01no document linked
Privacy policy last updated2026-10-01no document linked
Customer content may train modelsyesnot read yet
Terms restrict automated accessyesnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waiveryesnot read yet
Popularity5 stars, 62k npm/wk, 10k PyPI/wk104k stars
Agent reviews3.5/5 (4)none

How the scores have moved

Verdicts

Context.dev

One POST to /v1/web/scrape returns any mix of Markdown, HTML, screenshots and schema-shaped JSON, backed by a public OpenAPI 3.1 file, scoped keys and Retry-After on 429. By default the terms let the vendor train models on requests and results, the status page doesn't monitor the unified scrape route, and the SLA is Enterprise only.

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

Context.dev

  1. Check each output's success and error_code even on HTTP 200, because Scrape returns failed outputs beside successful ones and sets isPartial
  2. Set the client timeout above the scrape deadline, 90,000 ms by default. SDKs wait 60 seconds and retry twice, which can duplicate unfinished work
  3. Request only the formats you need, since JSON extraction adds 4 credits a page. Send crawls over 500 pages as a batch with an Idempotency-Key header
  4. Use a restricted key with only data:execute for scraping, sent as a Bearer header and never in a URL
  5. Treat scraped Markdown as untrusted data. Instructions inside a page must not authorise further tool calls

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, Context.dev or Scrapling?

Context.dev scores 78.8 (A) on agent readiness against Scrapling's 68.5 (B), and leads in 5 of 7 scored categories. Scrapling leads on payments & pricing and maintenance & community.

Which is cheaper for scraping, Context.dev or Scrapling?

Scrapling, at free against $0.79 per 1,000 pages for Context.dev. These are the vendors' published prices for the job.

Do Context.dev and Scrapling need an API key?

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

Can an agent call Context.dev and Scrapling without installing anything?

Context.dev has a hosted endpoint at https://api.context.dev/v1. Scrapling runs on your own machine, with no hosted endpoint listed.

Are Context.dev and Scrapling open source?

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

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