{ "data": { "a": { "slug": "nexscope", "name": "Nexscope", "vendor": "ECOCREATE TECHNOLOGY PTE. LTD.", "vendorUrl": "https://www.nexscope.ai", "kind": "platform", "category": "web-scrapers", "summary": "Nexscope is a hosted platform for ecommerce sellers with marketplace product, keyword and competitor data for Amazon, TikTok Shop, Walmart, Temu, 1688 and others, plus AI product images and video, through a web app, REST API and remote MCP server.", "url": "https://www.anchorterminal.com/tools/nexscope", "markdownUrl": "https://www.anchorterminal.com/tools/nexscope.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nexscope.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nexscope.json", "dns": "nexscope.grade.anchorterminal.com", "repo": "https://github.com/nexscope-ai/nexscope-ecommerce-api", "license": "Proprietary hosted service under the Nexscope terms (last updated 8 October 2026), whose contracting party is ECOCREATE TECHNOLOGY PTE. LTD. of Singapore. The OpenAPI file's licence is 'Proprietary API; use subject to Nexscope Terms'. In github.com/nexscope-ai/nexscope-ecommerce-api only the example clients, validation scripts, tests and workflow are MIT. The API documentation, catalogue, definitions and sample data stay copyright Nexscope", "transports": [ "streamable-http", "http" ], "remoteUrl": "https://api.nexscope.ai/mcp", "packages": [], "auth": "mixed", "authNotes": "The remote MCP server takes OAuth 2.1 (authorisation code with PKCE, scope `mcp:tools`) in clients that support it, or a Nexscope API key as `Authorization: Bearer nk-...`, which the tool pages call a compatibility option. The REST API takes the same key as a Bearer header. A person signs in and creates the key under API Access, API Keys. The full key is shown once, and keys can be expired, disabled or deleted, per the help page's troubleshooting. No key scopes, rotation rule or key-management API were found. Creative API key access needs an active subscription. Trial credits don't enable it. The OAuth metadata on api.nexscope.ai was not read (https://www.nexscope.ai/mcp-map/amazon-search, https://www.nexscope.ai/help/skills-external-access, https://github.com/nexscope-ai/nexscope-ecommerce-api, checked 2026-11-10).", "pricing": "paid", "pricingNotes": "Credits on a monthly subscription. A Free Trial gives 1,000 credits for 3 days with no card, at 1 API and 1 MCP request a second and 1 concurrent each, with no video API. Starter is $29 a month for 30,000 credits (3 requests a second, 2 concurrent), Growth $55 for 75,000 (5 and 4) and Pro $129 for 150,000 (10 and 8), each half price for the first period, with yearly billing and credits that reset monthly and don't roll over. Pay-as-you-go top-ups buy Data credits only, with no subscription. Each tool has its own credit cost, at least 10 for a Data API call. Amazon Search shows 'from 21 credits per call' and a recent average of 30. Refunds within 7 days if unused, per the terms. The home page listed Growth at $69 on the same day (https://www.nexscope.ai/pricing, https://www.nexscope.ai/mcp-map, https://www.nexscope.ai/terms, checked 2026-11-10).", "priceSummary": "$0.001 / credit", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page, the API quickstart, the MCP map, llms.txt, the visible part of the OpenAPI file or the GitHub repository on 2026-11-10. Credits come from a subscription or a Data top-up after a browser sign-in (https://www.nexscope.ai/pricing).", "endpoints": [] }, "toolCount": 382, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-10" }, "docsUrl": "https://www.nexscope.ai/api-docs", "llmsTxt": "https://www.nexscope.ai/llms.txt", "openapi": "https://api.nexscope.ai/openapi.json", "registryName": "io.github.nexscope/ecommerce", "capabilities": [ "web.extract", "shopping.search", "shopping.prices", "seo.keywords", "seo.backlinks", "search.serp", "image.generate", "image.edit", "video.generate", "video.image-to-video" ], "tags": [ "hosted", "official", "closed-source", "mcp", "remote-mcp", "oauth", "api-key", "openapi", "llms-txt", "marketplace", "shopping", "images", "video", "credits", "subscription", "free-trial", "no-card", "new" ], "lastRelease": "2026-11-09", "graded": true, "anchor": { "graded": true, "score": 46.2, "grade": "D", "agentReady": false, "rank": 1191, "ranked": true, "rankOf": 1520, "categoryRank": 28, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 44, "maintenance": 65, "payments": 35, "reliability": 39, "schema": 64, "security": 41, "transparency": 41 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-10" }, "negative": 0, "verdict": "An agent can reach Amazon, TikTok Shop, Temu, 1688 and other marketplace data, plus image and video models, on one credit balance through a remote MCP server with OAuth or a REST API with a public OpenAPI file. The connection loads 382 tools at once, and there is no status page, changelog or idempotency key.", "bestFor": "Agents that research ecommerce products, competitors, keywords, sourcing and patents across Amazon, TikTok Shop, Walmart, Temu, 1688 and other marketplaces, and that also make listing images and video, on one credit balance.", "strengths": [ "Marketplace product, keyword, competitor and sourcing data across more than ten marketplaces behind one key and one MCP endpoint", "OAuth 2.1 with PKCE and a `mcp:tools` scope on the MCP server, or a Bearer key shown once", "A public OpenAPI 3.1 file and a GitHub repository with request and response definitions, samples and standard-library clients for every documented API", "Per-plan API and MCP request limits published, and a 3-day trial of 1,000 credits with no card", "1688 order, payment-link, receipt and cancel calls each need an explicit JSON `true` confirmation field" ], "weaknesses": [ "The MCP connection advertises the full catalogue of 382 tools, with no toolsets or read-only subset", "No status page, SLA, public changelog or security.txt found", "No idempotency keys, and business errors answer HTTP 200 unless a header asks otherwise", "The privacy policy states no retention periods and names no hosting, AI or data suppliers", "Many Data definitions are field descriptors rather than JSON Schema, and the Amazon Search tool page omits the `keyword` argument its own examples pass" ], "agentNotes": [ "Check the outer `code` is 0 before reading `data`, or send `X-Nexscope-Http-Status: semantic` to get HTTP error statuses.", "Call an image or video tool once, keep the `taskId`, and poll `nexscope_media_task_result`. A second call bills a second job.", "Read the tool's credit cost before a call. Each tool costs at least 10 credits and some cost over 300.", "Before you set a 1688 confirmation field to `true`, show the user the preview and get approval.", "If the server returns 429 or 503, wait for `Retry-After` when present and back off." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 46.2 } ], "editorialScores": { "ergonomics": 44, "maintenance": 65, "payments": 35, "reliability": 39, "schema": 64, "security": 41, "transparency": 33 }, "provenanceScore": 48, "checked": { "categories": { "ergonomics": "2026-11-10", "maintenance": "2026-11-10", "payments": "2026-11-10", "reliability": "2026-11-10", "schema": "2026-11-10", "security": "2026-11-10", "transparency": "2026-11-10" }, "last": "2026-11-10", "oldest": "2026-11-10", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl --fail-with-body -X POST 'https://api.nexscope.ai/api/skill-api/v1/skills/amazon-search/run' \\\n -H \"Authorization: Bearer $NEXSCOPE_API_KEY\" \\\n -H 'Content-Type: application/json' \\\n -H 'X-Nexscope-Http-Status: semantic' \\\n -d '{\"keyword\":\"phone case\",\"page\":1}'", "config": { "mcpServers": { "nexscope": { "headers": { "Authorization": "Bearer YOUR_NEXSCOPE_API_KEY" }, "type": "streamableHttp", "url": "https://api.nexscope.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/web.extract", "tool": "https://letme.dev/nexscope" }, "area": "web-data", "unitPrices": [ { "item": "Nexscope credit (Starter)", "unit": "credit", "usd": 0.00097, "note": "$29 a month for 30,000 credits, half price in the first month. Credits reset monthly" }, { "item": "Nexscope credit (Pro)", "unit": "credit", "usd": 0.00086, "note": "$129 a month for 150,000 credits" }, { "item": "Amazon Search tool call (Starter)", "unit": "call", "usd": 0.029, "note": "A recent average of 30 credits, range 16 to 94, per the MCP tool page on 10 November 2026. About 20 results a page" }, { "item": "Starter plan", "unit": "month", "usd": 29, "note": "30,000 credits, 3 API and 3 MCP requests a second, 2 concurrent each" } ], "provenance": { "legalEntity": "ECOCREATE TECHNOLOGY PTE. LTD.", "domain": "nexscope.ai", "domainRegistered": "2026-03-04", "domainNote": "RDAP (Identity Digital) gives nexscope.ai a registration date of 4 March 2026 through GoDaddy, with the registrant behind Domains By Proxy. The terms and privacy policy name ECOCREATE TECHNOLOGY PTE. LTD., 'a company incorporated in Singapore', with no registration number or street address.", "endpointOnVendorDomain": true, "terms": "https://www.nexscope.ai/terms", "privacy": "https://www.nexscope.ai/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-10", "notes": [ "The terms (last updated 8 October 2026) name ECOCREATE TECHNOLOGY PTE. LTD. under the laws of Singapore with SIAC arbitration seated in Singapore, cap liability at the amount paid in the six months before a claim, promise no availability, permit the official APIs and MCP integrations within plan limits, forbid bots and scrapers outside them, and give notice of material changes through the service or by email.", "The privacy policy (last updated 8 October 2026) names the same company, says uploaded materials are not used to train AI models, names Google Analytics, Microsoft Clarity, Ahrefs Analytics, Google Ads, X advertising and FirstPromoter, lists hosting, storage, AI processing, payment, email, support and authentication providers only by type, gives no retention periods ('this policy does not specify a single deletion deadline for all data') and mentions no DPA.", "https://www.nexscope.ai/.well-known/security.txt answered a client error. No status page or changelog is linked from the home page, llms.txt, the API quickstart or the MCP map.", "robots.txt on www.nexscope.ai gives `*` and twelve named crawlers, ClaudeBot among them, the same rules and disallows /api/ and /share/. Nothing there was fetched. api.nexscope.ai publishes no robots.txt (/robots.txt answers a JSON login error). Only /openapi.json and one GET to /mcp were sent there, per the batch. The MCP registry's /robots.txt answered a client error.", "firstReleased is 2026-08-07, the date on Nexscope's launch post ('Updated Aug 07, 2026', no earlier publication date shown), which names API, MCP and Skills as the ways to connect an agent and 1,000 free starting credits. The API repository dates its snapshot of an already public directory of 225 APIs to 10 September 2026, and the OpenAPI version label is 2026-08-28-public-catalog-v1. The domain dates from 4 March 2026 and the npm `nexscope` skills CLI from 20 March 2026, but neither reaches the API. lastRelease is 2026-11-09, when the 1688 procurement API contracts were synced as released." ], "score": 48 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nexscope.json", "live": { "slug": "nexscope", "probe": { "target": "https://api.nexscope.ai/mcp", "method": "get", "lastAt": "2026-11-11T06:59:50.048088824Z", "lastOk": true, "lastStatus": 405, "lastMs": 305, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 271, "p95ms24h": 358, "samples24h": 43, "samples30d": 43, "days": [ { "date": "2026-11-11", "probes": 43, "ok": 43 } ], "since": "2026-11-11T02:53:20.057234625Z" }, "githubStars": 18, "updatedAt": "2026-11-11T06:59:50.048088824Z" }, "streak": { "days": 0, "from": "2026-11-11", "sinceWatching": true, "best": 0 } }, "answer": "Qovia scores 61.2 (C) on agent readiness against Nexscope's 46.2 (D), and leads in 6 of 7 scored categories. Nexscope leads on transparency \u0026 trust.", "b": { "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": 627, "ranked": true, "rankOf": 1520, "categoryRank": 18, "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-11T06:59:56.399668139Z", "lastOk": true, "lastStatus": 200, "lastMs": 561, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 488, "p95ms24h": 573, "samples24h": 244, "samples30d": 2259, "days": [ { "date": "2026-11-01", "probes": 44, "ok": 44 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 243, "ok": 243 }, { "date": "2026-11-08", "probes": 243, "ok": 243 }, { "date": "2026-11-09", "probes": 243, "ok": 243 }, { "date": "2026-11-10", "probes": 244, "ok": 244 }, { "date": "2026-11-11", "probes": 72, "ok": 72 } ], "since": "2026-11-01T00:00:00Z" }, "versions": [ { "registry": "mcp-registry", "name": "ai.qovia/qovia", "version": "0.1.1", "seenAt": "2026-11-10T19:22:02.357354042Z" }, { "registry": "pypi", "name": "qovia", "version": "0.1.1", "released": "2026-10-27", "seenAt": "2026-11-11T06:30:15.794367614Z" } ], "pypiWeekly": 15, "securityTxt": { "url": "https://qovia.ai/.well-known/security.txt", "state": "valid", "expires": "2027-11-06T00:00:00.000Z", "checkedAt": "2026-11-10T16:09:08.998304896Z" }, "llmsTxt": { "url": "https://qovia.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-10T15:44:21.168677212Z" }, "domain": { "domain": "qovia.ai", "registered": "2026-07-04", "source": "https://rdap.identitydigital.services/rdap/domain/qovia.ai", "checkedAt": "2026-11-08T14:50:57.681038601Z" }, "pages": [ { "url": "https://qovia.ai/changelog/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-10T16:28:57.044163277Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f876293b4cbf" }, { "url": "https://qovia.ai/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-10T16:28:59.254321355Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6713947e7188" }, { "url": "https://qovia.ai/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-10T16:29:01.209274183Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "88cfcd770908" } ], "mcpTools": { "url": "https://api.qovia.ai/mcp", "checkedAt": "2026-11-11T02:43:54.321384921Z", "status": "ok", "protocol": "2025-11-25", "tools": [ { "name": "search_endpoints", "title": "Search Qovia Endpoints", "description": "Search Qovia's data endpoints by keyword (Chinese or English) and/or platform slug (douyin, tiktok, xiaohongshu, pgy, bilibili, tieba, wechat, taobao, jd, fliggy, xingtu, huahuo, cljx, ...). Returns ids, titles, price per call and whether each endpoint is live. Free; no sign-in required.", "inputSchema": { "additionalProperties": false, "properties": { "include_unavailable": { "default": false, "description": "Also list endpoints that are not live yet", "type": "boolean" }, "platform": { "description": "Platform slug", "maxLength": 50, "type": "string" }, "query": { "description": "Words in the id, path or title", "maxLength": 100, "type": "string" } }, "type": "object" }, "annotations": { "destructiveHint": false, "readOnlyHint": true, "title": "Search Qovia Endpoints" } }, { "name": "get_endpoint", "title": "Get Endpoint Details", "description": "Show one endpoint: what it returns, its parameters (JSON Schema), example parameters, a response example and the price. Free; no sign-in required.", "inputSchema": { "additionalProperties": false, "properties": { "endpoint_id": { "description": "e.g. raw.douyin.video", "type": "string" } }, "required": [ "endpoint_id" ], "type": "object" }, "annotations": { "destructiveHint": false, "readOnlyHint": true, "title": "Get Endpoint Details" } }, { "name": "call_endpoint", "title": "Call Qovia Endpoint", "description": "Run an endpoint and return its data plus billing info (charged_usd and remaining credit). Requires a Qovia account connected to this MCP server; billed only when data is returned, so empty results and failures are free.", "inputSchema": { "additionalProperties": false, "properties": { "endpoint_id": { "description": "e.g. raw.douyin.video", "type": "string" }, "params": { "description": "The endpoint's parameters (see get_endpoint)", "type": "object" } }, "required": [ "endpoint_id" ], "type": "object" }, "annotations": { "destructiveHint": false, "openWorldHint": true, "readOnlyHint": true, "title": "Call Qovia Endpoint" } }, { "name": "get_account", "title": "Get Qovia Account", "description": "Show the connected Qovia account's credit, plan and rate limit. Free; counts toward the rate limit.", "inputSchema": { "additionalProperties": false, "properties": {}, "type": "object" }, "annotations": { "destructiveHint": false, "readOnlyHint": true, "title": "Get Qovia Account" } } ], "schemaTokens": 653, "changedAt": "2026-11-07T01:47:04.314060831Z", "check": { "checker": "anchor-check/1.0", "totalTokens": 653, "counts": { "error": 0, "note": 1, "warn": 1 }, "findings": [ { "rule": "TC13", "severity": "warn", "tool": "call_endpoint", "message": "params (object with no properties)", "fix": "Declare the properties (or additionalProperties with a schema) and the array's items." }, { "rule": "TC24", "severity": "note", "message": "4 of 4 tools have no outputSchema", "fix": "Declare outputSchema for tools that return structured data, and return structuredContent that matches it." } ] } }, "github": { "repo": "qovia/qovia-mcp", "checkedAt": "2026-11-02T08:22:59.675177389Z", "stars": 0, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-01T09:41:18Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0 }, "updatedAt": "2026-11-11T06:59:56.399668139Z" }, "streak": { "days": 10, "from": "2026-11-01", "sinceWatching": true, "best": 10 } }, "edges": [ { "by": 33, "category": "ergonomics", "leads": "qovia", "name": "Agent ergonomics", "reasons": { "a": "Read on the MCP server, with the REST API where a line covers it. The MCP map lists 382 tools and says the category manifests 'narrow metadata for your integration; the MCP connection still advertises the full catalog'. That is more than 30 tools with no toolsets, dynamic loading or read-only subset found (5). Search tools page by `page` (about 20 results), with filters such as marketplace, category node, sort and device per tool, but no general pagination model or field selection, and output size depends on each tool (12 of 20). By default business errors answer HTTP 200 with an outer `code`. The `X-Nexscope-Http-Status: semantic` header maps them to HTTP statuses, the OpenAPI file names codes such as `DATA_IMAGE_DOWNLOAD_FAILED` and `CAPABILITY_BACKEND_UNAVAILABLE` in field text, and MCP errors aren't documented. SandBase earned 16 with typed bridge errors (11 of 20). Data calls only read. No idempotency keys and no readOnlyHint or destructiveHint documented. Async jobs return a `taskId` with a poll tool and a rule not to resubmit, and 1688 order, payment-link, receipt and cancel calls need an explicit JSON `true` confirmation (8 of 20). Few required parameters with defaults on most. No official SDK package, only standard-library clients in the repository for JavaScript and Python, which SoldFetch earned 8 for (8 of 15). 5+12+11+8+8 = 44.", "b": "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." }, "scores": { "a": 44, "b": 77 } }, { "by": 22, "category": "schema", "leads": "qovia", "name": "Schema \u0026 documentation", "reasons": { "a": "A public OpenAPI 3.1 file at api.nexscope.ai/openapi.json, about 3.8 MB, linked from the quickstart. Visible request bodies are typed with required fields, patterns, enums and `additionalProperties: false`, but responses are open `data` objects and the components section, with the security scheme and the shared error response, wasn't reached. In the repository 166 of 252 request definitions are field descriptors rather than JSON Schema. The hosted tools/list wasn't read. SoldFetch took 17 with untyped responses and SandBase 22 with components unread (19 of 25). llms.txt on www.nexscope.ai and Markdown references for every API in the repository (10). MCP tool descriptions are one line ('Find Amazon products by keyword and marketplace. Results come back as structured JSON.'), with no when-not-to-use. The repository's references carry long trigger text ('trigger this skill whenever their need involves real-time Amazon search results'), not guidance on when to pick another tool (10 of 20). Tool pages list types, defaults, enums and length limits, but the Amazon Search page marks no argument required and omits the `keyword` its own examples pass, and many limits sit in prose (8 of 15). Every API has a request sample, a response fixture and cURL, JavaScript and Python clients, though most fixtures are labelled historical. Errors are an HTTP table, two named codes (11209, 12001) and a semantic error response whose schema wasn't read. MCP errors aren't documented (10 of 15). Path versioning under /v1, MCP v2 beside a legacy v1, and a dated OpenAPI version label, but no public changelog. SandBase earned 7 on the same pattern (7 of 15). 19+10+10+8+10+7 = 64.", "b": "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." }, "scores": { "a": 64, "b": 86 } }, { "by": 20, "category": "payments", "leads": "qovia", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 on pricing, the quickstart, the MCP map, llms.txt or the visible OpenAPI paths. Credits come from a subscription or a Data top-up (0). Plans and credits per plan are public without a login ($29 for 30,000, $55 for 75,000, $129 for 150,000), and tool pages show credits per call, such as Amazon Search from 21 credits with a recent average of 30. Many tools on the MCP map list no cost and pricing is marked 'dynamic-credits'. Manifold earned 20 with a cost for every tool (15 of 20). A Free Trial of 1,000 credits for 3 days with 'No credit card required', API and MCP limits included. Creative API keys need a subscription (20). A person signs in through the browser to approve OAuth or create a key, and no keyless or programmatic route was found (0). 0+15+20+0 = 35.", "b": "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." }, "scores": { "a": 35, "b": 55 } }, { "by": 19, "category": "security", "leads": "qovia", "name": "Security \u0026 auth", "reasons": { "a": "The MCP server takes OAuth 2.1 with PKCE and one scope, `mcp:tools`, per the tool pages, or a Bearer `nk-` API key. Keys are created by a person under API Access, shown once, and can be expired, disabled or deleted, with no scopes or rotation found. The OAuth metadata on api.nexscope.ai wasn't read. No query-string key option was found. Manifold earned 22 with OAuth and hashed keys whose storage it documents (20 of 30). Most tools read. Writes exist (1688 procurement on the user's own buyer account, Amazon Ads entity operations through an owned connection, paid generation jobs), and the 1688 calls need an explicit JSON `true` per action after a preview, with the guide saying to get the user's approval first. Credits cap spend. No read-only key or tool allowlist (12 of 20). Tools return third-party listings, reviews, social posts and web pages, and no prompt-injection guidance was found. Manifold, the closest marketing-data MCP, took 0 (0). The Account credits and Account usage APIs, `costToken` in data responses and credits charged on task results give per-call visibility. No key-level audit was found (9 of 15). security.txt answered a client error. No disclosure policy, bug bounty or certification found (0 of 20). 20+12+0+9+0 = 41.", "b": "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." }, "scores": { "a": 41, "b": 60 } }, { "by": 12, "category": "maintenance", "leads": "qovia", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service with a public documentation repository. The repository synced the released 1688 procurement contracts on 9 November 2026 and committed again on 10 November (30). No releases or changelog. The dated record is the registry's four versions on 14 and 16 October, repository commits on 8, 9, 20 and 29 October and 2, 9 and 10 November, and source notes dating WooCommerce (29 October) and design search (2 November) additions. SoldFetch earned 10 for dated commits without releases (10 of 20). No public changelog. Support is service@nexscope.ai, WhatsApp and a booked call, untested. The repository's one merged pull request came from the organisation itself, and GitHub's API refused us, so issues weren't read (5 of 15). The official MCP registry lists `io.github.nexscope/ecommerce`, active, latest 1.0.3 of 16 October 2026, read first-hand (15). A CI workflow runs offline catalogue validation and unit tests on standard-library clients with no dependencies. The run results weren't read (5 of 10). 30+10+5+15+5 = 65.", "b": "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." }, "scores": { "a": 65, "b": 77 } }, { "by": 11, "category": "transparency", "leads": "nexscope", "name": "Transparency \u0026 trust", "reasons": { "a": "The editorial half. The service is closed. The terms (8 October 2026) name ECOCREATE TECHNOLOGY PTE. LTD. under Singapore law with no registration number or address. The repository's MIT licence covers client code only, and the documentation and definitions stay copyright Nexscope. Scrapewise earned 15 for closed terms with MIT side code (15 of 30). The privacy policy (8 October 2026) says uploads are not used to train AI models and that connected selling-partner data is deleted or de-identified when no longer needed, but 'this policy does not specify a single deletion deadline for all data', and no DPA was found. SandBase took 12 with no retention periods (10 of 30). No deprecation policy or dated notices. The terms promise notice of material changes before they take effect where practicable, and the MCP map keeps a legacy v1 beside v2 (3 of 20). Analytics and advertising vendors are named (Google Analytics, Microsoft Clarity, Ahrefs, Google Ads, X, FirstPromoter), but hosting, AI processing and payment providers only by type, with no data locations. The repository's source notes say supplier references 'are presented as Nexscope', so the data suppliers go unnamed except LinkFox Agent for 1688 authorisation (5 of 20). 15+10+3+5 = 33. The provenance half is computed from the provenance block.", "b": "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." }, "scores": { "a": 41, "b": 30 } } ], "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "ECOCREATE TECHNOLOGY PTE. LTD.", "b": "Qovia", "name": "Vendor" }, { "a": "https://api.nexscope.ai/mcp", "b": "https://api.qovia.ai", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service under the Nexscope terms (last updated 8 October 2026), whose contracting party is ECOCREATE TECHNOLOGY PTE. LTD. of Singapore. The OpenAPI file's licence is 'Proprietary API; use subject to Nexscope Terms'. In github.com/nexscope-ai/nexscope-ecommerce-api only the example clients, validation scripts, tests and workflow are MIT. The API documentation, catalogue, definitions and sample data stay copyright Nexscope", "b": "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", "name": "Licence" }, { "a": "382", "b": "141", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.nexscope/ecommerce", "b": "ai.qovia/qovia", "name": "MCP registry" }, { "a": "2026-11-09", "b": "2026-10-28", "name": "Last release" }, { "a": "none", "b": "0 stars", "name": "Popularity" } ], "faq": [ { "answer": "Qovia scores 61.2 (C) on agent readiness against Nexscope's 46.2 (D), and leads in 6 of 7 scored categories. Nexscope leads on transparency \u0026 trust.", "question": "Which is better for AI agents, Nexscope or Qovia?" }, { "answer": "Yes. Nexscope has a hosted endpoint at https://api.nexscope.ai/mcp and Qovia at https://api.qovia.ai.", "question": "Can an agent call Nexscope and Qovia without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Transparency \u0026 trust, 41 against 30" ], "also": [ "Free to start without a card" ], "goodFor": "Agents that research ecommerce products, competitors, keywords, sourcing and patents across Amazon, TikTok Shop, Walmart, Temu, 1688 and other marketplaces, and that also make listing images and video, on one credit balance.", "slug": "nexscope", "watchFor": "The MCP connection advertises the full catalogue of 382 tools, with no toolsets or read-only subset" }, { "aheadOn": [ "Schema \u0026 documentation, 86 against 64", "Agent ergonomics, 77 against 44", "Security \u0026 auth, 60 against 41", "Payments \u0026 pricing, 55 against 35", "Maintenance \u0026 community, 77 against 65" ], "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`" } ], "history": null, "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/browseract-vs-nexscope.json", "title": "BrowserAct vs Nexscope", "url": "https://www.anchorterminal.com/compare/browseract-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/browseract-vs-qovia.json", "title": "BrowserAct vs Qovia", "url": "https://www.anchorterminal.com/compare/browseract-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-nexscope.json", "title": "Context.dev vs Nexscope", "url": "https://www.anchorterminal.com/compare/context-dev-vs-nexscope" }, { "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/crawl4ai-vs-nexscope.json", "title": "Crawl4AI vs Nexscope", "url": "https://www.anchorterminal.com/compare/crawl4ai-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/crawl4ai-vs-qovia.json", "title": "Crawl4AI vs Qovia", "url": "https://www.anchorterminal.com/compare/crawl4ai-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-nexscope.json", "title": "fastCRW vs Nexscope", "url": "https://www.anchorterminal.com/compare/crw-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-qovia.json", "title": "fastCRW vs Qovia", "url": "https://www.anchorterminal.com/compare/crw-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/decodo-vs-nexscope.json", "title": "Decodo Web Data API vs Nexscope", "url": "https://www.anchorterminal.com/compare/decodo-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/decodo-vs-qovia.json", "title": "Decodo Web Data API vs Qovia", "url": "https://www.anchorterminal.com/compare/decodo-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/diffbot-vs-nexscope.json", "title": "Diffbot vs Nexscope", "url": "https://www.anchorterminal.com/compare/diffbot-vs-nexscope" }, { "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/firecrawl-mcp-vs-nexscope.json", "title": "Firecrawl MCP vs Nexscope", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-nexscope.json", "title": "jevcrawl vs Nexscope", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-nexscope" }, { "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/microlink-vs-nexscope.json", "title": "Microlink vs Nexscope", "url": "https://www.anchorterminal.com/compare/microlink-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/microlink-vs-qovia.json", "title": "Microlink vs Qovia", "url": "https://www.anchorterminal.com/compare/microlink-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-olostep.json", "title": "Nexscope vs Olostep", "url": "https://www.anchorterminal.com/compare/nexscope-vs-olostep" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-outcrawl.json", "title": "Nexscope vs Outcrawl", "url": "https://www.anchorterminal.com/compare/nexscope-vs-outcrawl" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-oxylabs-web-scraper.json", "title": "Nexscope vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/nexscope-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-printfriendly-mcp.json", "title": "Nexscope vs PrintFriendly MCP server", "url": "https://www.anchorterminal.com/compare/nexscope-vs-printfriendly-mcp" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapeatlas.json", "title": "Nexscope vs ScrapeAtlas", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapeatlas" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapegraphai.json", "title": "Nexscope vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapeops.json", "title": "Nexscope vs ScrapeOps Proxy API Aggregator", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapeops" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scraperapi.json", "title": "Nexscope vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapewise.json", "title": "Nexscope vs Scrapewise", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapfly.json", "title": "Nexscope vs Scrapfly", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapingant.json", "title": "Nexscope vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapingbee.json", "title": "Nexscope vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapingdog.json", "title": "Nexscope vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-soldfetch.json", "title": "Nexscope vs SoldFetch", "url": "https://www.anchorterminal.com/compare/nexscope-vs-soldfetch" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-spider-cloud.json", "title": "Nexscope vs Spider", "url": "https://www.anchorterminal.com/compare/nexscope-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-webscraping-ai.json", "title": "Nexscope vs WebScraping.AI", "url": "https://www.anchorterminal.com/compare/nexscope-vs-webscraping-ai" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-zenrows.json", "title": "Nexscope vs ZenRows", "url": "https://www.anchorterminal.com/compare/nexscope-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-zyte.json", "title": "Nexscope vs Zyte API", "url": "https://www.anchorterminal.com/compare/nexscope-vs-zyte" }, { "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/outcrawl-vs-qovia.json", "title": "Outcrawl vs Qovia", "url": "https://www.anchorterminal.com/compare/outcrawl-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/printfriendly-mcp-vs-qovia.json", "title": "PrintFriendly MCP server vs Qovia", "url": "https://www.anchorterminal.com/compare/printfriendly-mcp-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-scrapeops.json", "title": "Qovia vs ScrapeOps Proxy API Aggregator", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapeops" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi.json", "title": "Qovia vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise.json", "title": "Qovia vs Scrapewise", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapfly.json", "title": "Qovia vs Scrapfly", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant.json", "title": "Qovia vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-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-soldfetch.json", "title": "Qovia vs SoldFetch", "url": "https://www.anchorterminal.com/compare/qovia-vs-soldfetch" }, { "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-webscraping-ai.json", "title": "Qovia vs WebScraping.AI", "url": "https://www.anchorterminal.com/compare/qovia-vs-webscraping-ai" }, { "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" } ], "panel": null, "scores": [ { "by": 1, "edge": "qovia", "key": "reliability", "name": "Reliability", "nexscope": 39, "qovia": 40, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 22, "edge": "qovia", "key": "schema", "name": "Schema \u0026 documentation", "nexscope": 64, "qovia": 86, "weight": 13 }, { "by": 33, "edge": "qovia", "key": "ergonomics", "name": "Agent ergonomics", "nexscope": 44, "qovia": 77, "weight": 13 }, { "by": 19, "edge": "qovia", "key": "security", "name": "Security \u0026 auth", "nexscope": 41, "qovia": 60, "weight": 14 }, { "by": 20, "edge": "qovia", "key": "payments", "name": "Payments \u0026 pricing", "nexscope": 35, "qovia": 55, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "qovia", "key": "maintenance", "name": "Maintenance \u0026 community", "nexscope": 65, "qovia": 77, "weight": 7 }, { "by": 11, "edge": "nexscope", "key": "transparency", "name": "Transparency \u0026 trust", "nexscope": 41, "qovia": 30, "weight": 7 } ], "summary": "Qovia scores 61.2 (C) on agent readiness against Nexscope's 46.2 (D), and leads in 6 of 7 scored categories. Nexscope leads on transparency \u0026 trust. Both do extraction.", "tasks": null, "tutorials": [], "verdicts": { "nexscope": "An agent can reach Amazon, TikTok Shop, Temu, 1688 and other marketplace data, plus image and video models, on one credit balance through a remote MCP server with OAuth or a REST API with a public OpenAPI file. The connection loads 382 tools at once, and there is no status page, changelog or idempotency key.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/nexscope-vs-qovia", "json": "https://www.anchorterminal.com/compare/nexscope-vs-qovia.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/nexscope-vs-qovia.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/nexscope-vs-qovia.min.md" }, "markdown": "Qovia scores 61.2 (C) on agent readiness against Nexscope's 46.2 (D), and leads in 6 of 7 scored categories. Nexscope leads on transparency \u0026 trust. Both do extraction.\n\n- Nexscope: grade D, 46.2/100, rank #1191 of 1520. Markdown https://www.anchorterminal.com/tools/nexscope.md · JSON https://www.anchorterminal.com/api/v1/tools/nexscope.json\n- Qovia: grade C, 61.2/100, rank #627 of 1520. Markdown https://www.anchorterminal.com/tools/qovia.md · JSON https://www.anchorterminal.com/api/v1/tools/qovia.json\n- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md\n- All 533 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md\n\n## Which one, for what\n\n### Nexscope (D)\n\nGood for: Agents that research ecommerce products, competitors, keywords, sourcing and patents across Amazon, TikTok Shop, Walmart, Temu, 1688 and other marketplaces, and that also make listing images and video, on one credit balance.\n\nAhead on:\n- Transparency \u0026 trust, 41 against 30\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: The MCP connection advertises the full catalogue of 382 tools, with no toolsets or read-only subset\n\n### Qovia (C)\n\nGood for: Agents that need structured public data from Chinese platforms (Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Zhihu, WeChat official accounts, Taobao and JD reviews) or the Xingtu and Pugongying creator marketplaces, with TikTok, YouTube, Instagram, X and Reddit beside them, paid per successful call from a prepaid balance.\n\nAhead on:\n- Schema \u0026 documentation, 86 against 64\n- Agent ergonomics, 77 against 44\n- Security \u0026 auth, 60 against 41\n- Payments \u0026 pricing, 55 against 35\n- Maintenance \u0026 community, 77 against 65\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\n## Why the edge\n\n### Agent ergonomics: Qovia +33\n\n- Nexscope (44): Read on the MCP server, with the REST API where a line covers it. The MCP map lists 382 tools and says the category manifests 'narrow metadata for your integration; the MCP connection still advertises the full catalog'. That is more than 30 tools with no toolsets, dynamic loading or read-only subset found (5). Search tools page by `page` (about 20 results), with filters such as marketplace, category node, sort and device per tool, but no general pagination model or field selection, and output size depends on each tool (12 of 20). By default business errors answer HTTP 200 with an outer `code`. The `X-Nexscope-Http-Status: semantic` header maps them to HTTP statuses, the OpenAPI file names codes such as `DATA_IMAGE_DOWNLOAD_FAILED` and `CAPABILITY_BACKEND_UNAVAILABLE` in field text, and MCP errors aren't documented. SandBase earned 16 with typed bridge errors (11 of 20). Data calls only read. No idempotency keys and no readOnlyHint or destructiveHint documented. Async jobs return a `taskId` with a poll tool and a rule not to resubmit, and 1688 order, payment-link, receipt and cancel calls need an explicit JSON `true` confirmation (8 of 20). Few required parameters with defaults on most. No official SDK package, only standard-library clients in the repository for JavaScript and Python, which SoldFetch earned 8 for (8 of 15). 5+12+11+8+8 = 44.\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\n### Schema \u0026 documentation: Qovia +22\n\n- Nexscope (64): A public OpenAPI 3.1 file at api.nexscope.ai/openapi.json, about 3.8 MB, linked from the quickstart. Visible request bodies are typed with required fields, patterns, enums and `additionalProperties: false`, but responses are open `data` objects and the components section, with the security scheme and the shared error response, wasn't reached. In the repository 166 of 252 request definitions are field descriptors rather than JSON Schema. The hosted tools/list wasn't read. SoldFetch took 17 with untyped responses and SandBase 22 with components unread (19 of 25). llms.txt on www.nexscope.ai and Markdown references for every API in the repository (10). MCP tool descriptions are one line ('Find Amazon products by keyword and marketplace. Results come back as structured JSON.'), with no when-not-to-use. The repository's references carry long trigger text ('trigger this skill whenever their need involves real-time Amazon search results'), not guidance on when to pick another tool (10 of 20). Tool pages list types, defaults, enums and length limits, but the Amazon Search page marks no argument required and omits the `keyword` its own examples pass, and many limits sit in prose (8 of 15). Every API has a request sample, a response fixture and cURL, JavaScript and Python clients, though most fixtures are labelled historical. Errors are an HTTP table, two named codes (11209, 12001) and a semantic error response whose schema wasn't read. MCP errors aren't documented (10 of 15). Path versioning under /v1, MCP v2 beside a legacy v1, and a dated OpenAPI version label, but no public changelog. SandBase earned 7 on the same pattern (7 of 15). 19+10+10+8+10+7 = 64.\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\n### Payments \u0026 pricing: Qovia +20\n\n- Nexscope (35): No x402, MPP or L402 on pricing, the quickstart, the MCP map, llms.txt or the visible OpenAPI paths. Credits come from a subscription or a Data top-up (0). Plans and credits per plan are public without a login ($29 for 30,000, $55 for 75,000, $129 for 150,000), and tool pages show credits per call, such as Amazon Search from 21 credits with a recent average of 30. Many tools on the MCP map list no cost and pricing is marked 'dynamic-credits'. Manifold earned 20 with a cost for every tool (15 of 20). A Free Trial of 1,000 credits for 3 days with 'No credit card required', API and MCP limits included. Creative API keys need a subscription (20). A person signs in through the browser to approve OAuth or create a key, and no keyless or programmatic route was found (0). 0+15+20+0 = 35.\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\n### Security \u0026 auth: Qovia +19\n\n- Nexscope (41): The MCP server takes OAuth 2.1 with PKCE and one scope, `mcp:tools`, per the tool pages, or a Bearer `nk-` API key. Keys are created by a person under API Access, shown once, and can be expired, disabled or deleted, with no scopes or rotation found. The OAuth metadata on api.nexscope.ai wasn't read. No query-string key option was found. Manifold earned 22 with OAuth and hashed keys whose storage it documents (20 of 30). Most tools read. Writes exist (1688 procurement on the user's own buyer account, Amazon Ads entity operations through an owned connection, paid generation jobs), and the 1688 calls need an explicit JSON `true` per action after a preview, with the guide saying to get the user's approval first. Credits cap spend. No read-only key or tool allowlist (12 of 20). Tools return third-party listings, reviews, social posts and web pages, and no prompt-injection guidance was found. Manifold, the closest marketing-data MCP, took 0 (0). The Account credits and Account usage APIs, `costToken` in data responses and credits charged on task results give per-call visibility. No key-level audit was found (9 of 15). security.txt answered a client error. No disclosure policy, bug bounty or certification found (0 of 20). 20+12+0+9+0 = 41.\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\n### Maintenance \u0026 community: Qovia +12\n\n- Nexscope (65): Read as a closed service with a public documentation repository. The repository synced the released 1688 procurement contracts on 9 November 2026 and committed again on 10 November (30). No releases or changelog. The dated record is the registry's four versions on 14 and 16 October, repository commits on 8, 9, 20 and 29 October and 2, 9 and 10 November, and source notes dating WooCommerce (29 October) and design search (2 November) additions. SoldFetch earned 10 for dated commits without releases (10 of 20). No public changelog. Support is service@nexscope.ai, WhatsApp and a booked call, untested. The repository's one merged pull request came from the organisation itself, and GitHub's API refused us, so issues weren't read (5 of 15). The official MCP registry lists `io.github.nexscope/ecommerce`, active, latest 1.0.3 of 16 October 2026, read first-hand (15). A CI workflow runs offline catalogue validation and unit tests on standard-library clients with no dependencies. The run results weren't read (5 of 10). 30+10+5+15+5 = 65.\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\n### Transparency \u0026 trust: Nexscope +11\n\n- Nexscope (41): The editorial half. The service is closed. The terms (8 October 2026) name ECOCREATE TECHNOLOGY PTE. LTD. under Singapore law with no registration number or address. The repository's MIT licence covers client code only, and the documentation and definitions stay copyright Nexscope. Scrapewise earned 15 for closed terms with MIT side code (15 of 30). The privacy policy (8 October 2026) says uploads are not used to train AI models and that connected selling-partner data is deleted or de-identified when no longer needed, but 'this policy does not specify a single deletion deadline for all data', and no DPA was found. SandBase took 12 with no retention periods (10 of 30). No deprecation policy or dated notices. The terms promise notice of material changes before they take effect where practicable, and the MCP map keeps a legacy v1 beside v2 (3 of 20). Analytics and advertising vendors are named (Google Analytics, Microsoft Clarity, Ahrefs, Google Ads, X, FirstPromoter), but hosting, AI processing and payment providers only by type, with no data locations. The repository's source notes say supplier references 'are presented as Nexscope', so the data suppliers go unnamed except LinkFox Agent for 1688 authorisation (5 of 20). 15+10+3+5 = 33. The provenance half is computed from the provenance block.\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\n## Score by category\n\n| Category | Weight | Nexscope | Qovia | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 39 | 40 | Qovia +1 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 64 | 86 | Qovia +22 |\n| Agent ergonomics | 13% (16.2 this run) | 44 | 77 | Qovia +33 |\n| Security \u0026 auth | 14% (17.5 this run) | 41 | 60 | Qovia +19 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 55 | Qovia +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 65 | 77 | Qovia +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 41 | 30 | Nexscope +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **46.2 · D** | **61.2 · C** | |\n\n## Facts side by side\n\n| Fact | Nexscope | Qovia |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | ECOCREATE TECHNOLOGY PTE. LTD. | Qovia |\n| Hosted endpoint | `https://api.nexscope.ai/mcp` | `https://api.qovia.ai` |\n| Transports | Streamable HTTP, HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary hosted service under the Nexscope terms (last updated 8 October 2026), whose contracting party is ECOCREATE TECHNOLOGY PTE. LTD. of Singapore. The OpenAPI file's licence is 'Proprietary API; use subject to Nexscope Terms'. In github.com/nexscope-ai/nexscope-ecommerce-api only the example clients, validation scripts, tests and workflow are MIT. The API documentation, catalogue, definitions and sample data stay copyright Nexscope | 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 |\n| Tools exposed | 382 | 141 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.nexscope/ecommerce` | `ai.qovia/qovia` |\n| Last release | 2026-11-09 | 2026-10-28 |\n| Popularity | none | 0 stars |\n\n## Verdicts\n\n**Nexscope.** An agent can reach Amazon, TikTok Shop, Temu, 1688 and other marketplace data, plus image and video models, on one credit balance through a remote MCP server with OAuth or a REST API with a public OpenAPI file. The connection loads 382 tools at once, and there is no status page, changelog or idempotency key.\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## Before you call either\n\n### Nexscope\n\n1. Check the outer `code` is 0 before reading `data`, or send `X-Nexscope-Http-Status: semantic` to get HTTP error statuses.\n2. Call an image or video tool once, keep the `taskId`, and poll `nexscope_media_task_result`. A second call bills a second job.\n3. Read the tool's credit cost before a call. Each tool costs at least 10 credits and some cost over 300.\n4. Before you set a 1688 confirmation field to `true`, show the user the preview and get approval.\n5. If the server returns 429 or 503, wait for `Retry-After` when present and back off.\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## Questions\n\n### Which is better for AI agents, Nexscope or Qovia?\n\nQovia scores 61.2 (C) on agent readiness against Nexscope's 46.2 (D), and leads in 6 of 7 scored categories. Nexscope leads on transparency \u0026 trust.\n\n### Can an agent call Nexscope and Qovia without installing anything?\n\nYes. Nexscope has a hosted endpoint at https://api.nexscope.ai/mcp and Qovia at https://api.qovia.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/nexscope-vs-qovia.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nexscope-vs-qovia.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"nexscope\", \"b\": \"qovia\"}`. From a terminal: `anchor compare nexscope qovia`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/nexscope.json and https://www.anchorterminal.com/api/v1/tools/qovia.json\n\n## Other comparisons with Nexscope or Qovia\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- [BrowserAct vs Nexscope](https://www.anchorterminal.com/compare/browseract-vs-nexscope.md)\n- [BrowserAct vs Qovia](https://www.anchorterminal.com/compare/browseract-vs-qovia.md)\n- [Context.dev vs Nexscope](https://www.anchorterminal.com/compare/context-dev-vs-nexscope.md)\n- [Context.dev vs Qovia](https://www.anchorterminal.com/compare/context-dev-vs-qovia.md)\n- [Crawl4AI vs Nexscope](https://www.anchorterminal.com/compare/crawl4ai-vs-nexscope.md)\n- [Crawl4AI vs Qovia](https://www.anchorterminal.com/compare/crawl4ai-vs-qovia.md)\n- [fastCRW vs Nexscope](https://www.anchorterminal.com/compare/crw-vs-nexscope.md)\n- [fastCRW vs Qovia](https://www.anchorterminal.com/compare/crw-vs-qovia.md)\n- [Decodo Web Data API vs Nexscope](https://www.anchorterminal.com/compare/decodo-vs-nexscope.md)\n- [Decodo Web Data API vs Qovia](https://www.anchorterminal.com/compare/decodo-vs-qovia.md)\n- [Diffbot vs Nexscope](https://www.anchorterminal.com/compare/diffbot-vs-nexscope.md)\n- [Diffbot vs Qovia](https://www.anchorterminal.com/compare/diffbot-vs-qovia.md)\n- [Firecrawl MCP vs Nexscope](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-nexscope.md)\n- [jevcrawl vs Nexscope](https://www.anchorterminal.com/compare/jevcrawl-vs-nexscope.md)\n- [jevcrawl vs Qovia](https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.md)\n- [Microlink vs Nexscope](https://www.anchorterminal.com/compare/microlink-vs-nexscope.md)\n- [Microlink vs Qovia](https://www.anchorterminal.com/compare/microlink-vs-qovia.md)\n- [Nexscope vs Olostep](https://www.anchorterminal.com/compare/nexscope-vs-olostep.md)\n- [Nexscope vs Outcrawl](https://www.anchorterminal.com/compare/nexscope-vs-outcrawl.md)\n- [Nexscope vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/nexscope-vs-oxylabs-web-scraper.md)\n- [Nexscope vs PrintFriendly MCP server](https://www.anchorterminal.com/compare/nexscope-vs-printfriendly-mcp.md)\n- [Nexscope vs ScrapeAtlas](https://www.anchorterminal.com/compare/nexscope-vs-scrapeatlas.md)\n- [Nexscope vs ScrapeGraphAI](https://www.anchorterminal.com/compare/nexscope-vs-scrapegraphai.md)\n- [Nexscope vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/nexscope-vs-scrapeops.md)\n- [Nexscope vs ScraperAPI](https://www.anchorterminal.com/compare/nexscope-vs-scraperapi.md)\n- [Nexscope vs Scrapewise](https://www.anchorterminal.com/compare/nexscope-vs-scrapewise.md)\n- [Nexscope vs Scrapfly](https://www.anchorterminal.com/compare/nexscope-vs-scrapfly.md)\n- [Nexscope vs ScrapingAnt](https://www.anchorterminal.com/compare/nexscope-vs-scrapingant.md)\n- [Nexscope vs ScrapingBee](https://www.anchorterminal.com/compare/nexscope-vs-scrapingbee.md)\n- [Nexscope vs Scrapingdog](https://www.anchorterminal.com/compare/nexscope-vs-scrapingdog.md)\n- [Nexscope vs SoldFetch](https://www.anchorterminal.com/compare/nexscope-vs-soldfetch.md)\n- [Nexscope vs Spider](https://www.anchorterminal.com/compare/nexscope-vs-spider-cloud.md)\n- [Nexscope vs WebScraping.AI](https://www.anchorterminal.com/compare/nexscope-vs-webscraping-ai.md)\n- [Nexscope vs ZenRows](https://www.anchorterminal.com/compare/nexscope-vs-zenrows.md)\n- [Nexscope vs Zyte API](https://www.anchorterminal.com/compare/nexscope-vs-zyte.md)\n- [Olostep vs Qovia](https://www.anchorterminal.com/compare/olostep-vs-qovia.md)\n- [Outcrawl vs Qovia](https://www.anchorterminal.com/compare/outcrawl-vs-qovia.md)\n- [Oxylabs Web Scraper API vs Qovia](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.md)\n- [PrintFriendly MCP server vs Qovia](https://www.anchorterminal.com/compare/printfriendly-mcp-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 ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/qovia-vs-scrapeops.md)\n- [Qovia vs ScraperAPI](https://www.anchorterminal.com/compare/qovia-vs-scraperapi.md)\n- [Qovia vs Scrapewise](https://www.anchorterminal.com/compare/qovia-vs-scrapewise.md)\n- [Qovia vs Scrapfly](https://www.anchorterminal.com/compare/qovia-vs-scrapfly.md)\n- [Qovia vs ScrapingAnt](https://www.anchorterminal.com/compare/qovia-vs-scrapingant.md)\n- [Qovia vs 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 SoldFetch](https://www.anchorterminal.com/compare/qovia-vs-soldfetch.md)\n- [Qovia vs Spider](https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.md)\n- [Qovia vs WebScraping.AI](https://www.anchorterminal.com/compare/qovia-vs-webscraping-ai.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", "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-11", "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": "Nexscope vs Qovia", "url": "" } ], "description": "Qovia scores 61.2 (C) to Nexscope's 46.2 (D) for extraction. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Nexscope D 46.2", "Qovia C 61.2", "scores" ], "h1": "Nexscope vs Qovia", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/nexscope-vs-qovia", "published": "2026-10-01", "section": "tools", "title": "Nexscope vs Qovia for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-11", "url": "https://www.anchorterminal.com/compare/nexscope-vs-qovia" }, "tokens": { "markdown": 7150, "slim": 1180 }, "version": 1 }