Jina Reader vs Oxylabs Web Scraper API

Jina Reader

One URL prefix, no key needed, Markdown back. No price per token in any currency on the public page.

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.

Jina Reader

1. Prefix the URL, https://r.jina.ai/https://example.com, and read the Markdown
2. Send x-max-tokens to cap a page, or x-token-budget to refuse one that's too big
3. Use x-target-selector when you need one part of a page
4. Keyless is 20 requests a minute and can't search. Add a key for loops or s.jina.ai
5. Send x-no-cache: true when a page may have changed or a blocked response got cached

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