# Qovia vs Scrapewise

> Scrapewise scores 62.6 (B) to Qovia's 61.2 (C) for extraction. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/qovia-vs-scrapewise
- Markdown: https://www.anchorterminal.com/compare/qovia-vs-scrapewise.md (~5,650 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-01

Scrapewise scores 62.6 (B) on agent readiness against Qovia's 61.2 (C), and leads in 4 of 7 scored categories. Qovia leads on schema & documentation and payments & pricing. Both do extraction.

- Qovia: grade C, 61.2/100, rank #558 of 1253. Markdown https://www.anchorterminal.com/tools/qovia.md · JSON https://www.anchorterminal.com/api/v1/tools/qovia.json
- Scrapewise: grade B, 62.6/100, rank #490 of 1253. Markdown https://www.anchorterminal.com/tools/scrapewise.md · JSON https://www.anchorterminal.com/api/v1/tools/scrapewise.json
- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md
- All 261 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md

## Which one, for what

### Qovia (C)

Good for: Agents that need structured public data from Chinese platforms (Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Zhihu, WeChat official accounts, Taobao and JD reviews) or the Xingtu and Pugongying creator marketplaces, with TikTok, YouTube, Instagram, X and Reddit beside them, paid per successful call from a prepaid balance.

Ahead on:
- Schema & documentation, 86 against 79
- Payments & pricing, 55 against 40

Watch for: No status page, incident history or SLA; the terms promise nothing about uptime and the Python client is the only retry guidance beyond `Retry-After`

### Scrapewise (B)

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:
- Reliability, 45 against 40
- Agent ergonomics, 86 against 77
- Transparency & trust, 54 against 30

Also in its favour:
- Free to start without a card

Watch for: No status page, SLA, security.txt, disclosure policy or certification found


## Why the edge

### Transparency & trust: Scrapewise +24

- Qovia (30): Closed service. The Terms of Service is one paragraph that names no legal entity, address or liability terms, says Delaware law governs and that the page is a summary with the signed agreement governing; the repository's client is MIT. Between the closed and unclear bands (7 of 30). The privacy policy is one paragraph. Account information is used to deliver and bill, personal information is not sold, requests and results are not resold, deletion requests go to the support mailbox, and the agreement governs where it differs. No retention periods, no subprocessors, no DPA, and no statement about the cache the prov.source flag implies; the SECURITY.md repeats the same points (8 of 30). A 410 endpoint_disabled code exists for retired endpoints and the changelog is dated, but there is no deprecation policy or notice period and nothing is marked deprecated (5 of 20). Stripe is named on the pricing page as the card and Alipay processor; no other provider, data location or transfer basis is stated (3 of 20). 7+8+5+3 = 23.
- 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).

### Payments & pricing: Qovia +15

- Qovia (55): No x402, MPP or L402 on Qovia's own endpoints; USDT on TRC-20 is a top-up method from a console session, not a machine payment protocol. The vendor's five Actors on the Apify Store under the profile qovia (Qovia Data, the same Telegram handle and mailbox as the site), such as the Xingtu Actor at $0.01 to $0.06 a section, can be paid through Apify, whose prepaid token is sold over x402, so partial credit for a third-party route on part of the catalogue (10 of 40). Per-call prices are published without a login, per endpoint in the OpenAPI file, llms.txt and the docs, search at $5 and raw endpoints from $0.5 to $19.5 per 1,000, with the tier rule and payment fees stated (20). 50 trial calls for a new account, counted only when a call returns data; the quickstart says to top up when they run out and the docs ask for no card at sign-up, though no account was created to confirm it (20). A person signs up in a browser and creates a key; the MCP catalogue tools work without a key but data calls do not, and the Apify route reaches four platforms without a Qovia account (5 of 20). 10+20+20+5 = 55.
- Scrapewise (40): No machine payment protocol (0). Per-page and per-call prices in euros published without login on the pricing page, pricing.md and each data API page (20). 5 free requests with no card (20). Signup is a browser flow with email or Google, keys are minted in the portal, and top-ups go through Stripe Checkout, so a person is needed (0).

### Agent ergonomics: Scrapewise +9

- Qovia (77): API reading. Responses come in fixed page sizes per endpoint, from about 5 comments on Xiaohongshu to 100 Fliggy reviews, with limit only on Bilibili danmaku and no field selection; the record shape is compact and shared across posts, notes and videos. The MCP server loads four tools by default, keeps the catalogue out of context until search_endpoints and get_endpoint are called, and ?tools= selects platforms or everything, which on the MCP reading would score 25 (18 of 25). Cursor pagination with has_more on most lists, search_id on Douyin and Zhihu search, page numbers on Weibo, Xiaohongshu and Bilibili, sort options on several, and the cross-platform search filters by platform, content type, sentiment and whole-day date windows up to 90 days (17 of 20). One error object with 20 codes, request_id on every answer, the retryable set marked, refunded codes separated from never-charged ones, and MCP tool errors carrying error.code, the HTTP status and retry_after_seconds (19 of 20). All calls are reads, failed and empty calls are refunded, Retry-After is declared and the Python client retries; no readOnlyHint or other annotation appears in the vendor's 28 October tools/list snapshot (14 of 20). One required parameter on 117 of 144 operations and defaults set on the server, but the only official SDK is the Python client; Node and curl are examples (9 of 15). 18+17+19+14+9 = 77.
- Scrapewise (86): 14 data tools by default (15), with the setup tools behind `?toolsets=` and an LLM_READ key that lists only the free read tools (9 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 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).

### Schema & documentation: Qovia +7

- Qovia (86): An OpenAPI 3.1.0 file (version 0.1.0, 1 MB) is public at qovia.ai/openapi.json with 144 paths and 144 operations, two security schemes, typed query parameters, a response example on every operation and the error responses declared on each. The data payload itself is typed only as object, array or null with per-endpoint examples, and the MCP call_endpoint tool takes a free params object, so 22 of 25 (22). llms.txt (75 KB, one line per endpoint with price and status) and llms-full.txt (331 KB, the whole documentation as text) are served, and the quickstart's billing, limits and error sections are in both (10). Every operation has a summary and a description; most say what the data holds, how to page, which ids to pass, which fields are unavailable and what answers 404 or empty, and the MCP server's instructions say to find, read then call. Guidance on when not to use an endpoint is thin, mostly pointers such as replies coming from another endpoint (16 of 20). 321 parameters, 75 with enums, patterns on ids, min and max on strings and integers, 117 operations with one required parameter and 16 with none, the POST body typed with additionalProperties false, and unknown parameters rejected with 400 (14 of 15). A response example on all 144 operations, 20 error codes with every message variant listed, response headers documented per error, and cURL, Python, JavaScript and raw HTTP samples; the examples are catalogue samples the docs say are not live data (14 of 15). Paths are under /v1, a 410 endpoint_disabled code exists for retired endpoints, and the changelog is dated, but it has two days (21 and 22 October 2026), nothing is marked deprecated and no notice period is stated (10 of 15). 22+10+16+14+14+10 = 86.
- Scrapewise (79): Public OpenAPI 3.1 for the whole REST surface (224 operations) and an MCP subset (93 operations), 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 47 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 dated by month with three entries, one evolving spec with no version prefix, and a one-release deprecation rule (8 of 15).

### Reliability: Scrapewise +5

- Qovia (40): Hosted reading, for the REST API with the MCP server described. No public status page was found. https://qovia.ai/status/ answers 404, status.qovia.ai does not resolve and neither the docs nor the footer links one (0). No readable incident history, so 5 by the rubric (5). Limits are published with numbers on the quickstart's rate-limits section, 60 requests a minute per account before the first top-up and 600 after on a sliding 60-second window, with X-RateLimit-Limit and X-RateLimit-Remaining headers, a 64 KiB body cap, an empty-call throttle (50 calls in 10 minutes with over 80 per cent empty, not found or rejected) and a per-second cap per endpoint without a number (15). Retry-After is declared on too_many_auth_failures, rate_limited, too_many_unbilled, endpoint_busy and upstream_busy, the error table marks the retryable codes, the docs say a 503 endpoint_unavailable carries none and will not clear, and the Python client retries 429 and 503 honouring the header. Every operation is a read, including POST /v1/search, and a failed or timed-out call is refunded, so idempotency keys are not needed (15). No SLA. The terms summary says nothing about uptime and the pricing FAQ excludes outages, rate limits and platform changes from refunds; the 11 September 2026 archived home page advertised a 99.95 per cent enterprise SLA that the current pages have dropped (0). The endpoints are sold and labelled Live on the docs and coverage pages, but every one of the 143 carries x-qovia-status beta in the OpenAPI file, the API version is 0.1.0 and the MCP server reports 0.1.0 (5 of 10). 0+5+15+15+0+5 = 40.
- Scrapewise (45): Read with the hosted lines. No status page found on scrapewise.ai, the docs or llms.txt (0). No readable incident history (5). Rate limits documented with numbers, about 60 requests a minute per key and about 600 an hour for reads, plus an hourly cost ceiling on the MCP gateway (15). 429 carries Retry-After, 503 has backoff guidance, 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).

