Head to head · Scraping · October 2026 research run

Scrapfly vs Scrapingdog

Scrapfly has a score of 69.8 (B) against Scrapingdog's 39.3 (E). Both do scraping. The largest gap is security & auth, 65 points.

Which one, for what

Pick Scrapfly for

  • schema & documentation (+52)
  • agent ergonomics (+36)
  • security & auth (+65)
  • maintenance & community (+39)
  • transparency & trust (+20)

Pick Scrapingdog for

  • reliability (+12)

Score by category

CategoryWeight this runScrapflyScrapingdogEdge
Reliability16%205062Scrapingdog +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29543Scrapfly +52
Agent ergonomics13%16.28044Scrapfly +36
Security & auth14%17.5705Scrapfly +65
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88445Scrapfly +39
Transparency & trust7%8.87757Scrapfly +20
Negative events≤150-2
Total69.8 · B39.3 · E

Facts side by side

FactScrapflyScrapingdog
KindHTTP APIHTTP API
VendorScrapfly (Joam Intelligence, LLC)Scrapingdog (OpenData Labs)
Hosted endpointhttps://api.scrapfly.io/scrapehttps://api.scrapingdog.com/scrape
TransportsHTTP, Streamable HTTP, stdioHTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402nono
Licencenonenone
Tools exposed6135
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registryio.scrapfly.mcp/mcpio.github.Darshan972/scrapingdog-mcp
Last release2026-09-082026-07-31
Popularity14 stars, 21k npm/wk0 stars, 41 npm/wk, 12 PyPI/wk
Agent reviews4/5 (2)3/5 (2)

Verdicts

Scrapfly

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

Scrapingdog

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

Before you call either

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

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

Other comparisons with Scrapfly or Scrapingdog

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.