{ "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 ScraperAPI's 52.1 (D), and leads in 5 of 7 scored categories. ScraperAPI leads on reliability and transparency \u0026 trust.", "b": { "slug": "scraperapi", "name": "ScraperAPI", "vendor": "ScraperAPI (saas.group)", "vendorUrl": "https://www.scraperapi.com", "kind": "http-api", "category": "web-scrapers", "summary": "Web scraping API that fetches a URL through rotating proxies with optional JavaScript rendering and anti-bot bypass, and returns HTML, Markdown, text or parsed JSON. It has async jobs, a crawler, structured data endpoints and an MCP server.", "url": "https://www.anchorterminal.com/tools/scraperapi", "markdownUrl": "https://www.anchorterminal.com/tools/scraperapi.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/scraperapi.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/scraperapi.json", "dns": "scraperapi.grade.anchorterminal.com", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.scraperapi.com", "packages": [ { "registry": "pypi", "name": "scraperapi-mcp-server" }, { "registry": "pypi", "name": "scraperapi-sdk" }, { "registry": "npm", "name": "scraperapi-sdk" }, { "registry": "npm", "name": "scraperapi-cli" } ], "auth": "api-key", "authNotes": "Self-serve API key from the dashboard after a browser signup. The sync API takes it as the `api_key` query parameter by default or as an `x-sapi-api_key` header. The async, crawler and AI parser APIs take it in the JSON body, and the remote MCP server takes `Authorization: Bearer`. One key per account, regenerated at most once every 24 hours, with no scopes.", "pricing": "freemium", "pricingNotes": "Free plan of 1,000 credits a month with 5 concurrent threads, and 5,000 credits for the first 7 days, no card. Hobby $49 a month (100,000 credits, 20 threads), Startup $149 (1 million, 50), Business $299 (3 million, 100), Scaling $475 (5 million, 200), Professional $975 (10.5 million, 300), Advanced $1,975 (21.5 million, 500), Enterprise custom. Annual billing takes 10% off. A plain request costs 1 credit, rendering or premium proxies 10, Google and Bing 25. Only 200 and 404 responses are charged. Pay-as-you-go overage starts at Scaling (https://www.scraperapi.com/pricing/).", "priceSummary": "$49 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the pricing page or llms.txt (checked 2026-10-09).", "endpoints": [] }, "toolCount": 28, "popularity": { "githubStars": 5, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.scraperapi.com/", "llmsTxt": "https://docs.scraperapi.com/llms.txt", "capabilities": [ "web.scrape", "web.extract", "web.crawl", "scraping.proxies", "scraping.js-render", "scraping.anti-bot", "scraping.screenshot", "scraping.serp" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "api-key", "mcp", "llms-txt", "proxies", "async-jobs", "webhooks", "cli", "python", "javascript", "php", "ruby", "java", "closed-source" ], "lastRelease": "2026-08-07", "graded": true, "anchor": { "graded": true, "score": 52.1, "grade": "D", "agentReady": false, "rank": 904, "ranked": true, "rankOf": 1253, "categoryRank": 19, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 61, "payments": 40, "reliability": 45, "schema": 67, "security": 29, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "One GET request with a key and a URL returns a page, and the MCP server's 28 tools carry read-only and destructive hints. No status page, OpenAPI file, security.txt or certification was found, and the documented default puts the API key in the URL query string.", "bestFor": "Agents that want a single GET to fetch pages through proxies, with parsed JSON for Amazon, Google, Walmart, eBay and Redfin and a batch API of up to 50,000 URLs.", "strengths": [ "Only `api_key` and `url` are required, and JavaScript rendering is off by default, so a plain request costs 1 credit", "Failed requests are not charged. Only 200 and 404 responses are billed, and each response carries an `sa-credit-cost` header", "`max_cost` caps the credits one request may spend, and `/account/urlcost` returns the cost of a URL before it is scraped", "The open-source MCP server (MIT) defines 28 typed tools, each with read-only, destructive and idempotent hints", "Free plan of 1,000 credits a month with no card, plus 5,000 credits for the first 7 days" ], "weaknesses": [ "No status page is linked from the home, pricing, support or docs pages, although the pricing page lists a 99.9% uptime guarantee", "The documented default sends the API key in the URL query string. A header alternative, `x-sapi-api_key`, exists", "No OpenAPI file, security.txt, bug bounty, certification or sub-processor list was found", "The site's robots.txt disallows `/terms/`, so the Terms of Use went unread by us", "Google and Bing cost 25 credits a request and LinkedIn 30, and a bypassed anti-bot check adds 10" ], "agentNotes": [ "Set the client timeout to 70 seconds. The API retries for that long before it returns 500, and a request cancelled earlier is still charged", "Send the key as the `x-sapi-api_key` header to keep it out of URLs and logs", "Pass `max_cost` on each request, or call `/account/urlcost` first, because domain and anti-bot surcharges vary from 1 to 75 credits", "Use `output_format=markdown` or `text` to cut response size, and `autoparse=true` only on supported domains", "On 429 reduce concurrency to the plan limit (5 on Free, 20 on Hobby). The request is rejected, not queued" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 52.1 } ], "editorialScores": { "ergonomics": 74, "maintenance": 61, "payments": 40, "reliability": 45, "schema": 67, "security": 29, "transparency": 35 }, "provenanceScore": 73, "checked": { "categories": { "ergonomics": "2026-10-09", "maintenance": "2026-10-09", "payments": "2026-10-09", "reliability": "2026-10-09", "schema": "2026-10-09", "security": "2026-10-09", "transparency": "2026-10-09" }, "last": "2026-10-09", "lastMoved": "2026-10-28", "oldest": "2026-10-09", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install scraperapi-mcp-server", "http": "curl --request GET \\\n--url 'https://api.scraperapi.com?api_key=API_KEY\u0026url=https://www.example.com'", "claudeCode": "claude mcp add scraperapi -- npx mcp-remote https://mcp.scraperapi.com/mcp --header \"Authorization: Bearer {YOUR_API_KEY}\"", "config": { "mcpServers": { "ScraperAPIRemote": { "args": [ "mcp-remote", "https://mcp.scraperapi.com/mcp", "--header", "Authorization: Bearer {YOUR_API_KEY}" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/scraperapi" }, "area": "web-data", "unitPrices": [ { "item": "Hobby plan", "unit": "month", "usd": 49, "note": "100,000 credits, 20 concurrent threads" }, { "item": "Startup plan", "unit": "month", "usd": 149, "note": "1 million credits, 50 concurrent threads" }, { "item": "Business plan", "unit": "month", "usd": 299, "note": "3 million credits, 100 concurrent threads" }, { "item": "Plain request on Hobby", "unit": "1k-requests", "usd": 0.49, "note": "1 credit each, no rendering" }, { "item": "Rendered request on Hobby", "unit": "1k-requests", "usd": 4.9, "note": "render=true, 10 credits each" }, { "item": "Google or Bing request on Hobby", "unit": "1k-requests", "usd": 12.25, "note": "25 credits each" } ], "provenance": { "legalEntity": "ScraperAPI LLC", "domain": "scraperapi.com", "domainRegistered": "2018-05-14", "endpointOnVendorDomain": true, "terms": "https://www.scraperapi.com/terms/", "privacy": "https://www.scraperapi.com/privacy/", "statusPage": "", "changelog": "https://docs.scraperapi.com/resources/release-notes", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The legal entity is taken from a November 2025 release note that says the service now operates as ScraperAPI LLC. The privacy policy names ScraperAPI and Saas.group Inc. and carries no date.", "robots.txt disallows `/terms/` for every agent, so the Terms of Use were not read. The link is the one in the site footer.", "No status page is linked from the home, pricing, support or docs pages read on 9 October 2026." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/scraperapi.json", "live": { "slug": "scraperapi", "probe": { "target": "https://api.scraperapi.com", "method": "get", "lastAt": "2026-11-01T22:08:45.904017303Z", "lastOk": true, "lastStatus": 404, "lastMs": 260, "authRequired": false, "uptime24h": 100, "uptime30d": 99.98, "p50ms24h": 291, "p95ms24h": 434, "samples24h": 250, "samples30d": 5829, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "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": 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": 252 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 230, "ok": 230 } ] }, "versions": [ { "registry": "npm", "name": "scraperapi-cli", "version": "1.0.0", "seenAt": "2026-11-01T17:31:36.03581719Z" }, { "registry": "npm", "name": "scraperapi-sdk", "version": "2.0.1", "seenAt": "2026-11-01T17:31:35.196857035Z" }, { "registry": "pypi", "name": "scraperapi-mcp-server", "version": "1.1.1", "released": "2026-07-17", "seenAt": "2026-11-01T17:31:33.109995512Z" }, { "registry": "pypi", "name": "scraperapi-sdk", "version": "1.6.1", "released": "2026-07-20", "seenAt": "2026-11-01T17:31:33.250468395Z" } ], "npmWeekly": 1751, "pypiWeekly": 32, "securityTxt": { "url": "https://scraperapi.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:43:17.355880106Z" }, "llmsTxt": { "url": "https://docs.scraperapi.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:14:57.677799728Z" }, "domain": { "domain": "scraperapi.com", "registered": "2018-05-14", "source": "https://rdap.verisign.com/com/v1/domain/scraperapi.com", "checkedAt": "2026-11-01T14:21:47.113145139Z" }, "pages": [ { "url": "https://docs.scraperapi.com/resources/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-11-01T06:42:46.974013747Z", "changedAt": "2026-10-29T05:05:41.120736069Z", "fingerprint": "ea252f3935ad" }, { "url": "https://www.scraperapi.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-01T07:04:05.497633054Z", "changedAt": "2026-10-13T20:31:43.227356571Z", "fingerprint": "44573b8fc12d" }, { "url": "https://www.scraperapi.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-01T07:04:08.062254873Z", "changedAt": "2026-10-13T20:31:45.532386274Z", "fingerprint": "487e967f92ce" }, { "url": "https://www.scraperapi.com/terms/", "kind": "terms", "status": 0, "checkedAt": "2026-11-01T07:04:09.860785415Z", "changedAt": "0001-01-01T00:00:00Z", "blockedByRobots": true } ], "updatedAt": "2026-11-01T22:08:45.904017303Z" } }, "edges": [ { "by": 31, "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, regenerated from the dashboard at most once every 24 hours. No scopes (20). The documented default puts the key in the URL query string, so less 10, although an `x-sapi-api_key` header and a Bearer header on the remote MCP server exist (10 of 30). No read-only or restricted keys. `max_cost`, a monthly pay-as-you-go spending cap and destructive hints on the two MCP delete tools limit damage (6 of 20). The API returns untrusted web content and no prompt-injection guidance was found in the docs, the MCP README or the skills (2 of 15). The dashboard has analytics with error logs, each response carries `sa-credit-cost`, and the privacy policy says activity logs are deleted after 7 days (9 of 15). `/.well-known/security.txt` returned 404, and no disclosure policy, bug bounty or certification was found. The home page claims CCPA and GDPR compliance (2 of 20)." }, "scores": { "a": 60, "b": 29 } }, { "by": 24, "category": "transparency", "leads": "scraperapi", "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. The MCP server and skills are MIT. Terms of Use exist at `/terms/`, but robots.txt disallows that path, so we could not confirm what they say (10 of 30). The privacy policy says activity logs are deleted after 7 days and account data within 60 days of a request, async results are kept up to 72 hours and DataPipeline results 30 days. The policy is undated, names Saas.group Inc. while a November 2025 release note says the service operates as ScraperAPI LLC, and no DPA was found (14 of 30). The terms and billing change was announced with effective dates of 4 November 2025 and 5 January 2026. No standing deprecation policy (8 of 20). No sub-processor list or hosting location found, only a general statement on transfers outside the EEA (3 of 20)." }, "scores": { "a": 30, "b": 54 } }, { "by": 19, "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 file found. The MCP server's source defines typed pydantic inputs for all 28 tools (12 of 25). The docs publish llms.txt, llms-full.txt and a Markdown twin of every page (10). MCP tool descriptions state when to use a tool and when not to, and the API reference describes each parameter with its credit cost (15 of 20). MCP inputs use enums for device type and output format. The HTTP API's parameters are query strings described in prose tables (10 of 15). Examples in cURL, Python, Node.js, PHP, Ruby and Java, a status code table that says which codes are billed, and an error table for the AI parser (12 of 15). Release notes are grouped by month without day dates, the HTTP API has no version, and the MCP server uses semver tags (8 of 15)." }, "scores": { "a": 86, "b": 67 } }, { "by": 16, "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 skills plugin was last updated on 7 August 2026, 63 days before the check, and the MCP server's v1.1.1 is from 17 July 2026 (20 of 30). MCP v1.1.0 and v1.1.1 on 17 July and the plugin update on 7 August fall within 90 days, with two July 2026 release notes dated by month only (20). Monthly release notes and support through the dashboard and email. We did not read the repository's issues (8 of 15). SDKs are documented for five languages, but we did not check their release dates, and the MCP server's registry entry was not checked (8 of 15). The MCP repository has unit tests and a lock file with current dependencies but no public CI workflow (5 of 10)." }, "scores": { "a": 77, "b": 61 } }, { "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 found in the docs index or pricing page (0). Plan prices and credit costs per request type are public without a login (20). Free plan of 1,000 credits a month and a 7-day trial of 5,000 credits, no card (20). A person signs up in a browser to get a key (0)." }, "scores": { "a": 55, "b": 40 } }, { "by": 5, "category": "reliability", "leads": "scraperapi", "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": "No status page is linked from the home, pricing, support or docs pages we read (0). No readable incident history (5). Concurrency limits are published per plan, 5 threads on Free, 20 on Hobby, 50, 100, 200, 300 and 500 above it, and the local MCP server limits itself to 10 calls in 60 seconds (15). 429 is documented as a concurrency rejection with no charge, the API retries a target for up to 70 seconds before returning 500, and the docs tell clients to retry failed requests. No Retry-After header or idempotency key was found (10 of 15). The pricing page lists a 99.9% uptime guarantee on every plan, with no SLA document or credit terms found, and the Terms of Use were unread (5 of 10). The API, async service and crawler are generally available (10)." }, "scores": { "a": 40, "b": 45 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Qovia", "b": "ScraperAPI (saas.group)", "name": "Vendor" }, { "a": "https://api.qovia.ai", "b": "https://api.scraperapi.com", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable 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": "28", "name": "Tools exposed" }, { "a": "no", "b": "yes", "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-08-07", "name": "Last release" }, { "a": "not read yet", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "not read yet", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not read yet", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "0 stars", "b": "5 stars", "name": "Popularity" } ], "faq": [ { "answer": "Qovia scores 61.2 (C) on agent readiness against ScraperAPI's 52.1 (D), and leads in 5 of 7 scored categories. ScraperAPI leads on reliability and transparency \u0026 trust.", "question": "Which is better for AI agents, Qovia or ScraperAPI?" }, { "answer": "Both need an API key.", "question": "Do Qovia and ScraperAPI need an API key?" }, { "answer": "Yes. Qovia has a hosted endpoint at https://api.qovia.ai and ScraperAPI at https://api.scraperapi.com.", "question": "Can an agent call Qovia and ScraperAPI without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 86 against 67", "Security \u0026 auth, 60 against 29", "Payments \u0026 pricing, 55 against 40", "Maintenance \u0026 community, 77 against 61" ], "also": null, "goodFor": "Agents that need structured public data from Chinese platforms (Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Zhihu, WeChat official accounts, Taobao and JD reviews) or the Xingtu and Pugongying creator marketplaces, with TikTok, YouTube, Instagram, X and Reddit beside them, paid per successful call from a prepaid balance.", "slug": "qovia", "watchFor": "No status page, incident history or SLA; the terms promise nothing about uptime and the Python client is the only retry guidance beyond `Retry-After`" }, { "aheadOn": [ "Reliability, 45 against 40", "Transparency \u0026 trust, 54 against 30" ], "also": [ "Runs on your own machine", "Free to start without a card" ], "goodFor": "Agents that want a single GET to fetch pages through proxies, with parsed JSON for Amazon, Google, Walmart, eBay and Redfin and a batch API of up to 50,000 URLs.", "slug": "scraperapi", "watchFor": "No status page is linked from the home, pricing, support or docs pages, although the pricing page lists a 99.9% uptime guarantee" } ], "history": { "qovia": null, "scraperapi": [ { "causes": [ "correction" ], "date": "2026-10-28", "delta": 0, "from": 52.1, "fromGrade": "D", "to": 52.1, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0, "from": 52.1, "fromGrade": "D", "to": 52.1, "toGrade": "D" } ] }, "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/bright-data-vs-scraperapi.json", "title": "Bright Data vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-scraperapi.json", "title": "Context.dev vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/context-dev-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/jina-reader-vs-scraperapi.json", "title": "Jina Reader vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/jina-reader-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/olostep-vs-scraperapi.json", "title": "Olostep vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/olostep-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scraperapi.json", "title": "Oxylabs Web Scraper API vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/scrape-do-vs-scraperapi.json", "title": "Scrape.do vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/scrape-do-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scraperapi.json", "title": "ScrapeGraphAI vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/scrapeless-vs-scraperapi.json", "title": "Scrapeless vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/scrapeless-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapewise.json", "title": "ScraperAPI vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapfly.json", "title": "ScraperAPI vs Scrapfly", "url": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapingant.json", "title": "ScraperAPI vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapingant" }, { "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/scraperapi-vs-scrapingdog.json", "title": "ScraperAPI vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/scraperapi-vs-spider-cloud.json", "title": "ScraperAPI vs Spider", "url": "https://www.anchorterminal.com/compare/scraperapi-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scraperapi-vs-zenrows.json", "title": "ScraperAPI vs ZenRows", "url": "https://www.anchorterminal.com/compare/scraperapi-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/scraperapi-vs-zyte.json", "title": "ScraperAPI vs Zyte API", "url": "https://www.anchorterminal.com/compare/scraperapi-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-scraperapi.json", "title": "Diffbot vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/diffbot-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scraperapi.json", "title": "Firecrawl MCP vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scraperapi" }, { "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-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-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-scraperapi.json", "title": "ScrapeAtlas vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scraperapi.json", "title": "Apify MCP Server vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scraperapi.json", "title": "jevcrawl vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scraperapi" } ], "panel": null, "scores": [ { "by": 5, "edge": "scraperapi", "key": "reliability", "name": "Reliability", "qovia": 40, "scraperapi": 45, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 19, "edge": "qovia", "key": "schema", "name": "Schema \u0026 documentation", "qovia": 86, "scraperapi": 67, "weight": 13 }, { "by": 3, "edge": "qovia", "key": "ergonomics", "name": "Agent ergonomics", "qovia": 77, "scraperapi": 74, "weight": 13 }, { "by": 31, "edge": "qovia", "key": "security", "name": "Security \u0026 auth", "qovia": 60, "scraperapi": 29, "weight": 14 }, { "by": 15, "edge": "qovia", "key": "payments", "name": "Payments \u0026 pricing", "qovia": 55, "scraperapi": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 16, "edge": "qovia", "key": "maintenance", "name": "Maintenance \u0026 community", "qovia": 77, "scraperapi": 61, "weight": 7 }, { "by": 24, "edge": "scraperapi", "key": "transparency", "name": "Transparency \u0026 trust", "qovia": 30, "scraperapi": 54, "weight": 7 } ], "summary": "Qovia scores 61.2 (C) on agent readiness against ScraperAPI's 52.1 (D), and leads in 5 of 7 scored categories. ScraperAPI 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.", "scraperapi": "One GET request with a key and a URL returns a page, and the MCP server's 28 tools carry read-only and destructive hints. No status page, OpenAPI file, security.txt or certification was found, and the documented default puts the API key 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-scraperapi", "json": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi.min.md" }, "markdown": "Qovia scores 61.2 (C) on agent readiness against ScraperAPI's 52.1 (D), and leads in 5 of 7 scored categories. ScraperAPI 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- ScraperAPI: grade D, 52.1/100, rank #904 of 1253. Markdown https://www.anchorterminal.com/tools/scraperapi.md · JSON https://www.anchorterminal.com/api/v1/tools/scraperapi.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 67\n- Security \u0026 auth, 60 against 29\n- Payments \u0026 pricing, 55 against 40\n- Maintenance \u0026 community, 77 against 61\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### ScraperAPI (D)\n\nGood for: Agents that want a single GET to fetch pages through proxies, with parsed JSON for Amazon, Google, Walmart, eBay and Redfin and a batch API of up to 50,000 URLs.\n\nAhead on:\n- Reliability, 45 against 40\n- Transparency \u0026 trust, 54 against 30\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: No status page is linked from the home, pricing, support or docs pages, although the pricing page lists a 99.9% uptime guarantee\n\n\n## Why the edge\n\n### Security \u0026 auth: Qovia +31\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- ScraperAPI (29): One API key per account, regenerated from the dashboard at most once every 24 hours. No scopes (20). The documented default puts the key in the URL query string, so less 10, although an `x-sapi-api_key` header and a Bearer header on the remote MCP server exist (10 of 30). No read-only or restricted keys. `max_cost`, a monthly pay-as-you-go spending cap and destructive hints on the two MCP delete tools limit damage (6 of 20). The API returns untrusted web content and no prompt-injection guidance was found in the docs, the MCP README or the skills (2 of 15). The dashboard has analytics with error logs, each response carries `sa-credit-cost`, and the privacy policy says activity logs are deleted after 7 days (9 of 15). `/.well-known/security.txt` returned 404, and no disclosure policy, bug bounty or certification was found. The home page claims CCPA and GDPR compliance (2 of 20).\n\n### Transparency \u0026 trust: ScraperAPI +24\n\n- Qovia (30): Closed service. The Terms of Service is one paragraph that names no legal entity, address or liability terms, says Delaware law governs and that the page is a summary with the signed agreement governing; the repository's client is MIT. Between the closed and unclear bands (7 of 30). The privacy policy is one paragraph. Account information is used to deliver and bill, personal information is not sold, requests and results are not resold, deletion requests go to the support mailbox, and the agreement governs where it differs. No retention periods, no subprocessors, no DPA, and no statement about the cache the prov.source flag implies; the SECURITY.md repeats the same points (8 of 30). A 410 endpoint_disabled code exists for retired endpoints and the changelog is dated, but there is no deprecation policy or notice period and nothing is marked deprecated (5 of 20). Stripe is named on the pricing page as the card and Alipay processor; no other provider, data location or transfer basis is stated (3 of 20). 7+8+5+3 = 23.\n- ScraperAPI (54): Closed service. The MCP server and skills are MIT. Terms of Use exist at `/terms/`, but robots.txt disallows that path, so we could not confirm what they say (10 of 30). The privacy policy says activity logs are deleted after 7 days and account data within 60 days of a request, async results are kept up to 72 hours and DataPipeline results 30 days. The policy is undated, names Saas.group Inc. while a November 2025 release note says the service operates as ScraperAPI LLC, and no DPA was found (14 of 30). The terms and billing change was announced with effective dates of 4 November 2025 and 5 January 2026. No standing deprecation policy (8 of 20). No sub-processor list or hosting location found, only a general statement on transfers outside the EEA (3 of 20).\n\n### Schema \u0026 documentation: Qovia +19\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- ScraperAPI (67): No OpenAPI file found. The MCP server's source defines typed pydantic inputs for all 28 tools (12 of 25). The docs publish llms.txt, llms-full.txt and a Markdown twin of every page (10). MCP tool descriptions state when to use a tool and when not to, and the API reference describes each parameter with its credit cost (15 of 20). MCP inputs use enums for device type and output format. The HTTP API's parameters are query strings described in prose tables (10 of 15). Examples in cURL, Python, Node.js, PHP, Ruby and Java, a status code table that says which codes are billed, and an error table for the AI parser (12 of 15). Release notes are grouped by month without day dates, the HTTP API has no version, and the MCP server uses semver tags (8 of 15).\n\n### Maintenance \u0026 community: Qovia +16\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- ScraperAPI (61): The skills plugin was last updated on 7 August 2026, 63 days before the check, and the MCP server's v1.1.1 is from 17 July 2026 (20 of 30). MCP v1.1.0 and v1.1.1 on 17 July and the plugin update on 7 August fall within 90 days, with two July 2026 release notes dated by month only (20). Monthly release notes and support through the dashboard and email. We did not read the repository's issues (8 of 15). SDKs are documented for five languages, but we did not check their release dates, and the MCP server's registry entry was not checked (8 of 15). The MCP repository has unit tests and a lock file with current dependencies but no public CI workflow (5 of 10).\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- ScraperAPI (40): No x402, MPP or L402 found in the docs index or pricing page (0). Plan prices and credit costs per request type are public without a login (20). Free plan of 1,000 credits a month and a 7-day trial of 5,000 credits, no card (20). A person signs up in a browser to get a key (0).\n\n### Reliability: ScraperAPI +5\n\n- Qovia (40): Hosted reading, for the REST API with the MCP server described. No public status page was found. https://qovia.ai/status/ answers 404, status.qovia.ai does not resolve and neither the docs nor the footer links one (0). No readable incident history, so 5 by the rubric (5). Limits are published with numbers on the quickstart's rate-limits section, 60 requests a minute per account before the first top-up and 600 after on a sliding 60-second window, with X-RateLimit-Limit and X-RateLimit-Remaining headers, a 64 KiB body cap, an empty-call throttle (50 calls in 10 minutes with over 80 per cent empty, not found or rejected) and a per-second cap per endpoint without a number (15). Retry-After is declared on too_many_auth_failures, rate_limited, too_many_unbilled, endpoint_busy and upstream_busy, the error table marks the retryable codes, the docs say a 503 endpoint_unavailable carries none and will not clear, and the Python client retries 429 and 503 honouring the header. Every operation is a read, including POST /v1/search, and a failed or timed-out call is refunded, so idempotency keys are not needed (15). No SLA. The terms summary says nothing about uptime and the pricing FAQ excludes outages, rate limits and platform changes from refunds; the 11 September 2026 archived home page advertised a 99.95 per cent enterprise SLA that the current pages have dropped (0). The endpoints are sold and labelled Live on the docs and coverage pages, but every one of the 143 carries x-qovia-status beta in the OpenAPI file, the API version is 0.1.0 and the MCP server reports 0.1.0 (5 of 10). 0+5+15+15+0+5 = 40.\n- ScraperAPI (45): No status page is linked from the home, pricing, support or docs pages we read (0). No readable incident history (5). Concurrency limits are published per plan, 5 threads on Free, 20 on Hobby, 50, 100, 200, 300 and 500 above it, and the local MCP server limits itself to 10 calls in 60 seconds (15). 429 is documented as a concurrency rejection with no charge, the API retries a target for up to 70 seconds before returning 500, and the docs tell clients to retry failed requests. No Retry-After header or idempotency key was found (10 of 15). The pricing page lists a 99.9% uptime guarantee on every plan, with no SLA document or credit terms found, and the Terms of Use were unread (5 of 10). The API, async service and crawler are generally available (10).\n\n## Score by category\n\n| Category | Weight | Qovia | ScraperAPI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 45 | ScraperAPI +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 67 | Qovia +19 |\n| Agent ergonomics | 13% (16.2 this run) | 77 | 74 | Qovia +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 29 | Qovia +31 |\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 | 61 | Qovia +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 30 | 54 | ScraperAPI +24 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.2 · C** | **52.1 · D** | |\n\n## Facts side by side\n\n| Fact | Qovia | ScraperAPI |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Qovia | ScraperAPI (saas.group) |\n| Hosted endpoint | `https://api.qovia.ai` | `https://api.scraperapi.com` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable 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 | 28 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | `ai.qovia/qovia` | not listed |\n| Last release | 2026-10-28 | 2026-08-07 |\n| Terms last updated | not read yet | couldn't be read |\n| Privacy policy last updated | not read yet | no date given |\n| Customer content may train models | not read yet | couldn't be read |\n| Terms restrict automated access | not read yet | couldn't be read |\n| Terms restrict benchmarking | not read yet | couldn't be read |\n| Terms or service can change without notice | not read yet | couldn't be read |\n| Arbitration or class-action waiver | not read yet | couldn't be read |\n| Popularity | 0 stars | 5 stars |\n\n## How the scores have moved\n\n### Qovia\n\nNo score change since it was listed.\n\n### ScraperAPI\n\n- no change on 28 October 2026: correction\n- no change on 27 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**ScraperAPI.** One GET request with a key and a URL returns a page, and the MCP server's 28 tools carry read-only and destructive hints. No status page, OpenAPI file, security.txt or certification was found, and the documented default puts the API key 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### ScraperAPI\n\n1. Set the client timeout to 70 seconds. The API retries for that long before it returns 500, and a request cancelled earlier is still charged\n2. Send the key as the `x-sapi-api_key` header to keep it out of URLs and logs\n3. Pass `max_cost` on each request, or call `/account/urlcost` first, because domain and anti-bot surcharges vary from 1 to 75 credits\n4. Use `output_format=markdown` or `text` to cut response size, and `autoparse=true` only on supported domains\n5. On 429 reduce concurrency to the plan limit (5 on Free, 20 on Hobby). The request is rejected, not queued\n\n## Questions\n\n### Which is better for AI agents, Qovia or ScraperAPI?\n\nQovia scores 61.2 (C) on agent readiness against ScraperAPI's 52.1 (D), and leads in 5 of 7 scored categories. ScraperAPI leads on reliability and transparency \u0026 trust.\n\n### Do Qovia and ScraperAPI need an API key?\n\nBoth need an API key.\n\n### Can an agent call Qovia and ScraperAPI without installing anything?\n\nYes. Qovia has a hosted endpoint at https://api.qovia.ai and ScraperAPI at https://api.scraperapi.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/qovia-vs-scraperapi.json, and with the fewest tokens: https://www.anchorterminal.com/compare/qovia-vs-scraperapi.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"qovia\", \"b\": \"scraperapi\"}`. From a terminal: `anchor compare qovia scraperapi`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/qovia.json and https://www.anchorterminal.com/api/v1/tools/scraperapi.json\n\n## Other comparisons with Qovia or ScraperAPI\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- [Bright Data vs ScraperAPI](https://www.anchorterminal.com/compare/bright-data-vs-scraperapi.md)\n- [Context.dev vs ScraperAPI](https://www.anchorterminal.com/compare/context-dev-vs-scraperapi.md)\n- [Jina Reader vs ScraperAPI](https://www.anchorterminal.com/compare/jina-reader-vs-scraperapi.md)\n- [Olostep vs ScraperAPI](https://www.anchorterminal.com/compare/olostep-vs-scraperapi.md)\n- [Oxylabs Web Scraper API vs ScraperAPI](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scraperapi.md)\n- [Scrape.do vs ScraperAPI](https://www.anchorterminal.com/compare/scrape-do-vs-scraperapi.md)\n- [ScrapeGraphAI vs ScraperAPI](https://www.anchorterminal.com/compare/scrapegraphai-vs-scraperapi.md)\n- [Scrapeless vs ScraperAPI](https://www.anchorterminal.com/compare/scrapeless-vs-scraperapi.md)\n- [ScraperAPI vs Scrapewise](https://www.anchorterminal.com/compare/scraperapi-vs-scrapewise.md)\n- [ScraperAPI vs Scrapfly](https://www.anchorterminal.com/compare/scraperapi-vs-scrapfly.md)\n- [ScraperAPI vs ScrapingAnt](https://www.anchorterminal.com/compare/scraperapi-vs-scrapingant.md)\n- [ScraperAPI vs ScrapingBee](https://www.anchorterminal.com/compare/scraperapi-vs-scrapingbee.md)\n- [ScraperAPI vs Scrapingdog](https://www.anchorterminal.com/compare/scraperapi-vs-scrapingdog.md)\n- [ScraperAPI vs Spider](https://www.anchorterminal.com/compare/scraperapi-vs-spider-cloud.md)\n- [ScraperAPI vs ZenRows](https://www.anchorterminal.com/compare/scraperapi-vs-zenrows.md)\n- [ScraperAPI vs Zyte API](https://www.anchorterminal.com/compare/scraperapi-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 ScraperAPI](https://www.anchorterminal.com/compare/diffbot-vs-scraperapi.md)\n- [Firecrawl MCP vs ScraperAPI](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scraperapi.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 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 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 ScraperAPI](https://www.anchorterminal.com/compare/scrapeatlas-vs-scraperapi.md)\n- [Apify MCP Server vs ScraperAPI](https://www.anchorterminal.com/compare/apify-mcp-vs-scraperapi.md)\n- [jevcrawl vs ScraperAPI](https://www.anchorterminal.com/compare/jevcrawl-vs-scraperapi.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 ScraperAPI", "url": "" } ], "description": "Qovia scores 61.2 (C) to ScraperAPI's 52.1 (D) for extraction. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Qovia C 61.2", "ScraperAPI D 52.1", "scores" ], "h1": "Qovia vs ScraperAPI", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/qovia-vs-scraperapi", "published": "2026-10-01", "section": "tools", "title": "Qovia vs ScraperAPI for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi" }, "tokens": { "markdown": 6100, "slim": 3930 }, "version": 1 }