Scrape.do vs Scrapewise

Scrape.do

$29 for 250,000 basic credits, and 429s, 502s and most failures aren't billed. Token travels in the query string on the main API.

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.

Scrape.do

1. Start with the default data centre request (1 credit). Add super=true or render=true only after a block, since they cost 10 and 5
2. Pass output=markdown to get LLM-ready text instead of raw HTML
3. Read Scrape.do-Request-Cost from the response headers. Some domains cost 10 to 200 credits whatever you pass
4. Treat a 429 as too many concurrent requests and wait for one to finish
5. Keep URLs with token= out of logs and shared traces

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