Qovia

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.