# Qovia > 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. - Canonical: https://www.anchorterminal.com/tools/qovia - Pricing: https://www.anchorterminal.com/tools/qovia#pricing - Reviews: https://www.anchorterminal.com/tools/qovia#reviews - Markdown: https://www.anchorterminal.com/tools/qovia.md (~12,300 tokens) - Slim: https://www.anchorterminal.com/tools/qovia.min.md (~3,130 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/qovia.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT qovia.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-01 ## Overview **Grade C · 61.2/100 · rank #565 of 1253 · #14 in Web scraping & crawling · not agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Qovia (https://qovia.ai) | | Kind | HTTP API | | Category | Web scraping & crawling (https://www.anchorterminal.com/categories/web-scrapers) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://api.qovia.ai` | | Auth | API key · 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:` 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 | Pay per use ($5 / 1k req) · 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. | | x402 | No · 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. | | 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 | | Tools exposed | 141 | | Packages | pypi: `qovia` | | MCP registry name | `ai.qovia/qovia` | | Source | https://github.com/qovia/qovia-mcp | | Docs | https://qovia.ai/docs/ | | llms.txt | https://qovia.ai/llms.txt | | Last release | 2026-10-28 | | GitHub stars | 0 (as of 2026-11-01) | | Surface listed | The REST API at https://api.qovia.ai and the hosted MCP server at https://api.qovia.ai/mcp, read from the docs, the OpenAPI file, llms.txt and llms-full.txt, the MCP page, the pricing, coverage, changelog, about, contact and legal pages, the qovia/qovia-mcp repository, PyPI, the official MCP registry and the Apify Store on 1 November 2026. No account was created, no API call or MCP session was made and nothing was run; the one GET to /mcp (405) is the 1 November listing check's | | API | OpenAPI 3.1.0, version 0.1.0, 144 paths and 144 operations (143 GET, 1 POST), 321 parameters with 75 enums and patterns on ids, 4 component schemas (SuccessEnvelope, Meta, Error, Account). 137 live data endpoints across 21 platform groups, from 16 on Douyin Xingtu and 12 on Cili Juxing to 1 each on Taobao and JD.com; 6 coming soon (3 Shopee, 2 Amazon, 1 News). Each operation carries `x-qovia-price`, `x-qovia-scope`, `x-qovia-availability` and `x-qovia-status: beta`, with Chinese titles and descriptions beside the English | | Response envelope | `request_id` (the usage record ID, also in `X-Request-Id`), `data` (object, array or null) and `meta` {billed, charged_usd, balance_usd, empty}; `meta.trial_calls_remaining` counts down on trial accounts. Posts, notes and videos share one record shape (`id`, `src`, `platform`, `text`, `author`, `metrics`, `extra`, `prov` {hash, ts, source}). Headers `X-Qovia-Charged` and `X-Qovia-Balance` repeat the charge | | Credentials | API key `sk-qovia-` plus 43 characters, in `Authorization: Bearer` or `x-api-key` only. Scopes `*`, `search`, `raw:*` or `raw:` across 24 groups, picked at creation; optional `expires_at`; revocation in the console; hashed storage, shown once. GET /v1/account returns the key's scopes, expiry, balance, plan (free, payg, enterprise) and per-minute limit at no charge. Calling outside the scope answers 403 `scope_denied` | | Rate limits | 60 requests a minute per account before the first top-up, 600 after, sliding 60-second window, shared by every key and the console playground. 429 `rate_limited` with `Retry-After`; 429 `endpoint_busy` when an endpoint's global per-second cap is full (retry in 1 second, not counted against the minute); 429 `too_many_unbilled` when at least 50 calls in 10 minutes and over 80 per cent came back empty, not found or rejected; 413 above 64 KiB of body. Some endpoints are slow by design (Xingtu transcript about 8 seconds, Pugongying creator notes 5 to 10 seconds) | | Pagination | Opaque `cursor` on most list endpoints with `has_more`, `search_id` beside it on Douyin and Zhihu search, page numbers on Weibo and Xiaohongshu search (up to 50 pages) and Bilibili creator videos (up to 100), `limit` on Bilibili danmaku. Cross-platform search takes 10 or 20 results a page up to page 50, `since` and `until` as whole Beijing days up to 90, platform, content-type and sentiment filters. Page sizes are fixed per endpoint, from about 5 to 100 | | Errors | 20 codes in one `error` object. 401 `invalid_api_key`; 403 `account_disabled`, `scope_denied`; 400 `invalid_params`, `upstream_rejected`; 402 `insufficient_balance`; 404 `endpoint_not_found`, `not_found`; 405 `method_not_allowed`; 410 `endpoint_disabled`; 413 `payload_too_large`; 429 `rate_limited`, `too_many_unbilled`, `endpoint_busy`, `too_many_auth_failures`; 502 and 503 `upstream_error`; 503 `upstream_busy`, `endpoint_unavailable`; 504 `upstream_timeout`, `reservation_expired`. Upstream codes and `not_found` are refunded, the rest never charged. The docs say an unexpected 500 may be plain text and PUT or DELETE get a framework 405 | | MCP | Streamable HTTP at https://api.qovia.ai/mcp, stateless, JSON answers, protocol 2025-06-18, server version 0.1.0, tools only (no resources or prompts, `listChanged` false). Four default tools with JSON Schema inputs and `additionalProperties: false`; `call_endpoint` takes `endpoint_id` and a free `params` object. `?tools=all` adds one tool per live endpoint named after its id (`raw_douyin_video`), `?tools=` only some. Tool errors carry `error.code`, the HTTP status and `retry_after_seconds`. No tool annotations in the vendor's 28 October tools/list snapshot. Registry ai.qovia/qovia 0.1.0 (22 October) and 0.1.1 (28 October 2026); the same card at https://qovia.ai/.well-known/mcp.json | | SDK and integrations | Python client `qovia` 0.1.1 on PyPI (27 October 2026, MIT, Python 3.9 or newer, no dependencies) with `get`, `post`, `search`, `account` and a `pages` iterator, two retries on 429 and 503 honouring `Retry-After`. Node and curl examples. Claude Code plugin and marketplace manifests, a Cursor plugin manifest, a Gemini CLI extension with GEMINI.md, an mcp.json and an llms-install.md for Cline. Five Actors on the Apify Store under the profile `qovia` (Qovia Data, joined October 2026, 10 users) | | Prices | Search $0.005 a call. Fixed-price raw endpoints at $0.0005 (15), $0.001 (61), $0.0015 (18), $0.002 (3), $0.005 (11), $0.01 (21), $0.0135 (Taobao reviews) and $0.0195 (JD.com reviews) a call. Tieba, Fliggy and the six coming-soon endpoints at a tiered $0.0015, $0.001 past 5,000,000 billed calls in a calendar month. 50 trial calls, then prepaid top-ups by card or Alipay through Stripe (4.4 per cent plus $0.30) or USDT TRC-20 (2 per cent plus $0.30). The Xingtu Actor on Apify costs $0.01 a basic section, $0.06 a premium section and $0.03 a video section per creator | | SLA | None. The terms summary says nothing about uptime, and the pricing FAQ counts temporary outages, rate limits and platform changes as no ground for a refund. The 11 September 2026 archived home page advertised a 99.95 per cent enterprise SLA; the current pages do not | | Data handling | The privacy policy is one paragraph. Account information (email, company) is used to deliver the service and bill, personal information is not sold, requests and returned results are not resold, deletion requests go to the support mailbox, and a signed agreement governs where it differs. No retention periods, subprocessors, data locations or DPA. Stripe is named for payments on the pricing page. Responses carry `prov.source` (live or cache) and a capture time, so some results are cached, with no stated period. The vendor says it is an unofficial data service and users are responsible for downstream use under the law and the source platforms' rules | | Status | No status page. https://qovia.ai/status/ answers 404, status.qovia.ai does not resolve and neither the docs nor the footer links one | | 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 | | JSON | https://www.anchorterminal.com/api/v1/tools/qovia.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-11-01 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 40 | 8.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 86 | 14.0 | | Agent ergonomics | 13% | 16.2 | 77 | 12.5 | | Security & auth | 14% | 17.5 | 60 | 10.5 | | Payments & pricing | 10% | 12.5 | 55 | 6.9 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 77 | 6.7 | | Transparency & trust (editorial 23, provenance 36) | 7% | 8.8 | 30 | 2.6 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **61.2 → C** | ### Why each score - Reliability 40 (checked 2026-11-01): 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. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 86 (checked 2026-11-01): 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. - Agent ergonomics 77 (checked 2026-11-01): 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. - Security & auth 60 (checked 2026-11-01): 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. - Payments & pricing 55 (checked 2026-11-01): 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. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 77 (checked 2026-11-01): 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. - Transparency & trust 30 (checked 2026-11-01): 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. Fix list, everything this grade says the listing lacks, the biggest gain first (26 items). What it covers is at https://www.anchorterminal.com/fixes/qovia.md (JSON https://www.anchorterminal.com/fixes/qovia.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "qovia", "plan": "read"}`, free while the beta runs ### What we couldn't check - Kind is `http-api`. The quickstart leads with a key, a top-up, GET /v1/account and a first REST call, llms.txt lists the API first and the MCP server as one line, the OpenAPI file is the contract, and the MCP server's four tools wrap the same endpoints through call_endpoint. The use-cases page calls Qovia an MCP server and the registry entry is DNS-verified, so the MCP server is described in full; on the MCP reading, ergonomics would rise (four compact tools with ?tools= subsets) and the rest would stand. - unchecked: the live tools/list, tool annotations, the ?tools=all tool count and whether tools/list is paged. No session was opened; the four tools are read from the vendor's 28 October 2026 snapshot in the repository, and 141 is 4 plus the 137 live endpoints the docs say ?tools=all adds. - unchecked: whether sign-up asks for a card, whether the 50 trial calls work before a top-up, and whether keys can be rotated. No account was created. The docs describe trial calls, a prepaid balance and keys created with scopes and an optional expiry. - unchecked: the endpoint_busy per-second cap, which has no number, and whether Retry-After is sent as documented. No call was made. - Where the data comes from. The about page says every platform has its own signing, accounts and anti-bot rules and that Qovia keeps up with them and sells the result per call; the terms call it an unofficial data service with no affiliation to the platforms and make users responsible for downstream use under applicable law and the source platforms' rules; the Xingtu coverage page says Xingtu's data is normally viewed inside the Ocean Engine dashboard by brands and agencies, and Pugongying note search covers registered creators only. Whether the vendor holds platform accounts or licences for Xingtu, Pugongying, Cili Juxing and Huahuo is not stated. 'Public data', '20+ platforms' and '100+ endpoints' are the vendor's words; the OpenAPI file has 137 live endpoints across 21 platform groups, which supports the counts. - The legal entity. The terms and privacy pages name none, say Delaware law governs and defer to a signed agreement; the footer reads © 2026 QoviaAI; RDAP shows a Domains By Proxy registrant; the PyPI, GitHub and Apify records name only Qovia and a mailbox. Web searches for a Qovia company, a Delaware filing or funding found nothing first-hand. legalEntity is recorded as absent. - firstReleased is 2026-10-21, the changelog's first dated entry, when search, Xiaohongshu, WeChat, Taobao and JD are recorded as live; the other platforms, the registry entry and the MCP guide are dated 22 October and the repository 23 October. The 11 September 2026 Wayback copy sold an API key with a free 1,000 calls a month and showed a search widget labelled live, but dates nothing and its figures (10B+ records a month, under 900 ms p95, 99.95 per cent SLA, 25+ platforms) are gone from the current site. Recorded as site history, not deducted, since the current pages make none of those claims. - Every endpoint carries x-qovia-status beta in the OpenAPI file while the docs, llms.txt and coverage pages label the same endpoints Live. Scored at 5 of 10 for general availability and listed as a weakness; not deducted, since the file is the vendor's own disclosure. - The home page's 'What's new' dates every platform launch to 22 October while the changelog also has 21 October entries, and llms.txt says 143 endpoints where llms-full.txt says 137 live; both agree with the OpenAPI file once the six coming-soon endpoints are counted or not. - The product is ten days old at the check by its own changelog, so the maintenance and transparency scores rest on a short record, as the checklist reads it, not on where it may go. - The vendor's GitHub account (created 23 October 2026) holds nine forks of awesome-lists and directories beside the one repository, the footer carries about thirty directory badges, and llms-install.md and GEMINI.md address AI agents directly. Read as data; recorded as a fact about the site. - The Apify Store profile qovia (Qovia Data) is taken as the same vendor because it names the same Telegram handle and mailbox as qovia.ai; the payments score gives 10 of 40 for that third-party route, as for ScrapeAtlas's Actors. - Qovia doesn't do LocalGhost's or letme's job. It returns platform data for an agent to use; it neither hides an agent's identity nor chooses tools for a task. ### Sources - home page: (seen 2026-11-01) - quickstart with auth, scopes, billing, rate limits and errors: (seen 2026-11-01) - API reference index: (seen 2026-11-01) - MCP page: (seen 2026-11-01) - OpenAPI 3.1 file: (seen 2026-11-01) - llms.txt: (seen 2026-11-01) - llms-full.txt: (seen 2026-11-01) - pricing page with FAQ and fees: (seen 2026-11-01) - changelog (What's new): (seen 2026-11-01) - platform directory with live, coming soon and planned: (seen 2026-11-01) - Douyin Xingtu coverage page (marketplace data): (seen 2026-11-01) - Douyin coverage page: (seen 2026-11-01) - AI agents use case: (seen 2026-11-01) - MCP guide (dated 22 October 2026): (seen 2026-11-01) - enterprise and custom data page: (seen 2026-11-01) - datasets catalogue: (seen 2026-11-01) - about page: (seen 2026-11-01) - contact page: (seen 2026-11-01) - Terms of Service: (seen 2026-11-01) - privacy policy: (seen 2026-11-01) - robots.txt: (seen 2026-11-01) - MCP server card: (seen 2026-11-01) - agent discovery file: (seen 2026-11-01) - sitemap: (seen 2026-11-01) - official MCP registry: (seen 2026-11-01) - repository README: (seen 2026-11-01) - repository SECURITY.md: (seen 2026-11-01) - tools/list snapshot of 28 October 2026: (seen 2026-11-01) - Python client source: (seen 2026-11-01) - repository metadata and commits (GitHub API): (seen 2026-11-01) - PyPI, qovia: (seen 2026-11-01) - Apify Store profile, Qovia Data: (seen 2026-11-01) - Apify Store, Xingtu Actor pricing: (seen 2026-11-01) - RDAP for qovia.ai: (seen 2026-11-01) - Wayback Machine capture of 11 September 2026: (seen 2026-11-01) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/qovia/history.json - 2026-11-01: graded 61.2 C (methodology 0.7) ## Who's behind it (provenance 36/100, checked 2026-11-01) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | not found | 0/20 | | Domain age | qovia.ai, registered 2026-07-04 (under a year) | 0/15 | | Endpoint on the vendor's domain | api.qovia.ai | 15/15 | | Terms of service | published, not read by us yet | 4/10 | | Privacy policy | published, not read by us yet | 4/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | | People named | not researched yet | n/a | | Support route | a support address, help pages, a community | 5/5 | 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://qovia.ai/terms/), not read yet. **Privacy policy** (https://qovia.ai/privacy/), not read yet. ## Humans behind the project (researched 2026-11-01 from public pages, not part of the grade) ### Key people - No people named yet. - Note: No person has a role on any first-hand page. The about page describes the product only, the terms and privacy pages name no company or person, and the contact page gives a Telegram handle, a WhatsApp link, a WeChat QR code and one mailbox without a name. The PyPI package, the plugin manifests and the Apify Store profile give the author as Qovia with the same mailbox and Telegram handle; a first name appears in that mailbox and handle but no page gives the person a role, so nobody is listed. The submitter's name was not used. The 11 September 2026 Wayback copy of the home page linked a LinkedIn company page (linkedin.com/company/qovia-ai) and an X account that the current footer no longer carries; LinkedIn was not opened. The current footer, the README and the Apify profile link the X account @QoviaAI and the GitHub account qovia. Ownership is unknown because no page names a legal entity; the terms say Delaware law governs and that a signed agreement governs. Investors were looked for on qovia.ai (about, contact, products, enterprise, pricing, changelog, terms, privacy, the sitemap, which has no blog or press section), in the repository and the GitHub user record, on PyPI and the Apify profile, and in web searches for the company, a legal entity, a Delaware filing and a funding round, which returned only unrelated companies with similar names and a directory profile; nothing on a round. - Qovia: X https://x.com/QoviaAI GitHub https://github.com/qovia ### Getting support - Support email: scott@qovia.ai - Help: https://qovia.ai/contact/ - Help: https://qovia.ai/docs/ - Community (Telegram support): https://t.me/scott10081 - Community (GitHub issues, qovia/qovia-mcp): https://github.com/qovia/qovia-mcp/issues - Sources: https://qovia.ai/about/, https://qovia.ai/contact/, https://qovia.ai/terms/, https://qovia.ai/privacy/, https://qovia.ai/, https://qovia.ai/sitemap.xml, https://github.com/qovia/qovia-mcp, https://api.github.com/users/qovia, https://pypi.org/pypi/qovia/json, https://apify.com/qovia, https://registry.modelcontextprotocol.io/v0/servers?search=qovia, https://rdap.identitydigital.services/rdap/domain/qovia.ai, https://web.archive.org/web/20260911151935/https://qovia.ai/ ## Live (updated 2026-11-01 21:32 UTC) - Right now: up, HTTP 200, 569 ms, checked 2026-11-01 21:32 UTC (get on `https://api.qovia.ai`) - Uptime 24h 100.0% (19 probes) · 30 days 100.0% (19 probes) · p50 524 ms · p95 657 ms - Always current: https://www.anchorterminal.com/api/v1/live/qovia.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Cross-platform search | $5 | per 1,000 requests | POST /v1/search, successful non-empty calls only, pricing page and OpenAPI file checked 1 November 2026 | | Lowest raw endpoints (Douyin, Bilibili, Xingtu keywords) | $0.50 | per 1,000 requests | 15 fixed-price endpoints at $0.0005 a successful call | | Most raw endpoints (TikTok, YouTube, X, Reddit, Weibo, Zhihu, Kuaishou and others) | $1 | per 1,000 requests | 61 fixed-price endpoints at $0.001 a successful call | | Tiered raw endpoints (Tieba, Fliggy, coming-soon platforms) | $1.50 | per 1,000 requests | $1 per 1,000 after 5,000,000 billed calls in a calendar month | | Xiaohongshu and WeChat endpoints | $5 | per 1,000 requests | 11 fixed-price endpoints at $0.005 a successful call | | Xingtu and Pugongying creator marketplace endpoints | $10 | per 1,000 requests | 21 fixed-price endpoints at $0.01 a successful call | | JD.com product reviews | $19.50 | per 1,000 requests | the dearest endpoint; Taobao and Tmall reviews are $13.5 | | Apify Store, Xingtu Actor premium section | $0.06 | per record | per creator per section, paid through Apify with no Qovia account; basic sections $0.01, video sections $0.03 | Across all listings: https://www.anchorterminal.com/prices/index.md ## 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 ## Before you call it (notes for agents) 1. 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. 2. 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. 3. 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`. 4. 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. 5. 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. ## Connect Install: ```bash pip install qovia ``` First request: ```bash curl "https://api.qovia.ai/v1/raw/weibo/hot_search" -H "Authorization: Bearer $QOVIA_API_KEY" ``` Claude Code: ```bash claude mcp add --transport http qovia https://api.qovia.ai/mcp --header "Authorization: Bearer $QOVIA_API_KEY" ``` Through letme: https://letme.dev/qovia. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Tavily API + MCP | BB | 77.1 | 30 | web.search, web.extract | no | https://www.anchorterminal.com/tools/tavily-mcp.md | | You.com APIs | BB | 76.1 | 38 | web.search, web.extract | no | https://www.anchorterminal.com/tools/you-com-api.md | | Context.dev | BB | 75.7 | 46 | web.extract, web.search | no | https://www.anchorterminal.com/tools/context-dev.md | | Firecrawl MCP | BB | 75 | 59 | web.search, web.extract | no | https://www.anchorterminal.com/tools/firecrawl-mcp.md | | Parallel Search and Task APIs | BB | 75 | 60 | web.search, web.extract | no | https://www.anchorterminal.com/tools/parallel-search-api.md | | Spider | BB | 74.6 | 65 | web.extract, web.search | yes | https://www.anchorterminal.com/tools/spider-cloud.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The OpenAPI 3.1 file (version 0.1.0, 1 MB) has 144 paths and 144 operations, 143 GET and 1 POST, of which 137 are live data endpoints across 21 platform groups, 6 marked coming soon (Shopee, Amazon, News, answering 503 `endpoint_unavailable`) and GET /v1/account. Every operation carries a response example, the 401, 403 and 429 responses, and most the 400, 402, 404, 502, 503 and 504 responses; every endpoint also carries `x-qovia-status: beta` while the docs label it Live (source: ) - Every success is HTTP 200 with `request_id`, `data` and `meta` {billed, charged_usd, balance_usd, empty}; every error is `{error: {code, message, request_id, support}}` with 20 codes, retryable ones marked, and the docs say to branch on `code` because one code has several messages (source: ) - Limits are 60 requests a minute per account before the first top-up and 600 after, on a sliding 60-second window shared by every key and the console playground, with `X-RateLimit-Limit` and `X-RateLimit-Remaining` headers and `Retry-After` on 429 and 503 answers; 50 or more calls in 10 minutes with over 80 per cent empty, not found or rejected answer 429 `too_many_unbilled` (source: ) - The remote MCP server at https://api.qovia.ai/mcp is stateless Streamable HTTP with four tools by default, `search_endpoints`, `get_endpoint`, `call_endpoint` and `get_account`; `?tools=all` adds one typed tool per live endpoint and `?tools=douyin,kuaishou` only some platforms. It is in the official MCP registry as ai.qovia/qovia 0.1.1 under a DNS-verified namespace (source: ) - The vendor calls itself an unofficial data service with no affiliation to the platforms, says users are responsible for downstream use under applicable law and the source platforms' rules, and four endpoint groups (Douyin Xingtu, Xiaohongshu Pugongying, Cili Juxing, Huahuo) read creator marketplaces the vendor says are normally viewed inside dashboards by brands and agencies (source: ) - The terms and privacy policy are one paragraph each, name no legal entity, address or retention period, say Delaware law governs and that the signed agreement governs where it differs; support is Telegram, WhatsApp, WeChat and one mailbox (source: ) - No status page (/status answers 404, status.qovia.ai does not resolve), no security.txt on either host, no SLA; the repository's SECURITY.md gives a reporting address. The dated changelog has two days, 21 and 22 October 2026, and the domain was registered on 4 July 2026 (source: ) - The Python client on PyPI (qovia 0.1.1, 27 October 2026, MIT, standard library only) retries 429 and 503 answers honouring `Retry-After`; Claude Code, Cursor and Gemini CLI plugin manifests and an llms-install.md for agents sit in the same repository (source: ) - #14 of 23 in Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md - All 261 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md ## Compare - [Bright Data vs Qovia](https://www.anchorterminal.com/compare/bright-data-vs-qovia.md): C 60 vs C 61.2 - [Firecrawl MCP vs Qovia](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia.md): BB 75 vs C 61.2 - [Context.dev vs Qovia](https://www.anchorterminal.com/compare/context-dev-vs-qovia.md): BB 75.7 vs C 61.2 - [Diffbot vs Qovia](https://www.anchorterminal.com/compare/diffbot-vs-qovia.md): C 54.3 vs C 61.2 - [jevcrawl vs Qovia](https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.md): B 64.3 vs C 61.2 - [Olostep vs Qovia](https://www.anchorterminal.com/compare/olostep-vs-qovia.md): B 63.1 vs C 61.2 - [Oxylabs Web Scraper API vs Qovia](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.md): B 63.1 vs C 61.2 - [Qovia vs ScrapeAtlas](https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.md): C 61.2 vs B 62.8 - [Qovia vs ScrapeGraphAI](https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.md): C 61.2 vs B 68.3 - [Qovia vs ScraperAPI](https://www.anchorterminal.com/compare/qovia-vs-scraperapi.md): C 61.2 vs D 52.1 - [Qovia vs Scrapewise](https://www.anchorterminal.com/compare/qovia-vs-scrapewise.md): C 61.2 vs B 62.6 - [Qovia vs Scrapfly](https://www.anchorterminal.com/compare/qovia-vs-scrapfly.md): C 61.2 vs BB 74.5 - [Qovia vs ScrapingAnt](https://www.anchorterminal.com/compare/qovia-vs-scrapingant.md): C 61.2 vs F 35.8 - [Qovia vs ScrapingBee](https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.md): C 61.2 vs C 59.4 - [Qovia vs Scrapingdog](https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.md): C 61.2 vs E 39.3 - [Qovia vs Spider](https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.md): C 61.2 vs BB 74.6 - [Qovia vs ZenRows](https://www.anchorterminal.com/compare/qovia-vs-zenrows.md): C 61.2 vs BB 75.9 - [Qovia vs Zyte API](https://www.anchorterminal.com/compare/qovia-vs-zyte.md): C 61.2 vs B 69.7 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on qovia.ai or one of its subdomains, or the README at the root of github.com/qovia/qovia-mcp. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "qovia", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Qovia on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Qovia on Anchor Terminal](https://www.anchorterminal.com/badges/qovia.svg)](https://www.anchorterminal.com/tools/qovia) ``` Plain link: ```html Qovia on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Qovia is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/qovia-dark.png - Light: https://www.anchorterminal.com/assets/share/qovia-light.png - Create a video and download its frames: https://www.anchorterminal.com/assets/listing-video/index.html?listing=qovia --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp