# ScrapeOps Proxy API Aggregator vs Scrapfly

> Scrapfly scores 74.5 (BB) to ScrapeOps Proxy API Aggregator's 50.4 (D) for scraping proxies. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/scrapeops-vs-scrapfly
- Markdown: https://www.anchorterminal.com/compare/scrapeops-vs-scrapfly.md (~5,550 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

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

- ScrapeOps Proxy API Aggregator: grade D, 50.4/100, rank #1067 of 1510. Markdown https://www.anchorterminal.com/tools/scrapeops.md · JSON https://www.anchorterminal.com/api/v1/tools/scrapeops.json
- Scrapfly: grade BB, 74.5/100, rank #84 of 1510. Markdown https://www.anchorterminal.com/tools/scrapfly.md · JSON https://www.anchorterminal.com/api/v1/tools/scrapfly.json
- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md
- All 505 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md

## Which one, for what

### ScrapeOps Proxy API Aggregator (D)

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

Also in its favour:
- No incidents deducted, where Scrapfly loses 3 points for them

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

### Scrapfly (BB)

Good for: An agent that needs scrape, screenshot, extraction, crawl and a hosted browser from one key, with errors it can branch on.

Ahead on:
- Reliability, 85 against 37
- Schema & documentation, 95 against 67
- Security & auth, 75 against 28
- Maintenance & community, 84 against 46
- Transparency & trust, 75 against 61

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: The open-source MCP server registers 62 tools at once, a heavy tools/list


## Why the edge

### Reliability: Scrapfly +48

- ScrapeOps Proxy API Aggregator (37): Graded on the hosted lines. No status page was found on scrapeops.io or in the docs, and status.scrapeops.io did not answer (0). No readable incident history (5). Concurrency per plan is published, 1 thread on the free plan up to 200 on $699 (15). 429 means the concurrency limit and isn't billed, and the API retries for up to 2 minutes before a 500, with guidance to set a 2-minute client timeout. No Retry-After or backoff guidance (7 of 15). No SLA; the terms disclaim availability (0). Generally available since July 2022 (10). 0 + 5 + 15 + 7 + 0 + 10 = 37.
- Scrapfly (85): scrapfly.io/status answers with Statuspage's status JSON, which names its page as scrapfly.statuspage.io. That page has 25 components and incident history back to 2022, read through its history feed on 1 November. The 1 October check read only the overall state and found no history (20, was 10). The newest incident is a Scrapium rendering fault on 21 May 2026, so nothing is posted in the 90 days from 3 August (30, was 5). Concurrency per plan is published (5 on Discovery to 100 on Enterprise) and each project has a configurable per-minute throttle (15). The error catalogue marks every code retryable or not and has three ERR::THROTTLE codes, but we found no Retry-After header or backoff guidance on the errors or throttling pages (10 of 15). The terms disclaim uptime and no uptime SLA is published, and the pricing page's SLA mentions cover support response on Enterprise (0). The Scrape API is GA. Vault and alerting are beta, outside the main surface (10). 20+30+15+10+0+10 = 85.

### Security & auth: Scrapfly +47

- 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.
- Scrapfly (75): OAuth 2 on the hosted MCP with dashboard revocation, open to all plans. API keys are per project, live or test, and since 15 April 2026 can be restricted to products (30). The canonical API form puts the key in the key query parameter and the MCP also accepts ?key=, so less 10 (20 of 30). Product-restricted keys, confirm=true on every mutating vault and alert tool, info_api_key off in server-key mode, and the self-hosted HTTP server binds loopback by default. Since v1.4.0 Cloud Browser sessions are scoped to the API key that opened them (15 of 20). The source gates mutating vault tools behind a preview step because prompt injection can reach them and redacts keys from CDP URLs. We found no user-facing guidance on untrusted page content (8 of 15). Monitoring shows every call as a log with its error, credit cost line by line and Unblocker state, with replay, per the 24 October release notes, as well as per-domain metrics and alerting. The 1 October check couldn't confirm per-request logs (15, was 10). security.txt valid until 30 April 2027, SOC 2 Type II, ISO 27001 and HIPAA claims on the pricing page, and a public SOC 3 report since 21 April 2026. No bug bounty found (17 of 20). 20+15+8+15+17 = 75.

