# Decodo Web Data API vs ScrapeOps Proxy API Aggregator (slim)

> Decodo Web Data scores 61.8 (C) to ScrapeOps Proxy API Aggregator's 50.4 (D) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/decodo-vs-scrapeops.md (~4,650 tokens) · this version ~1,880 tokens · JSON https://www.anchorterminal.com/compare/decodo-vs-scrapeops.json · canonical https://www.anchorterminal.com/compare/decodo-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)

Decodo Web Data API scores 61.8 (C) on agent readiness against ScrapeOps Proxy API Aggregator's 50.4 (D), and leads in 5 of 7 scored categories. Both do scraping.

- Decodo Web Data API: C 61.8, rank #591 of 1486 · https://www.anchorterminal.com/tools/decodo.min.md
- ScrapeOps Proxy API Aggregator: D 50.4, rank #1057 of 1486 · https://www.anchorterminal.com/tools/scrapeops.min.md
- Decodo Web Data API, good for Agents that need pages, Google results and e-commerce or social templates through one key with published per-1,000 prices and a free plan. Ahead on Reliability, 59 against 37; Security & auth, 45 against 28; Maintenance & community, 85 against 46.
- ScrapeOps Proxy API Aggregator, good for Teams that want one key across many proxy APIs, paid only on success, with cost caps per request.

| Category | Decodo Web Data API | ScrapeOps Proxy API Aggregator |
| --- | --- | --- |
| Reliability (16%) | 59 | 37 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 67 | 67 |
| Agent ergonomics (13%) | 82 | 79 |
| Security & auth (14%) | 45 | 28 |
| Payments & pricing (10%) | 40 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 85 | 46 |
| Transparency & trust (7%) | 62 | 61 |

| Fact (where they differ) | Decodo Web Data API | ScrapeOps Proxy API Aggregator |
| --- | --- | --- |
| Vendor | Decodo (UAB "Data troops") | ScrapeOps Limited |
| Hosted endpoint | `https://mcp.decodo.com/mcp` | `https://mcp.scrapeops.io/mcp` |
| Transports | Streamable HTTP, stdio | stdio, Streamable HTTP |
| Price for scraping | $0.50 per 1,000 requests | not published |
| Tools exposed | 33 | 3 |
| MCP registry | `io.github.Decodo/mcp-server` | not listed |
| Last release | 2026-10-30 | 2026-10 |
| Terms last updated | 2025-06-16 | no date given |
| Privacy policy last updated | 2026-05-21 | no date given |
| Terms restrict automated access | not found in the text | yes |

Why the edge:
- Maintenance & community, Decodo Web Data API +39: Decodo Web Data API 85 (Read for a closed service with open clients. The newest releases are MCP server 1.7.0 on 29 October 2026 and @decodo/sdk-ts 3.0.0 on 30 October (30). Since 8 August, MCP server 1.2.5 to 1.7.0 (ten versions in the official registry) and sdk-ts 2.4.0 to 3.0.0 (20). No public API changelog. Support by 24/7 live chat, email and Discord, and the MCP repository had commits by Decodo staff on most days from 6 October to 5 November. GitHub issues couldn't be read, since api.github.com refused us (10 of 25). In the official MCP registry as io.github.Decodo/mcp-server, with current SDKs in three languages (15). The MCP repository lints, builds and tests on Node 22 and 24 for every pull request (10). 30 + 20 + 10 + 15 + 10 = 85.); 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.)
- Reliability, Decodo Web Data API +22: Decodo Web Data API 59 (Graded on the hosted lines. Instatus page at status.decodo.com with Web Data API and each legacy scraping API as components, with RSS history (20). In the 90 days to 6 November, every scraping API was out for 2 hours 51 minutes on 30 October, the main outage, with outages of 13 minutes on 26 October and 21 minutes on 15 October across the same components. The rest of the incidents hit proxies, payments or the website. One major (10). Per-plan request rates are published, 10 to 200 a second, though the same page's FAQ says paid plans support 10 to 50 (12 of 15). The response code table tells the agent to wait a couple of minutes on 429 and to retry 500, 524 and 613, which aren't billed, and the MCP client backs off exponentially. No Retry-After or idempotency guidance (7 of 15). No SLA; the License Agreement disclaims uninterrupted service (0). Web Data API is the current, unflagged product (10). 20 + 10 + 12 + 7 + 0 + 10 = 59.); 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.)
- Security & auth, Decodo Web Data API +17: Decodo Web Data API 45 (One Bearer API key per Web Data API subscription with no scopes, and no rotation or revocation steps found in the reviewed docs. The hosted MCP server adds OAuth 2.1 with PKCE and dynamic registration, but its metadata advertises no scopes. No query-string credential is documented (20 of 30). Scraping only reads, and the MCP tools are annotated read-only, but `http_method: POST` sends requests to target sites and there is no read-only key (8 of 20). No guidance on treating scraped content as untrusted was found in the docs or the MCP README (0 of 15). The dashboard statistics API reports traffic by target, and each response carries an `x-task-id`. No per-call audit log (7 of 15). ISO/IEC 27001:2022 for proxies and the Scraping API, a SafeBase trust centre and KYC at signup. security.txt answers 404 and no disclosure policy or bug bounty was found (10 of 20). 20 + 8 + 0 + 7 + 10 = 45.); 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.)