ScraperAPI vs ScrapingAnt

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.

ScrapingAnt

10,000 free credits a month with no card. API Basics puts the key in the query string, so it lands in logs.

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

ScrapingAnt

1. Send the key in the x-api-key header rather than the query string
2. Use /v2/markdown for LLM input, and set browser=false on static pages to pay 1 credit instead of 10
3. Switch to proxy_type=residential only after a 423 (anti-bot) response. It raises a browser request from 10 to 125 credits
4. On the free plan a second concurrent request gets 409. Wait for the first to finish
5. Google, Bing and Yandex result pages come back as raw HTML through /v2/general, so you parse them yourself