Scrapewise vs Scrapingdog

Scrapewise

Agents get 14 priced MCP tools by default, each with a free quote_only price check and idempotency keys, read-only or full-access keys, and public euro prices from €0.15 per 1,000 plain pages. There is no status page, SLA or vulnerability disclosure policy, and the terms claim ownership of all scraped data under a perpetual licence.

Scrapingdog

A plain request is 1 credit, about $0.20 per 1,000 on Lite. API key only travels in the URL query string.

Scrapewise

1. Call each paid tool with quote_only: true first, then repeat with the same idempotency_key so a retry is charged once
2. Connect to https://mcp.scrapewise.ai/mcp?toolsets=outcome,admin to build scrapers; a misspelt toolsets is ignored silently and leaves the 14 data tools
3. Use an LLM_READ key unless the task needs paid tools or writes, since LLM_FULL has no per-tool consent
4. Treat 402 WALLET_INSUFFICIENT_BALANCE as final and ask the user to top up; on 429 wait for Retry-After, and on 429 cost_exceeded wait for the next hour
5. Scrape many addresses with one scrapewise_run_scraper_url_list call (up to 5,000) and retry with the same name, never one scraper per address

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