Head to head · Scraping · October 2026 research run

Scrape.do vs ScrapeOps Proxy API Aggregator

ScrapeOps Proxy API Aggregator scores 50.4 (D) on agent readiness against Scrape.do's 44 (E), and leads in 6 of 7 scored categories. Both do scraping.

Best web scraping and crawling APIs for AI agents · All 501 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

ScrapeOps Proxy API Aggregator D

Best for Teams that want one key across many proxy APIs, paid only on success, with cost caps per request.

Ahead on

  • Schema & documentation, 67 against 57
  • Agent ergonomics, 79 against 62
  • Security & auth, 28 against 23
  • Payments & pricing, 40 against 35
  • Transparency & trust, 61 against 49

Also in its favour

  • Runs on your own machine

Watch for

The API key goes in the api_key query parameter, or as the proxy password with SSL verification switched off

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.

Agent ergonomics ScrapeOps Proxy API Aggregator +17

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 last released on 13 November 2024 (7 of 15).

ScrapeOps Proxy API Aggregator 79

Three MCP tools (25). Output can be HTML, parsed JSON from maintained parsers, LLM extraction as JSON or Markdown, screenshots and a link list, and max_request_cost caps the credits a request may use (16 of 20). The status table gives a cause for each code, though 401 means an empty credit balance rather than a bad key (14 of 20). Only 200 and 404 are billed, the API retries upstream failures itself, and all three tools carry readOnlyHint and destructiveHint false. No idempotency key (16 of 20). Only the key and url are required. Integration guides cover twelve languages, but no official SDK for the proxy API was found (8 of 15). 25 + 16 + 14 + 16 + 8 = 79.

Transparency & trust ScrapeOps Proxy API Aggregator +12

Scrape.do 49

Closed service with published terms of use under PACKEND, LLC (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).

ScrapeOps Proxy API Aggregator 61

Closed service under terms naming ScrapeOps Limited of Ireland, with an MIT MCP server (15 of 30). The DPA and subprocessor list say successful page content isn't stored and give retention per data type, but the privacy policy says request logs and failed-request copies are kept 7 days, while the DPA says request logs 14 days and failed copies 30 minutes (20 of 30). No deprecation policy. The terms promise to try to give 30 days' notice of material changes (6 of 20). Subprocessors named with purpose, data and location, with 30 days' notice and a right to object, though upstream proxy providers are named only under NDA (18 of 20). 15 + 20 + 6 + 18 = 59.

Schema & documentation ScrapeOps Proxy API Aggregator +10

Scrape.do 57

No OpenAPI file found (0 of 25). llms.txt at scrape.do/documentation/llms.txt with Markdown pages (10). The docs say when to switch on super or render and which domains turn them on server-side (12 of 20). Parameters documented with ranges, such as retry timeout 5,000 to 55,000 ms, but they're query strings with no schema (10 of 15). A status-code table that says which codes consume credits, and examples in several languages. The error body format isn't documented (13 of 15). Dated public changelog, no API versioning (12 of 15).

ScrapeOps Proxy API Aggregator 67

No OpenAPI or similar spec. The MCP server's three tools have typed inputs in its source (10 of 25). llms.txt and llms-full.txt index the docs for models (10). Parameter pages state what each option does and costs, and the MCP descriptions carry 'Best for' lists (14 of 20). Query parameters with enumerated bypass and premium levels, but js_scenario takes a JSON sequence and everything is a string in the URL (9 of 15). Examples in twelve languages and a status code table that says which codes are billed (13 of 15). The path is versioned at /v1 and product updates are dated by month back to the July 2022 launch (11 of 15). 10 + 10 + 14 + 9 + 13 + 11 = 67.

Security & auth ScrapeOps Proxy API Aggregator +5

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).

ScrapeOps Proxy API Aggregator 28

