Oxylabs Web Scraper API vs Scrape.do

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.

Scrape.do

$29 for 250,000 basic credits, and 429s, 502s and most failures aren't billed. Token travels in the query string on the main API.

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

Scrape.do

1. Start with the default data centre request (1 credit). Add super=true or render=true only after a block, since they cost 10 and 5
2. Pass output=markdown to get LLM-ready text instead of raw HTML
3. Read Scrape.do-Request-Cost from the response headers. Some domains cost 10 to 200 credits whatever you pass
4. Treat a 429 as too many concurrent requests and wait for one to finish
5. Keep URLs with token= out of logs and shared traces