{ "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 ScrapingBee's 59.4 (C), and leads in 4 of 7 scored categories. ScrapingBee leads on reliability, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "scrapingbee", "name": "ScrapingBee", "vendor": "ScrapingBee (Oxylabs group)", "vendorUrl": "https://www.scrapingbee.com", "kind": "http-api", "category": "web-scrapers", "summary": "HTML API that fetches a URL through rotating, premium or stealth proxies with headless rendering, JavaScript scenarios, screenshots and CSS or AI extraction.", "url": "https://www.anchorterminal.com/tools/scrapingbee", "markdownUrl": "https://www.anchorterminal.com/tools/scrapingbee.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/scrapingbee.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/scrapingbee.json", "dns": "scrapingbee.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://app.scrapingbee.com/api/v1/", "packages": [ { "registry": "pypi", "name": "scrapingbee" }, { "registry": "npm", "name": "scrapingbee" }, { "registry": "pypi", "name": "scrapingbee-cli" } ], "auth": "api-key", "authNotes": "The HTML API takes the key as a Bearer token in the Authorization header, and the Python (v2.2.0) and Node (v2.0.0) SDKs send it that way since 1 September 2026. The older api_key query parameter still works but is deprecated. remote-mcp.txt says the hosted MCP takes the key only as an api_key query parameter in its URL, while the official CLI's AGENTS.md (5 September 2026) says it takes a Bearer header.", "pricing": "paid", "pricingNotes": "Trial of 1,000 credits, no card. Hobby $19 a month (75,000 credits, 25 concurrent), Freelance $49 (250,000, 50), Startup $99 (1 million, 100), Business $249 (3 million, 200), Business+ $599 (8 million, 400), excluding VAT. JavaScript rendering is on by default, so a basic call costs 5 credits, 1 without rendering, 10 or 25 with premium proxies and 75 with stealth proxies. Google search costs 10 credits (https://www.scrapingbee.com/pricing/).", "priceSummary": "$19 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 in the pricing page, llms.txt or the HTML API and MCP references (checked 2026-09-30).", "endpoints": [] }, "toolCount": 18, "popularity": { "githubStars": 132, "npmWeekly": 48527, "pypiWeekly": 71721, "asOf": "2026-09-30" }, "docsUrl": "https://www.scrapingbee.com/documentation/", "llmsTxt": "https://www.scrapingbee.com/llms.txt", "capabilities": [ "web.scrape", "web.extract", "web.search", "scraping.proxies", "scraping.js-render", "scraping.anti-bot", "scraping.screenshot", "scraping.serp" ], "tags": [ "hosted", "no-card", "mcp", "llms-txt", "proxies", "python", "typescript", "closed-source" ], "lastRelease": "2026-09-11", "graded": true, "anchor": { "graded": true, "score": 59.4, "grade": "C", "agentReady": false, "rank": 647, "ranked": true, "rankOf": 1253, "categoryRank": 16, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 85, "payments": 40, "reliability": 70, "schema": 60, "security": 37, "transparency": 65 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Dedicated Google, Amazon, Walmart, YouTube, ChatGPT and Gemini endpoints next to the general HTML API. remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL.", "bestFor": "Agents that mix general scraping with ready-made Google, Amazon and YouTube endpoints and want spend capped per call.", "strengths": [ "Dedicated Google, Amazon, Walmart, YouTube, ChatGPT and Gemini endpoints next to the general HTML API", "Auto mode with a max_cost cap bills only the tier that works, and 429s and failures aren't billed", "Per-endpoint llms files plus a reference-notes file that lists 9 known conflicts in its own docs", "Seven SDK and CLI releases between 8 July and 11 September 2026, with tests in CI", "The official CLI skills tell agents to treat scraped output as data and flag instruction-like content" ], "weaknesses": [ "remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL", "JavaScript rendering on by default makes a plain call 5 credits instead of 1", "Only a one-off 1,000-credit trial, no monthly free tier", "No API changelog, security.txt, bug bounty or certification found", "HTML scraper degraded for about 24 hours from 28 July 2026, and dedicated APIs down for about 40 minutes on 24 July" ], "agentNotes": [ "Send render_js=false for static pages and files. It cuts the cost from 5 credits to 1", "Use mode=auto with max_cost=25 to stop it escalating to 75-credit stealth requests", "Keep the MCP URL with ?api_key= out of logs and shared configs", "Back off exponentially on 429 from the MCP, since its concurrency is shared across customers", "Expect 404 and 410 from the target to be billed. Other failures aren't" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.4 } ], "editorialScores": { "ergonomics": 68, "maintenance": 85, "payments": 40, "reliability": 70, "schema": 60, "security": 37, "transparency": 51 }, "provenanceScore": 78, "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 --get 'https://app.scrapingbee.com/api/v1/' \\\n --header \"Authorization: Bearer $SCRAPINGBEE_API_KEY\" \\\n --data-urlencode 'url=https://example.com' --data-urlencode 'render_js=false'", "claudeCode": "claude mcp add --transport http scrapingbee \"https://mcp.scrapingbee.com/mcp?api_key=$SCRAPINGBEE_API_KEY\"", "config": { "mcpServers": { "scrapingbee": { "args": [ "mcp-remote", "https://mcp.scrapingbee.com/mcp?api_key=${SCRAPINGBEE_API_KEY}" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/scrapingbee" }, "area": "web-data", "unitPrices": [ { "item": "Hobby plan", "unit": "month", "usd": 19, "note": "75,000 credits, 25 concurrent, excluding VAT" }, { "item": "Freelance plan", "unit": "month", "usd": 49, "note": "250,000 credits, 50 concurrent" }, { "item": "Startup plan", "unit": "month", "usd": 99, "note": "1 million credits, 100 concurrent" }, { "item": "Default request on Hobby", "unit": "1k-requests", "usd": 1.27, "note": "JavaScript rendering on by default, 5 credits each" }, { "item": "Request without rendering on Hobby", "unit": "1k-requests", "usd": 0.25, "note": "render_js=false, 1 credit each" } ], "provenance": { "legalEntity": "VostokInc SAS", "domain": "scrapingbee.com", "domainRegistered": "2019-09-18", "endpointOnVendorDomain": true, "terms": "https://www.scrapingbee.com/terms-and-conditions/", "privacy": "https://www.scrapingbee.com/privacy-policy/", "statusPage": "https://status.scrapingbee.com", "changelog": "", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "VostokInc is a Paris société par actions simplifiée, registration number 843 352 683, per the legal notices at https://www.scrapingbee.com/legal-notices/.", "Owned by the Oxylabs company group since June 2025. The terms still name VostokInc." ], "score": 78 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/scrapingbee.json", "live": { "slug": "scrapingbee", "probe": { "target": "https://app.scrapingbee.com/api/v1/", "method": "get", "lastAt": "2026-11-01T22:08:45.973918957Z", "lastOk": true, "lastStatus": 400, "lastMs": 51, "authRequired": false, "uptime24h": 100, "uptime30d": 99.86, "p50ms24h": 53, "p95ms24h": 118, "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": 262 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "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": 247 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "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 } ], "outages": [ { "start": "2026-10-06T05:06:59.544908317Z", "end": "2026-10-06T06:01:15.865578543Z", "note": "HTTP 503 server error" } ] }, "vendorStatus": { "page": "https://status.scrapingbee.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-01T22:10:03.181642569Z" }, "versions": [ { "registry": "npm", "name": "scrapingbee", "version": "2.0.0", "seenAt": "2026-11-01T17:31:48.824282109Z" }, { "registry": "pypi", "name": "scrapingbee", "version": "2.2.0", "released": "2026-09-01", "seenAt": "2026-11-01T17:31:47.266662937Z" }, { "registry": "pypi", "name": "scrapingbee-cli", "version": "1.6.0", "released": "2026-09-11", "seenAt": "2026-11-01T17:31:49.722164441Z" } ], "npmWeekly": 65582, "pypiWeekly": 65211, "securityTxt": { "url": "https://scrapingbee.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:43:32.39655072Z" }, "llmsTxt": { "url": "https://www.scrapingbee.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:14:57.653797103Z" }, "domain": { "domain": "scrapingbee.com", "registered": "2019-09-18", "source": "https://rdap.verisign.com/com/v1/domain/scrapingbee.com", "checkedAt": "2026-11-01T14:27:12.930849527Z" }, "pages": [ { "url": "https://www.scrapingbee.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-01T07:04:09.860820562Z", "changedAt": "2026-10-31T06:31:59.040013117Z", "fingerprint": "f47ff8019b11" }, { "url": "https://www.scrapingbee.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-01T07:04:11.997068771Z", "changedAt": "2026-10-31T06:32:01.131405162Z", "fingerprint": "a5dda7f0024b" }, { "url": "https://www.scrapingbee.com/terms-and-conditions/", "kind": "terms", "status": 200, "checkedAt": "2026-11-01T07:04:14.025155754Z", "changedAt": "2026-10-31T06:32:03.172674824Z", "fingerprint": "a1afecd53f79" } ], "updatedAt": "2026-11-01T22:10:03.181642569Z" } }, "edges": [ { "by": 35, "category": "transparency", "leads": "scrapingbee", "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 naming VostokInc SAS, Paris, registration 843 352 683 (15 of 30). The privacy policy, effective 15 July 2024, keeps prospect and customer data up to 3 years and links a DPA. It doesn't mention the Oxylabs group or say whether scraped content is stored (18 of 30). The Node SDK changelog dates removals, for example youtubeTranscript() dropped in v2.0.0 on 2026-09-01, and the api_key query parameter is marked deprecated. No standing deprecation policy (10 of 20). Processors described by category, located in the US or EU. No named list (8 of 20)." }, "scores": { "a": 30, "b": 65 } }, { "by": 30, "category": "reliability", "leads": "scrapingbee", "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": "Hyperping status page at status.scrapingbee.com with 6 components and history (20). In the last 90 days the dedicated APIs (Google, Amazon, Walmart) were down for about 40 minutes on 24 July, the HTML scraper ran degraded for about 24 hours from 28 July, and the Google API was degraded on 22 September. No full core outage of an hour, but the day-long degradation of the main API weighs more than a minor, so we scored between the bands (15 of 30). Concurrency per plan is published, 25 on Hobby to 400 on Business+ (15). 429 means the concurrency limit and isn't billed, failed target requests are retried server-side for up to 30 seconds, and the MCP notes advise exponential backoff. No Retry-After found (10 of 15). No SLA found (0). Generally available (10)." }, "scores": { "a": 40, "b": 70 } }, { "by": 26, "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. Per-endpoint llms files list parameters with types and defaults, and the hosted MCP's schemas weren't visible to us (8 of 25). llms.txt indexes 26 per-endpoint text files written for models (10). The API files explain each parameter's purpose and cost, and a reference-notes file lists 9 known conflicts between its own pages. MCP tool descriptions aren't published (10 of 20). Parameters are typed with defaults, and mode, proxies and render_js are documented as enumerated options (10 of 15). Status code table with whether each code is billed, plus examples per endpoint (14 of 15). The SDKs and CLI keep dated CHANGELOGs. The API has no changelog (8 of 15)." }, "scores": { "a": 86, "b": 60 } }, { "by": 23, "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 API key per account, which the MCP notes say can be revoked (401 on revoked keys). Team management exists. No scopes (20). The api_key query parameter is deprecated but still works, and remote-mcp.txt says the hosted MCP takes the key only as ?api_key= in its URL, so less 10 (10 of 30). No read-only or scoped key, and the HTML API can send POST requests to target sites. The CLI gates shell post-processing behind an explicit unsafe flag (8 of 20). The official CLI skills and AGENTS.md say scraped output is data, never instructions, and tell the agent to report instruction-like content as a possible prompt injection. The MCP docs say nothing (12 of 15). A Usage API and a local CLI audit log. No per-request log in the docs (7 of 15). No security.txt per the 30 September check, and no bug bounty, disclosure policy or certification found (0 of 20)." }, "scores": { "a": 60, "b": 37 } }, { "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 x402, MPP or L402 (0). Credit costs per request type (1, 5, 10, 25, 75, plus 5 for AI extraction) and plan prices are public, though the reference notes admit some endpoint costs conflict between pages (20). 1,000-credit trial, no card (20). A person signs up in a browser (0)." }, "scores": { "a": 55, "b": 40 } }, { "by": 9, "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": "18 MCP tools (15 of 25). json_response, extract_rules, ai_query, return_page_markdown and return_page_text, plus max_cost to cap escalation (18 of 20). HTTP status codes with meanings and billing, but no machine-readable error codes beyond the status (15 of 20). Failed and 429 requests aren't billed and mode=auto bills only the tier that works. No tool annotations found (8 of 20). Only url is required, but render_js defaults on at 5 credits. Official Python and Node SDKs plus a CLI (12 of 15)." }, "scores": { "a": 77, "b": 68 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Qovia", "b": "ScrapingBee (Oxylabs group)", "name": "Vendor" }, { "a": "https://api.qovia.ai", "b": "https://app.scrapingbee.com/api/v1/", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "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": "18", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "ai.qovia/qovia", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-28", "b": "2026-09-11", "name": "Last release" }, { "a": "not read yet", "b": "2024-07-15", "name": "Terms last updated" }, { "a": "not read yet", "b": "2024-07-15", "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": "132 stars, 49k npm/wk, 72k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "4/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Qovia scores 61.2 (C) on agent readiness against ScrapingBee's 59.4 (C), and leads in 4 of 7 scored categories. ScrapingBee leads on reliability, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Qovia or ScrapingBee?" }, { "answer": "Both need an API key.", "question": "Do Qovia and ScrapingBee need an API key?" }, { "answer": "Yes. Qovia has a hosted endpoint at https://api.qovia.ai and ScrapingBee at https://app.scrapingbee.com/api/v1/.", "question": "Can an agent call Qovia and ScrapingBee without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 86 against 60", "Agent ergonomics, 77 against 68", "Security \u0026 auth, 60 against 37", "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, 70 against 40", "Maintenance \u0026 community, 85 against 77", "Transparency \u0026 trust, 65 against 30" ], "also": [ "Free to start without a card" ], "goodFor": "Agents that mix general scraping with ready-made Google, Amazon and YouTube endpoints and want spend capped per call.", "slug": "scrapingbee", "watchFor": "remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL" } ], "history": { "qovia": null, "scrapingbee": [ { "causes": [ "evidence" ], "date": "2026-10-27", "delta": 0.2, "from": 59.2, "fromGrade": "C", "to": 59.4, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.1, "from": 59.3, "fromGrade": "C", "to": 59.2, "toGrade": "C" } ] }, "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-scrapingbee.json", "title": "Firecrawl MCP vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingbee.json", "title": "Apify MCP Server vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapingbee.json", "title": "Bright Data vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-scrapingbee.json", "title": "Context.dev vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/context-dev-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingbee.json", "title": "jevcrawl vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/jina-reader-vs-scrapingbee.json", "title": "Jina Reader vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/jina-reader-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/olostep-vs-scrapingbee.json", "title": "Olostep vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/olostep-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingbee.json", "title": "Oxylabs Web Scraper API vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/scrape-do-vs-scrapingbee.json", "title": "Scrape.do vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/scrape-do-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingbee.json", "title": "ScrapeGraphAI vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/scrapeless-vs-scrapingbee.json", "title": "Scrapeless vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/scrapeless-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapingbee.json", "title": "ScraperAPI vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapingbee" }, { "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/scrapfly-vs-scrapingbee.json", "title": "Scrapfly vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/scrapfly-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/scrapingant-vs-scrapingbee.json", "title": "ScrapingAnt vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/scrapingant-vs-scrapingbee" }, { "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/scrapingbee-vs-spider-cloud.json", "title": "ScrapingBee vs Spider", "url": "https://www.anchorterminal.com/compare/scrapingbee-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scrapingbee-vs-zenrows.json", "title": "ScrapingBee vs ZenRows", "url": "https://www.anchorterminal.com/compare/scrapingbee-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/scrapingbee-vs-zyte.json", "title": "ScrapingBee vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapingbee-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-scrapingbee.json", "title": "Diffbot vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/diffbot-vs-scrapingbee" }, { "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-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-scrapingbee.json", "title": "ScrapeAtlas vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingbee" } ], "panel": null, "scores": [ { "by": 30, "edge": "scrapingbee", "key": "reliability", "name": "Reliability", "qovia": 40, "scrapingbee": 70, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 26, "edge": "qovia", "key": "schema", "name": "Schema \u0026 documentation", "qovia": 86, "scrapingbee": 60, "weight": 13 }, { "by": 9, "edge": "qovia", "key": "ergonomics", "name": "Agent ergonomics", "qovia": 77, "scrapingbee": 68, "weight": 13 }, { "by": 23, "edge": "qovia", "key": "security", "name": "Security \u0026 auth", "qovia": 60, "scrapingbee": 37, "weight": 14 }, { "by": 15, "edge": "qovia", "key": "payments", "name": "Payments \u0026 pricing", "qovia": 55, "scrapingbee": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 8, "edge": "scrapingbee", "key": "maintenance", "name": "Maintenance \u0026 community", "qovia": 77, "scrapingbee": 85, "weight": 7 }, { "by": 35, "edge": "scrapingbee", "key": "transparency", "name": "Transparency \u0026 trust", "qovia": 30, "scrapingbee": 65, "weight": 7 } ], "summary": "Qovia scores 61.2 (C) on agent readiness against ScrapingBee's 59.4 (C), and leads in 4 of 7 scored categories. ScrapingBee leads on reliability, maintenance \u0026 community 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.", "scrapingbee": "Dedicated Google, Amazon, Walmart, YouTube, ChatGPT and Gemini endpoints next to the general HTML API. remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee", "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.min.md" }, "markdown": "Qovia scores 61.2 (C) on agent readiness against ScrapingBee's 59.4 (C), and leads in 4 of 7 scored categories. ScrapingBee leads on reliability, maintenance \u0026 community 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- ScrapingBee: grade C, 59.4/100, rank #647 of 1253. Markdown https://www.anchorterminal.com/tools/scrapingbee.md · JSON https://www.anchorterminal.com/api/v1/tools/scrapingbee.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 60\n- Agent ergonomics, 77 against 68\n- Security \u0026 auth, 60 against 37\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### ScrapingBee (C)\n\nGood for: Agents that mix general scraping with ready-made Google, Amazon and YouTube endpoints and want spend capped per call.\n\nAhead on:\n- Reliability, 70 against 40\n- Maintenance \u0026 community, 85 against 77\n- Transparency \u0026 trust, 65 against 30\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL\n\n\n## Why the edge\n\n### Transparency \u0026 trust: ScrapingBee +35\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- ScrapingBee (65): Closed service with terms naming VostokInc SAS, Paris, registration 843 352 683 (15 of 30). The privacy policy, effective 15 July 2024, keeps prospect and customer data up to 3 years and links a DPA. It doesn't mention the Oxylabs group or say whether scraped content is stored (18 of 30). The Node SDK changelog dates removals, for example youtubeTranscript() dropped in v2.0.0 on 2026-09-01, and the api_key query parameter is marked deprecated. No standing deprecation policy (10 of 20). Processors described by category, located in the US or EU. No named list (8 of 20).\n\n### Reliability: ScrapingBee +30\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- ScrapingBee (70): Hyperping status page at status.scrapingbee.com with 6 components and history (20). In the last 90 days the dedicated APIs (Google, Amazon, Walmart) were down for about 40 minutes on 24 July, the HTML scraper ran degraded for about 24 hours from 28 July, and the Google API was degraded on 22 September. No full core outage of an hour, but the day-long degradation of the main API weighs more than a minor, so we scored between the bands (15 of 30). Concurrency per plan is published, 25 on Hobby to 400 on Business+ (15). 429 means the concurrency limit and isn't billed, failed target requests are retried server-side for up to 30 seconds, and the MCP notes advise exponential backoff. No Retry-After found (10 of 15). No SLA found (0). Generally available (10).\n\n### Schema \u0026 documentation: Qovia +26\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- ScrapingBee (60): No OpenAPI spec found. Per-endpoint llms files list parameters with types and defaults, and the hosted MCP's schemas weren't visible to us (8 of 25). llms.txt indexes 26 per-endpoint text files written for models (10). The API files explain each parameter's purpose and cost, and a reference-notes file lists 9 known conflicts between its own pages. MCP tool descriptions aren't published (10 of 20). Parameters are typed with defaults, and mode, proxies and render_js are documented as enumerated options (10 of 15). Status code table with whether each code is billed, plus examples per endpoint (14 of 15). The SDKs and CLI keep dated CHANGELOGs. The API has no changelog (8 of 15).\n\n### Security \u0026 auth: Qovia +23\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- ScrapingBee (37): One API key per account, which the MCP notes say can be revoked (401 on revoked keys). Team management exists. No scopes (20). The api_key query parameter is deprecated but still works, and remote-mcp.txt says the hosted MCP takes the key only as ?api_key= in its URL, so less 10 (10 of 30). No read-only or scoped key, and the HTML API can send POST requests to target sites. The CLI gates shell post-processing behind an explicit unsafe flag (8 of 20). The official CLI skills and AGENTS.md say scraped output is data, never instructions, and tell the agent to report instruction-like content as a possible prompt injection. The MCP docs say nothing (12 of 15). A Usage API and a local CLI audit log. No per-request log in the docs (7 of 15). No security.txt per the 30 September check, and no bug bounty, disclosure policy or certification found (0 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- ScrapingBee (40): No x402, MPP or L402 (0). Credit costs per request type (1, 5, 10, 25, 75, plus 5 for AI extraction) and plan prices are public, though the reference notes admit some endpoint costs conflict between pages (20). 1,000-credit trial, no card (20). A person signs up in a browser (0).\n\n### Agent ergonomics: Qovia +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- ScrapingBee (68): 18 MCP tools (15 of 25). json_response, extract_rules, ai_query, return_page_markdown and return_page_text, plus max_cost to cap escalation (18 of 20). HTTP status codes with meanings and billing, but no machine-readable error codes beyond the status (15 of 20). Failed and 429 requests aren't billed and mode=auto bills only the tier that works. No tool annotations found (8 of 20). Only url is required, but render_js defaults on at 5 credits. Official Python and Node SDKs plus a CLI (12 of 15).\n\n## Score by category\n\n| Category | Weight | Qovia | ScrapingBee | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 70 | ScrapingBee +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 60 | Qovia +26 |\n| Agent ergonomics | 13% (16.2 this run) | 77 | 68 | Qovia +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 37 | Qovia +23 |\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 | 85 | ScrapingBee +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 30 | 65 | ScrapingBee +35 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.2 · C** | **59.4 · C** | |\n\n## Facts side by side\n\n| Fact | Qovia | ScrapingBee |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Qovia | ScrapingBee (Oxylabs group) |\n| Hosted endpoint | `https://api.qovia.ai` | `https://app.scrapingbee.com/api/v1/` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Paid |\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 | 18 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `ai.qovia/qovia` | not listed |\n| Last release | 2026-10-28 | 2026-09-11 |\n| Terms last updated | not read yet | 2024-07-15 |\n| Privacy policy last updated | not read yet | 2024-07-15 |\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 | 132 stars, 49k npm/wk, 72k PyPI/wk |\n| Agent reviews | none | 4/5 (2) |\n\n## How the scores have moved\n\n### Qovia\n\nNo score change since it was listed.\n\n### ScrapingBee\n\n- +0.2 on 27 October 2026: new evidence\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**ScrapingBee.** Dedicated Google, Amazon, Walmart, YouTube, ChatGPT and Gemini endpoints next to the general HTML API. remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL.\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### ScrapingBee\n\n1. Send render_js=false for static pages and files. It cuts the cost from 5 credits to 1\n2. Use mode=auto with max_cost=25 to stop it escalating to 75-credit stealth requests\n3. Keep the MCP URL with ?api_key= out of logs and shared configs\n4. Back off exponentially on 429 from the MCP, since its concurrency is shared across customers\n5. Expect 404 and 410 from the target to be billed. Other failures aren't\n\n## Questions\n\n### Which is better for AI agents, Qovia or ScrapingBee?\n\nQovia scores 61.2 (C) on agent readiness against ScrapingBee's 59.4 (C), and leads in 4 of 7 scored categories. ScrapingBee leads on reliability, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Qovia and ScrapingBee need an API key?\n\nBoth need an API key.\n\n### Can an agent call Qovia and ScrapingBee without installing anything?\n\nYes. Qovia has a hosted endpoint at https://api.qovia.ai and ScrapingBee at https://app.scrapingbee.com/api/v1/.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.json, and with the fewest tokens: https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"qovia\", \"b\": \"scrapingbee\"}`. From a terminal: `anchor compare qovia scrapingbee`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/qovia.json and https://www.anchorterminal.com/api/v1/tools/scrapingbee.json\n\n## Other comparisons with Qovia or ScrapingBee\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 ScrapingBee](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapingbee.md)\n- [Apify MCP Server vs ScrapingBee](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingbee.md)\n- [Bright Data vs ScrapingBee](https://www.anchorterminal.com/compare/bright-data-vs-scrapingbee.md)\n- [Context.dev vs ScrapingBee](https://www.anchorterminal.com/compare/context-dev-vs-scrapingbee.md)\n- [jevcrawl vs ScrapingBee](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingbee.md)\n- [Jina Reader vs ScrapingBee](https://www.anchorterminal.com/compare/jina-reader-vs-scrapingbee.md)\n- [Olostep vs ScrapingBee](https://www.anchorterminal.com/compare/olostep-vs-scrapingbee.md)\n- [Oxylabs Web Scraper API vs ScrapingBee](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingbee.md)\n- [Scrape.do vs ScrapingBee](https://www.anchorterminal.com/compare/scrape-do-vs-scrapingbee.md)\n- [ScrapeGraphAI vs ScrapingBee](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingbee.md)\n- [Scrapeless vs ScrapingBee](https://www.anchorterminal.com/compare/scrapeless-vs-scrapingbee.md)\n- [ScraperAPI vs ScrapingBee](https://www.anchorterminal.com/compare/scraperapi-vs-scrapingbee.md)\n- [Scrapewise vs ScrapingBee](https://www.anchorterminal.com/compare/scrapewise-vs-scrapingbee.md)\n- [Scrapfly vs ScrapingBee](https://www.anchorterminal.com/compare/scrapfly-vs-scrapingbee.md)\n- [ScrapingAnt vs ScrapingBee](https://www.anchorterminal.com/compare/scrapingant-vs-scrapingbee.md)\n- [ScrapingBee vs Scrapingdog](https://www.anchorterminal.com/compare/scrapingbee-vs-scrapingdog.md)\n- [ScrapingBee vs Spider](https://www.anchorterminal.com/compare/scrapingbee-vs-spider-cloud.md)\n- [ScrapingBee vs ZenRows](https://www.anchorterminal.com/compare/scrapingbee-vs-zenrows.md)\n- [ScrapingBee vs Zyte API](https://www.anchorterminal.com/compare/scrapingbee-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 ScrapingBee](https://www.anchorterminal.com/compare/diffbot-vs-scrapingbee.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 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 ScrapingBee](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingbee.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 ScrapingBee", "url": "" } ], "description": "Qovia scores 61.2 (C) to ScrapingBee's 59.4 (C) for extraction. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Qovia C 61.2", "ScrapingBee C 59.4", "scores" ], "h1": "Qovia vs ScrapingBee", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/qovia-vs-scrapingbee", "published": "2026-10-01", "section": "tools", "title": "Qovia vs ScrapingBee for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee" }, "tokens": { "markdown": 6000, "slim": 3880 }, "version": 1 }