{ "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": "Qovia scores 61.2 (C) on agent readiness against Scrapingdog's 39.3 (E), and leads in 5 of 7 scored categories. Scrapingdog leads on reliability and transparency \u0026 trust.", "b": { "slug": "scrapingdog", "name": "Scrapingdog", "vendor": "Scrapingdog (OpenData Labs)", "vendorUrl": "https://www.scrapingdog.com", "kind": "http-api", "category": "web-scrapers", "summary": "Web scraping API billed by credits.", "url": "https://www.anchorterminal.com/tools/scrapingdog", "markdownUrl": "https://www.anchorterminal.com/tools/scrapingdog.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/scrapingdog.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/scrapingdog.json", "dns": "scrapingdog.grade.anchorterminal.com", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.scrapingdog.com/scrape", "packages": [ { "registry": "npm", "name": "scrapingdog-mcp" }, { "registry": "npm", "name": "scrapingdog-sdk" }, { "registry": "pypi", "name": "scrapingdog" } ], "auth": "api-key", "authNotes": "The key goes in the api_key query parameter on every request. The docs show no header option. The MCP server reads SCRAPINGDOG_API_KEY from the environment.", "pricing": "freemium", "pricingNotes": "Free plan of 100 credits with 1 concurrent request, no card (the docs say 200 requests a month). Lite $40 a month (200,000 credits, 5 concurrent), Standard $90 (1M, 50), Pro $200 (3M, 100), Premium $350 (6M, 150), then plans up to $30,000 a month. Annual billing gives 2 months free. A plain request costs 1 credit, JS rendering 5, premium proxy or geotargeting 10, both 25, Google SERP 5 to 10, LinkedIn profiles 10 to 100. Failed requests aren't charged (https://www.scrapingdog.com/pricing/).", "priceSummary": "$40 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402 mention on the site, docs or pricing (checked 2026-09-30).", "endpoints": [] }, "toolCount": 35, "popularity": { "githubStars": 0, "npmWeekly": 41, "pypiWeekly": 12, "asOf": "2026-09-30" }, "docsUrl": "https://www.scrapingdog.com/documentation/", "llmsTxt": "https://www.scrapingdog.com/llms.txt", "registryName": "io.github.Darshan972/scrapingdog-mcp", "capabilities": [ "web.scrape", "web.extract", "web.search", "scraping.proxies", "scraping.js-render", "scraping.anti-bot", "scraping.screenshot", "scraping.serp" ], "tags": [ "hosted", "freemium", "no-card", "mcp", "llms-txt", "proxies", "closed-source", "python", "typescript" ], "lastRelease": "2026-07-31", "graded": true, "anchor": { "graded": true, "score": 39.3, "grade": "E", "agentReady": false, "rank": 1135, "ranked": true, "rankOf": 1253, "categoryRank": 22, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 44, "maintenance": 45, "payments": 40, "reliability": 62, "schema": 43, "security": 5, "transparency": 56 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": -2, "negativeNotes": [ "2026-08-01: the vendor-linked MCP server's web_scrape tool describes dynamic as `(API default: false)`, while https://www.scrapingdog.com/documentation/javascript-rendering/ says rendering is on by default at 5 credits. The MCP omits unset parameters, so a model that trusts the description pays 5 times the plain rate (https://github.com/Darshan972/Scrapingdog-mcp, src/endpoints.ts) (-2)." ], "verdict": "A plain request is 1 credit, about $0.20 per 1,000 on Lite. API key only travels in the URL query string.", "bestFor": "A budget agent that wants parsed Google, Amazon or LinkedIn results and can keep the key out of logs.", "strengths": [ "A plain request is 1 credit, about $0.20 per 1,000 on Lite", "Parsed JSON endpoints for Google, Amazon, LinkedIn, YouTube and more under one key", "Terms let you store and redistribute returned data during the subscription, and the privacy policy says API calls aren't stored or logged", "Failed requests aren't charged, and a public SLA page compensates downtime in credits", "Concurrency per plan is published, from 1 up to 2,200" ], "weaknesses": [ "API key only travels in the URL query string", "Rendering defaults on at 5 credits, and the MCP's web_scrape description says the default is off", "MCP server published 2026-08-01 from a personal account, with 35 tools, no CI, no tags and no release since", "No changelog, security.txt or prompt-injection guidance", "The free allowance differs between pricing (100 credits) and docs (200 a month)" ], "agentNotes": [ "Add dynamic=false unless the page needs JavaScript. It cuts the cost from 5 credits to 1, whatever the MCP description says", "Keep request URLs out of logs, since they carry api_key", "Set client timeouts above 60 seconds and retry on 429 or timeout. Failures aren't billed", "Prefer the parsed endpoints (Google, Amazon) over scraping the raw page when one exists" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 39.3 } ], "editorialScores": { "ergonomics": 44, "maintenance": 45, "payments": 40, "reliability": 62, "schema": 43, "security": 5, "transparency": 37 }, "provenanceScore": 75, "checked": { "categories": { "ergonomics": "2026-10-01", "maintenance": "2026-10-01", "payments": "2026-10-01", "reliability": "2026-10-01", "schema": "2026-10-01", "security": "2026-10-01", "transparency": "2026-10-01" }, "last": "2026-10-01", "lastMoved": "2026-10-27", "oldest": "2026-10-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.scrapingdog.com/scrape?api_key=$SCRAPINGDOG_API_KEY\u0026url=https://example.com\u0026dynamic=false\"", "claudeCode": "claude mcp add scrapingdog -e SCRAPINGDOG_API_KEY=$SCRAPINGDOG_API_KEY -- npx -y scrapingdog-mcp", "config": { "mcpServers": { "scrapingdog": { "args": [ "-y", "scrapingdog-mcp" ], "command": "npx", "env": { "SCRAPINGDOG_API_KEY": "${SCRAPINGDOG_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/scrapingdog" }, "area": "web-data", "unitPrices": [ { "item": "Lite plan", "unit": "month", "usd": 40, "note": "200,000 credits, 5 concurrent" }, { "item": "Standard plan", "unit": "month", "usd": 90, "note": "1,000,000 credits, 50 concurrent" }, { "item": "Pro plan", "unit": "month", "usd": 200, "note": "3,000,000 credits, 100 concurrent" }, { "item": "Plain request on Lite", "unit": "1k-requests", "usd": 0.2, "note": "1 credit each, dynamic=false" }, { "item": "JS-rendered request on Lite", "unit": "1k-requests", "usd": 1, "note": "5 credits each, the default" } ], "provenance": { "legalEntity": "OpenData Labs Private Limited", "domain": "scrapingdog.com", "domainRegistered": "2020-04-04", "endpointOnVendorDomain": true, "terms": "https://www.scrapingdog.com/terms/", "privacy": "https://www.scrapingdog.com/privacy/", "statusPage": "https://stats.uptimerobot.com/SAQkQwbOYj", "changelog": "", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Legal entity from the site footer. The terms are governed by the laws of Rajasthan, India.", "The status page is a hosted UptimeRobot page linked from the footer." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/scrapingdog.json", "live": { "slug": "scrapingdog", "probe": { "target": "https://api.scrapingdog.com/scrape", "method": "get", "lastAt": "2026-11-01T22:08:46.025712342Z", "lastOk": true, "lastStatus": 400, "lastMs": 134, "authRequired": false, "uptime24h": 100, "uptime30d": 99.94, "p50ms24h": 141, "p95ms24h": 283, "samples24h": 250, "samples30d": 8145, "days": [ { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 271 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 247 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 251 }, { "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": 250 }, { "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 } ] }, "vendorStatus": { "page": "https://stats.uptimerobot.com/SAQkQwbOYj", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-01T22:10:03.217045371Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.github.Darshan972/scrapingdog-mcp", "version": "0.1.1", "seenAt": "2026-11-01T16:10:44.053973489Z" }, { "registry": "npm", "name": "scrapingdog-mcp", "version": "0.1.1", "seenAt": "2026-11-01T17:31:50.613082294Z" }, { "registry": "npm", "name": "scrapingdog-sdk", "version": "1.0.1", "seenAt": "2026-11-01T17:31:51.71317717Z" }, { "registry": "pypi", "name": "scrapingdog", "version": "1.1.0", "released": "2026-07-31", "seenAt": "2026-11-01T17:31:53.0829523Z" } ], "npmWeekly": 36, "pypiWeekly": 17, "securityTxt": { "url": "https://scrapingdog.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:43:24.210099938Z" }, "llmsTxt": { "url": "https://www.scrapingdog.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:14:57.789945152Z" }, "domain": { "domain": "scrapingdog.com", "registered": "2020-04-04", "source": "https://rdap.verisign.com/com/v1/domain/scrapingdog.com", "checkedAt": "2026-11-01T14:22:25.336057403Z" }, "pages": [ { "url": "https://www.scrapingdog.com/terms/", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-01T07:04:16.014273306Z", "changedAt": "2026-11-01T07:04:16.014273306Z", "fingerprint": "ef5bfb177fa9" }, { "url": "https://www.scrapingdog.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-01T07:04:11.822647537Z", "changedAt": "2026-11-01T07:04:11.822647537Z", "fingerprint": "755b86993220" }, { "url": "https://www.scrapingdog.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-01T07:04:14.231298905Z", "changedAt": "2026-11-01T07:04:14.231298905Z", "fingerprint": "b1c75e68dee7" } ], "updatedAt": "2026-11-01T22:10:03.217045371Z" } }, "edges": [ { "by": 55, "category": "security", "leads": "qovia", "name": "Security \u0026 auth", "reasons": { "a": "API keys with scopes chosen at creation (every endpoint, search, every raw endpoint or one of 24 platform groups), an optional expiry, revocation in the console and hashed storage; the docs say the key is read from the Authorization or x-api-key header only, never the URL or a cookie, and 30 failed authentications from one IP in a minute are throttled. No OAuth and no rotation feature beyond creating another key (24 of 30). The whole surface is read-only retrieval, scopes restrict a key to platforms, the two MCP catalogue tools need no key, and the docs and SECURITY.md tell users to give AI tools a separate scoped key (17 of 20). Every response is third-party platform text, and the only related statement is that error messages never contain the data source's own text; nothing on treating returned content as untrusted (3 of 15). request_id is the usage record ID on every answer, the console lists every charge in a usage log, X-Qovia-Charged and X-Qovia-Balance headers report each call, and GET /v1/account returns the key's scopes and balance at no charge; no exportable audit log or per-call endpoint was found (11 of 15). No security.txt on qovia.ai or api.qovia.ai (404), no bug bounty, SOC 2 or ISO 27001; the repository's SECURITY.md names a Telegram handle and a mailbox for reports covering both hosts (5 of 20). 24+17+3+11+5 = 60.", "b": "One account key with no scopes, and we found no rotation or revocation docs (10). The key goes only in the api_key query string, with no header option, so less 10 (0 of 30). No read-only mode or least-privilege key. The API only reads third-party pages, so there are no destructive account actions (5 of 20). No prompt-injection guidance in the docs or the MCP README (0 of 15). No request log or per-call audit found (0 of 15). No security.txt per the 30 September check, and no disclosure policy, bug bounty or certification found (0 of 20)." }, "scores": { "a": 60, "b": 5 } }, { "by": 43, "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": "No OpenAPI spec found. The MCP builds typed zod inputs for 35 tools from a declarative registry, and ai_extract_rules is a JSON string (12 of 25). llms.txt per the 30 September check (10). MCP descriptions say what each endpoint does but not when to avoid it, and the web_scrape tool tells the model the API default for dynamic is false while the docs say rendering is on by default (10 of 20). Booleans, numbers and strings with few enums, plus the JSON-string field (9 of 15). Code examples on each docs page and 8 documented status codes (12 of 15). No changelog and no versioned API paths found (0)." }, "scores": { "a": 86, "b": 43 } }, { "by": 33, "category": "ergonomics", "leads": "qovia", "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": "35 MCP tools with no toolsets or subsets (5 of 25). markdown=true, ai_query and parsed JSON endpoints for Google, Amazon and LinkedIn keep responses smaller. No documented pagination or size limits on the raw scrape (12 of 20). 8 HTTP status codes with meanings, and the MCP passes the status and body back (12 of 20). Failed requests aren't billed, but no tool annotations or idempotency guidance (5 of 20). Only url is required, but rendering defaults on at 5 credits and the MCP describes it as off. Node and Python SDKs (10 of 15)." }, "scores": { "a": 77, "b": 44 } }, { "by": 32, "category": "maintenance", "leads": "qovia", "name": "Maintenance \u0026 community", "reasons": { "a": "The newest changes are the registry entry ai.qovia/qovia 0.1.1 and the repository's tools snapshot and plugin manifests on 28 October 2026, after the Python client 0.1.1 on PyPI on 27 October; the repository was pushed on 1 November (30). Eight changelog entries on 21 and 22 October, two registry versions (22 and 28 October) and two PyPI releases (25 and 27 October) are more than three dated entries in 90 days, all within ten days (20). Closed service with a public changelog. Support is Telegram, WhatsApp, WeChat and one mailbox, with a one-business-day reply promised for email; GitHub issues are enabled on the repository with none opened, and no forum, Discord or community was found (7 of 15). ai.qovia/qovia is in the official MCP registry under a DNS-verified reverse-DNS namespace at 0.1.1, marked latest, and the Python client is an official package on PyPI (15). The client is standard-library Python with a test file, MIT, no dependencies and no CI workflow in the repository tree; the account's other nine repositories are forks of lists and directories (5 of 10). 30+20+7+15+5 = 77.", "b": "The SDKs and MCP server were first published on 31 July and 1 August 2026, 61 days ago. No API changelog or later release found (20). Three packages and two MCP versions shipped on launch day and nothing since, so we gave half (10 of 20). We couldn't read GitHub issues. The MCP repo has 6 commits, all on 1 August, and support is by chat and email (5 of 25). The MCP is in the official registry under the personal namespace io.github.Darshan972, though the vendor's SDK page links it as its own. SDKs are current (8 of 15). No CI, tests or tags in the MCP repo (2 of 10)." }, "scores": { "a": 77, "b": 45 } }, { "by": 26, "category": "transparency", "leads": "scrapingdog", "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 revised 13 January 2026, naming OpenData Labs Private Limited under the laws of Rajasthan, India, with no postal address. The MCP is MIT (15 of 30). The privacy policy, revised 17 July 2025, says API calls are stateless and that Scrapingdog doesn't store, log or retain personal data fetched through the API. A DPA is published. No retention periods for account data (22 of 30). No deprecation policy or dated notices found (0). No processors or data locations named (0 of 20)." }, "scores": { "a": 30, "b": 56 } }, { "by": 22, "category": "reliability", "leads": "scrapingdog", "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": "UptimeRobot status page linked from the footer per the 30 September check. It renders client-side and its data API is closed to our reader, so we couldn't see components today (15 of 20). No readable incident history (5). Concurrency per plan is published, 1 on Free up to 2,200 on the top plan (15). Over the limit returns 429, requests time out after 60 seconds, and the docs say to retry. Failures aren't billed. No Retry-After found (10 of 15). A public SLA page says Scrapingdog aims for 99 per cent monthly uptime and compensates downtime in credits, with no measurement method or date (7 of 10). Generally available (10)." }, "scores": { "a": 40, "b": 62 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Qovia", "b": "Scrapingdog (OpenData Labs)", "name": "Vendor" }, { "a": "https://api.qovia.ai", "b": "https://api.scrapingdog.com/scrape", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "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": "35", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "ai.qovia/qovia", "b": "io.github.Darshan972/scrapingdog-mcp", "name": "MCP registry" }, { "a": "2026-10-28", "b": "2026-07-31", "name": "Last release" }, { "a": "not read yet", "b": "2026-01-13", "name": "Terms last updated" }, { "a": "not read yet", "b": "2025-07-17", "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": "yes", "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": "0 stars, 41 npm/wk, 12 PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Qovia scores 61.2 (C) on agent readiness against Scrapingdog's 39.3 (E), and leads in 5 of 7 scored categories. Scrapingdog leads on reliability and transparency \u0026 trust.", "question": "Which is better for AI agents, Qovia or Scrapingdog?" }, { "answer": "Both need an API key.", "question": "Do Qovia and Scrapingdog need an API key?" }, { "answer": "Yes. Qovia has a hosted endpoint at https://api.qovia.ai and Scrapingdog at https://api.scrapingdog.com/scrape.", "question": "Can an agent call Qovia and Scrapingdog without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 86 against 43", "Agent ergonomics, 77 against 44", "Security \u0026 auth, 60 against 5", "Payments \u0026 pricing, 55 against 40", "Maintenance \u0026 community, 77 against 45" ], "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, 62 against 40", "Transparency \u0026 trust, 56 against 30" ], "also": [ "Runs on your own machine", "Free to start without a card" ], "goodFor": "A budget agent that wants parsed Google, Amazon or LinkedIn results and can keep the key out of logs.", "slug": "scrapingdog", "watchFor": "API key only travels in the URL query string" } ], "history": { "qovia": null, "scrapingdog": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 39.2, "fromGrade": "E", "to": 39.3, "toGrade": "E" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.1, "from": 39.3, "fromGrade": "E", "to": 39.2, "toGrade": "E" } ] }, "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-scrapingdog.json", "title": "Firecrawl MCP vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingdog.json", "title": "Apify MCP Server vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapingdog.json", "title": "Bright Data vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-scrapingdog.json", "title": "Context.dev vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/context-dev-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingdog.json", "title": "jevcrawl vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/jina-reader-vs-scrapingdog.json", "title": "Jina Reader vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/jina-reader-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/olostep-vs-scrapingdog.json", "title": "Olostep vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/olostep-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingdog.json", "title": "Oxylabs Web Scraper API vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/scrape-do-vs-scrapingdog.json", "title": "Scrape.do vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scrape-do-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingdog.json", "title": "ScrapeGraphAI vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/scrapeless-vs-scrapingdog.json", "title": "Scrapeless vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scrapeless-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapingdog.json", "title": "ScraperAPI vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapingdog" }, { "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/scrapfly-vs-scrapingdog.json", "title": "Scrapfly vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scrapfly-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/scrapingant-vs-scrapingdog.json", "title": "ScrapingAnt vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scrapingant-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/scrapingbee-vs-scrapingdog.json", "title": "ScrapingBee vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scrapingbee-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/scrapingdog-vs-spider-cloud.json", "title": "Scrapingdog vs Spider", "url": "https://www.anchorterminal.com/compare/scrapingdog-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scrapingdog-vs-zenrows.json", "title": "Scrapingdog vs ZenRows", "url": "https://www.anchorterminal.com/compare/scrapingdog-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/scrapingdog-vs-zyte.json", "title": "Scrapingdog vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapingdog-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-scrapingdog.json", "title": "Diffbot vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/diffbot-vs-scrapingdog" }, { "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-scrapewise.json", "title": "Qovia vs Scrapewise", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise" }, { "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-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-scrapingdog.json", "title": "ScrapeAtlas vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingdog" } ], "panel": null, "scores": [ { "by": 22, "edge": "scrapingdog", "key": "reliability", "name": "Reliability", "qovia": 40, "scrapingdog": 62, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 43, "edge": "qovia", "key": "schema", "name": "Schema \u0026 documentation", "qovia": 86, "scrapingdog": 43, "weight": 13 }, { "by": 33, "edge": "qovia", "key": "ergonomics", "name": "Agent ergonomics", "qovia": 77, "scrapingdog": 44, "weight": 13 }, { "by": 55, "edge": "qovia", "key": "security", "name": "Security \u0026 auth", "qovia": 60, "scrapingdog": 5, "weight": 14 }, { "by": 15, "edge": "qovia", "key": "payments", "name": "Payments \u0026 pricing", "qovia": 55, "scrapingdog": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 32, "edge": "qovia", "key": "maintenance", "name": "Maintenance \u0026 community", "qovia": 77, "scrapingdog": 45, "weight": 7 }, { "by": 26, "edge": "scrapingdog", "key": "transparency", "name": "Transparency \u0026 trust", "qovia": 30, "scrapingdog": 56, "weight": 7 } ], "summary": "Qovia scores 61.2 (C) on agent readiness against Scrapingdog's 39.3 (E), and leads in 5 of 7 scored categories. Scrapingdog leads on reliability and transparency \u0026 trust. 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.", "scrapingdog": "A plain request is 1 credit, about $0.20 per 1,000 on Lite. API key only travels in the URL query string." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog", "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.min.md" }, "markdown": "Qovia scores 61.2 (C) on agent readiness against Scrapingdog's 39.3 (E), and leads in 5 of 7 scored categories. Scrapingdog leads on reliability and transparency \u0026 trust. 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- Scrapingdog: grade E, 39.3/100, rank #1135 of 1253. Markdown https://www.anchorterminal.com/tools/scrapingdog.md · JSON https://www.anchorterminal.com/api/v1/tools/scrapingdog.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 43\n- Agent ergonomics, 77 against 44\n- Security \u0026 auth, 60 against 5\n- Payments \u0026 pricing, 55 against 40\n- Maintenance \u0026 community, 77 against 45\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### Scrapingdog (E)\n\nGood for: A budget agent that wants parsed Google, Amazon or LinkedIn results and can keep the key out of logs.\n\nAhead on:\n- Reliability, 62 against 40\n- Transparency \u0026 trust, 56 against 30\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: API key only travels in the URL query string\n\n\n## Why the edge\n\n### Security \u0026 auth: Qovia +55\n\n- Qovia (60): API keys with scopes chosen at creation (every endpoint, search, every raw endpoint or one of 24 platform groups), an optional expiry, revocation in the console and hashed storage; the docs say the key is read from the Authorization or x-api-key header only, never the URL or a cookie, and 30 failed authentications from one IP in a minute are throttled. No OAuth and no rotation feature beyond creating another key (24 of 30). The whole surface is read-only retrieval, scopes restrict a key to platforms, the two MCP catalogue tools need no key, and the docs and SECURITY.md tell users to give AI tools a separate scoped key (17 of 20). Every response is third-party platform text, and the only related statement is that error messages never contain the data source's own text; nothing on treating returned content as untrusted (3 of 15). request_id is the usage record ID on every answer, the console lists every charge in a usage log, X-Qovia-Charged and X-Qovia-Balance headers report each call, and GET /v1/account returns the key's scopes and balance at no charge; no exportable audit log or per-call endpoint was found (11 of 15). No security.txt on qovia.ai or api.qovia.ai (404), no bug bounty, SOC 2 or ISO 27001; the repository's SECURITY.md names a Telegram handle and a mailbox for reports covering both hosts (5 of 20). 24+17+3+11+5 = 60.\n- Scrapingdog (5): One account key with no scopes, and we found no rotation or revocation docs (10). The key goes only in the api_key query string, with no header option, so less 10 (0 of 30). No read-only mode or least-privilege key. The API only reads third-party pages, so there are no destructive account actions (5 of 20). No prompt-injection guidance in the docs or the MCP README (0 of 15). No request log or per-call audit found (0 of 15). No security.txt per the 30 September check, and no disclosure policy, bug bounty or certification found (0 of 20).\n\n### Schema \u0026 documentation: Qovia +43\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- Scrapingdog (43): No OpenAPI spec found. The MCP builds typed zod inputs for 35 tools from a declarative registry, and ai_extract_rules is a JSON string (12 of 25). llms.txt per the 30 September check (10). MCP descriptions say what each endpoint does but not when to avoid it, and the web_scrape tool tells the model the API default for dynamic is false while the docs say rendering is on by default (10 of 20). Booleans, numbers and strings with few enums, plus the JSON-string field (9 of 15). Code examples on each docs page and 8 documented status codes (12 of 15). No changelog and no versioned API paths found (0).\n\n### Agent ergonomics: Qovia +33\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- Scrapingdog (44): 35 MCP tools with no toolsets or subsets (5 of 25). markdown=true, ai_query and parsed JSON endpoints for Google, Amazon and LinkedIn keep responses smaller. No documented pagination or size limits on the raw scrape (12 of 20). 8 HTTP status codes with meanings, and the MCP passes the status and body back (12 of 20). Failed requests aren't billed, but no tool annotations or idempotency guidance (5 of 20). Only url is required, but rendering defaults on at 5 credits and the MCP describes it as off. Node and Python SDKs (10 of 15).\n\n### Maintenance \u0026 community: Qovia +32\n\n- Qovia (77): The newest changes are the registry entry ai.qovia/qovia 0.1.1 and the repository's tools snapshot and plugin manifests on 28 October 2026, after the Python client 0.1.1 on PyPI on 27 October; the repository was pushed on 1 November (30). Eight changelog entries on 21 and 22 October, two registry versions (22 and 28 October) and two PyPI releases (25 and 27 October) are more than three dated entries in 90 days, all within ten days (20). Closed service with a public changelog. Support is Telegram, WhatsApp, WeChat and one mailbox, with a one-business-day reply promised for email; GitHub issues are enabled on the repository with none opened, and no forum, Discord or community was found (7 of 15). ai.qovia/qovia is in the official MCP registry under a DNS-verified reverse-DNS namespace at 0.1.1, marked latest, and the Python client is an official package on PyPI (15). The client is standard-library Python with a test file, MIT, no dependencies and no CI workflow in the repository tree; the account's other nine repositories are forks of lists and directories (5 of 10). 30+20+7+15+5 = 77.\n- Scrapingdog (45): The SDKs and MCP server were first published on 31 July and 1 August 2026, 61 days ago. No API changelog or later release found (20). Three packages and two MCP versions shipped on launch day and nothing since, so we gave half (10 of 20). We couldn't read GitHub issues. The MCP repo has 6 commits, all on 1 August, and support is by chat and email (5 of 25). The MCP is in the official registry under the personal namespace io.github.Darshan972, though the vendor's SDK page links it as its own. SDKs are current (8 of 15). No CI, tests or tags in the MCP repo (2 of 10).\n\n### Transparency \u0026 trust: Scrapingdog +26\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- Scrapingdog (56): Closed service with terms revised 13 January 2026, naming OpenData Labs Private Limited under the laws of Rajasthan, India, with no postal address. The MCP is MIT (15 of 30). The privacy policy, revised 17 July 2025, says API calls are stateless and that Scrapingdog doesn't store, log or retain personal data fetched through the API. A DPA is published. No retention periods for account data (22 of 30). No deprecation policy or dated notices found (0). No processors or data locations named (0 of 20).\n\n### Reliability: Scrapingdog +22\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- Scrapingdog (62): UptimeRobot status page linked from the footer per the 30 September check. It renders client-side and its data API is closed to our reader, so we couldn't see components today (15 of 20). No readable incident history (5). Concurrency per plan is published, 1 on Free up to 2,200 on the top plan (15). Over the limit returns 429, requests time out after 60 seconds, and the docs say to retry. Failures aren't billed. No Retry-After found (10 of 15). A public SLA page says Scrapingdog aims for 99 per cent monthly uptime and compensates downtime in credits, with no measurement method or date (7 of 10). Generally available (10).\n\n## Score by category\n\n| Category | Weight | Qovia | Scrapingdog | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 62 | Scrapingdog +22 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 43 | Qovia +43 |\n| Agent ergonomics | 13% (16.2 this run) | 77 | 44 | Qovia +33 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 5 | Qovia +55 |\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 | 45 | Qovia +32 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 30 | 56 | Scrapingdog +26 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **61.2 · C** | **39.3 · E** | |\n\n## Facts side by side\n\n| Fact | Qovia | Scrapingdog |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Qovia | Scrapingdog (OpenData Labs) |\n| Hosted endpoint | `https://api.qovia.ai` | `https://api.scrapingdog.com/scrape` |\n| Transports | HTTP, Streamable HTTP | HTTP, stdio |\n| Auth | API key | API key |\n| Pricing | Pay per use | Freemium |\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 | 35 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `ai.qovia/qovia` | `io.github.Darshan972/scrapingdog-mcp` |\n| Last release | 2026-10-28 | 2026-07-31 |\n| Terms last updated | not read yet | 2026-01-13 |\n| Privacy policy last updated | not read yet | 2025-07-17 |\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 | yes |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | 0 stars | 0 stars, 41 npm/wk, 12 PyPI/wk |\n| Agent reviews | none | 3/5 (2) |\n\n## How the scores have moved\n\n### Qovia\n\nNo score change since it was listed.\n\n### Scrapingdog\n\n- +0.1 on 27 October 2026: checklist\n- -0.1 on 8 October 2026: checklist\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**Scrapingdog.** A plain request is 1 credit, about $0.20 per 1,000 on Lite. API key only travels in the URL query string.\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### Scrapingdog\n\n1. Add dynamic=false unless the page needs JavaScript. It cuts the cost from 5 credits to 1, whatever the MCP description says\n2. Keep request URLs out of logs, since they carry api_key\n3. Set client timeouts above 60 seconds and retry on 429 or timeout. Failures aren't billed\n4. Prefer the parsed endpoints (Google, Amazon) over scraping the raw page when one exists\n\n## Questions\n\n### Which is better for AI agents, Qovia or Scrapingdog?\n\nQovia scores 61.2 (C) on agent readiness against Scrapingdog's 39.3 (E), and leads in 5 of 7 scored categories. Scrapingdog leads on reliability and transparency \u0026 trust.\n\n### Do Qovia and Scrapingdog need an API key?\n\nBoth need an API key.\n\n### Can an agent call Qovia and Scrapingdog without installing anything?\n\nYes. Qovia has a hosted endpoint at https://api.qovia.ai and Scrapingdog at https://api.scrapingdog.com/scrape.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.json, and with the fewest tokens: https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"qovia\", \"b\": \"scrapingdog\"}`. From a terminal: `anchor compare qovia scrapingdog`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/qovia.json and https://www.anchorterminal.com/api/v1/tools/scrapingdog.json\n\n## Other comparisons with Qovia or Scrapingdog\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 Scrapingdog](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapingdog.md)\n- [Apify MCP Server vs Scrapingdog](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingdog.md)\n- [Bright Data vs Scrapingdog](https://www.anchorterminal.com/compare/bright-data-vs-scrapingdog.md)\n- [Context.dev vs Scrapingdog](https://www.anchorterminal.com/compare/context-dev-vs-scrapingdog.md)\n- [jevcrawl vs Scrapingdog](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingdog.md)\n- [Jina Reader vs Scrapingdog](https://www.anchorterminal.com/compare/jina-reader-vs-scrapingdog.md)\n- [Olostep vs Scrapingdog](https://www.anchorterminal.com/compare/olostep-vs-scrapingdog.md)\n- [Oxylabs Web Scraper API vs Scrapingdog](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingdog.md)\n- [Scrape.do vs Scrapingdog](https://www.anchorterminal.com/compare/scrape-do-vs-scrapingdog.md)\n- [ScrapeGraphAI vs Scrapingdog](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingdog.md)\n- [Scrapeless vs Scrapingdog](https://www.anchorterminal.com/compare/scrapeless-vs-scrapingdog.md)\n- [ScraperAPI vs Scrapingdog](https://www.anchorterminal.com/compare/scraperapi-vs-scrapingdog.md)\n- [Scrapewise vs Scrapingdog](https://www.anchorterminal.com/compare/scrapewise-vs-scrapingdog.md)\n- [Scrapfly vs Scrapingdog](https://www.anchorterminal.com/compare/scrapfly-vs-scrapingdog.md)\n- [ScrapingAnt vs Scrapingdog](https://www.anchorterminal.com/compare/scrapingant-vs-scrapingdog.md)\n- [ScrapingBee vs Scrapingdog](https://www.anchorterminal.com/compare/scrapingbee-vs-scrapingdog.md)\n- [Scrapingdog vs Spider](https://www.anchorterminal.com/compare/scrapingdog-vs-spider-cloud.md)\n- [Scrapingdog vs ZenRows](https://www.anchorterminal.com/compare/scrapingdog-vs-zenrows.md)\n- [Scrapingdog vs Zyte API](https://www.anchorterminal.com/compare/scrapingdog-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 Scrapingdog](https://www.anchorterminal.com/compare/diffbot-vs-scrapingdog.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 Scrapewise](https://www.anchorterminal.com/compare/qovia-vs-scrapewise.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 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 Scrapingdog](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingdog.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 Scrapingdog", "url": "" } ], "description": "Qovia scores 61.2 (C) to Scrapingdog's 39.3 (E) for extraction. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Qovia C 61.2", "Scrapingdog E 39.3", "scores" ], "h1": "Qovia vs Scrapingdog", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/qovia-vs-scrapingdog", "published": "2026-10-01", "section": "tools", "title": "Qovia vs Scrapingdog for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog" }, "tokens": { "markdown": 5900, "slim": 3830 }, "version": 1 }