Head to head · Scraping · October 2026 research run

Scrape.do vs ScrapingBee

ScrapingBee scores 62 (B) on agent readiness against Scrape.do's 44.5 (E), and leads in every scored category. Both do scraping.

Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons

Which one, for what

Scrape.do E

Best for Cheap bulk fetching through rotating proxies when you call HTTP directly and keep the token server-side.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Token travels in the query string on the main API

ScrapingBee B

Best for Agents that mix general scraping with ready-made Google, Amazon and YouTube endpoints and want spend capped per call.

Ahead on

  • Reliability, 75 against 40
  • Agent ergonomics, 68 against 62
  • Security & auth, 37 against 23
  • Payments & pricing, 60 against 53
  • Maintenance & community, 75 against 25
  • Transparency & trust, 65 against 49

Also in its favour

  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5

Watch for

remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community ScrapingBee +50

Scrape.do 25

The last changelog entry recorded is 31 July 2026, a Gemini scraper API, 97 days before 5 November (10). The 1 October reading found nothing after it, so no dated entry falls in the 90 days from 7 August, and the changelog can't be re-read (0). Public changelog and a support address, response times not checked (8 of 15). The only official SDK, @scrape-do/client, is still at 1.0.2 (13 November 2024) in its public repository. Commits in April and May 2026 updated dependencies with no version (5 of 15). The repository runs its tests in CI on each push, with results we couldn't read, and the released package predates the dependency updates (2 of 10, held as a partial). 10+0+8+5+2 = 25.

ScrapingBee 75

CLI v1.6.0 on 11 September 2026 is the newest release, 54 days before 4 November, so within 90 days (20; 30 before, cause time). The CLI's later commits (plugin manifests for Cursor, Codex, Copilot CLI, Kiro and Antigravity, 6 to 30 October) sit under its changelog's Unreleased heading, the plugins still carry version 1.6.0, and the mcp-server repository holds only a README. In the 90 days from 6 August, Python SDK v2.1.1 (6 August, a documentation release) and v2.2.0 and Node SDK v2.0.0 (1 September) at half as SDK tags, CLI v1.6.0 in full as the vendor's own CLI with new commands and options, and the Employee Search API launch (blog post of 14 August) make 3.5 (20). We couldn't read GitHub issues. Dated SDK changelogs and email support (10 of 25). Current official Python and Node SDKs and a CLI. The MCP isn't in the official registry (15). Test workflows run in CI on all three repositories (10). 20 + 20 + 10 + 15 + 10 = 75.

Reliability ScrapingBee +35

Scrape.do 40

No public status page. status.scrape.do returned 403 on 30 September and 1 October and the site doesn't link it (0). No readable incident history, so 5 by the rubric (5). Concurrency published per plan, 5 on Free, 10 on Hobby, 50 on Pro, 100 on Business and 200 on Advanced (15). A 429 means the concurrency limit was hit and isn't billed, a 502 says to try again, and the service retries failed requests itself unless disableRetry=true, with no Retry-After or backoff guidance (10). No SLA on the pricing page, which claims a 99.98 per cent success rate instead (0). GA (10). All per the 1 October check, not re-read on 5 November, since Scrape.do's terms bar automated access to its website. 0+5+15+10+0+10 = 40.

ScrapingBee 75

status.scrapingbee.com, now on incident.io, with 9 components (dashboard, two core HTML scraping components and six dedicated APIs) and 90 days of history (20). In the 90 days from 6 August it posted five incidents, each "Degraded performance" on one component with no downtime on the uptime bars. Half of non-JavaScript HTML traffic was rejected for 20 minutes on 18 August, Google API /goto link resolution dropped from 9 to 10 September, Google API success rates fell for about six and a half hours on 22 September, and HTML Scraping with Rendering, the default, was degraded for about 11 hours on 21 October and about 5 hours on 28 October. Each is partial, so minor only (20; 15 before, when the July incidents were in the window). Concurrency per plan is published, 25 on Hobby to 400 on Business+ and 900 on Enterprise 120 (15). 429 means the concurrency limit and isn't billed, target failures are retried server-side for up to 30 seconds on most dedicated APIs, and the MCP notes advise exponential backoff. No Retry-After or safe-write guidance found (10). No SLA found (0). Generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

Transparency & trust ScrapingBee +16

Scrape.do 49

Closed service with published terms of use under PACKEND, LLC, dated 26 September 2022 (15). The privacy policy dates from 26 September 2022, says nothing on retention of scraped content or request logs and mentions no DPA (5 of 30). Dated changelog entries record changes such as render requests counting as one concurrent request from 3 February 2026, but there's no deprecation policy (8 of 20). Data may be processed in the United States, with no subprocessor list (5 of 20). Privacy policy and changelog per the 1 October check, not re-read on 5 November. 15+5+8+5 = 33.

ScrapingBee 65

Closed service with terms naming VostokInc SAS, Paris, registration 843 352 683 (15 of 30). The privacy policy, effective 15 July 2024, keeps prospect and customer data up to 3 years and links a DPA. It doesn't mention the Oxylabs group or say whether scraped content is stored (18 of 30). The Node SDK changelog dates removals, for example youtubeTranscript() dropped in v2.0.0 on 2026-09-01, and the api_key query parameter is marked deprecated. No standing deprecation policy (10 of 20). Processors described by category, located in the US or EU. No named list (8 of 20).