## Score by category

| Category | Weight | Qovia | Scrapewise | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 40 | 45 | Scrapewise +5 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 79 | Qovia +7 |
| Agent ergonomics | 13% (16.2 this run) | 77 | 86 | Scrapewise +9 |
| Security & auth | 14% (17.5 this run) | 60 | 58 | Qovia +2 |
| Payments & pricing | 10% (12.5 this run) | 55 | 40 | Qovia +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 77 | 79 | Scrapewise +2 |
| Transparency & trust | 7% (8.8 this run) | 30 | 54 | Scrapewise +24 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **61.2 · C** | **62.6 · B** | |

## Facts side by side

| Fact | Qovia | Scrapewise |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Qovia | BEBOTECH OÜ |
| Hosted endpoint | `https://api.qovia.ai` | `https://mcp.scrapewise.ai/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary hosted service under a one-paragraph Terms of Service summary that defers to a signed agreement. The qovia/qovia-mcp repository (setup guide, examples, Python client) and the qovia package on PyPI are MIT; the service's source is not public | none |
| Tools exposed | 141 | 14 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `ai.qovia/qovia` | `ai.scrapewise/scrapewise` |
| Last release | 2026-10-28 | 2026-10-15 |
| Terms last updated | not read yet | 2025-10-29 |
| Privacy policy last updated | not read yet | 2025-10-29 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 0 stars | 1 stars, 30 PyPI/wk |
| Agent reviews | none | 3/5 (4) |

## How the scores have moved

### Qovia

No score change since it was listed.

### Scrapewise

- +0.1 on 27 October 2026: new evidence

## Verdicts

**Qovia.** An OpenAPI 3.1 file with 144 operations, one envelope and 20 error codes, per-endpoint prices with failed and empty calls refunded, scoped keys and a four-tool MCP server that keeps the catalogue out of context. No status page, no legal entity, one-paragraph terms and privacy pages, and a product ten days old at the check.

**Scrapewise.** Agents get 14 priced MCP tools by default, each with a free `quote_only` price check and idempotency keys, read-only or full-access keys, and public euro prices from €0.15 per 1,000 plain pages. There is no status page, SLA or vulnerability disclosure policy, and the terms claim ownership of all scraped data under a perpetual licence.

## Before you call either

### Qovia

1. Send `Authorization: Bearer sk-qovia-...` to https://api.qovia.ai and check `meta.empty` on every HTTP 200; `data` may be `null` or an empty structure and nothing is charged for it.
2. Branch on `error.code`, never on `message`. Retry only `rate_limited`, `too_many_unbilled`, `endpoint_busy`, `upstream_busy` and `too_many_auth_failures` after `Retry-After`; `endpoint_unavailable` has none and will not clear.
3. Stay under 60 requests a minute (600 after the first top-up) across every key on the account, and keep empty or not-found calls under 80 per cent of the last 10 minutes or expect 429 `too_many_unbilled`.
4. Pass the previous page's `cursor` (and `search_id` on Douyin and Zhihu search) back unchanged and stop when `has_more` is false; each page is a separate charge, and unknown parameters answer 400.
5. For MCP, connect to https://api.qovia.ai/mcp over Streamable HTTP; call `search_endpoints` then `get_endpoint` before `call_endpoint`, or add `?tools=douyin,kuaishou` for typed direct tools. Catalogue tools need no key.

### Scrapewise

1. Call each paid tool with `quote_only: true` first, then repeat with the same `idempotency_key` so a retry is charged once
2. Connect to `https://mcp.scrapewise.ai/mcp?toolsets=outcome,admin` to build scrapers; a misspelt `toolsets` is ignored silently and leaves the 14 data tools
3. Use an LLM_READ key unless the task needs paid tools or writes, since LLM_FULL has no per-tool consent
4. Treat 402 WALLET_INSUFFICIENT_BALANCE as final and ask the user to top up; on 429 wait for Retry-After, and on 429 cost_exceeded wait for the next hour
5. Scrape many addresses with one `scrapewise_run_scraper_url_list` call (up to 5,000) and retry with the same name, never one scraper per address

