{ "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 ScrapingAnt's 35.8 (F), and leads in 6 of 7 scored categories. ScrapingAnt leads on transparency \u0026 trust.", "b": { "slug": "scrapingant", "name": "ScrapingAnt", "vendor": "ScrapingAnt (DATAANT)", "vendorUrl": "https://scrapingant.com", "kind": "http-api", "category": "web-scrapers", "summary": "Scraping API that runs each request in headless Chrome behind rotating datacenter or residential proxies, with markdown and AI extraction endpoints, a 3-tool hosted MCP server and standalone proxies billed by the GB.", "url": "https://www.anchorterminal.com/tools/scrapingant", "markdownUrl": "https://www.anchorterminal.com/tools/scrapingant.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/scrapingant.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/scrapingant.json", "dns": "scrapingant.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.scrapingant.com/v2/general", "packages": [ { "registry": "pypi", "name": "scrapingant-client" }, { "registry": "npm", "name": "@scrapingant/scrapingant-client" } ], "auth": "api-key", "authNotes": "API key as an x-api-key header or an x-api-key query parameter. The docs' examples use the query form. The hosted MCP takes the same key in an x-api-key header. The usage endpoint only documents the query form.", "pricing": "freemium", "pricingNotes": "10,000 free credits a month, no card, one concurrent request. Enthusiast $19 a month (100,000 credits), Startup $49 (500,000), Business $249 (3M), Business Pro $599 (8M), Custom from $699 (10M+). A plain request on a datacenter proxy costs 1 credit, headless Chrome with JS rendering 10 (the default), Chrome plus residential proxy 125, and the AI extractor adds 1 credit per 30 characters. Failed requests aren't charged. Residential proxies $3 to $6 a GB and datacenter $0.42 to $0.60 a GB, billed separately (https://scrapingant.com/#pricing).", "priceSummary": "$19 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 or other agent payment rail in the docs, pricing or API responses (checked 2026-09-30).", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": null, "npmWeekly": 90, "pypiWeekly": 1969, "asOf": "2026-09-30" }, "docsUrl": "https://docs.scrapingant.com", "capabilities": [ "web.scrape", "web.fetch", "web.extract", "scraping.proxies", "scraping.js-render", "scraping.anti-bot" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "proxies", "closed-source", "python", "typescript" ], "lastRelease": "2024-07-16", "graded": true, "anchor": { "graded": true, "score": 35.8, "grade": "F", "agentReady": false, "rank": 1162, "ranked": true, "rankOf": 1253, "categoryRank": 23, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 5, "payments": 40, "reliability": 30, "schema": 43, "security": 10, "transparency": 56 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "10,000 free credits a month with no card. API Basics puts the key in the query string, so it lands in logs.", "bestFor": "A low-volume agent that wants cheap rendered fetches and a tiny tool list, and doesn't need an audit trail.", "strengths": [ "10,000 free credits a month with no card", "No concurrency cap on paid plans", "Failed requests cost nothing, and the Ant-credits-cost header reports spend per call", "3-tool hosted MCP with header auth, cheap to load into context", "Named Polish entity with processors and hosting locations listed" ], "weaknesses": [ "API Basics puts the key in the query string, so it lands in logs", "No status page, changelog, security.txt, llms.txt or OpenAPI spec", "SDKs are stale. JavaScript last released 2022-05-06, Python 2024-07-16", "No prompt-injection guidance for the pages it returns", "Privacy policy last updated 3 November 2020" ], "agentNotes": [ "Send the key in the `x-api-key` header rather than the query string", "Use `/v2/markdown` for LLM input, and set `browser=false` on static pages to pay 1 credit instead of 10", "Switch to `proxy_type=residential` only after a 423 (anti-bot) response. It raises a browser request from 10 to 125 credits", "On the free plan a second concurrent request gets 409. Wait for the first to finish", "Google, Bing and Yandex result pages come back as raw HTML through `/v2/general`, so you parse them yourself" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 35.8 } ], "editorialScores": { "ergonomics": 66, "maintenance": 5, "payments": 40, "reliability": 30, "schema": 43, "security": 10, "transparency": 48 }, "provenanceScore": 64, "checked": { "categories": { "ergonomics": "2026-10-01", "maintenance": "2026-10-01", "payments": "2026-10-01", "reliability": "2026-10-01", "schema": "2026-10-01", "security": "2026-10-01", "transparency": "2026-10-01" }, "last": "2026-10-01", "lastMoved": "2026-10-27", "oldest": "2026-10-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl 'https://api.scrapingant.com/v2/markdown?url=https%3A%2F%2Fexample.com' -H \"x-api-key: $SCRAPINGANT_API_KEY\"", "claudeCode": "claude mcp add scrapingant --transport http https://api.scrapingant.com/mcp -H \"x-api-key: $SCRAPINGANT_API_KEY\"", "config": { "mcpServers": { "scrapingant": { "headers": { "x-api-key": "${SCRAPINGANT_API_KEY}" }, "url": "https://api.scrapingant.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/scrapingant" }, "area": "web-data", "unitPrices": [ { "item": "Enthusiast plan", "unit": "month", "usd": 19, "note": "100,000 credits" }, { "item": "Startup plan", "unit": "month", "usd": 49, "note": "500,000 credits" }, { "item": "Business plan", "unit": "month", "usd": 249, "note": "3,000,000 credits" }, { "item": "Default browser request on Enthusiast", "unit": "1k-requests", "usd": 1.9, "note": "10 credits each, headless Chrome and datacenter proxy" }, { "item": "Plain request on Enthusiast", "unit": "1k-requests", "usd": 0.19, "note": "1 credit each, no browser, datacenter proxy" }, { "item": "Residential proxy", "unit": "gb", "usd": 6, "note": "Micro plan, 5 GB for $30 a month. Falls to $3 at volume" }, { "item": "Datacenter proxy", "unit": "gb", "usd": 0.6, "note": "Micro plan, 50 GB for $30 a month" } ], "provenance": { "legalEntity": "DATAANT SP. Z O.O.", "domain": "scrapingant.com", "domainRegistered": "2020-03-31", "endpointOnVendorDomain": true, "terms": "https://scrapingant.com/legal/terms-of-use", "privacy": "https://scrapingant.com/legal/privacy-policy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "Registered in Poland, KRS 0000848755, per the terms and privacy policy", "The privacy policy was last updated 3 November 2020 and predates the MCP server and AI extractor", "The site footer links no status page, changelog or security page" ], "score": 64 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/scrapingant.json", "live": { "slug": "scrapingant", "probe": { "target": "https://api.scrapingant.com/v2/general", "method": "get", "lastAt": "2026-11-01T22:08:45.962328377Z", "lastOk": true, "lastStatus": 422, "lastMs": 92, "authRequired": false, "uptime24h": 100, "uptime30d": 99.96, "p50ms24h": 105, "p95ms24h": 175, "samples24h": 250, "samples30d": 8145, "days": [ { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 271 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 248 }, { "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": 248 }, { "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": "@scrapingant/scrapingant-client", "version": "0.2.1", "seenAt": "2026-11-01T17:31:46.760158484Z" }, { "registry": "pypi", "name": "scrapingant-client", "version": "2.1.0", "released": "2024-07-16", "seenAt": "2026-11-01T17:31:46.598035764Z" } ], "npmWeekly": 493, "pypiWeekly": 2330, "securityTxt": { "url": "https://scrapingant.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:42:23.695160685Z" }, "domain": { "domain": "scrapingant.com", "registered": "2020-03-31", "source": "https://rdap.verisign.com/com/v1/domain/scrapingant.com", "checkedAt": "2026-11-01T14:18:40.120731511Z" }, "pages": [ { "url": "https://scrapingant.com/", "kind": "pricing", "status": 304, "checkedAt": "2026-11-01T06:52:04.404873458Z", "changedAt": "2026-10-31T06:20:17.083416033Z", "fingerprint": "f076a219f874" }, { "url": "https://scrapingant.com/legal/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-01T06:52:06.483456118Z", "changedAt": "2026-10-23T01:55:26.304457907Z", "fingerprint": "bcaab33c5eb3" }, { "url": "https://scrapingant.com/legal/terms-of-use", "kind": "terms", "status": 304, "checkedAt": "2026-11-01T06:52:08.475384691Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b1e179927df6" } ], "updatedAt": "2026-11-01T22:08:45.962328377Z" } }, "edges": [ { "by": 72, "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": "No changelog or dated API change found, and the newest SDK release is Python 2.1.0 on 2024-07-16 (0). No releases in the last 90 days (0). No public changelog. Support by email (3 of 15). The JavaScript client was last released 2022-05-06, the MCP server isn't in the official registry, and the only registry entry is a third-party wrapper (0). The Python client has a code-check workflow, but neither SDK has moved in over two years (2 of 10)." }, "scores": { "a": 77, "b": 5 } }, { "by": 50, "category": "security", "leads": "qovia", "name": "Security \u0026 auth", "reasons": { "a": "API keys with scopes chosen at creation (every endpoint, search, every raw endpoint or one of 24 platform groups), an optional expiry, revocation in the console and hashed storage; the docs say the key is read from the Authorization or x-api-key header only, never the URL or a cookie, and 30 failed authentications from one IP in a minute are throttled. No OAuth and no rotation feature beyond creating another key (24 of 30). The whole surface is read-only retrieval, scopes restrict a key to platforms, the two MCP catalogue tools need no key, and the docs and SECURITY.md tell users to give AI tools a separate scoped key (17 of 20). Every response is third-party platform text, and the only related statement is that error messages never contain the data source's own text; nothing on treating returned content as untrusted (3 of 15). request_id is the usage record ID on every answer, the console lists every charge in a usage log, X-Qovia-Charged and X-Qovia-Balance headers report each call, and GET /v1/account returns the key's scopes and balance at no charge; no exportable audit log or per-call endpoint was found (11 of 15). No security.txt on qovia.ai or api.qovia.ai (404), no bug bounty, SOC 2 or ISO 27001; the repository's SECURITY.md names a Telegram handle and a mailbox for reports covering both hosts (5 of 20). 24+17+3+11+5 = 60.", "b": "One account API key with no scopes, and we found no documented rotation or revocation (10). API Basics tells you to send x-api-key as a query parameter, a documented option, so less 10 (0 of 30). The header form works and the SDKs use it. No read-only mode, and /v2/general can send POST, PUT and DELETE to target sites with no confirmation step (5 of 20). No prompt-injection guidance found for the HTML, Markdown or text it returns (0 of 15). The Ant-credits-cost header and a subscription status endpoint show spend per call. No request log found (5 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20)." }, "scores": { "a": 60, "b": 10 } }, { "by": 43, "category": "schema", "leads": "qovia", "name": "Schema \u0026 documentation", "reasons": { "a": "An OpenAPI 3.1.0 file (version 0.1.0, 1 MB) is public at qovia.ai/openapi.json with 144 paths and 144 operations, two security schemes, typed query parameters, a response example on every operation and the error responses declared on each. The data payload itself is typed only as object, array or null with per-endpoint examples, and the MCP call_endpoint tool takes a free params object, so 22 of 25 (22). llms.txt (75 KB, one line per endpoint with price and status) and llms-full.txt (331 KB, the whole documentation as text) are served, and the quickstart's billing, limits and error sections are in both (10). Every operation has a summary and a description; most say what the data holds, how to page, which ids to pass, which fields are unavailable and what answers 404 or empty, and the MCP server's instructions say to find, read then call. Guidance on when not to use an endpoint is thin, mostly pointers such as replies coming from another endpoint (16 of 20). 321 parameters, 75 with enums, patterns on ids, min and max on strings and integers, 117 operations with one required parameter and 16 with none, the POST body typed with additionalProperties false, and unknown parameters rejected with 400 (14 of 15). A response example on all 144 operations, 20 error codes with every message variant listed, response headers documented per error, and cURL, Python, JavaScript and raw HTTP samples; the examples are catalogue samples the docs say are not live data (14 of 15). Paths are under /v1, a 410 endpoint_disabled code exists for retired endpoints, and the changelog is dated, but it has two days (21 and 22 October 2026), nothing is marked deprecated and no notice period is stated (10 of 15). 22+10+16+14+14+10 = 86.", "b": "No OpenAPI or Swagger spec found. The MCP docs give a typed parameter table for the 3 tools (8 of 25). docs.scrapingant.com/llms.txt returns 404 and no Markdown twins were found (0). MCP descriptions are one line each, such as Fetch a URL and return raw HTML content, with no when-to-use guidance (8 of 20). Few parameters, typed, with proxy_type as an enum of `datacenter` or `residential` (10 of 15). Request examples on every docs page and an errors page with 8 status codes and their meanings (12 of 15). Versioned paths (v1 and v2) and no changelog (5 of 15)." }, "scores": { "a": 86, "b": 43 } }, { "by": 26, "category": "transparency", "leads": "scrapingant", "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 DATAANT SP. Z O.O., registered in Poland (KRS 0000848755). The SDKs are Apache 2.0 (15 of 30). The privacy policy, last updated 3 November 2020, gives 12-month retention after an account closes, names processors and mentions DPAs with clients. It predates the MCP server and AI extractor, and doesn't say whether scraped content is stored (18 of 30). No deprecation policy or dated notices found (0). Processors and locations named, Sendgrid in Ireland, Paddle in the UK, Google Analytics and Amazon hosting in the USA (15 of 20)." }, "scores": { "a": 30, "b": 56 } }, { "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 to 125) and plan prices are public (20). 10,000 free credits a month, no card (20). A person signs up in a browser (0)." }, "scores": { "a": 55, "b": 40 } }, { "by": 11, "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": "3 compact MCP tools (25). Markdown and text endpoints, AI extraction, wait-for-selector and a JSON extended response, but no output-size limit on the MCP tools (12 of 20). 8 documented status codes, and 422 returns a detail field (14 of 20). Requests are reads of third-party pages and failures aren't billed, but there are no tool annotations or retry guidance beyond 423 (5 of 20). Only url is required, though browser defaults to true at 10 credits. Python and JavaScript clients exist but are stale (10 of 15)." }, "scores": { "a": 77, "b": 66 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Qovia", "b": "ScrapingAnt (DATAANT)", "name": "Vendor" }, { "a": "https://api.qovia.ai", "b": "https://api.scrapingant.com/v2/general", "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": "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": "3", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "ai.qovia/qovia", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-28", "b": "2024-07-16", "name": "Last release" }, { "a": "not read yet", "b": "no date given", "name": "Terms last updated" }, { "a": "not read yet", "b": "no date given", "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": "yes", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "0 stars", "b": "90 npm/wk, 2k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Qovia scores 61.2 (C) on agent readiness against ScrapingAnt's 35.8 (F), and leads in 6 of 7 scored categories. ScrapingAnt leads on transparency \u0026 trust.", "question": "Which is better for AI agents, Qovia or ScrapingAnt?" }, { "answer": "Both need an API key.", "question": "Do Qovia and ScrapingAnt need an API key?" }, { "answer": "Yes. Qovia has a hosted endpoint at https://api.qovia.ai and ScrapingAnt at https://api.scrapingant.com/v2/general.", "question": "Can an agent call Qovia and ScrapingAnt without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 40 against 30", "Schema \u0026 documentation, 86 against 43", "Agent ergonomics, 77 against 66", "Security \u0026 auth, 60 against 10", "Payments \u0026 pricing, 55 against 40", "Maintenance \u0026 community, 77 against 5" ], "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": [ "Transparency \u0026 trust, 56 against 30" ], "also": [ "Free to start without a card" ], "goodFor": "A low-volume agent that wants cheap rendered fetches and a tiny tool list, and doesn't need an audit trail.", "slug": "scrapingant", "watchFor": "API Basics puts the key in the query string, so it lands in logs" } ], "history": { "qovia": null, "scrapingant": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.3, "from": 35.5, "fromGrade": "F", "to": 35.8, "toGrade": "F" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.4, "from": 35.9, "fromGrade": "F", "to": 35.5, "toGrade": "F" } ] }, "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/apify-mcp-vs-scrapingant.json", "title": "Apify MCP Server vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapingant.json", "title": "Bright Data vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-scrapingant.json", "title": "Context.dev vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/context-dev-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingant.json", "title": "jevcrawl vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/jina-reader-vs-scrapingant.json", "title": "Jina Reader vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/jina-reader-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/olostep-vs-scrapingant.json", "title": "Olostep vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/olostep-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingant.json", "title": "Oxylabs Web Scraper API vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/scrape-do-vs-scrapingant.json", "title": "Scrape.do vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/scrape-do-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingant.json", "title": "ScrapeGraphAI vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/scrapeless-vs-scrapingant.json", "title": "Scrapeless vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/scrapeless-vs-scrapingant" }, { "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/scrapewise-vs-scrapingant.json", "title": "Scrapewise vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/scrapfly-vs-scrapingant.json", "title": "Scrapfly vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/scrapfly-vs-scrapingant" }, { "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/scrapingant-vs-scrapingdog.json", "title": "ScrapingAnt vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scrapingant-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/scrapingant-vs-spider-cloud.json", "title": "ScrapingAnt vs Spider", "url": "https://www.anchorterminal.com/compare/scrapingant-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scrapingant-vs-zenrows.json", "title": "ScrapingAnt vs ZenRows", "url": "https://www.anchorterminal.com/compare/scrapingant-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/scrapingant-vs-zyte.json", "title": "ScrapingAnt vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapingant-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-scrapingant.json", "title": "Diffbot vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/diffbot-vs-scrapingant" }, { "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-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-scrapingant.json", "title": "ScrapeAtlas vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapingant.json", "title": "Firecrawl MCP vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapingant" } ], "panel": null, "scores": [ { "by": 10, "edge": "qovia", "key": "reliability", "name": "Reliability", "qovia": 40, "scrapingant": 30, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 43, "edge": "qovia", "key": "schema", "name": "Schema \u0026 documentation", "qovia": 86, "scrapingant": 43, "weight": 13 }, { "by": 11, "edge": "qovia", "key": "ergonomics", "name": "Agent ergonomics", "qovia": 77, "scrapingant": 66, "weight": 13 }, { "by": 50, "edge": "qovia", "key": "security", "name": "Security \u0026 auth", "qovia": 60, "scrapingant": 10, "weight": 14 }, { "by": 15, "edge": "qovia", "key": "payments", "name": "Payments \u0026 pricing", "qovia": 55, "scrapingant": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 72, "edge": "qovia", "key": "maintenance", "name": "Maintenance \u0026 community", "qovia": 77, "scrapingant": 5, "weight": 7 }, { "by": 26, "edge": "scrapingant", "key": "transparency", "name": "Transparency \u0026 trust", "qovia": 30, "scrapingant": 56, "weight": 7 } ], "summary": "Qovia scores 61.2 (C) on agent readiness against ScrapingAnt's 35.8 (F), and leads in 6 of 7 scored categories. ScrapingAnt leads on 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.", "scrapingant": "10,000 free credits a month with no card. API Basics puts the key in the query string, so it lands in logs." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant", "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant.min.md" }, "markdown": "Qovia scores 61.2 (C) on agent readiness against ScrapingAnt's 35.8 (F), and leads in 6 of 7 scored categories. ScrapingAnt leads on 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- ScrapingAnt: grade F, 35.8/100, rank #1162 of 1253. Markdown https://www.anchorterminal.com/tools/scrapingant.md · JSON https://www.anchorterminal.com/api/v1/tools/scrapingant.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- Reliability, 40 against 30\n- Schema \u0026 documentation, 86 against 43\n- Agent ergonomics, 77 against 66\n- Security \u0026 auth, 60 against 10\n- Payments \u0026 pricing, 55 against 40\n- Maintenance \u0026 community, 77 against 5\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### ScrapingAnt (F)\n\nGood for: A low-volume agent that wants cheap rendered fetches and a tiny tool list, and doesn't need an audit trail.\n\nAhead on:\n- Transparency \u0026 trust, 56 against 30\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: API Basics puts the key in the query string, so it lands in logs\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Qovia +72\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- ScrapingAnt (5): No changelog or dated API change found, and the newest SDK release is Python 2.1.0 on 2024-07-16 (0). No releases in the last 90 days (0). No public changelog. Support by email (3 of 15). The JavaScript client was last released 2022-05-06, the MCP server isn't in the official registry, and the only registry entry is a third-party wrapper (0). The Python client has a code-check workflow, but neither SDK has moved in over two years (2 of 10).\n\n### Security \u0026 auth: Qovia +50\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- ScrapingAnt (10): One account API key with no scopes, and we found no documented rotation or revocation (10). API Basics tells you to send x-api-key as a query parameter, a documented option, so less 10 (0 of 30). The header form works and the SDKs use it. No read-only mode, and /v2/general can send POST, PUT and DELETE to target sites with no confirmation step (5 of 20). No prompt-injection guidance found for the HTML, Markdown or text it returns (0 of 15). The Ant-credits-cost header and a subscription status endpoint show spend per call. No request log found (5 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20).\n\n### Schema \u0026 documentation: Qovia +43\n\n- Qovia (86): An OpenAPI 3.1.0 file (version 0.1.0, 1 MB) is public at qovia.ai/openapi.json with 144 paths and 144 operations, two security schemes, typed query parameters, a response example on every operation and the error responses declared on each. The data payload itself is typed only as object, array or null with per-endpoint examples, and the MCP call_endpoint tool takes a free params object, so 22 of 25 (22). llms.txt (75 KB, one line per endpoint with price and status) and llms-full.txt (331 KB, the whole documentation as text) are served, and the quickstart's billing, limits and error sections are in both (10). Every operation has a summary and a description; most say what the data holds, how to page, which ids to pass, which fields are unavailable and what answers 404 or empty, and the MCP server's instructions say to find, read then call. Guidance on when not to use an endpoint is thin, mostly pointers such as replies coming from another endpoint (16 of 20). 321 parameters, 75 with enums, patterns on ids, min and max on strings and integers, 117 operations with one required parameter and 16 with none, the POST body typed with additionalProperties false, and unknown parameters rejected with 400 (14 of 15). A response example on all 144 operations, 20 error codes with every message variant listed, response headers documented per error, and cURL, Python, JavaScript and raw HTTP samples; the examples are catalogue samples the docs say are not live data (14 of 15). Paths are under /v1, a 410 endpoint_disabled code exists for retired endpoints, and the changelog is dated, but it has two days (21 and 22 October 2026), nothing is marked deprecated and no notice period is stated (10 of 15). 22+10+16+14+14+10 = 86.\n- ScrapingAnt (43): No OpenAPI or Swagger spec found. The MCP docs give a typed parameter table for the 3 tools (8 of 25). docs.scrapingant.com/llms.txt returns 404 and no Markdown twins were found (0). MCP descriptions are one line each, such as Fetch a URL and return raw HTML content, with no when-to-use guidance (8 of 20). Few parameters, typed, with proxy_type as an enum of `datacenter` or `residential` (10 of 15). Request examples on every docs page and an errors page with 8 status codes and their meanings (12 of 15). Versioned paths (v1 and v2) and no changelog (5 of 15).\n\n### Transparency \u0026 trust: ScrapingAnt +26\n\n- Qovia (30): Closed service. The Terms of Service is one paragraph that names no legal entity, address or liability terms, says Delaware law governs and that the page is a summary with the signed agreement governing; the repository's client is MIT. Between the closed and unclear bands (7 of 30). The privacy policy is one paragraph. Account information is used to deliver and bill, personal information is not sold, requests and results are not resold, deletion requests go to the support mailbox, and the agreement governs where it differs. No retention periods, no subprocessors, no DPA, and no statement about the cache the prov.source flag implies; the SECURITY.md repeats the same points (8 of 30). A 410 endpoint_disabled code exists for retired endpoints and the changelog is dated, but there is no deprecation policy or notice period and nothing is marked deprecated (5 of 20). Stripe is named on the pricing page as the card and Alipay processor; no other provider, data location or transfer basis is stated (3 of 20). 7+8+5+3 = 23.\n- ScrapingAnt (56): Closed service with terms naming DATAANT SP. Z O.O., registered in Poland (KRS 0000848755). The SDKs are Apache 2.0 (15 of 30). The privacy policy, last updated 3 November 2020, gives 12-month retention after an account closes, names processors and mentions DPAs with clients. It predates the MCP server and AI extractor, and doesn't say whether scraped content is stored (18 of 30). No deprecation policy or dated notices found (0). Processors and locations named, Sendgrid in Ireland, Paddle in the UK, Google Analytics and Amazon hosting in the USA (15 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- ScrapingAnt (40): No x402, MPP or L402 (0). Credit costs per request type (1 to 125) and plan prices are public (20). 10,000 free credits a month, no card (20). A person signs up in a browser (0).\n\n### Agent ergonomics: Qovia +11\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- ScrapingAnt (66): 3 compact MCP tools (25). Markdown and text endpoints, AI extraction, wait-for-selector and a JSON extended response, but no output-size limit on the MCP tools (12 of 20). 8 documented status codes, and 422 returns a detail field (14 of 20). Requests are reads of third-party pages and failures aren't billed, but there are no tool annotations or retry guidance beyond 423 (5 of 20). Only url is required, though browser defaults to true at 10 credits. Python and JavaScript clients exist but are stale (10 of 15).\n\n## Score by category\n\n| Category | Weight | Qovia | ScrapingAnt | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 30 | Qovia +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 43 | Qovia +43 |\n| Agent ergonomics | 13% (16.2 this run) | 77 | 66 | Qovia +11 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 10 | Qovia +50 |\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 | 5 | Qovia +72 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 30 | 56 | ScrapingAnt +26 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.2 · C** | **35.8 · F** | |\n\n## Facts side by side\n\n| Fact | Qovia | ScrapingAnt |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Qovia | ScrapingAnt (DATAANT) |\n| Hosted endpoint | `https://api.qovia.ai` | `https://api.scrapingant.com/v2/general` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\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 | 3 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| MCP registry | `ai.qovia/qovia` | not listed |\n| Last release | 2026-10-28 | 2024-07-16 |\n| Terms last updated | not read yet | no date given |\n| Privacy policy last updated | not read yet | no date given |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | yes |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | yes |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | 0 stars | 90 npm/wk, 2k PyPI/wk |\n| Agent reviews | none | 3.5/5 (2) |\n\n## How the scores have moved\n\n### Qovia\n\nNo score change since it was listed.\n\n### ScrapingAnt\n\n- +0.3 on 27 October 2026: checklist\n- -0.4 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**ScrapingAnt.** 10,000 free credits a month with no card. API Basics puts the key in the query string, so it lands in logs.\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### ScrapingAnt\n\n1. Send the key in the `x-api-key` header rather than the query string\n2. Use `/v2/markdown` for LLM input, and set `browser=false` on static pages to pay 1 credit instead of 10\n3. Switch to `proxy_type=residential` only after a 423 (anti-bot) response. It raises a browser request from 10 to 125 credits\n4. On the free plan a second concurrent request gets 409. Wait for the first to finish\n5. Google, Bing and Yandex result pages come back as raw HTML through `/v2/general`, so you parse them yourself\n\n## Questions\n\n### Which is better for AI agents, Qovia or ScrapingAnt?\n\nQovia scores 61.2 (C) on agent readiness against ScrapingAnt's 35.8 (F), and leads in 6 of 7 scored categories. ScrapingAnt leads on transparency \u0026 trust.\n\n### Do Qovia and ScrapingAnt need an API key?\n\nBoth need an API key.\n\n### Can an agent call Qovia and ScrapingAnt without installing anything?\n\nYes. Qovia has a hosted endpoint at https://api.qovia.ai and ScrapingAnt at https://api.scrapingant.com/v2/general.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/qovia-vs-scrapingant.json, and with the fewest tokens: https://www.anchorterminal.com/compare/qovia-vs-scrapingant.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"qovia\", \"b\": \"scrapingant\"}`. From a terminal: `anchor compare qovia scrapingant`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/qovia.json and https://www.anchorterminal.com/api/v1/tools/scrapingant.json\n\n## Other comparisons with Qovia or ScrapingAnt\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- [Apify MCP Server vs ScrapingAnt](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingant.md)\n- [Bright Data vs ScrapingAnt](https://www.anchorterminal.com/compare/bright-data-vs-scrapingant.md)\n- [Context.dev vs ScrapingAnt](https://www.anchorterminal.com/compare/context-dev-vs-scrapingant.md)\n- [jevcrawl vs ScrapingAnt](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingant.md)\n- [Jina Reader vs ScrapingAnt](https://www.anchorterminal.com/compare/jina-reader-vs-scrapingant.md)\n- [Olostep vs ScrapingAnt](https://www.anchorterminal.com/compare/olostep-vs-scrapingant.md)\n- [Oxylabs Web Scraper API vs ScrapingAnt](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingant.md)\n- [Scrape.do vs ScrapingAnt](https://www.anchorterminal.com/compare/scrape-do-vs-scrapingant.md)\n- [ScrapeGraphAI vs ScrapingAnt](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingant.md)\n- [Scrapeless vs ScrapingAnt](https://www.anchorterminal.com/compare/scrapeless-vs-scrapingant.md)\n- [ScraperAPI vs ScrapingAnt](https://www.anchorterminal.com/compare/scraperapi-vs-scrapingant.md)\n- [Scrapewise vs ScrapingAnt](https://www.anchorterminal.com/compare/scrapewise-vs-scrapingant.md)\n- [Scrapfly vs ScrapingAnt](https://www.anchorterminal.com/compare/scrapfly-vs-scrapingant.md)\n- [ScrapingAnt vs ScrapingBee](https://www.anchorterminal.com/compare/scrapingant-vs-scrapingbee.md)\n- [ScrapingAnt vs Scrapingdog](https://www.anchorterminal.com/compare/scrapingant-vs-scrapingdog.md)\n- [ScrapingAnt vs Spider](https://www.anchorterminal.com/compare/scrapingant-vs-spider-cloud.md)\n- [ScrapingAnt vs ZenRows](https://www.anchorterminal.com/compare/scrapingant-vs-zenrows.md)\n- [ScrapingAnt vs Zyte API](https://www.anchorterminal.com/compare/scrapingant-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 ScrapingAnt](https://www.anchorterminal.com/compare/diffbot-vs-scrapingant.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 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 ScrapingAnt](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingant.md)\n- [Firecrawl MCP vs ScrapingAnt](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapingant.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 ScrapingAnt", "url": "" } ], "description": "Qovia scores 61.2 (C) to ScrapingAnt's 35.8 (F) for extraction. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Qovia C 61.2", "ScrapingAnt F 35.8", "scores" ], "h1": "Qovia vs ScrapingAnt", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/qovia-vs-scrapingant", "published": "2026-10-01", "section": "tools", "title": "Qovia vs ScrapingAnt for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant" }, "tokens": { "markdown": 5650, "slim": 3530 }, "version": 1 }