{ "data": { "a": { "slug": "qovia", "name": "Qovia", "vendor": "Qovia", "vendorUrl": "https://qovia.ai", "kind": "http-api", "category": "web-scrapers", "summary": "Qovia is a hosted API that returns posts, comments, creator profiles, hot lists and product reviews from Douyin, Xiaohongshu, Weibo, Bilibili, TikTok, YouTube, X and other platforms as one JSON envelope, with a cross-platform search and a remote MCP server.", "url": "https://www.anchorterminal.com/tools/qovia", "markdownUrl": "https://www.anchorterminal.com/tools/qovia.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/qovia.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/qovia.json", "dns": "qovia.grade.anchorterminal.com", "repo": "https://github.com/qovia/qovia-mcp", "license": "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", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.qovia.ai", "packages": [ { "registry": "pypi", "name": "qovia" } ], "auth": "api-key", "authNotes": "An API key created in the console (prefix `sk-qovia-` plus 43 characters), sent as `Authorization: Bearer` or `x-api-key` to https://api.qovia.ai; the docs say the key is read from those two headers only, never from the URL or a cookie, and browser requests from other sites are refused by CORS. A key carries one or more scopes chosen at creation (`*`, `search`, `raw:*` or `raw:\u003cplatform\u003e` for each of 24 platform groups), an optional expiry, and is revoked in the console; the server stores a hash and shows the full key once. 30 failed authentications from one IP in a minute answer 429 `too_many_auth_failures`. The MCP server at https://api.qovia.ai/mcp takes the same key as a Bearer header; its `search_endpoints` and `get_endpoint` tools need no key, `call_endpoint` and `get_account` do. No OAuth metadata is served (404 on /.well-known/oauth-protected-resource per the 1 November listing check).", "pricing": "usage", "pricingNotes": "50 trial calls for a new account, counted only when a call returns data, then a prepaid balance in USD topped up by card or Alipay through Stripe (4.4 per cent plus $0.30 fee) or USDT on TRC-20 (2 per cent plus $0.30), no monthly fee (1 November 2026). Only an HTTP 200 with a non-empty result is charged; empty results, errors, timeouts and upstream failures are refunded. Cross-platform search is $5 per 1,000 calls. Raw endpoints are priced per endpoint, from $0.5 per 1,000 (8 Douyin, 5 Bilibili and 2 Xingtu endpoints) through $1 (61 endpoints), $1.5 (Cili Juxing, Huahuo), $2 (3 Instagram), $5 (WeChat, Xiaohongshu, 1 Pugongying), $10 (11 Xingtu, 10 Pugongying), $13.5 (Taobao reviews) to $19.5 (JD.com reviews); Tieba, Fliggy and the six coming-soon endpoints are on a tiered $1.5 rate that drops to $1 after 5,000,000 billed calls in a month. Top-ups are non-refundable except within 7 days when the vendor confirms a paid endpoint cannot be used. Datasets and bulk or custom data are quoted. Five Actors by the same vendor on the Apify Store are paid through Apify per section.", "priceSummary": "$5 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on qovia.ai, in the docs, llms.txt, the OpenAPI file or the repository (checked 2026-11-01). Top-ups take card and Alipay through Stripe or USDT on TRC-20 from a console session; USDT is a payment method, not a machine payment protocol. The only route without a Qovia account is the vendor's five Actors on the Apify Store (profile `qovia`, Qovia Data), paid through Apify.", "endpoints": [] }, "toolCount": 141, "popularity": { "githubStars": 0, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-01" }, "docsUrl": "https://qovia.ai/docs/", "llmsTxt": "https://qovia.ai/llms.txt", "openapi": "https://qovia.ai/openapi.json", "registryName": "ai.qovia/qovia", "capabilities": [ "web.extract", "social.analytics", "web.search" ], "tags": [ "hosted", "official", "closed-source", "openapi", "llms-txt", "mcp", "python", "free-trial", "prepaid", "usage-priced", "api-key", "beta", "new" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 61.2, "grade": "C", "agentReady": false, "rank": 558, "ranked": true, "rankOf": 1253, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 77, "payments": 55, "reliability": 40, "schema": 86, "security": 60, "transparency": 30 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "A public OpenAPI 3.1 file with 144 operations, patterns or enums on parameters, a response example on every operation and the error responses declared on each", "One envelope on every call, `request_id`, `data` and `meta` with the charge and balance, and 20 error codes sorted into not charged and refunded, with `Retry-After` on the retryable ones", "Only HTTP 200 with a non-empty result is charged; empty results, 404s, timeouts and upstream failures are refunded, and 50 trial calls come with a new account", "API keys carry per-platform scopes and an optional expiry, are read from headers only, and the docs tell users to give AI tools a separate scoped key", "The MCP server loads four tools by default and lets an agent find, read and call any of 137 endpoints, with `?tools=` subsets for direct tools; listed in the official registry under ai.qovia/qovia", "Published limits of 60 and 600 requests a minute with `X-RateLimit-*` headers, and a documented empty-call throttle" ], "weaknesses": [ "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`", "The terms and privacy policy are one paragraph each, name no legal entity, address, retention period or subprocessor, and say a signed agreement governs", "Every endpoint is marked `beta` in the OpenAPI file while the docs call it Live, and the API version is 0.1.0", "No security.txt, disclosure policy beyond a SECURITY.md, bug bounty or certification; the only support channels are Telegram, WhatsApp, WeChat and one mailbox", "Every response is third-party platform content and the docs carry no guidance on treating it as untrusted; four endpoint groups read login-gated creator marketplaces", "The changelog has two dated days, the domain is four months old, and the GitHub account was created the week of the request with nine forked lists beside the one repository" ], "agentNotes": [ "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.", "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.", "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`.", "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.", "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." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.2 } ], "editorialScores": { "ergonomics": 77, "maintenance": 77, "payments": 55, "reliability": 40, "schema": 86, "security": 60, "transparency": 23 }, "provenanceScore": 36, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install qovia", "http": "curl \"https://api.qovia.ai/v1/raw/weibo/hot_search\" -H \"Authorization: Bearer $QOVIA_API_KEY\"", "claudeCode": "claude mcp add --transport http qovia https://api.qovia.ai/mcp --header \"Authorization: Bearer $QOVIA_API_KEY\"" }, "letme": { "capability": "https://letme.dev/web.extract", "tool": "https://letme.dev/qovia" }, "area": "web-data", "unitPrices": [ { "item": "Cross-platform search", "unit": "1k-requests", "usd": 5, "note": "POST /v1/search, successful non-empty calls only, pricing page and OpenAPI file checked 1 November 2026" }, { "item": "Lowest raw endpoints (Douyin, Bilibili, Xingtu keywords)", "unit": "1k-requests", "usd": 0.5, "note": "15 fixed-price endpoints at $0.0005 a successful call" }, { "item": "Most raw endpoints (TikTok, YouTube, X, Reddit, Weibo, Zhihu, Kuaishou and others)", "unit": "1k-requests", "usd": 1, "note": "61 fixed-price endpoints at $0.001 a successful call" }, { "item": "Tiered raw endpoints (Tieba, Fliggy, coming-soon platforms)", "unit": "1k-requests", "usd": 1.5, "note": "$1 per 1,000 after 5,000,000 billed calls in a calendar month" }, { "item": "Xiaohongshu and WeChat endpoints", "unit": "1k-requests", "usd": 5, "note": "11 fixed-price endpoints at $0.005 a successful call" }, { "item": "Xingtu and Pugongying creator marketplace endpoints", "unit": "1k-requests", "usd": 10, "note": "21 fixed-price endpoints at $0.01 a successful call" }, { "item": "JD.com product reviews", "unit": "1k-requests", "usd": 19.5, "note": "the dearest endpoint; Taobao and Tmall reviews are $13.5" }, { "item": "Apify Store, Xingtu Actor premium section", "unit": "record", "usd": 0.06, "note": "per creator per section, paid through Apify with no Qovia account; basic sections $0.01, video sections $0.03" } ], "provenance": { "legalEntity": "", "domain": "qovia.ai", "domainRegistered": "2026-07-04", "endpointOnVendorDomain": true, "terms": "https://qovia.ai/terms/", "privacy": "https://qovia.ai/privacy/", "statusPage": "", "changelog": "https://qovia.ai/changelog/", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "No legal entity is named anywhere read. The terms and privacy pages are one paragraph each, say Delaware law governs and that the signed agreement governs where it differs, and name no company, address or jurisdiction beyond the state. The footer reads © 2026 QoviaAI, a brand name, not an entity, so legalEntity is left empty.", "RDAP for qovia.ai gives a registration date of 2026-07-04 through GoDaddy with a Domains By Proxy registrant and Cloudflare nameservers. The Wayback Machine's only capture before the check is the home page of 11 September 2026, which advertised sign-up with a free 1,000 calls a month, 25+ platforms, a 99.95 per cent enterprise SLA and a team@ mailbox; none of those claims is on the current site.", "firstReleased is the changelog's first dated entry, 21 October 2026, when the search, Xiaohongshu, WeChat, Taobao and JD endpoints are recorded as live; the remaining platforms are dated 22 October, the registry entry is 22 October and the GitHub account and repository were created on 23 October 2026. The 11 September page sold an API key but dates nothing live.", "https://qovia.ai/.well-known/security.txt, https://qovia.ai/security.txt and https://api.qovia.ai/.well-known/security.txt answer 404. The repository's SECURITY.md gives a Telegram handle and a mailbox for reports and says it covers qovia.ai and api.qovia.ai.", "api.qovia.ai has no robots.txt (404); only its OAuth metadata (404) and /mcp (405 on GET) were touched, both by the 1 November listing check. qovia.ai's robots.txt disallows /console/, /account/, /order/ and /admin/ and their /zh/ twins, which were not fetched." ], "score": 36 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/qovia.json", "live": { "slug": "qovia", "probe": { "target": "https://api.qovia.ai", "method": "get", "lastAt": "2026-11-01T22:08:43.664510387Z", "lastOk": true, "lastStatus": 200, "lastMs": 491, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 521, "p95ms24h": 626, "samples24h": 25, "samples30d": 25, "days": [ { "date": "2026-11-01", "probes": 25, "ok": 25 } ] }, "updatedAt": "2026-11-01T22:08:43.664510387Z" } }, "answer": "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 \u0026 documentation and payments \u0026 pricing.", "b": { "slug": "scrapewise", "name": "Scrapewise", "vendor": "BEBOTECH OÜ", "vendorUrl": "https://scrapewise.ai", "kind": "http-api", "category": "web-scrapers", "summary": "Scrapewise is a hosted scraping service from BEBOTECH OÜ for product and price data. It has ready APIs for Amazon, Walmart and Google, AI scrapers for other sites, price cleaning and product matching, through REST and a remote MCP server.", "url": "https://www.anchorterminal.com/tools/scrapewise", "markdownUrl": "https://www.anchorterminal.com/tools/scrapewise.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/scrapewise.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/scrapewise.json", "dns": "scrapewise.grade.anchorterminal.com", "repo": "https://github.com/BEBOTECH-OU/scrapewise-mcp", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.scrapewise.ai/mcp", "packages": [ { "registry": "pypi", "name": "scrapewise" }, { "registry": "pypi", "name": "langchain-scrapewise" } ], "auth": "api-key", "authNotes": "Bearer API key (`sw_live_\u003cprefix\u003e.\u003csecret\u003e`) minted in the portal under Settings \u003e API Keys after a browser signup. Scopes are fixed at minting. USER keys reach the REST API only, LLM_READ keys read through MCP, LLM_FULL keys also run paid tools and change or delete data. Secrets are stored as hashes, revoked at once, and rotated by minting a new key and revoking the old. No expiry found.", "pricing": "usage", "pricingNotes": "€0.15 per 1,000 plain pages, prepaid from a euro wallet with no plan or subscription. Rendered pages €0.75, residential proxy €1.50, both €3.75 per 1,000. Data APIs €0.15 to €3.75 per 1,000 calls. MCP credits are €0.00015 each. Five free requests, no card. Top-ups €5 to €1,000, not refunded.", "priceSummary": "$0.17 / 1k pages", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, OpenAPI specs, llms.txt or pricing.md (checked 2026-10-15). An empty wallet returns 402 with WALLET_INSUFFICIENT_BALANCE and no payment requirements; top-ups go through Stripe Checkout in a browser.", "endpoints": [] }, "toolCount": 14, "popularity": { "githubStars": 1, "npmWeekly": null, "pypiWeekly": 30, "asOf": "2026-10-15" }, "docsUrl": "https://docs.scrapewise.ai/", "llmsTxt": "https://scrapewise.ai/llms.txt", "openapi": "https://portal.scrapewise.ai/api/scraper-api/v3/api-docs", "registryName": "ai.scrapewise/scrapewise", "capabilities": [ "web.scrape", "web.extract", "scraping.js-render", "scraping.proxies", "web.crawl", "web.fetch", "web.search", "search.serp", "lead.search" ], "tags": [ "hosted", "usage", "prepaid", "no-card", "free-tier", "mcp", "remote-mcp", "mcp-registry", "llms-txt", "openapi", "proxies", "python", "eu" ], "lastRelease": "2026-10-15", "graded": true, "anchor": { "graded": true, "score": 62.6, "grade": "B", "agentReady": false, "rank": 490, "ranked": true, "rankOf": 1253, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 86, "maintenance": 79, "payments": 40, "reliability": 45, "schema": 79, "security": 58, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-15" }, "negative": 0, "verdict": "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.", "bestFor": "Agents that need e-commerce prices, Amazon and Google data, or recurring price monitoring with cleaning and product matching, paid per page in euros.", "strengths": [ "Every paid MCP tool takes `quote_only: true`, which returns the maximum price and wallet balance without spending, and each result reports its cost", "Separate key scopes (USER for REST, LLM_READ and LLM_FULL for MCP), hashed, revocable and listed with last-used time", "Public OpenAPI 3.1 at /v3/api-docs with an MCP subset, plus llms.txt, agents.md and pricing.md", "Prices per 1,000 pages published without login (€0.15 plain to €3.75 rendered with residential proxy), failed pages not charged, 5 free requests with no card", "Verified namespace `ai.scrapewise/scrapewise` in the official MCP registry since 6 October 2026" ], "weaknesses": [ "No status page, SLA, security.txt, disclosure policy or certification found", "Terms of 29 October 2025 say all collected and derived data is owned by Scrapewise, with a perpetual, sublicensable licence", "Signup and every wallet top-up (Stripe Checkout, €5 to €1,000) need a person in a browser, and there is no machine payment protocol", "Docs show two error envelope shapes, a placeholder FAQ, and a scope table that contradicts the tool catalogue on minting keys", "The prompt-injection contract relies on a `type: \"scraped\"` content block that the MCP specification does not define" ], "agentNotes": [ "Call each paid tool with `quote_only: true` first, then repeat with the same `idempotency_key` so a retry is charged once", "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", "Use an LLM_READ key unless the task needs paid tools or writes, since LLM_FULL has no per-tool consent", "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", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.6 } ], "editorialScores": { "ergonomics": 86, "maintenance": 79, "payments": 40, "reliability": 45, "schema": 79, "security": 58, "transparency": 38 }, "provenanceScore": 69, "checked": { "categories": { "ergonomics": "2026-10-15", "maintenance": "2026-10-15", "payments": "2026-10-15", "reliability": "2026-10-15", "schema": "2026-10-15", "security": "2026-10-15", "transparency": "2026-10-15" }, "last": "2026-10-15", "lastMoved": "2026-10-27", "oldest": "2026-10-15", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install scrapewise", "http": "curl -H \"Authorization: Bearer $SCRAPEWISE_KEY\" https://portal.scrapewise.ai/api/scraper-api/api/key/whoami", "claudeCode": "claude mcp add scrapewise --transport http https://mcp.scrapewise.ai/mcp --header 'Authorization: Bearer YOUR_SCRAPEWISE_API_KEY'", "config": { "mcpServers": { "scrapewise": { "headers": { "Authorization": "Bearer YOUR_SCRAPEWISE_API_KEY" }, "url": "https://mcp.scrapewise.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/scrapewise" }, "area": "web-data", "unitPrices": [ { "item": "Plain page", "unit": "1k-pages", "usd": 0.17, "note": "€0.15, converted at the ECB rate of 15 October 2026 (1.1208)" }, { "item": "Rendered page", "unit": "1k-pages", "usd": 0.84, "note": "€0.75" }, { "item": "Residential proxy page", "unit": "1k-pages", "usd": 1.68, "note": "€1.50" }, { "item": "Rendered page with residential proxy", "unit": "1k-pages", "usd": 4.2, "note": "€3.75" }, { "item": "Google search", "unit": "1k-requests", "usd": 1.68, "note": "€1.50" }, { "item": "MCP credit", "unit": "credit", "usd": 0.000168, "note": "€0.00015, the price of one plain page" } ], "provenance": { "legalEntity": "BEBOTECH OÜ", "domain": "scrapewise.ai", "domainRegistered": "2025-05-19", "endpointOnVendorDomain": true, "terms": "https://scrapewise.ai/terms-of-service", "privacy": "https://scrapewise.ai/privacy-policy", "statusPage": "", "changelog": "https://docs.scrapewise.ai/changelog", "securityTxt": "none", "checked": "2026-10-15", "notes": [ "BEBOTECH OÜ is named as author in the PyPI metadata of scrapewise and langchain-scrapewise and in the scrapewise-python licence. The terms and privacy policy name only Scrapewise.ai, under Estonian law.", "Terms of service and privacy policy are both effective 29 October 2025. The terms contain no clause on automated access to the website.", "scrapewise.ai/robots.txt allows all crawlers and names ClaudeBot and anthropic-ai as allowed. docs.scrapewise.ai/robots.txt allows all.", "RDAP gives scrapewise.ai a registration date of 19 May 2025.", "/.well-known/security.txt and /security.txt return 404. No status page found." ], "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/scrapewise.json", "live": { "slug": "scrapewise", "probe": { "target": "https://mcp.scrapewise.ai/mcp", "method": "get", "lastAt": "2026-11-01T22:08:45.93952899Z", "lastOk": true, "lastStatus": 401, "lastMs": 141, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 158, "p95ms24h": 238, "samples24h": 250, "samples30d": 4152, "days": [ { "date": "2026-10-16", "probes": 151, "ok": 151 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 230, "ok": 230 } ] }, "versions": [ { "registry": "mcp-registry", "name": "ai.scrapewise/scrapewise", "version": "0.1.1", "seenAt": "2026-11-01T16:10:44.053973489Z" }, { "registry": "pypi", "name": "langchain-scrapewise", "version": "0.1.0", "released": "2026-10-07", "seenAt": "2026-11-01T17:31:37.602523352Z" }, { "registry": "pypi", "name": "scrapewise", "version": "0.1.0", "released": "2026-10-07", "seenAt": "2026-11-01T17:31:37.412394505Z" } ], "githubStars": 1, "pypiWeekly": 8, "securityTxt": { "url": "https://scrapewise.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:42:41.451591532Z" }, "llmsTxt": { "url": "https://scrapewise.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:14:57.524819596Z" }, "domain": { "domain": "scrapewise.ai", "registered": "2025-05-19", "source": "https://rdap.identitydigital.services/rdap/domain/scrapewise.ai", "checkedAt": "2026-11-01T14:16:04.618199498Z" }, "pages": [ { "url": "https://docs.scrapewise.ai/changelog", "kind": "changelog", "status": 304, "checkedAt": "2026-11-01T06:42:47.282499088Z", "changedAt": "2026-10-24T02:16:26.522434614Z", "fingerprint": "5a9abedeb0cd" }, { "url": "https://scrapewise.ai/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-01T06:52:01.396278052Z", "changedAt": "2026-10-28T04:42:45.131846146Z", "fingerprint": "cc92fcdfe4d5" }, { "url": "https://scrapewise.ai/terms-of-service", "kind": "terms", "status": 304, "checkedAt": "2026-11-01T06:52:03.490271184Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e020071fdbd3" } ], "mcpTools": { "url": "https://mcp.scrapewise.ai/mcp", "checkedAt": "2026-10-08T21:34:41.756892902Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-07T21:27:38.119254487Z" }, "github": { "repo": "bebotech-ou/scrapewise-mcp", "checkedAt": "2026-10-26T07:14:29.517004344Z", "stars": 1, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-13T07:52:25Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 2 }, "updatedAt": "2026-11-01T22:08:45.93952899Z" } }, "edges": [ { "by": 24, "category": "transparency", "leads": "scrapewise", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 30, "b": 54 } }, { "by": 15, "category": "payments", "leads": "qovia", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 55, "b": 40 } }, { "by": 9, "category": "ergonomics", "leads": "scrapewise", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 77, "b": 86 } }, { "by": 7, "category": "schema", "leads": "qovia", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 86, "b": 79 } }, { "by": 5, "category": "reliability", "leads": "scrapewise", "name": "Reliability", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 40, "b": 45 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Qovia", "b": "BEBOTECH OÜ", "name": "Vendor" }, { "a": "https://api.qovia.ai", "b": "https://mcp.scrapewise.ai/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "none", "name": "Licence" }, { "a": "141", "b": "14", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "ai.qovia/qovia", "b": "ai.scrapewise/scrapewise", "name": "MCP registry" }, { "a": "2026-10-28", "b": "2026-10-15", "name": "Last release" }, { "a": "not read yet", "b": "2025-10-29", "name": "Terms last updated" }, { "a": "not read yet", "b": "2025-10-29", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "0 stars", "b": "1 stars, 30 PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "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 \u0026 documentation and payments \u0026 pricing.", "question": "Which is better for AI agents, Qovia or Scrapewise?" }, { "answer": "Both need an API key.", "question": "Do Qovia and Scrapewise need an API key?" }, { "answer": "Yes. Qovia has a hosted endpoint at https://api.qovia.ai and Scrapewise at https://mcp.scrapewise.ai/mcp.", "question": "Can an agent call Qovia and Scrapewise without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 86 against 79", "Payments \u0026 pricing, 55 against 40" ], "also": null, "goodFor": "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.", "slug": "qovia", "watchFor": "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`" }, { "aheadOn": [ "Reliability, 45 against 40", "Agent ergonomics, 86 against 77", "Transparency \u0026 trust, 54 against 30" ], "also": [ "Free to start without a card" ], "goodFor": "Agents that need e-commerce prices, Amazon and Google data, or recurring price monitoring with cleaning and product matching, paid per page in euros.", "slug": "scrapewise", "watchFor": "No status page, SLA, security.txt, disclosure policy or certification found" } ], "history": { "qovia": null, "scrapewise": [ { "causes": [ "evidence" ], "date": "2026-10-27", "delta": 0.1, "from": 62.5, "fromGrade": "B", "to": 62.6, "toGrade": "B" } ] }, "job": { "capability": "web.extract", "name": "Extraction" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bright-data-vs-qovia.json", "title": "Bright Data vs Qovia", "url": "https://www.anchorterminal.com/compare/bright-data-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia.json", "title": "Firecrawl MCP vs Qovia", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapewise.json", "title": "Firecrawl MCP vs Scrapewise", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapewise.json", "title": "Bright Data vs Scrapewise", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-scrapewise.json", "title": "Context.dev vs Scrapewise", "url": "https://www.anchorterminal.com/compare/context-dev-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/jina-reader-vs-scrapewise.json", "title": "Jina Reader vs Scrapewise", "url": "https://www.anchorterminal.com/compare/jina-reader-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/olostep-vs-scrapewise.json", "title": "Olostep vs Scrapewise", "url": "https://www.anchorterminal.com/compare/olostep-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapewise.json", "title": "Oxylabs Web Scraper API vs Scrapewise", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scrape-do-vs-scrapewise.json", "title": "Scrape.do vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scrape-do-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapewise.json", "title": "ScrapeGraphAI vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scrapeless-vs-scrapewise.json", "title": "Scrapeless vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scrapeless-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapewise.json", "title": "ScraperAPI vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapfly.json", "title": "Scrapewise vs Scrapfly", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingant.json", "title": "Scrapewise vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingbee.json", "title": "Scrapewise vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingdog.json", "title": "Scrapewise vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-spider-cloud.json", "title": "Scrapewise vs Spider", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-zenrows.json", "title": "Scrapewise vs ZenRows", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-zyte.json", "title": "Scrapewise vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-qovia.json", "title": "Context.dev vs Qovia", "url": "https://www.anchorterminal.com/compare/context-dev-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/diffbot-vs-qovia.json", "title": "Diffbot vs Qovia", "url": "https://www.anchorterminal.com/compare/diffbot-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/diffbot-vs-scrapewise.json", "title": "Diffbot vs Scrapewise", "url": "https://www.anchorterminal.com/compare/diffbot-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.json", "title": "jevcrawl vs Qovia", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/olostep-vs-qovia.json", "title": "Olostep vs Qovia", "url": "https://www.anchorterminal.com/compare/olostep-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.json", "title": "Oxylabs Web Scraper API vs Qovia", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.json", "title": "Qovia vs ScrapeAtlas", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.json", "title": "Qovia vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi.json", "title": "Qovia vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapfly.json", "title": "Qovia vs Scrapfly", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant.json", "title": "Qovia vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.json", "title": "Qovia vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.json", "title": "Qovia vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.json", "title": "Qovia vs Spider", "url": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-zenrows.json", "title": "Qovia vs ZenRows", "url": "https://www.anchorterminal.com/compare/qovia-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-zyte.json", "title": "Qovia vs Zyte API", "url": "https://www.anchorterminal.com/compare/qovia-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapewise.json", "title": "ScrapeAtlas vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapewise.json", "title": "Apify MCP Server vs Scrapewise", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapewise.json", "title": "jevcrawl vs Scrapewise", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapewise" } ], "panel": null, "scores": [ { "by": 5, "edge": "scrapewise", "key": "reliability", "name": "Reliability", "qovia": 40, "scrapewise": 45, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 7, "edge": "qovia", "key": "schema", "name": "Schema \u0026 documentation", "qovia": 86, "scrapewise": 79, "weight": 13 }, { "by": 9, "edge": "scrapewise", "key": "ergonomics", "name": "Agent ergonomics", "qovia": 77, "scrapewise": 86, "weight": 13 }, { "by": 2, "edge": "qovia", "key": "security", "name": "Security \u0026 auth", "qovia": 60, "scrapewise": 58, "weight": 14 }, { "by": 15, "edge": "qovia", "key": "payments", "name": "Payments \u0026 pricing", "qovia": 55, "scrapewise": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 2, "edge": "scrapewise", "key": "maintenance", "name": "Maintenance \u0026 community", "qovia": 77, "scrapewise": 79, "weight": 7 }, { "by": 24, "edge": "scrapewise", "key": "transparency", "name": "Transparency \u0026 trust", "qovia": 30, "scrapewise": 54, "weight": 7 } ], "summary": "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 \u0026 documentation and payments \u0026 pricing. Both do extraction.", "tasks": null, "tutorials": [], "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise", "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise.min.md" }, "markdown": "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 \u0026 documentation and payments \u0026 pricing. Both do extraction.\n\n- 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\n- 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\n- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md\n- All 261 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md\n\n## Which one, for what\n\n### Qovia (C)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 86 against 79\n- Payments \u0026 pricing, 55 against 40\n\nWatch 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`\n\n### Scrapewise (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 45 against 40\n- Agent ergonomics, 86 against 77\n- Transparency \u0026 trust, 54 against 30\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No status page, SLA, security.txt, disclosure policy or certification found\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Scrapewise +24\n\n- 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.\n- 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).\n\n### Payments \u0026 pricing: Qovia +15\n\n- 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.\n- 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).\n\n### Agent ergonomics: Scrapewise +9\n\n- 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.\n- 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).\n\n### Schema \u0026 documentation: Qovia +7\n\n- 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.\n- 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).\n\n### Reliability: Scrapewise +5\n\n- 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.\n- 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).\n\n## Score by category\n\n| Category | Weight | Qovia | Scrapewise | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 45 | Scrapewise +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 79 | Qovia +7 |\n| Agent ergonomics | 13% (16.2 this run) | 77 | 86 | Scrapewise +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 58 | Qovia +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 55 | 40 | Qovia +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 77 | 79 | Scrapewise +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 30 | 54 | Scrapewise +24 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.2 · C** | **62.6 · B** | |\n\n## Facts side by side\n\n| Fact | Qovia | Scrapewise |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Qovia | BEBOTECH OÜ |\n| Hosted endpoint | `https://api.qovia.ai` | `https://mcp.scrapewise.ai/mcp` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| 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 |\n| Tools exposed | 141 | 14 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `ai.qovia/qovia` | `ai.scrapewise/scrapewise` |\n| Last release | 2026-10-28 | 2026-10-15 |\n| Terms last updated | not read yet | 2025-10-29 |\n| Privacy policy last updated | not read yet | 2025-10-29 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | 0 stars | 1 stars, 30 PyPI/wk |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### Qovia\n\nNo score change since it was listed.\n\n### Scrapewise\n\n- +0.1 on 27 October 2026: new evidence\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Qovia\n\n1. 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.\n2. 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.\n3. 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`.\n4. 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.\n5. 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.\n\n### Scrapewise\n\n1. Call each paid tool with `quote_only: true` first, then repeat with the same `idempotency_key` so a retry is charged once\n2. 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\n3. Use an LLM_READ key unless the task needs paid tools or writes, since LLM_FULL has no per-tool consent\n4. 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\n5. 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\n\n## Questions\n\n### Which is better for AI agents, Qovia or Scrapewise?\n\nScrapewise 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 \u0026 documentation and payments \u0026 pricing.\n\n### Do Qovia and Scrapewise need an API key?\n\nBoth need an API key.\n\n### Can an agent call Qovia and Scrapewise without installing anything?\n\nYes. Qovia has a hosted endpoint at https://api.qovia.ai and Scrapewise at https://mcp.scrapewise.ai/mcp.\n\n\n## For agents\n\n- 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\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"qovia\", \"b\": \"scrapewise\"}`. From a terminal: `anchor compare qovia scrapewise`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/qovia.json and https://www.anchorterminal.com/api/v1/tools/scrapewise.json\n\n## Other comparisons with Qovia or Scrapewise\n\n- [Bright Data vs Qovia](https://www.anchorterminal.com/compare/bright-data-vs-qovia.md)\n- [Firecrawl MCP vs Qovia](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia.md)\n- [Firecrawl MCP vs Scrapewise](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapewise.md)\n- [Bright Data vs Scrapewise](https://www.anchorterminal.com/compare/bright-data-vs-scrapewise.md)\n- [Context.dev vs Scrapewise](https://www.anchorterminal.com/compare/context-dev-vs-scrapewise.md)\n- [Jina Reader vs Scrapewise](https://www.anchorterminal.com/compare/jina-reader-vs-scrapewise.md)\n- [Olostep vs Scrapewise](https://www.anchorterminal.com/compare/olostep-vs-scrapewise.md)\n- [Oxylabs Web Scraper API vs Scrapewise](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapewise.md)\n- [Scrape.do vs Scrapewise](https://www.anchorterminal.com/compare/scrape-do-vs-scrapewise.md)\n- [ScrapeGraphAI vs Scrapewise](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapewise.md)\n- [Scrapeless vs Scrapewise](https://www.anchorterminal.com/compare/scrapeless-vs-scrapewise.md)\n- [ScraperAPI vs Scrapewise](https://www.anchorterminal.com/compare/scraperapi-vs-scrapewise.md)\n- [Scrapewise vs Scrapfly](https://www.anchorterminal.com/compare/scrapewise-vs-scrapfly.md)\n- [Scrapewise vs ScrapingAnt](https://www.anchorterminal.com/compare/scrapewise-vs-scrapingant.md)\n- [Scrapewise vs ScrapingBee](https://www.anchorterminal.com/compare/scrapewise-vs-scrapingbee.md)\n- [Scrapewise vs Scrapingdog](https://www.anchorterminal.com/compare/scrapewise-vs-scrapingdog.md)\n- [Scrapewise vs Spider](https://www.anchorterminal.com/compare/scrapewise-vs-spider-cloud.md)\n- [Scrapewise vs ZenRows](https://www.anchorterminal.com/compare/scrapewise-vs-zenrows.md)\n- [Scrapewise vs Zyte API](https://www.anchorterminal.com/compare/scrapewise-vs-zyte.md)\n- [Context.dev vs Qovia](https://www.anchorterminal.com/compare/context-dev-vs-qovia.md)\n- [Diffbot vs Qovia](https://www.anchorterminal.com/compare/diffbot-vs-qovia.md)\n- [Diffbot vs Scrapewise](https://www.anchorterminal.com/compare/diffbot-vs-scrapewise.md)\n- [jevcrawl vs Qovia](https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.md)\n- [Olostep vs Qovia](https://www.anchorterminal.com/compare/olostep-vs-qovia.md)\n- [Oxylabs Web Scraper API vs Qovia](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.md)\n- [Qovia vs ScrapeAtlas](https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.md)\n- [Qovia vs ScrapeGraphAI](https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.md)\n- [Qovia vs ScraperAPI](https://www.anchorterminal.com/compare/qovia-vs-scraperapi.md)\n- [Qovia vs Scrapfly](https://www.anchorterminal.com/compare/qovia-vs-scrapfly.md)\n- [Qovia vs ScrapingAnt](https://www.anchorterminal.com/compare/qovia-vs-scrapingant.md)\n- [Qovia vs ScrapingBee](https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.md)\n- [Qovia vs Scrapingdog](https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.md)\n- [Qovia vs Spider](https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.md)\n- [Qovia vs ZenRows](https://www.anchorterminal.com/compare/qovia-vs-zenrows.md)\n- [Qovia vs Zyte API](https://www.anchorterminal.com/compare/qovia-vs-zyte.md)\n- [ScrapeAtlas vs Scrapewise](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapewise.md)\n- [Apify MCP Server vs Scrapewise](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapewise.md)\n- [jevcrawl vs Scrapewise](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapewise.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-01", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Qovia vs Scrapewise", "url": "" } ], "description": "Scrapewise scores 62.6 (B) to Qovia's 61.2 (C) for extraction. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Qovia C 61.2", "Scrapewise B 62.6", "scores" ], "h1": "Qovia vs Scrapewise", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/qovia-vs-scrapewise", "published": "2026-10-01", "section": "tools", "title": "Qovia vs Scrapewise for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise" }, "tokens": { "markdown": 5650, "slim": 3430 }, "version": 1 }