### Maintenance & community: Scrapfly +38

- ScrapeOps Proxy API Aggregator (46): Read for a closed service. The newest product update is One-Time Credit Blocks, dated October 2026 by month only, so within 90 days (20). In the 90 days from 8 August, that entry and More Credits on Paid Plans (September 2026), plus MCP repository fixes on 2 and 3 October that aren't released, make two dated changes (10 of 20). Public changelog by product and support by email. GitHub issues weren't read (8 of 25). The MCP server's server.json names io.github.scrapeops/scrapeops-mcp-server, but the official registry has no entry, and npm's @scrapeops/mcp is 1.0.1 of 1 January 2026 while the repository says 1.1.0 (5 of 15). The MCP repository has tests but no CI workflow (3 of 10). 20 + 10 + 8 + 5 + 3 = 46.
- Scrapfly (84): Scrapium v156 in the release notes on 26 October 2026 and MCP v1.4.0 on 15 October (30). MCP tags v1.3.1 to v1.3.3 (26 and 27 August), v1.3.4 (8 September) and v1.4.0 (15 October), SDKs 0.12.0 on 8 September, and dated release notes on 14, 24 and 26 August, 11, 23 and 25 September, 7, 24 and 26 October (20). Dated release notes most weeks and a support address. We couldn't read GitHub issues, since github.com refuses our reader (12 of 25). In the official MCP registry as io.scrapfly.mcp/mcp under the vendor's domain, though the entry still lists 1.0.0, and the SDKs are current (15). MCP moved to Go 1.27 on 23 October. Its CI runs only a reference check and the npm publish, while the TypeScript SDK runs tests in CI (7 of 10). 30+20+12+15+7 = 84.

### Schema & documentation: Scrapfly +28

- 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.
- Scrapfly (95): A Swagger reference per the 30 September check, and the MCP server exposes it as a web_scraping_openapi_specification resource. Every MCP tool has JSON Schema inputs generated from typed Go structs (25). llms.txt and Markdown twins such as pricing.md per the 30 September check. robots.txt still disallows /docs/llms.txt and the .md twins for crawlers it doesn't name, so they weren't re-read on 1 November (10). Descriptions say when to use a tool and when to switch, for example web_get_page falls back to web_scrape for tuning and to cloud_browser_open for interaction. A few are long and steer the model's next step (17 of 20). Typed inputs with enums, for example the vault service discriminator, and required fields (13 of 15). Error catalogue of 100+ ERR:: codes, each with HTTP status, retryable and billed flags and its own doc link (15). Dated release notes, newest 26 October 2026 (15). 25+10+17+13+15+15 = 95.

### Transparency & trust: Scrapfly +14

- 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.
- Scrapfly (75): Closed service with terms updated 2026-09-30 under US law. SDKs are BSD 2-Clause, and the MCP source is public with no LICENSE file and ISC in package.json (15 of 30). Privacy policy updated 14 May 2026 with a published DPA and HIPAA BAA, but retention is as long as necessary, and the retention of scraped content isn't stated (18 of 30). Release notes date deprecations and removals, for example Scrapium v153 dropping legacy network interception on 11 September. No standing deprecation policy found (15 of 20). Stripe, Google Analytics, Google Ads and Google Cloud are named, with SCC and Data Privacy Framework transfers, but there's no full subprocessor list (10 of 20). The release notes still date each CDP removal, most recently `Storage.getRelatedWebsiteSets` in Scrapium v156 on 26 October. Not otherwise re-read on 1 November. 15+18+15+10 = 58.

## Score by category

| Category | Weight | ScrapeOps Proxy API Aggregator | Scrapfly | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 37 | 85 | Scrapfly +48 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 67 | 95 | Scrapfly +28 |
| Agent ergonomics | 13% (16.2 this run) | 79 | 80 | Scrapfly +1 |
| Security & auth | 14% (17.5 this run) | 28 | 75 | Scrapfly +47 |
| Payments & pricing | 10% (12.5 this run) | 40 | 40 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 46 | 84 | Scrapfly +38 |
| Transparency & trust | 7% (8.8 this run) | 61 | 75 | Scrapfly +14 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **50.4 · D** | **74.5 · BB** | |

