# Scrape.do vs ScrapeOps Proxy API Aggregator (slim)

> ScrapeOps Proxy API Aggregator scores 50.4 (D) to Scrape.do's 44 (E) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/scrape-do-vs-scrapeops.md (~4,850 tokens) · this version ~2,130 tokens · JSON https://www.anchorterminal.com/compare/scrape-do-vs-scrapeops.json · canonical https://www.anchorterminal.com/compare/scrape-do-vs-scrapeops
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- Scrape.do: E 44, rank #1236 of 1510 · https://www.anchorterminal.com/tools/scrape-do.min.md
- ScrapeOps Proxy API Aggregator: D 50.4, rank #1067 of 1510 · https://www.anchorterminal.com/tools/scrapeops.min.md
- Scrape.do, good for Cheap bulk fetching through rotating proxies when you call HTTP directly and keep the token server-side.
- ScrapeOps Proxy API Aggregator, good 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 Runs on your own machine.

| Category | Scrape.do | ScrapeOps Proxy API Aggregator |
| --- | --- | --- |
| Reliability (16%) | 40 | 37 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 57 | 67 |
| Agent ergonomics (13%) | 62 | 79 |
| Security & auth (14%) | 23 | 28 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 45 | 46 |
| Transparency & trust (7%) | 49 | 61 |

| Fact (where they differ) | Scrape.do | ScrapeOps Proxy API Aggregator |
| --- | --- | --- |
| Vendor | Scrape.do | ScrapeOps Limited |
| Hosted endpoint | `https://api.scrape.do/` | `https://mcp.scrapeops.io/mcp` |
| Transports | HTTP | stdio, Streamable HTTP |
| Auth | API key | OAuth or key |
| Tools exposed | none | 3 |
| Last release | 2026-07-31 | 2026-10 |
| Popularity | 2 npm/wk | none |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- 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.)