Scrapewise vs ZenRows

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.

ZenRows

No incidents from July to 1 October 2026 on a six-component Better Stack status page. The Fetch API only takes the key in the 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

ZenRows

1. Start with mode=auto and let it escalate. Force js_render or premium_proxy only when you know the site needs it
2. Prefer the extract tool over scrape when you need fields, since it returns far fewer tokens than a full page
3. Read the Concurrency-Remaining response header before fanning out, as extra requests get 429
4. Set ZENROWS_AUTO_SIGNUP=false in stdio configs so a missing key fails loudly instead of creating an account