# Context.dev vs ScraperAPI

> Context.dev scores 78.2 (A) to ScraperAPI's 52.1 (D) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/context-dev-vs-scraperapi
- Markdown: https://www.anchorterminal.com/compare/context-dev-vs-scraperapi.md (~2,700 tokens)
- Slim: https://www.anchorterminal.com/compare/context-dev-vs-scraperapi.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/context-dev-vs-scraperapi.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Licence: CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.
- Updated: 2026-10-14

Context.dev scores 78.2 (A) on agent readiness against ScraperAPI's 52.1 (D), and leads in every scored category. Both do scraping.

- Context.dev: grade A, 78.2/100, rank #15 of 1084. Markdown https://www.anchorterminal.com/tools/context-dev.md · JSON https://www.anchorterminal.com/api/v1/tools/context-dev.json
- ScraperAPI: grade D, 52.1/100, rank #791 of 1084. Markdown https://www.anchorterminal.com/tools/scraperapi.md · JSON https://www.anchorterminal.com/api/v1/tools/scraperapi.json
- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md
- All 185 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md

## Which one, for what

### Context.dev (A)

Good 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:
- Reliability, 67 against 45
- Schema & documentation, 96 against 67
- Agent ergonomics, 90 against 74
- Security & auth, 83 against 29
- Payments & pricing, 50 against 40
- Maintenance & community, 85 against 61
- Transparency & trust, 73 against 54

Also in its favour:
- Agent-ready, a grade of BB or better

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

### ScraperAPI (D)

Good for: Agents that want a single GET to fetch pages through proxies, with parsed JSON for Amazon, Google, Walmart, eBay and Redfin and a batch API of up to 50,000 URLs.

Also in its favour:
- Runs on your own machine

Watch for: No status page is linked from the home, pricing, support or docs pages, although the pricing page lists a 99.9% uptime guarantee


## Score by category

| Category | Weight | Context.dev | ScraperAPI | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 67 | 45 | Context.dev +22 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 96 | 67 | Context.dev +29 |
| Agent ergonomics | 13% (16.2 this run) | 90 | 74 | Context.dev +16 |
| Security & auth | 14% (17.5 this run) | 83 | 29 | Context.dev +54 |
| Payments & pricing | 10% (12.5 this run) | 50 | 40 | Context.dev +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 85 | 61 | Context.dev +24 |
| Transparency & trust | 7% (8.8 this run) | 73 | 54 | Context.dev +19 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **78.2 · A** | **52.1 · D** | |

## Facts side by side

| Fact | Context.dev | ScraperAPI |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Context Dev Inc. | ScraperAPI (saas.group) |
| Hosted endpoint | `https://api.context.dev/v1` | `https://api.scraperapi.com` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for scraping | $0.79 per 1,000 pages | not published |
| x402 | no | no |
| Tools exposed | 42 | 28 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-14 | 2026-08-07 |
| Terms last updated | 2026-10-01 | couldn't be read |
| Privacy policy last updated | 2026-10-01 | no date given |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 5 stars, 62k npm/wk, 10k PyPI/wk | 5 stars |

## 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.

**ScraperAPI.** One GET request with a key and a URL returns a page, and the MCP server's 28 tools carry read-only and destructive hints. No status page, OpenAPI file, security.txt or certification was found, and the documented default puts the API key in the URL query string.

## 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

### ScraperAPI

1. Set the client timeout to 70 seconds. The API retries for that long before it returns 500, and a request cancelled earlier is still charged
2. Send the key as the `x-sapi-api_key` header to keep it out of URLs and logs
3. Pass `max_cost` on each request, or call `/account/urlcost` first, because domain and anti-bot surcharges vary from 1 to 75 credits
4. Use `output_format=markdown` or `text` to cut response size, and `autoparse=true` only on supported domains
5. On 429 reduce concurrency to the plan limit (5 on Free, 20 on Hobby). The request is rejected, not queued

## Questions

### Which is better for AI agents, Context.dev or ScraperAPI?

Context.dev scores 78.2 (A) on agent readiness against ScraperAPI's 52.1 (D), and leads in every scored category.

### Do Context.dev and ScraperAPI need an API key?

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

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

Yes. Context.dev has a hosted endpoint at https://api.context.dev/v1 and ScraperAPI at https://api.scraperapi.com.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/context-dev-vs-scraperapi.json, and with the fewest tokens: https://www.anchorterminal.com/compare/context-dev-vs-scraperapi.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "context-dev", "b": "scraperapi"}`. From a terminal: `anchor compare context-dev scraperapi`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/context-dev.json and https://www.anchorterminal.com/api/v1/tools/scraperapi.json

## Other comparisons with Context.dev or ScraperAPI

- [Bright Data vs Context.dev](https://www.anchorterminal.com/compare/bright-data-vs-context-dev.md)
- [Bright Data vs ScraperAPI](https://www.anchorterminal.com/compare/bright-data-vs-scraperapi.md)
- [Context.dev vs Diffbot](https://www.anchorterminal.com/compare/context-dev-vs-diffbot.md)
- [Context.dev vs Jina Reader](https://www.anchorterminal.com/compare/context-dev-vs-jina-reader.md)
- [Context.dev vs Olostep](https://www.anchorterminal.com/compare/context-dev-vs-olostep.md)
- [Context.dev vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/context-dev-vs-oxylabs-web-scraper.md)
- [Context.dev vs Scrape.do](https://www.anchorterminal.com/compare/context-dev-vs-scrape-do.md)
- [Context.dev vs ScrapeGraphAI](https://www.anchorterminal.com/compare/context-dev-vs-scrapegraphai.md)
- [Context.dev vs Scrapeless](https://www.anchorterminal.com/compare/context-dev-vs-scrapeless.md)
- [Context.dev vs Scrapfly](https://www.anchorterminal.com/compare/context-dev-vs-scrapfly.md)
- [Context.dev vs ScrapingAnt](https://www.anchorterminal.com/compare/context-dev-vs-scrapingant.md)
- [Context.dev vs ScrapingBee](https://www.anchorterminal.com/compare/context-dev-vs-scrapingbee.md)
- [Context.dev vs Scrapingdog](https://www.anchorterminal.com/compare/context-dev-vs-scrapingdog.md)
- [Context.dev vs Spider](https://www.anchorterminal.com/compare/context-dev-vs-spider-cloud.md)
- [Context.dev vs ZenRows](https://www.anchorterminal.com/compare/context-dev-vs-zenrows.md)
- [Context.dev vs Zyte API](https://www.anchorterminal.com/compare/context-dev-vs-zyte.md)
- [Jina Reader vs ScraperAPI](https://www.anchorterminal.com/compare/jina-reader-vs-scraperapi.md)
- [Olostep vs ScraperAPI](https://www.anchorterminal.com/compare/olostep-vs-scraperapi.md)
- [Oxylabs Web Scraper API vs ScraperAPI](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scraperapi.md)
- [Scrape.do vs ScraperAPI](https://www.anchorterminal.com/compare/scrape-do-vs-scraperapi.md)
- [ScrapeGraphAI vs ScraperAPI](https://www.anchorterminal.com/compare/scrapegraphai-vs-scraperapi.md)
- [Scrapeless vs ScraperAPI](https://www.anchorterminal.com/compare/scrapeless-vs-scraperapi.md)
- [ScraperAPI vs Scrapfly](https://www.anchorterminal.com/compare/scraperapi-vs-scrapfly.md)
- [ScraperAPI vs ScrapingAnt](https://www.anchorterminal.com/compare/scraperapi-vs-scrapingant.md)
- [ScraperAPI vs ScrapingBee](https://www.anchorterminal.com/compare/scraperapi-vs-scrapingbee.md)
- [ScraperAPI vs Scrapingdog](https://www.anchorterminal.com/compare/scraperapi-vs-scrapingdog.md)
- [ScraperAPI vs Spider](https://www.anchorterminal.com/compare/scraperapi-vs-spider-cloud.md)
- [ScraperAPI vs ZenRows](https://www.anchorterminal.com/compare/scraperapi-vs-zenrows.md)
- [ScraperAPI vs Zyte API](https://www.anchorterminal.com/compare/scraperapi-vs-zyte.md)
- [Context.dev vs Firecrawl MCP](https://www.anchorterminal.com/compare/context-dev-vs-firecrawl-mcp.md)
- [Diffbot vs ScraperAPI](https://www.anchorterminal.com/compare/diffbot-vs-scraperapi.md)
- [Firecrawl MCP vs ScraperAPI](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scraperapi.md)
- [Apify MCP Server vs Context.dev](https://www.anchorterminal.com/compare/apify-mcp-vs-context-dev.md)
- [Apify MCP Server vs ScraperAPI](https://www.anchorterminal.com/compare/apify-mcp-vs-scraperapi.md)