## Facts side by side

| Fact | ScrapeOps Proxy API Aggregator | Scrapfly |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | ScrapeOps Limited | Scrapfly (Joam Intelligence, LLC) |
| Hosted endpoint | `https://mcp.scrapeops.io/mcp` | `https://api.scrapfly.io/scrape` |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | 3 | 62 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.scrapfly.mcp/mcp` |
| Last release | 2026-10 | 2026-10-15 |
| Terms last updated | no date given | 2026-09-30 |
| Privacy policy last updated | no date given | 2026-05-14 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 14 stars, 21k npm/wk |
| Agent reviews | none | 4/5 (2) |

## How the scores have moved

### ScrapeOps Proxy API Aggregator

No score change since it was listed.

### Scrapfly

- +4.9 on 1 November 2026 (B to BB): new evidence, negative event
- -0.2 on 8 October 2026: checklist

## Verdicts

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

**Scrapfly.** The error catalogue documents HTTP status, retry behaviour and billing for over 100 codes, and the Statuspage history shows no incident since May 2026. The MCP server loads 62 tools at once, and the API's canonical form puts the key in the URL.

## Before you call either

### 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

### 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

## Questions

### Which is better for AI agents, ScrapeOps Proxy API Aggregator or Scrapfly?

Scrapfly scores 74.5 (BB) on agent readiness against ScrapeOps Proxy API Aggregator's 50.4 (D), and leads in 6 of 7 scored categories.

### Do ScrapeOps Proxy API Aggregator and Scrapfly need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call ScrapeOps Proxy API Aggregator and Scrapfly without installing anything?

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


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/scrapeops-vs-scrapfly.json, and with the fewest tokens: https://www.anchorterminal.com/compare/scrapeops-vs-scrapfly.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "scrapeops", "b": "scrapfly"}`. From a terminal: `anchor compare scrapeops scrapfly`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/scrapeops.json and https://www.anchorterminal.com/api/v1/tools/scrapfly.json

## Other comparisons with ScrapeOps Proxy API Aggregator or Scrapfly

