# Decodo Web Data API vs Oxylabs Web Scraper API (slim)

> Oxylabs Web Scraper scores 62.9 (B) to Decodo Web Data's 61.8 (C) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

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

Oxylabs Web Scraper API scores 62.9 (B) on agent readiness against Decodo Web Data API's 61.8 (C), and leads in 4 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
- Oxylabs Web Scraper API: B 62.9, rank #535 of 1486 · https://www.anchorterminal.com/tools/oxylabs-web-scraper.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. Also No incidents deducted, where Oxylabs Web Scraper API loses 3 points for them.
- Oxylabs Web Scraper API, good for Agents that need parsed Google, Amazon and other large-site results or bulk asynchronous jobs through one API. Ahead on Reliability, 75 against 59; Security & auth, 53 against 45.

| Category | Decodo Web Data API | Oxylabs Web Scraper API |
| --- | --- | --- |
| Reliability (16%) | 59 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 67 | 68 |
| Agent ergonomics (13%) | 82 | 79 |
| Security & auth (14%) | 45 | 53 |
| Payments & pricing (10%) | 40 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 85 | 82 |
| Transparency & trust (7%) | 62 | 64 |

| Fact (where they differ) | Decodo Web Data API | Oxylabs Web Scraper API |
| --- | --- | --- |
| Vendor | Decodo (UAB "Data troops") | oxylabs, UAB |
| Hosted endpoint | `https://mcp.decodo.com/mcp` | `https://realtime.oxylabs.io/v1/queries` |
| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| Price for scraping | $0.50 per 1,000 requests | not published |
| Licence | none | Proprietary service under the Oxylabs General Conditions. The MCP server and the Python SDK on GitHub are MIT |
| Tools exposed | 33 | 10 |
| MCP registry | `io.github.Decodo/mcp-server` | `io.oxylabs/oxylabs-mcp` |
| Last release | 2026-10-30 | 2026-10-29 |
| Terms last updated | 2025-06-16 | 2026-10-05 |
| Privacy policy last updated | 2026-05-21 | 2024-10-14 |
| Customer content may train models | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 18k PyPI/wk |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Reliability, Oxylabs Web Scraper API +16: 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.); Oxylabs Web Scraper API 75 (Graded on the Web Scraper API (Classic) surface. Status page at uptime.oxylabs.io on incident.io with separate components for Scraper APIs Push-Pull and Real-Time (20). Its feed lists two incidents since 4 August 2026, a Datacenter Proxies outage on 13 August that doesn't touch this API and, on 26 October, 12 minutes (05:34 to 05:46 on the page's clock) on both Scraper API components and Web Unblocker. The page labels it a full outage, but its own text says users "may experience degraded performance, intermittent errors, or timeouts", so we read it as partial and minor (20 of 30). Job rates per plan are published, from 10 a second on the free trial to 100 on Business and Corporate, with rendered-job limits (15). 429 is not billed, responses carry `x-ratelimit` limit and remaining headers, and 612 and 613 faults can be retried at no cost. No Retry-After or backoff guidance was found for this API (10 of 15). No SLA is published. The General Conditions promise reasonable efforts (0). Generally available (10).)
- Security & auth, Oxylabs Web Scraper API +8: 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.); Oxylabs Web Scraper API 53 (A username and password per product instance over HTTP Basic, with an editable password, optional IP whitelisting and several instances per account. The MCP server's v0.10.0 (15 October 2026) adds Web Scraper API tokens sent as a Bearer header, but the API docs still describe only the username and password, and no scopes were found (20 of 30). The Proxy Endpoint puts the pair in the proxy URL and needs TLS verification switched off, which we note without the query-string deduction. Scraping is read-only apart from POST requests to targets, callbacks and uploads to the customer's bucket, each instance can take a spending limit that disables it, and every MCP tool is marked read-only (10 of 20). No guidance on untrusted page content was found in the Web Scraper API docs, the MCP README or the agent skill (2 of 15). `GET /v2/stats` and the dashboard report usage by day and source, and jobs accept client notes. No per-request access log was found (7 of 15). ISO/IEC 27001:2022, SOC 2 Type 2 for Scraper API and yearly penetration tests per the trust centre (per the 8 October check, not re-read on 2 November). The disclosure programme is still paused except for critical issues sent to security@oxylabs.io, security.txt returns 404 and no bug bounty was found. That is above the 12 given for certification claims with no disclosure route (fireworks-inference, people-data-labs), because a route for critical issues and penetration tests are published (14 of 20).)