ScraperAPI vs Scrapingdog

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.

Scrapingdog

A plain request is 1 credit, about $0.20 per 1,000 on Lite. API key only travels in the URL 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

Scrapingdog

1. Add dynamic=false unless the page needs JavaScript. It cuts the cost from 5 credits to 1, whatever the MCP description says
2. Keep request URLs out of logs, since they carry api_key
3. Set client timeouts above 60 seconds and retry on 429 or timeout. Failures aren't billed
4. Prefer the parsed endpoints (Google, Amazon) over scraping the raw page when one exists