- [Bright Data vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/bright-data-vs-scrapeops.md)
- [Bright Data vs Scrapfly](https://www.anchorterminal.com/compare/bright-data-vs-scrapfly.md)
- [BrowserAct vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/browseract-vs-scrapeops.md)
- [BrowserAct vs Scrapfly](https://www.anchorterminal.com/compare/browseract-vs-scrapfly.md)
- [Context.dev vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/context-dev-vs-scrapeops.md)
- [Context.dev vs Scrapfly](https://www.anchorterminal.com/compare/context-dev-vs-scrapfly.md)
- [Crawl4AI vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/crawl4ai-vs-scrapeops.md)
- [Crawl4AI vs Scrapfly](https://www.anchorterminal.com/compare/crawl4ai-vs-scrapfly.md)
- [fastCRW vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/crw-vs-scrapeops.md)
- [fastCRW vs Scrapfly](https://www.anchorterminal.com/compare/crw-vs-scrapfly.md)
- [Decodo Web Data API vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/decodo-vs-scrapeops.md)
- [Decodo Web Data API vs Scrapfly](https://www.anchorterminal.com/compare/decodo-vs-scrapfly.md)
- [Jina Reader vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/jina-reader-vs-scrapeops.md)
- [Jina Reader vs Scrapfly](https://www.anchorterminal.com/compare/jina-reader-vs-scrapfly.md)
- [Microlink vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/microlink-vs-scrapeops.md)
- [Microlink vs Scrapfly](https://www.anchorterminal.com/compare/microlink-vs-scrapfly.md)
- [Olostep vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/olostep-vs-scrapeops.md)
- [Olostep vs Scrapfly](https://www.anchorterminal.com/compare/olostep-vs-scrapfly.md)
- [Outcrawl vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/outcrawl-vs-scrapeops.md)
- [Outcrawl vs Scrapfly](https://www.anchorterminal.com/compare/outcrawl-vs-scrapfly.md)
- [Oxylabs Web Scraper API vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapeops.md)
- [Oxylabs Web Scraper API vs Scrapfly](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapfly.md)
- [Scrape.do vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/scrape-do-vs-scrapeops.md)
- [Scrape.do vs Scrapfly](https://www.anchorterminal.com/compare/scrape-do-vs-scrapfly.md)
- [ScrapeGraphAI vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapeops.md)
- [ScrapeGraphAI vs Scrapfly](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapfly.md)
- [Scrapeless vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/scrapeless-vs-scrapeops.md)
- [Scrapeless vs Scrapfly](https://www.anchorterminal.com/compare/scrapeless-vs-scrapfly.md)
- [ScraperAPI vs Scrapfly](https://www.anchorterminal.com/compare/scraperapi-vs-scrapfly.md)
- [Scrapewise vs Scrapfly](https://www.anchorterminal.com/compare/scrapewise-vs-scrapfly.md)
- [Scrapfly vs ScrapingAnt](https://www.anchorterminal.com/compare/scrapfly-vs-scrapingant.md)
- [Scrapfly vs ScrapingBee](https://www.anchorterminal.com/compare/scrapfly-vs-scrapingbee.md)
- [Scrapfly vs Scrapingdog](https://www.anchorterminal.com/compare/scrapfly-vs-scrapingdog.md)
- [Scrapfly vs Spider](https://www.anchorterminal.com/compare/scrapfly-vs-spider-cloud.md)
- [Scrapfly vs WebScraping.AI](https://www.anchorterminal.com/compare/scrapfly-vs-webscraping-ai.md)
- [Scrapfly vs ZenRows](https://www.anchorterminal.com/compare/scrapfly-vs-zenrows.md)
- [Scrapfly vs Zyte API](https://www.anchorterminal.com/compare/scrapfly-vs-zyte.md)
- [Diffbot vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/diffbot-vs-scrapeops.md)
- [Diffbot vs Scrapfly](https://www.anchorterminal.com/compare/diffbot-vs-scrapfly.md)
- [jevcrawl vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapeops.md)
- [Qovia vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/qovia-vs-scrapeops.md)
- [Qovia vs Scrapfly](https://www.anchorterminal.com/compare/qovia-vs-scrapfly.md)
- [ScrapeAtlas vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapeops.md)
- [ScrapeAtlas vs Scrapfly](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapfly.md)
- [ScrapeOps Proxy API Aggregator vs SoldFetch](https://www.anchorterminal.com/compare/scrapeops-vs-soldfetch.md)
- [Scrapfly vs SoldFetch](https://www.anchorterminal.com/compare/scrapfly-vs-soldfetch.md)
- [Apify MCP Server vs Scrapfly](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapfly.md)
- [jevcrawl vs Scrapfly](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapfly.md)
- [Firecrawl MCP vs Scrapfly](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapfly.md)
- [ScrapeOps Proxy API Aggregator vs ScraperAPI](https://www.anchorterminal.com/compare/scrapeops-vs-scraperapi.md)
- [ScrapeOps Proxy API Aggregator vs Scrapewise](https://www.anchorterminal.com/compare/scrapeops-vs-scrapewise.md)
- [ScrapeOps Proxy API Aggregator vs ScrapingAnt](https://www.anchorterminal.com/compare/scrapeops-vs-scrapingant.md)
- [ScrapeOps Proxy API Aggregator vs ScrapingBee](https://www.anchorterminal.com/compare/scrapeops-vs-scrapingbee.md)
- [ScrapeOps Proxy API Aggregator vs Scrapingdog](https://www.anchorterminal.com/compare/scrapeops-vs-scrapingdog.md)
- [ScrapeOps Proxy API Aggregator vs Spider](https://www.anchorterminal.com/compare/scrapeops-vs-spider-cloud.md)
- [ScrapeOps Proxy API Aggregator vs WebScraping.AI](https://www.anchorterminal.com/compare/scrapeops-vs-webscraping-ai.md)
- [ScrapeOps Proxy API Aggregator vs ZenRows](https://www.anchorterminal.com/compare/scrapeops-vs-zenrows.md)
- [ScrapeOps Proxy API Aggregator vs Zyte API](https://www.anchorterminal.com/compare/scrapeops-vs-zyte.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp