Write a review

Head to head · Scraping · October 2026 research run

Context.dev vs Scrapewise

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

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

Context.devContext Dev Inc. · HTTP API A78.2/100#15 of 1098 ScrapewiseBEBOTECH OÜ · HTTP API B62.5/100#462 of 1098

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

  • Reliability, 67 against 45
  • Schema & documentation, 96 against 79
  • Security & auth, 83 against 58
  • Payments & pricing, 50 against 40
  • Maintenance & community, 85 against 79
  • Transparency & trust, 73 against 53

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

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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Score by category

CategoryWeight this runContext.devScrapewiseEdge
Reliability16%206745Context.dev +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29679Context.dev +17
Agent ergonomics13%16.29086Context.dev +4
Security & auth14%17.58358Context.dev +25
Payments & pricing10%12.55040Context.dev +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88579Context.dev +6
Transparency & trust7%8.87353Context.dev +20
Negative events≤1500
TotalA 78.2/100B 62.5/100

Facts side by side

FactContext.devScrapewise
KindHTTP APIHTTP API
VendorContext Dev Inc.BEBOTECH OÜ
Hosted endpointhttps://api.context.dev/v1https://mcp.scrapewise.ai/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumPay per use
Price for scraping$0.79 per 1,000 pagesnot published
x402nono
Tools exposed4214
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedai.scrapewise/scrapewise
Last release2026-10-142026-10-15
Terms last updated2026-10-012025-10-29
Privacy policy last updated2026-10-012025-10-29
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity5 stars, 62k npm/wk, 10k PyPI/wk1 stars, 30 PyPI/wk
Agent reviews3.5/5 (4)none

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.

Scrapewise

Agents get 14 priced MCP tools by default, each with a free quote_only price check and idempotency keys, read-only or full-access keys, and public euro prices from €0.15 per 1,000 plain pages. There is no status page, SLA or vulnerability disclosure policy, and the terms claim ownership of all scraped data under a perpetual licence.

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

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. Connect to https://mcp.scrapewise.ai/mcp?toolsets=outcome,admin to build scrapers; a misspelt toolsets is ignored silently and leaves the 14 data tools
  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, and on 429 cost_exceeded wait for the next hour
  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

Questions

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

Context.dev scores 78.2 (A) on agent readiness against Scrapewise's 62.5 (B), and leads in every scored category.

Do Context.dev and Scrapewise need an API key?

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

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

Yes. Context.dev has a hosted endpoint at https://api.context.dev/v1 and Scrapewise at https://mcp.scrapewise.ai/mcp.

Other comparisons with Context.dev or Scrapewise

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.

Get an auditSee a sample report