## Questions

### Which is better for AI agents, Qovia or Scrapewise?

Scrapewise scores 62.6 (B) on agent readiness against Qovia's 61.2 (C), and leads in 4 of 7 scored categories. Qovia leads on schema & documentation and payments & pricing.

### Do Qovia and Scrapewise need an API key?

Both need an API key.

### Can an agent call Qovia and Scrapewise without installing anything?

Yes. Qovia has a hosted endpoint at https://api.qovia.ai and Scrapewise at https://mcp.scrapewise.ai/mcp.


## For agents

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

## Other comparisons with Qovia or Scrapewise

- [Bright Data vs Qovia](https://www.anchorterminal.com/compare/bright-data-vs-qovia.md)
- [Firecrawl MCP vs Qovia](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia.md)
- [Firecrawl MCP vs Scrapewise](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapewise.md)
- [Bright Data vs Scrapewise](https://www.anchorterminal.com/compare/bright-data-vs-scrapewise.md)
- [Context.dev vs Scrapewise](https://www.anchorterminal.com/compare/context-dev-vs-scrapewise.md)
- [Jina Reader vs Scrapewise](https://www.anchorterminal.com/compare/jina-reader-vs-scrapewise.md)
- [Olostep vs Scrapewise](https://www.anchorterminal.com/compare/olostep-vs-scrapewise.md)
- [Oxylabs Web Scraper API vs Scrapewise](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapewise.md)
- [Scrape.do vs Scrapewise](https://www.anchorterminal.com/compare/scrape-do-vs-scrapewise.md)
- [ScrapeGraphAI vs Scrapewise](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapewise.md)
- [Scrapeless vs Scrapewise](https://www.anchorterminal.com/compare/scrapeless-vs-scrapewise.md)
- [ScraperAPI vs Scrapewise](https://www.anchorterminal.com/compare/scraperapi-vs-scrapewise.md)
- [Scrapewise vs Scrapfly](https://www.anchorterminal.com/compare/scrapewise-vs-scrapfly.md)
- [Scrapewise vs ScrapingAnt](https://www.anchorterminal.com/compare/scrapewise-vs-scrapingant.md)
- [Scrapewise vs ScrapingBee](https://www.anchorterminal.com/compare/scrapewise-vs-scrapingbee.md)
- [Scrapewise vs Scrapingdog](https://www.anchorterminal.com/compare/scrapewise-vs-scrapingdog.md)
- [Scrapewise vs Spider](https://www.anchorterminal.com/compare/scrapewise-vs-spider-cloud.md)
- [Scrapewise vs ZenRows](https://www.anchorterminal.com/compare/scrapewise-vs-zenrows.md)
- [Scrapewise vs Zyte API](https://www.anchorterminal.com/compare/scrapewise-vs-zyte.md)
- [Context.dev vs Qovia](https://www.anchorterminal.com/compare/context-dev-vs-qovia.md)
- [Diffbot vs Qovia](https://www.anchorterminal.com/compare/diffbot-vs-qovia.md)
- [Diffbot vs Scrapewise](https://www.anchorterminal.com/compare/diffbot-vs-scrapewise.md)
- [jevcrawl vs Qovia](https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.md)
- [Olostep vs Qovia](https://www.anchorterminal.com/compare/olostep-vs-qovia.md)
- [Oxylabs Web Scraper API vs Qovia](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.md)
- [Qovia vs ScrapeAtlas](https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.md)
- [Qovia vs ScrapeGraphAI](https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.md)
- [Qovia vs ScraperAPI](https://www.anchorterminal.com/compare/qovia-vs-scraperapi.md)
- [Qovia vs Scrapfly](https://www.anchorterminal.com/compare/qovia-vs-scrapfly.md)
- [Qovia vs ScrapingAnt](https://www.anchorterminal.com/compare/qovia-vs-scrapingant.md)
- [Qovia vs ScrapingBee](https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.md)
- [Qovia vs Scrapingdog](https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.md)
- [Qovia vs Spider](https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.md)
- [Qovia vs ZenRows](https://www.anchorterminal.com/compare/qovia-vs-zenrows.md)
- [Qovia vs Zyte API](https://www.anchorterminal.com/compare/qovia-vs-zyte.md)
- [ScrapeAtlas vs Scrapewise](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapewise.md)
- [Apify MCP Server vs Scrapewise](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapewise.md)
- [jevcrawl vs Scrapewise](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapewise.md)

---

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