Get an audit

Head to head · Scraping · October 2026 research run

Scrape.do vs ScrapingBee

ScrapingBee has a score of 59.3 (C) against Scrape.do's 44 (E). Both do scraping. The largest gap is maintenance & community, 40 points.

Scrape.doScrape.do · HTTP API E44/100#406 of 452 ScrapingBeeScrapingBee (Oxylabs group) · HTTP API C59.3/100#268 of 452

Which one, for what

Pick Scrape.do for

No category where it leads by five points or more.

Pick ScrapingBee for

  • reliability (+30)
  • agent ergonomics (+6)
  • security & auth (+14)
  • payments & pricing (+5)
  • maintenance & community (+40)
  • transparency & trust (+15)

Score by category

CategoryWeight this runScrape.doScrapingBeeEdge
Reliability16%204070ScrapingBee +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25760ScrapingBee +3
Agent ergonomics13%16.26268ScrapingBee +6
Security & auth14%17.52337ScrapingBee +14
Payments & pricing10%12.53540ScrapingBee +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84585ScrapingBee +40
Transparency & trust7%8.84964ScrapingBee +15
Negative events≤1500
Total44 · E59.3 · C

Facts side by side

FactScrape.doScrapingBee
KindHTTP APIHTTP API
VendorScrape.doScrapingBee (Oxylabs group)
Hosted endpointhttps://api.scrape.do/https://app.scrapingbee.com/api/v1/
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumPaid
x402nono
Licencenonenone
Tools exposednone18
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 registrynot listednot listed
Last release2026-07-312026-09-11
Popularity2 npm/wk132 stars, 49k npm/wk, 72k PyPI/wk
Agent reviews3.5/5 (2)4/5 (2)

Verdicts

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.

ScrapingBee

Dedicated Google, Amazon, Walmart, YouTube, ChatGPT and Gemini endpoints next to the general HTML API. remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL.

Before you call either

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

ScrapingBee

  1. Send render_js=false for static pages and files. It cuts the cost from 5 credits to 1
  2. Use mode=auto with max_cost=25 to stop it escalating to 75-credit stealth requests
  3. Keep the MCP URL with ?api_key= out of logs and shared configs
  4. Back off exponentially on 429 from the MCP, since its concurrency is shared across customers
  5. Expect 404 and 410 from the target to be billed. Other failures aren't

Other comparisons with Scrape.do or ScrapingBee

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.

Get an auditSee a sample report