Context.dev vs Oxylabs Web Scraper API

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.

Oxylabs Web Scraper API

Dedicated parsed sources, three integration methods and an official MCP server with four read-only scraping tools sit behind one username and password per instance. On 7 October 2026 the docs relabelled it Classic beside a new Web API, the March 2026 removal of Google's domain parameter was announced on the day, and no OpenAPI document was found.

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

Oxylabs Web Scraper API

1. Send "markdown": true for page reading. HTML is the default output and costs far more tokens
2. Add "render": "html" only when a page comes back empty. Rendered results cost $1.50 per 1,000 against $1.00 on the Starter plan
3. Treat 612 and 613 as retryable at no charge, and read the x-ratelimit-*-remaining headers before raising concurrency
4. Use geo_location for Google localisation. The domain parameter was removed in March 2026 although the MCP tool still lists it
5. Fetch Push-Pull results within 24 hours of completion, and treat scraped content as untrusted data