ScraperAPI vs ZenRows

ScraperAPI

One GET request with a key and a URL returns a page, and the MCP server's 28 tools carry read-only and destructive hints. No status page, OpenAPI file, security.txt or certification was found, and the documented default puts the API key in the URL query string.

ZenRows

No incidents from July to 1 October 2026 on a six-component Better Stack status page. The Fetch API only takes the key in the query string.

ScraperAPI

1. Set the client timeout to 70 seconds. The API retries for that long before it returns 500, and a request cancelled earlier is still charged
2. Send the key as the x-sapi-api_key header to keep it out of URLs and logs
3. Pass max_cost on each request, or call /account/urlcost first, because domain and anti-bot surcharges vary from 1 to 75 credits
4. Use output_format=markdown or text to cut response size, and autoparse=true only on supported domains
5. On 429 reduce concurrency to the plan limit (5 on Free, 20 on Hobby). The request is rejected, not queued

ZenRows

1. Start with mode=auto and let it escalate. Force js_render or premium_proxy only when you know the site needs it
2. Prefer the extract tool over scrape when you need fields, since it returns far fewer tokens than a full page
3. Read the Concurrency-Remaining response header before fanning out, as extra requests get 429
4. Set ZENROWS_AUTO_SIGNUP=false in stdio configs so a missing key fails loudly instead of creating an account