# Decodo Web Data API vs Scrapewise (slim)

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

- Full: https://www.anchorterminal.com/compare/decodo-vs-scrapewise.md (~6,200 tokens) · this version ~3,380 tokens · JSON https://www.anchorterminal.com/compare/decodo-vs-scrapewise.json · canonical https://www.anchorterminal.com/compare/decodo-vs-scrapewise
- 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 Scrapewise's 60 (C), and leads in 4 of 7 scored categories. Scrapewise leads on schema & documentation and security & auth. Both do scraping.

- Decodo Web Data API: C 61.8, rank #591 of 1486 · https://www.anchorterminal.com/tools/decodo.min.md
- Scrapewise: C 60, rank #670 of 1486 · https://www.anchorterminal.com/tools/scrapewise.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 45; Agent ergonomics, 82 against 72; Maintenance & community, 85 against 79; Transparency & trust, 62 against 54. Also Runs on your own machine.
- Scrapewise, good for Agents that need e-commerce prices, Amazon and Google data, or recurring price monitoring with cleaning and product matching, paid per page in euros. Ahead on Schema & documentation, 79 against 67; Security & auth, 56 against 45.

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

| Fact (where they differ) | Decodo Web Data API | Scrapewise |
| --- | --- | --- |
| Vendor | Decodo (UAB "Data troops") | BEBOTECH OÜ |
| Hosted endpoint | `https://mcp.decodo.com/mcp` | `https://mcp.scrapewise.ai/mcp` |
| Transports | Streamable HTTP, stdio | Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| Price for scraping | $0.50 per 1,000 requests | not published |
| Tools exposed | 33 | 113 |
| MCP registry | `io.github.Decodo/mcp-server` | `ai.scrapewise/scrapewise` |
| Last release | 2026-10-30 | 2026-10-23 |
| Terms last updated | 2025-06-16 | 2025-10-29 |
| Privacy policy last updated | 2026-05-21 | 2025-10-29 |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | none | 1 stars, 30 PyPI/wk |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Reliability, Decodo Web Data API +14: 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.); Scrapewise 45 (Read with the hosted lines. No status page found on scrapewise.ai, the docs, llms.txt or agents.md on 2 November 2026 (0). No readable incident history (5). Rate limits documented with numbers, per account per second and per day by plan (30 a second and 50,000 a day on STARTER up to 1,000 and 100,000,000 on BUSINESS, 2 a second unauthenticated), and 30 requests a second per key on the MCP gateway, plus an hourly cost ceiling there (15). 429 carries Retry-After and X-RateLimit-Remaining, Idempotency-Key is supported on scraper create and run, and paid MCP tools take an idempotency_key remembered for 24 hours (15). No SLA found (0). The API and MCP server are not marked beta, though AI control is in a test phase (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.)
- Schema & documentation, Scrapewise +12: Decodo Web Data API 67 (No OpenAPI or similar contract for the Web Data API; the two published specs cover the proxy account API and dashboard statistics. The MCP server types every input with zod (12 of 25). llms.txt indexes 401 guide pages, each served as Markdown (10). Tool descriptions state purpose and when to use a tool, such as scrape_as_markdown 'when no site-specific tool fits', and link the docs page (14 of 20). Parameters are tabled with defaults, with enumerated proxy_pool, headless and device_type, but `headers` is a free object and POST bodies are base64 strings (10 of 15). Curl examples on every page, a response code table with fixes and billing, and parser status codes (14 of 15). Paths are versioned at /v1 and the MCP server's releases are tagged by semantic-release, but no API changelog was found (7 of 15). 12 + 10 + 14 + 10 + 14 + 7 = 67.); Scrapewise 79 (Public OpenAPI 3.1 for the whole REST surface (247 operations on 2 November, 224 on 15 October) and an MCP subset (114 operations, 93 on 15 October), and MCP tools are generated from it with JSON Schema inputs (25). llms.txt, agents.md and pricing.md on scrapewise.ai, though docs.scrapewise.ai has no llms.txt (10). The data tools' descriptions say when to use each, what it returns, its price and that it is free or paid. Setup tools carry one-line descriptions (16 of 20). Required fields are marked and there are 55 enums in the MCP subset, but limits such as 1 to 20 results sit in prose, not as constraints, and paid tools wrap arguments in a `body` object (10 of 15). Request examples throughout, error codes listed with fixes, but the docs show two error envelope shapes and the MCP subset documents only 200, 204, 400 and 402 (10 of 15). A changelog with six entries, the newest items dated by day up to 23 October 2026, one evolving spec with no version prefix, and a one-release deprecation rule (8 of 15).)
- Security & auth, Scrapewise +11: 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.); Scrapewise 56 (Scoped keys (USER for REST, LLM_READ and LLM_FULL for MCP) stored as hashes, revocable at once, several per account with last-used time, rotated by mint and revoke. No expiry and no finer scopes (26 of 30). LLM_READ cannot run paid tools or write, and deletes need a preview token committed within 5 minutes. Since 22 October the setup and destructive tools are no longer opt-in for a Full key, and LLM_FULL has no per-tool consent (16 of 20). A documented prompt-injection contract and guidance, but it rests on a `type: "scraped"` content block that the MCP specification of 25 November 2025 does not define, and the docs' statement that Anthropic's clients honour it by default was not confirmed (8 of 15). Every call is logged with a correlation id and key prefix and the wallet ledger itemises charges, but the operator sees logs only through support (6 of 15). No security.txt, disclosure policy, bug bounty or certification found, security.txt still 404 on 2 November (0 of 20).)
- Agent ergonomics, Decodo Web Data API +10: Decodo Web Data API 82 (The hosted MCP server lists 24 tools, with a `toolsets` parameter to load only web, search, ecommerce, social_media or ai, and `tokenLimit` caps page text at 45,000 characters by default with a truncation notice (20 of 25). Markdown output, parsing for templates, crawl `limit`, path filters and cursor paging, search paging, map limits and batch tasks (18 of 20). Documented status codes with a solution for each, `status_code` and `parse_status_code` in bodies, but 429 covers both the plan rate and a domain throttled for a low success rate (15 of 20). Every tool carries readOnlyHint true and destructiveHint false, server-side failures aren't billed and async results can be re-read for 24 hours. No idempotency key (16 of 20). Only `url` or `query` is required, though the default premium pool costs about twice the standard. Official Python, TypeScript and Go SDKs (13 of 15). 20 + 18 + 15 + 16 + 13 = 82.); Scrapewise 72 (Since 22 October 2026 a Full (LLM_FULL) key lists every tool, 113 in the tool catalogue and 114 operations in the MCP subset of the spec, and the `?toolsets=` address that kept the setup tools out of the default list is no longer documented, so more than 30 tools (5). A Read (LLM_READ) key lists only the read tools, a read-only subset of 48 (5 added back). Cursor pagination with `limit` up to 1,000, `q`, `sort`, `from` and `to` filters, and job results in pages of 100 (20). Error codes an agent can branch on, such as WALLET_INSUFFICIENT_BALANCE, scope_rejected, cost_exceeded, SCRAPER_RUN_ACTIVE and MCP_SHOP_LIMIT, with a troubleshooting table, though two envelope shapes are documented (16 of 20). Idempotency keys on paid tools and REST create and run, a same-name retry rule for list runs, and preview tokens before deletes. Annotations are documented but only some appear in the spec, and tools/list was not read (16 of 20). Few required fields and a free `quote_only` check, but only a Python SDK (10 of 15). 10 + 20 + 16 + 16 + 10 = 72.)
- Transparency & trust, Decodo Web Data API +8: Decodo Web Data API 62 (Closed service under a public License Agreement naming UAB "Data troops", with MIT clients (15 of 30). The privacy policy (21 May 2026) gives retention periods by category, says Decodo is processor for scraping and doesn't log proxy traffic content, and a DPA is published. Its general two-year rule sits beside longer specific periods without saying which wins, and no retention for scraped results beyond the 24-hour async window was found (18 of 30). The migration guide says legacy APIs keep working with no end date, and the License Agreement allows discontinuing the service without notice or refunds (6 of 20). The privacy policy names Stripe, DeepL and Paddle, but no subprocessor list or data locations were found in it or the trust centre (6 of 20). 15 + 18 + 6 + 6 = 45.); Scrapewise 54 (Closed service with terms under Estonian law, but the terms name no legal entity and claim ownership of all collected and derived data. The MCP manifest and Python SDK are MIT (15 of 30). The 90-day retention agrees across the terms, pricing.md and billing docs. The privacy policy still speaks of subscriptions and plan limits, calls service data confidential while the terms claim ownership of it, and no DPA or retention period for logs was found (10 of 30). The API reference states a one-release deprecation rule and the changelog records changed columns with old rows left as they were (8 of 20). Analytics tools on the website named, chat stored on Hetzner in Germany, Stripe and Firebase named in the docs, but no subprocessor list or data locations for the service (5 of 20).)
- Maintenance & community, Decodo Web Data API +6: 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.); Scrapewise 79 (Read as a closed service. Changelog items dated 18, 20, 21, 22 and 23 October 2026 (30). At least three dated changes in 90 days, the September entry and the October items among them (20). A public changelog, a support address and site chat. Two outside issues on the MCP repository from 11 and 15 October had no reply per the 15 October check; GitHub's issue pages couldn't be read on 2 November (8 of 15). Verified namespace in the official MCP registry, version 0.1.1 still the latest on 2 November (15). The Python SDK has CI and trusted publishing at version 0.1.0, Beta, with no commit since 7 October (6 of 10). 30 + 20 + 8 + 15 + 6 = 79.)