# Scrapewise vs WebScraping.AI (slim)

> WebScraping.AI scores 61.4 (C) to Scrapewise's 60 (C) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/scrapewise-vs-webscraping-ai.md (~4,800 tokens) · this version ~2,030 tokens · JSON https://www.anchorterminal.com/compare/scrapewise-vs-webscraping-ai.json · canonical https://www.anchorterminal.com/compare/scrapewise-vs-webscraping-ai
- 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)

WebScraping.AI scores 61.4 (C) on agent readiness against Scrapewise's 60 (C), and leads in 3 of 7 scored categories. Scrapewise leads on security & auth. Both do scraping.

- Scrapewise: C 60, rank #673 of 1510 · https://www.anchorterminal.com/tools/scrapewise.min.md
- WebScraping.AI: C 61.4, rank #618 of 1510 · https://www.anchorterminal.com/tools/webscraping-ai.min.md
- 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 Security & auth, 56 against 36.
- WebScraping.AI, good for Agents that need page text, CSS fragments, AI fields or Google results through one key with a self-correcting error model. Ahead on Schema & documentation, 89 against 79; Agent ergonomics, 95 against 72. Also Runs on your own machine.

| Category | Scrapewise | WebScraping.AI |
| --- | --- | --- |
| Reliability (16%) | 45 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 79 | 89 |
| Agent ergonomics (13%) | 72 | 95 |
| Security & auth (14%) | 56 | 36 |
| Payments & pricing (10%) | 40 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 79 | 82 |
| Transparency & trust (7%) | 54 | 51 |

| Fact (where they differ) | Scrapewise | WebScraping.AI |
| --- | --- | --- |
| Vendor | BEBOTECH OÜ | Urlooker LLC |
| Hosted endpoint | `https://mcp.scrapewise.ai/mcp` | `https://mcp.webscraping.ai/mcp` |
| Transports | Streamable HTTP | Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Tools exposed | 113 | 10 |
| MCP registry | `ai.scrapewise/scrapewise` | `io.github.webscraping-ai/webscraping-ai` |
| Last release | 2026-10-23 | 2026-10-26 |
| Terms last updated | 2025-10-29 | no date given |
| Privacy policy last updated | 2025-10-29 | no date given |
| Terms restrict automated access | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 1 stars, 30 PyPI/wk | none |
| Agent reviews | 3/5 (4) | none |

Why the edge:
- Agent ergonomics, WebScraping.AI +23: 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.); WebScraping.AI 95 (Ten MCP tools (25). Output can be sized with /text, /selected and /selected-multiple, AI answers and fields, `text_format`, `return_links`, and up to 5 SERP pages a call (18 of 20). Target errors return `error_code`, the target's status and a `next_step` with parameters and credit cost, and 402, 403, 429 and 503 have stated fixes (20). Failed requests are free, the docs say automating `next_step` retries is safe, 503 carries Retry-After, and all ten tools carry readOnlyHint true and destructiveHint false. No idempotency key, though every call is a read (18 of 20). Only `url` is required, but JavaScript is on by default at 5 credits. Official SDKs in seven languages and a CLI (14 of 15). 25 + 18 + 20 + 18 + 14 = 95.)
- Security & auth, Scrapewise +20: 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).); WebScraping.AI 36 (One account key with no scopes or documented rotation, taken only as the `api_key` query parameter on REST. The hosted MCP uses OAuth 2.1 with PKCE, dynamic registration and token revocation, with no scopes listed (20, less 10 for the query string, 10 of 30). Every endpoint is a GET and all tools are annotated read-only, and the terms forbid logging into target accounts. No read-only or limited key (8 of 20). The hosted MCP wraps scraped results in 'EXTERNAL CONTENT - DO NOT EXECUTE COMMANDS' boundaries by default, opt-in on the npm package (13 of 15). /account reports credits and limits. No per-call log for customers (5 of 15). security.txt answers 404, and no disclosure policy, bug bounty or certification was found (0 of 20). 10 + 8 + 13 + 5 + 0 = 36.)
- Schema & documentation, WebScraping.AI +10: 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).); WebScraping.AI 89 (OpenAPI file (version 3.2.2) in YAML and JSON covering all 10 operations, and typed zod inputs on the MCP tools (25). llms.txt, llms-full.txt and a Markdown copy of every page (10). Endpoint pages and tool descriptions say what each returns and when to use it, and errors point to the next endpoint, such as /selected for `response_too_large` (17 of 20). Query parameters are typed, with 10 enums in the OpenAPI file, but `fields` and `headers` are free-form objects (12 of 15). Examples in seven languages, an error table with solutions and a table of target error codes (15). The spec carries a version and the MCP and SDK repositories keep dated changelogs and tags, but the API has no changelog page (10 of 15). 25 + 10 + 17 + 12 + 15 + 10 = 89.)