ScraperAPI vs Scrapfly

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.

Scrapfly

The error catalogue documents HTTP status, retry behaviour and billing for over 100 codes. The MCP server loads 61 tools at once.

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

Scrapfly

1. Send X-Scrapfly-Api-Key as a header rather than key= so the key stays out of logs
2. Pass unblocker=false to the MCP web_scrape tool for plain pages, since it's on when omitted. asp is the deprecated alias
3. Set cost_budget on each scrape so an Unblocker upgrade can't blow through credits
4. Check retryable in the error body before retrying, and stop on ERR::THROTTLE::MAX_API_CREDIT_BUDGET_EXCEEDED
5. Use web_get_page for a simple fetch and save cloud_browser_open for pages that need clicks