Write a review

Head to head · Scraping · October 2026 research run

Context.dev vs Zyte API

Context.dev scores 78.2 (A) on agent readiness against Zyte API's 69.7 (B), and leads in 6 of 7 scored categories. Zyte API leads on reliability. Both do scraping.

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

Context.devContext Dev Inc. · HTTP API A78.2/100#15 of 1084 Zyte APIZyte Group Limited · HTTP API B69.7/100#182 of 1084

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 85
  • Agent ergonomics, 90 against 72
  • Security & auth, 83 against 55
  • Payments & pricing, 50 against 40
  • Maintenance & community, 85 against 77
  • Transparency & trust, 73 against 66

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

Zyte API B

Best for An agent or pipeline that fetches protected pages and wants the service to choose proxy and browser per site and to bill only success, and teams already on Scrapy.

Ahead on

  • Reliability, 85 against 67

Watch for

Request price depends on the target site's tier, from $0.13 to $1.27 per 1,000 HTTP requests and $1.01 to $16.08 with a browser on pay-as-you-go

Score by category

CategoryWeight this runContext.devZyte APIEdge
Reliability16%206785Zyte API +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29685Context.dev +11
Agent ergonomics13%16.29072Context.dev +18
Security & auth14%17.58355Context.dev +28
Payments & pricing10%12.55040Context.dev +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88577Context.dev +8
Transparency & trust7%8.87366Context.dev +7
Negative events≤1500
TotalA 78.2/100B 69.7/100

Facts side by side

FactContext.devZyte API
KindHTTP APIHTTP API
VendorContext Dev Inc.Zyte Group Limited
Hosted endpointhttps://api.context.dev/v1https://api.zyte.com/v1/extract
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPay per use
Price for scraping$0.79 per 1,000 pagesnot published
x402nono
LicencenoneProprietary service under Zyte's terms of service. The Python client is BSD 3-Clause, and the Agentic Web Data plugin is under Zyte's own end-user licence
Tools exposed4234
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-142026-10-05
Terms last updated2026-10-012026-09-22
Privacy policy last updated2026-10-012024-08-30
Customer content may train modelsyesyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity5 stars, 62k npm/wk, 10k PyPI/wk42k PyPI/wk

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.

Zyte API

One POST endpoint with an OpenAPI 3 contract picks proxies, browser rendering and extraction per site, bills only successful responses, and sends problem+json errors with Retry-After. Prices vary by target site across five tiers, so cost per request isn't known before the site is assigned one, and no dated API changelog was found.

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

Zyte API

  1. Send the API key as the Basic auth username with an empty password to https://api.zyte.com/v1/extract. Set only one of httpResponseBody or browserHtml, or one extraction field
  2. Ask for httpResponseBody before browserHtml. Browser requests cost about eight to thirteen times more per tier
  3. Retry 429, 503 and 520 after the Retry-After seconds, with backoff. They aren't billed. Don't retry 400, 401, 422 or 451
  4. Read statusCode in a 200 response. A target site's 404 comes back as a successful, billed Zyte API response
  5. Have the owner set a blocking spending limit on the key you use. A 403 /auth/account-suspended means the limit or the trial month ended

Questions

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

Context.dev scores 78.2 (A) on agent readiness against Zyte API's 69.7 (B), and leads in 6 of 7 scored categories. Zyte API leads on reliability.

Do Context.dev and Zyte API need an API key?

Both take an API key or an OAuth sign-in.

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

Yes. Context.dev has a hosted endpoint at https://api.context.dev/v1 and Zyte API at https://api.zyte.com/v1/extract.

Other comparisons with Context.dev or Zyte API

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