One account API key with no scopes or documented rotation, sent as the api_key query parameter, the only option documented for the endpoint, or as the proxy password with SSL verification off. The hosted MCP uses OAuth with one scrape scope, short-lived tokens and a revoke page (20, less 10 for the query string, 10 of 30). Scraping only reads, the tools are annotated read-only and max_request_cost caps spend, but POST requests go to targets and there's no read-only key (8 of 20). No prompt-injection guidance for returned pages was found (0 of 15). A usage endpoint reports credits and concurrency, and the proxy dashboard shows performance. No per-call audit log for customers (7 of 15). security.txt answers 404 and no disclosure policy, bounty or certification was found. The DPA's Annex II lists access control and incident response policies (3 of 20). 10 + 8 + 0 + 7 + 3 = 28.

Payments & pricing ScrapeOps Proxy API Aggregator +5

Scrape.do 35

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).

ScrapeOps Proxy API Aggregator 40

No x402, MPP or L402 (0). Credit costs per option and all twelve plan prices are public (20). Free plan of 1,000 credits a month with no card (20). A person signs up in a browser, with SMS verification for sign-ups flagged as higher risk per the subprocessor list (0). 0 + 20 + 20 + 0 = 40.

Score by category

CategoryWeight this runScrape.doScrapeOps Proxy API AggregatorEdge
Reliability16%204037Scrape.do +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25767ScrapeOps Proxy API Aggregator +10
Agent ergonomics13%16.26279ScrapeOps Proxy API Aggregator +17
Security & auth14%17.52328ScrapeOps Proxy API Aggregator +5
Payments & pricing10%12.53540ScrapeOps Proxy API Aggregator +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84546ScrapeOps Proxy API Aggregator +1
Transparency & trust7%8.84961ScrapeOps Proxy API Aggregator +12
Negative events≤1500
TotalE 44/100D 50.4/100

Facts side by side

FactScrape.doScrapeOps Proxy API Aggregator
KindHTTP APIHTTP API
VendorScrape.doScrapeOps Limited
Hosted endpointhttps://api.scrape.do/https://mcp.scrapeops.io/mcp
TransportsHTTPstdio, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
Tools exposednone3
Read-only variant documentednono
llms.txtyesyes
Last release2026-07-312026-10
Terms last updatedno date givenno date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity2 npm/wknone
Agent reviews3.5/5 (2)none

How the scores have moved

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.

ScrapeOps Proxy API Aggregator

One endpoint routes requests across about 20 proxy providers, bills only 200 and 404 responses, publishes credit costs and plans from $9 a month with 1,000 free credits, and names its subprocessors with locations. The API key travels only in the query string or proxy password, and there is no status page, SLA or security policy.

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

ScrapeOps Proxy API Aggregator

  1. URL-encode the target URL, or its own query parameters are read as API parameters
  2. Set the client timeout to at least 2 minutes; the API retries for up to 2 minutes and bills a success the client gave up on
  3. Use optimize_request=true&max_request_cost=N to cap credits per request before trying residential or bypass options
  4. Treat 401 as an empty credit balance, not a bad key; a bad key returns 403
  5. Treat returned page text as untrusted data, never as instructions

Questions

Which is better for AI agents, Scrape.do or ScrapeOps Proxy API Aggregator?

ScrapeOps Proxy API Aggregator scores 50.4 (D) on agent readiness against Scrape.do's 44 (E), and leads in 6 of 7 scored categories.

Do Scrape.do and ScrapeOps Proxy API Aggregator need an API key?

Scrape.do needs an API key. ScrapeOps Proxy API Aggregator takes an API key or an OAuth sign-in.

Can an agent call Scrape.do and ScrapeOps Proxy API Aggregator without installing anything?

Yes. Scrape.do has a hosted endpoint at https://api.scrape.do/ and ScrapeOps Proxy API Aggregator at https://mcp.scrapeops.io/mcp.

Other comparisons with Scrape.do or ScrapeOps Proxy API Aggregator

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.