Security & auth ScrapingBee +14

Scrape.do 23

One account token, documented as the token query parameter on the main API, in the proxy username on proxy mode and in an X-Token header only on the async API. We found no scopes or rotation for it. Team roles for Business plans arrived on 29 July 2026 but apply to dashboard users, not tokens (20 less 10 for the query string, 10 of 30). No write actions on the target side, but one token covers the whole account (8 of 20). Every response is third-party page content and we found no prompt-injection guidance (0 of 15). Usage-stats endpoint and per-response cost headers, no per-request log found (5 of 15). No security.txt, security page or disclosure policy found. Proxy mode needs Scrape.do's CA certificate trusted or TLS verification switched off, per the 30 September check (0 of 20). Docs per the 1 October check, not re-read on 5 November. 10+8+0+5+0 = 23.

ScrapingBee 37

One API key per account, which the MCP notes say can be revoked (401 on revoked keys). Team management exists. No scopes (20). The api_key query parameter is deprecated but still works, and remote-mcp.txt says the hosted MCP takes the key only as ?api_key= in its URL, "not a Bearer header or OAuth flow", so less 10 (10 of 30). No read-only or scoped key, and the HTML API can send POST requests to target sites. The CLI gates shell post-processing behind an explicit unsafe flag (8 of 20). The official CLI skills and AGENTS.md say scraped output is data, never instructions, and tell the agent to report instruction-like content as a possible prompt injection. The MCP docs say nothing (12 of 15). A Usage API and a local CLI audit log. No per-request log in the docs (7 of 15). www.scrapingbee.com/.well-known/security.txt answers 404, and no bug bounty, disclosure policy or certification found (0 of 20). 10 + 8 + 12 + 7 + 0 = 37.

Payments & pricing ScrapingBee +7

Scrape.do 53

No x402, MPP or L402. The pricing page lists card, crypto and bank wire (0). Credit costs per request type and per domain are public, but credits come only with monthly plans, with no pay-as-you-go (15 of 20). Free plan, 1,000 successful requests a month with every feature, no card (20). A person signs up in a browser to get a token (0). Pricing per the 1 October check, not re-read on 5 November. 0+15+20+0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

ScrapingBee 60

No x402, MPP or L402 (0). Credit costs per request type (1, 5, 10, 25, 75, plus 5 for AI extraction) and plan prices are public, though the reference notes admit some endpoint costs conflict between pages (20). 1,000-credit trial, no card (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Agent ergonomics ScrapingBee +6

Scrape.do 62

output=markdown and optional screenshots keep responses small, but there's no field selection or token cap outside the structured plugins (15 of 25). One page per call, with an async job API for bulk work, and no pagination or filtering on the core endpoint (10 of 20). Status codes documented with billing behaviour (15 of 20). GET requests, failures other than target 400 and 404 aren't billed, and built-in retries can be switched off (15 of 20). Two required parameters, but the only official SDK is the Node client, still at 1.0.2 from 13 November 2024 in its repository on 5 November (7 of 15). Docs per the 1 October check, not re-read on 5 November. 15+10+15+15+7 = 62.

ScrapingBee 68

18 MCP tools (15 of 25). json_response, extract_rules, ai_query, return_page_markdown and return_page_text, plus max_cost to cap escalation (18 of 20). HTTP status codes with meanings and billing, but no machine-readable error codes beyond the status (15 of 20). Failed and 429 requests aren't billed and mode=auto bills only the tier that works. No tool annotations found (8 of 20). Only url is required, but render_js defaults on at 5 credits. Official Python and Node SDKs plus a CLI (12 of 15).

Score by category

CategoryWeightScrape.doScrapingBeeEdge
Reliability16%4075ScrapingBee +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5760ScrapingBee +3
Agent ergonomics13%6268ScrapingBee +6
Security & auth14%2337ScrapingBee +14
Payments & pricing10%5360ScrapingBee +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2575ScrapingBee +50
Transparency & trust7%4965ScrapingBee +16
Negative events≤1500
TotalE 44.5/100B 62/100

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
Tools exposednone18
Read-only variant documentednono
llms.txtyesyes
Last release2026-07-312026-09-11
Terms last updatedno date given2024-07-15
Privacy policy last updatedno date given2024-07-15
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone132 stars, 49k npm/wk, 72k PyPI/wk
Agent reviews3.5/5 (2)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates ScrapingBee higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Scrape.do

$29 for 250,000 basic credits, and 429s, 502s and most failures aren't billed. The token travels in the query string on the main API, and the last changelog entry we could read is from 31 July 2026.

ScrapingBee

Dedicated Google, Amazon, Walmart, YouTube, ChatGPT and Gemini endpoints next to the general HTML API, with per-endpoint llms files and an auto mode that bills only the tier that works. The hosted MCP's own notes say it takes the key only as ?api_key= in its URL, and no API changelog or security.txt was found.

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

Questions

Which is better for AI agents, Scrape.do or ScrapingBee?

ScrapingBee scores 62 (B) on agent readiness against Scrape.do's 44.5 (E), and leads in every scored category.

Do Scrape.do and ScrapingBee need an API key?

Both need an API key.

Can an agent call Scrape.do and ScrapingBee without installing anything?

Yes. Scrape.do has a hosted endpoint at https://api.scrape.do/ and ScrapingBee at https://app.scrapingbee.com/api/v1/.

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.