Apify MCP Server vs Oxylabs Web Scraper API

Apify MCP Server

x402 on Apify's own domains, a prepaid token from agi.apify.com for any Actor and per-run payment on mcp.apify.com for Pay Per Event Actors. API and Actor runs timed out for about 12 hours on 21 and 22 July 2026.

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.

Apify MCP Server

1. Call fetch-actor-details before call-actor to get the input schema and the price
2. Use apify--web-fetch for one known URL and apify--rag-web-browser for search and read
3. Read results with get-dataset-items and set fields and limit. The default is 20 rows
4. Buy an AGI token for anything that isn't a Pay Per Event Actor, since direct ?payment=x402 refuses the rest. Tokens last 14 days and unused balance isn't refunded
5. Ask for get-actor-run-log, not get-actor-log. The old name is ignored without an error

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