{ "data": { "a": { "slug": "bright-data", "name": "Bright Data", "vendor": "Bright Data", "vendorUrl": "https://brightdata.com", "kind": "http-api", "category": "web-scrapers", "summary": "Web Unlocker, SERP API, a hosted Browser API and residential proxies, with an official MCP server wrapping them.", "url": "https://www.anchorterminal.com/tools/bright-data", "markdownUrl": "https://www.anchorterminal.com/tools/bright-data.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bright-data.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bright-data.json", "dns": "bright-data.grade.anchorterminal.com", "repo": "https://github.com/brightdata/brightdata-mcp", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.brightdata.com/request", "packages": [ { "registry": "npm", "name": "@brightdata/mcp" } ], "auth": "mixed", "authNotes": "Bearer key for the API. Keys take a role (Admin, Finance, Ops, Limit or User) and an optional expiry. Proxy-style access uses Basic auth on port 44445. The hosted MCP takes the key as `?token=` in the URL by default, or OAuth 2.1 (PKCE S256, scope `mcp`) with an `Authorization: Bearer` header. MCP agent keys are listed separately in account settings and can be revoked.", "pricing": "freemium", "pricingNotes": "5,000 free requests a month including MCP, no card. Web Unlocker and SERP $1.50 per 1,000 successful requests, $1.30 on Scale ($499 a month). Browser API $8 a GB (https://brightdata.com/pricing).", "priceSummary": "$1.50 / 1k req", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 69, "popularity": { "githubStars": 2600, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-26" }, "docsUrl": "https://docs.brightdata.com", "llmsTxt": "https://docs.brightdata.com/llms.txt", "registryName": "io.github.brightdata/brightdata-mcp", "capabilities": [ "web.scrape", "web.search", "browser.hosted", "web.crawl" ], "tags": [ "hosted", "freemium", "no-card", "mcp", "llms-txt", "proxies" ], "lastRelease": "2026-09-15", "graded": true, "anchor": { "graded": true, "score": 60, "grade": "C", "agentReady": false, "rank": 622, "ranked": true, "rankOf": 1253, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 82, "maintenance": 84, "payments": 40, "reliability": 35, "schema": 74, "security": 57, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Pay only for successful requests, $1.50 per 1,000 on Web Unlocker and SERP. No public status page or incident history.", "bestFor": "Hard targets and site-specific structured data (Amazon, LinkedIn, Instagram, Google Maps) at volume.", "strengths": [ "Pay only for successful requests, $1.50 per 1,000 on Web Unlocker and SERP", "5,000 free requests a month with no card", "Five tools by default out of 69, with groups for e-commerce, social, browser and more", "Role-based API keys with expiry, and OAuth 2.1 with PKCE on the hosted MCP", "ISO 27001, SOC 2 Type II and a private bug bounty" ], "weaknesses": [ "No public status page or incident history", "The default hosted MCP URL carries the key as `?token=`", "No prompt-injection guidance for scraped content", "No retention periods, DPA or subprocessor list in the privacy policy", "MCP registry entry lags npm by two minor versions" ], "agentNotes": [ "Connect with OAuth or keep the `?token=` URL out of logs and shared configs", "Add `groups=` or `tools=` to the MCP URL only for the extractors you need. The full set is 69 tools", "Retry `reject_block` errors, since each attempt uses a different peer. Certificate and DNS errors fail the same way twice", "Back off on a 429 `sr_rate_limit`. Bright Data throttles a target whose success rate drops", "Use the batch tools for up to 10 searches or scrapes in one call" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60 } ], "editorialScores": { "ergonomics": 82, "maintenance": 84, "payments": 40, "reliability": 35, "schema": 74, "security": 57, "transparency": 43 }, "provenanceScore": 79, "checked": { "categories": { "ergonomics": "2026-10-01", "maintenance": "2026-10-01", "payments": "2026-10-01", "reliability": "2026-10-01", "schema": "2026-10-01", "security": "2026-10-01", "transparency": "2026-10-01" }, "last": "2026-10-01", "lastMoved": "2026-10-27", "oldest": "2026-10-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.brightdata.com/request -H \"Authorization: Bearer $BRIGHTDATA_TOKEN\" \\\n -H \"content-type: application/json\" -d '{\"zone\":\"web_unlocker1\",\"url\":\"https://example.com\",\"format\":\"raw\"}'", "claudeCode": "claude mcp add --transport http brightdata \"https://mcp.brightdata.com/mcp?token=$BRIGHTDATA_TOKEN\"" }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/bright-data" }, "area": "web-data", "unitPrices": [ { "item": "Web Unlocker", "unit": "1k-requests", "usd": 1.5, "note": "successful requests only" }, { "item": "Web Unlocker on Scale", "unit": "1k-requests", "usd": 1.3, "note": "$499 a month plan" }, { "item": "SERP API", "unit": "1k-requests", "usd": 1.5 }, { "item": "Browser API", "unit": "gb", "usd": 8 } ], "provenance": { "legalEntity": "Bright Data Ltd.", "domain": "brightdata.com", "domainRegistered": "2002-05-26", "domainNote": "brightdata.com was registered in 2002, long before the rename from Luminati.", "endpointOnVendorDomain": true, "terms": "https://brightdata.com/license", "privacy": "https://brightdata.com/privacy", "statusPage": "", "changelog": "https://docs.brightdata.com/release-notes", "securityTxt": "none", "checked": "2026-09-26", "score": 79 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bright-data.json", "live": { "slug": "bright-data", "probe": { "target": "https://api.brightdata.com/request", "method": "get", "lastAt": "2026-11-01T22:08:24.128806621Z", "lastOk": true, "lastStatus": 404, "lastMs": 266, "authRequired": false, "uptime24h": 100, "uptime30d": 99.8, "p50ms24h": 266, "p95ms24h": 384, "samples24h": 250, "samples30d": 8145, "days": [ { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 271 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 245 }, { "date": "2026-10-11", "probes": 247, "ok": 246 }, { "date": "2026-10-12", "probes": 247, "ok": 246 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 248 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 249 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 249 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 246 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 249 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 250 }, { "date": "2026-11-01", "probes": 230, "ok": 230 } ] }, "versions": [ { "registry": "github", "name": "brightdata/brightdata-mcp", "version": "v4.2.0", "released": "2026-11-01", "seenAt": "2026-11-01T16:47:19.874782734Z" }, { "registry": "mcp-registry", "name": "io.github.brightdata/brightdata-mcp", "version": "4.2.0", "seenAt": "2026-11-01T16:10:44.053973489Z" }, { "registry": "npm", "name": "@brightdata/mcp", "version": "4.2.0", "seenAt": "2026-11-01T16:47:19.388059269Z" } ], "githubStars": 2703, "npmWeekly": 15737, "securityTxt": { "url": "https://brightdata.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:42:37.044023889Z" }, "llmsTxt": { "url": "https://docs.brightdata.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:13:04.289387639Z" }, "domain": { "domain": "brightdata.com", "registered": "2002-05-26", "source": "https://rdap.verisign.com/com/v1/domain/brightdata.com", "checkedAt": "2026-11-01T14:20:01.121970964Z" }, "pages": [ { "url": "https://docs.brightdata.com/release-notes", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-01T06:40:53.453993673Z", "changedAt": "2026-10-29T05:03:38.867827318Z", "fingerprint": "8f9ad0fbcaf5" }, { "url": "https://brightdata.com/license", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-01T06:36:55.807284743Z", "changedAt": "2026-10-23T01:41:14.244480086Z", "fingerprint": "64091a076f66" }, { "url": "https://brightdata.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-01T06:36:58.108770961Z", "changedAt": "2026-10-23T01:41:16.713922299Z", "fingerprint": "16cec52a96ec" }, { "url": "https://brightdata.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-01T06:37:00.072571762Z", "changedAt": "2026-10-23T01:41:18.547717076Z", "fingerprint": "a31501129740" } ], "github": { "repo": "brightdata/brightdata-mcp", "checkedAt": "2026-10-26T07:15:59.521964575Z", "stars": 2687, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-20T09:53:42Z", "openIssues": 15, "openPRs": 25, "issuesOpened90d": 7, "issuesClosed90d": 0, "prsMerged90d": 11, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-20T09:54:15Z" }, "replies": { "sampled": 25, "unanswered": 12, "medianDays": 3.7 } }, "updatedAt": "2026-11-01T22:08:24.128806621Z" } }, "answer": "Qovia scores 61.2 (C) on agent readiness against Bright Data's 60 (C), and leads in 4 of 7 scored categories. Bright Data leads on agent ergonomics, maintenance \u0026 community and 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": 558, "ranked": true, "rankOf": 1253, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 77, "payments": 55, "reliability": 40, "schema": 86, "security": 60, "transparency": 30 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "An OpenAPI 3.1 file with 144 operations, one envelope and 20 error codes, per-endpoint prices with failed and empty calls refunded, scoped keys and a four-tool MCP server that keeps the catalogue out of context. No status page, no legal entity, one-paragraph terms and privacy pages, and a product ten days old at the check.", "bestFor": "Agents that need structured public data from Chinese platforms (Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Zhihu, WeChat official accounts, Taobao and JD reviews) or the Xingtu and Pugongying creator marketplaces, with TikTok, YouTube, Instagram, X and Reddit beside them, paid per successful call from a prepaid balance.", "strengths": [ "A public OpenAPI 3.1 file with 144 operations, patterns or enums on parameters, a response example on every operation and the error responses declared on each", "One envelope on every call, `request_id`, `data` and `meta` with the charge and balance, and 20 error codes sorted into not charged and refunded, with `Retry-After` on the retryable ones", "Only HTTP 200 with a non-empty result is charged; empty results, 404s, timeouts and upstream failures are refunded, and 50 trial calls come with a new account", "API keys carry per-platform scopes and an optional expiry, are read from headers only, and the docs tell users to give AI tools a separate scoped key", "The MCP server loads four tools by default and lets an agent find, read and call any of 137 endpoints, with `?tools=` subsets for direct tools; listed in the official registry under ai.qovia/qovia", "Published limits of 60 and 600 requests a minute with `X-RateLimit-*` headers, and a documented empty-call throttle" ], "weaknesses": [ "No status page, incident history or SLA; the terms promise nothing about uptime and the Python client is the only retry guidance beyond `Retry-After`", "The terms and privacy policy are one paragraph each, name no legal entity, address, retention period or subprocessor, and say a signed agreement governs", "Every endpoint is marked `beta` in the OpenAPI file while the docs call it Live, and the API version is 0.1.0", "No security.txt, disclosure policy beyond a SECURITY.md, bug bounty or certification; the only support channels are Telegram, WhatsApp, WeChat and one mailbox", "Every response is third-party platform content and the docs carry no guidance on treating it as untrusted; four endpoint groups read login-gated creator marketplaces", "The changelog has two dated days, the domain is four months old, and the GitHub account was created the week of the request with nine forked lists beside the one repository" ], "agentNotes": [ "Send `Authorization: Bearer sk-qovia-...` to https://api.qovia.ai and check `meta.empty` on every HTTP 200; `data` may be `null` or an empty structure and nothing is charged for it.", "Branch on `error.code`, never on `message`. Retry only `rate_limited`, `too_many_unbilled`, `endpoint_busy`, `upstream_busy` and `too_many_auth_failures` after `Retry-After`; `endpoint_unavailable` has none and will not clear.", "Stay under 60 requests a minute (600 after the first top-up) across every key on the account, and keep empty or not-found calls under 80 per cent of the last 10 minutes or expect 429 `too_many_unbilled`.", "Pass the previous page's `cursor` (and `search_id` on Douyin and Zhihu search) back unchanged and stop when `has_more` is false; each page is a separate charge, and unknown parameters answer 400.", "For MCP, connect to https://api.qovia.ai/mcp over Streamable HTTP; call `search_endpoints` then `get_endpoint` before `call_endpoint`, or add `?tools=douyin,kuaishou` for typed direct tools. Catalogue tools need no key." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.2 } ], "editorialScores": { "ergonomics": 77, "maintenance": 77, "payments": 55, "reliability": 40, "schema": 86, "security": 60, "transparency": 23 }, "provenanceScore": 36, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install qovia", "http": "curl \"https://api.qovia.ai/v1/raw/weibo/hot_search\" -H \"Authorization: Bearer $QOVIA_API_KEY\"", "claudeCode": "claude mcp add --transport http qovia https://api.qovia.ai/mcp --header \"Authorization: Bearer $QOVIA_API_KEY\"" }, "letme": { "capability": "https://letme.dev/web.extract", "tool": "https://letme.dev/qovia" }, "area": "web-data", "unitPrices": [ { "item": "Cross-platform search", "unit": "1k-requests", "usd": 5, "note": "POST /v1/search, successful non-empty calls only, pricing page and OpenAPI file checked 1 November 2026" }, { "item": "Lowest raw endpoints (Douyin, Bilibili, Xingtu keywords)", "unit": "1k-requests", "usd": 0.5, "note": "15 fixed-price endpoints at $0.0005 a successful call" }, { "item": "Most raw endpoints (TikTok, YouTube, X, Reddit, Weibo, Zhihu, Kuaishou and others)", "unit": "1k-requests", "usd": 1, "note": "61 fixed-price endpoints at $0.001 a successful call" }, { "item": "Tiered raw endpoints (Tieba, Fliggy, coming-soon platforms)", "unit": "1k-requests", "usd": 1.5, "note": "$1 per 1,000 after 5,000,000 billed calls in a calendar month" }, { "item": "Xiaohongshu and WeChat endpoints", "unit": "1k-requests", "usd": 5, "note": "11 fixed-price endpoints at $0.005 a successful call" }, { "item": "Xingtu and Pugongying creator marketplace endpoints", "unit": "1k-requests", "usd": 10, "note": "21 fixed-price endpoints at $0.01 a successful call" }, { "item": "JD.com product reviews", "unit": "1k-requests", "usd": 19.5, "note": "the dearest endpoint; Taobao and Tmall reviews are $13.5" }, { "item": "Apify Store, Xingtu Actor premium section", "unit": "record", "usd": 0.06, "note": "per creator per section, paid through Apify with no Qovia account; basic sections $0.01, video sections $0.03" } ], "provenance": { "legalEntity": "", "domain": "qovia.ai", "domainRegistered": "2026-07-04", "endpointOnVendorDomain": true, "terms": "https://qovia.ai/terms/", "privacy": "https://qovia.ai/privacy/", "statusPage": "", "changelog": "https://qovia.ai/changelog/", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "No legal entity is named anywhere read. The terms and privacy pages are one paragraph each, say Delaware law governs and that the signed agreement governs where it differs, and name no company, address or jurisdiction beyond the state. The footer reads © 2026 QoviaAI, a brand name, not an entity, so legalEntity is left empty.", "RDAP for qovia.ai gives a registration date of 2026-07-04 through GoDaddy with a Domains By Proxy registrant and Cloudflare nameservers. The Wayback Machine's only capture before the check is the home page of 11 September 2026, which advertised sign-up with a free 1,000 calls a month, 25+ platforms, a 99.95 per cent enterprise SLA and a team@ mailbox; none of those claims is on the current site.", "firstReleased is the changelog's first dated entry, 21 October 2026, when the search, Xiaohongshu, WeChat, Taobao and JD endpoints are recorded as live; the remaining platforms are dated 22 October, the registry entry is 22 October and the GitHub account and repository were created on 23 October 2026. The 11 September page sold an API key but dates nothing live.", "https://qovia.ai/.well-known/security.txt, https://qovia.ai/security.txt and https://api.qovia.ai/.well-known/security.txt answer 404. The repository's SECURITY.md gives a Telegram handle and a mailbox for reports and says it covers qovia.ai and api.qovia.ai.", "api.qovia.ai has no robots.txt (404); only its OAuth metadata (404) and /mcp (405 on GET) were touched, both by the 1 November listing check. qovia.ai's robots.txt disallows /console/, /account/, /order/ and /admin/ and their /zh/ twins, which were not fetched." ], "score": 36 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/qovia.json", "live": { "slug": "qovia", "probe": { "target": "https://api.qovia.ai", "method": "get", "lastAt": "2026-11-01T22:08:43.664510387Z", "lastOk": true, "lastStatus": 200, "lastMs": 491, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 521, "p95ms24h": 626, "samples24h": 25, "samples30d": 25, "days": [ { "date": "2026-11-01", "probes": 25, "ok": 25 } ] }, "updatedAt": "2026-11-01T22:08:43.664510387Z" } }, "edges": [ { "by": 31, "category": "transparency", "leads": "bright-data", "name": "Transparency \u0026 trust", "reasons": { "a": "The API is closed under the Bright Data licence, and the MCP server is MIT, so we gave 20 between the closed and open bands (20 of 30). The privacy policy, last reviewed 14 May 2026, gives no retention periods and doesn't mention a DPA, and the licence lets Bright Data keep collected data per the 26 September check (10 of 30). Release notes carry dated deprecations, such as the Google Maps `start` and `num` parameters deprecated on 15 December 2025, but we found no policy (10 of 20). No subprocessor list. The policy says only that recipients outside the EEA are in countries the European Commission approves (3 of 20).", "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": 61, "b": 30 } }, { "by": 15, "category": "payments", "leads": "qovia", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402. Issue #126 asks for x402 and is open (0). Web Unlocker and SERP at $1.50 per 1,000 successful requests, $1.30 on Scale, published without a login (20). 5,000 requests a month, 'No credit card required' (20). A person has to sign up and create a key in the control panel (0).", "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": 40, "b": 55 } }, { "by": 12, "category": "schema", "leads": "qovia", "name": "Schema \u0026 documentation", "reasons": { "a": "No OpenAPI file found for the API. The MCP server has zod schemas on every tool, so partial credit (15 of 25). llms.txt at docs.brightdata.com with Markdown pages (10). MCP descriptions say what each tool returns, and the dataset tools say when to use them instead of the one-record web_data_* tools (14 of 20). Typed inputs with enums such as engine google, bing or yandex (12 of 15). Per-product error catalogues for Web Unlocker, Browser API and scrapers, and curl examples (13 of 15). Release notes, last entry 14 June 2026, and an MCP CHANGELOG with a gap between 2.6.0 and 2.10.0 (10 of 15).", "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": 74, "b": 86 } }, { "by": 7, "category": "maintenance", "leads": "bright-data", "name": "Maintenance \u0026 community", "reasons": { "a": "MCP v2.11.3 on 2026-09-15 (30). v2.11.1 on 27 July, v2.11.2 on 11 September and v2.11.3 on 15 September (20). 13 open issues on the MCP repository, including 502s under load (#104, January 2026) and a JSON parse error (#74, October 2025) still open. We couldn't see reply dates (12 of 25). io.github.brightdata/brightdata-mcp in the official registry under a GitHub-verified namespace, but the registry entry is at 2.9.4 against 2.11.3 on npm (12 of 15). Tests run in CI on every push to main (10).", "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": 84, "b": 77 } }, { "by": 5, "category": "reliability", "leads": "qovia", "name": "Reliability", "reasons": { "a": "No public status page found. status.brightdata.com doesn't resolve and the docs index and security overview link none (0). No readable incident history, so 5 by the rubric (5). Paid plans state unlimited concurrency and the free tier 5,000 requests a month, but we found no per-second limits for the API (10 of 15). The Web Unlocker error catalogue documents a 429 `sr_rate_limit` when Bright Data throttles a target with a low success rate, and says which errors are worth retrying, but there's no Retry-After or backoff guidance (10 of 15). The pricing page names a Premium SLA for Enterprise and claims 99.99 per cent uptime, with no SLA terms published (0). GA (10).", "b": "Hosted reading, for the REST API with the MCP server described. No public status page was found. https://qovia.ai/status/ answers 404, status.qovia.ai does not resolve and neither the docs nor the footer links one (0). No readable incident history, so 5 by the rubric (5). Limits are published with numbers on the quickstart's rate-limits section, 60 requests a minute per account before the first top-up and 600 after on a sliding 60-second window, with X-RateLimit-Limit and X-RateLimit-Remaining headers, a 64 KiB body cap, an empty-call throttle (50 calls in 10 minutes with over 80 per cent empty, not found or rejected) and a per-second cap per endpoint without a number (15). Retry-After is declared on too_many_auth_failures, rate_limited, too_many_unbilled, endpoint_busy and upstream_busy, the error table marks the retryable codes, the docs say a 503 endpoint_unavailable carries none and will not clear, and the Python client retries 429 and 503 honouring the header. Every operation is a read, including POST /v1/search, and a failed or timed-out call is refunded, so idempotency keys are not needed (15). No SLA. The terms summary says nothing about uptime and the pricing FAQ excludes outages, rate limits and platform changes from refunds; the 11 September 2026 archived home page advertised a 99.95 per cent enterprise SLA that the current pages have dropped (0). The endpoints are sold and labelled Live on the docs and coverage pages, but every one of the 143 carries x-qovia-status beta in the OpenAPI file, the API version is 0.1.0 and the MCP server reports 0.1.0 (5 of 10). 0+5+15+15+0+5 = 40." }, "scores": { "a": 35, "b": 40 } }, { "by": 5, "category": "ergonomics", "leads": "bright-data", "name": "Agent ergonomics", "reasons": { "a": "Five base tools by default out of 69 per the README, with `groups=` and `tools=` on the hosted URL or GROUPS and TOOLS locally (25). Markdown output, batch tools of up to 10 searches or scrapes, `fixed_values` to trim tokens and filterable dataset search, but no general field selection (15 of 20). Error codes with a retry-or-fix classification (17 of 20). Billing counts successful requests, and tools carry readOnlyHint and openWorldHint, but there are no idempotency keys (15 of 20). One required secret and auto-created zones. We didn't confirm official SDKs in two languages (10 of 15).", "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": 82, "b": 77 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Bright Data", "b": "Qovia", "name": "Vendor" }, { "a": "https://api.brightdata.com/request", "b": "https://api.qovia.ai", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "not published", "b": "$5 per 1,000 requests", "name": "Price for web search" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "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": "69", "b": "141", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.brightdata/brightdata-mcp", "b": "ai.qovia/qovia", "name": "MCP registry" }, { "a": "2026-09-15", "b": "2026-10-28", "name": "Last release" }, { "a": "2026-06-16", "b": "not read yet", "name": "Terms last updated" }, { "a": "2026-05-14", "b": "not read yet", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not read yet", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "2.6k stars", "b": "0 stars", "name": "Popularity" }, { "a": "4/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Qovia scores 61.2 (C) on agent readiness against Bright Data's 60 (C), and leads in 4 of 7 scored categories. Bright Data leads on agent ergonomics, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Bright Data or Qovia?" }, { "answer": "Bright Data takes an API key or an OAuth sign-in. Qovia needs an API key.", "question": "Do Bright Data and Qovia need an API key?" }, { "answer": "Yes. Bright Data has a hosted endpoint at https://api.brightdata.com/request and Qovia at https://api.qovia.ai.", "question": "Can an agent call Bright Data and Qovia without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 82 against 77", "Maintenance \u0026 community, 84 against 77", "Transparency \u0026 trust, 61 against 30" ], "also": [ "Free to start without a card" ], "goodFor": "Hard targets and site-specific structured data (Amazon, LinkedIn, Instagram, Google Maps) at volume.", "slug": "bright-data", "watchFor": "No public status page or incident history" }, { "aheadOn": [ "Reliability, 40 against 35", "Schema \u0026 documentation, 86 against 74", "Payments \u0026 pricing, 55 against 40" ], "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": { "bright-data": [ { "causes": [ "evidence" ], "date": "2026-10-27", "delta": 0.2, "from": 59.8, "fromGrade": "C", "to": 60, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 60.1, "fromGrade": "C", "to": 59.8, "toGrade": "C" } ], "qovia": null }, "job": { "capability": "web.search", "name": "Web search" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bright-data-vs-firecrawl-mcp.json", "title": "Bright Data vs Firecrawl MCP", "url": "https://www.anchorterminal.com/compare/bright-data-vs-firecrawl-mcp" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia.json", "title": "Firecrawl MCP vs Qovia", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-context-dev.json", "title": "Bright Data vs Context.dev", "url": "https://www.anchorterminal.com/compare/bright-data-vs-context-dev" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-diffbot.json", "title": "Bright Data vs Diffbot", "url": "https://www.anchorterminal.com/compare/bright-data-vs-diffbot" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-jevcrawl.json", "title": "Bright Data vs jevcrawl", "url": "https://www.anchorterminal.com/compare/bright-data-vs-jevcrawl" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-jina-reader.json", "title": "Bright Data vs Jina Reader", "url": "https://www.anchorterminal.com/compare/bright-data-vs-jina-reader" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-olostep.json", "title": "Bright Data vs Olostep", "url": "https://www.anchorterminal.com/compare/bright-data-vs-olostep" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-oxylabs-web-scraper.json", "title": "Bright Data vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/bright-data-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrape-do.json", "title": "Bright Data vs Scrape.do", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrape-do" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapegraphai.json", "title": "Bright Data vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapeless.json", "title": "Bright Data vs Scrapeless", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapeless" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scraperapi.json", "title": "Bright Data vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapewise.json", "title": "Bright Data vs Scrapewise", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapfly.json", "title": "Bright Data vs Scrapfly", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapingant.json", "title": "Bright Data vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapingbee.json", "title": "Bright Data vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapingdog.json", "title": "Bright Data vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-spider-cloud.json", "title": "Bright Data vs Spider", "url": "https://www.anchorterminal.com/compare/bright-data-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-zenrows.json", "title": "Bright Data vs ZenRows", "url": "https://www.anchorterminal.com/compare/bright-data-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-zyte.json", "title": "Bright Data vs Zyte API", "url": "https://www.anchorterminal.com/compare/bright-data-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-qovia.json", "title": "Context.dev vs Qovia", "url": "https://www.anchorterminal.com/compare/context-dev-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/diffbot-vs-qovia.json", "title": "Diffbot vs Qovia", "url": "https://www.anchorterminal.com/compare/diffbot-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.json", "title": "jevcrawl vs Qovia", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/olostep-vs-qovia.json", "title": "Olostep vs Qovia", "url": "https://www.anchorterminal.com/compare/olostep-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.json", "title": "Oxylabs Web Scraper API vs Qovia", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.json", "title": "Qovia vs ScrapeAtlas", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.json", "title": "Qovia vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi.json", "title": "Qovia vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise.json", "title": "Qovia vs Scrapewise", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapfly.json", "title": "Qovia vs Scrapfly", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant.json", "title": "Qovia vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.json", "title": "Qovia vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.json", "title": "Qovia vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.json", "title": "Qovia vs Spider", "url": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-zenrows.json", "title": "Qovia vs ZenRows", "url": "https://www.anchorterminal.com/compare/qovia-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-zyte.json", "title": "Qovia vs Zyte API", "url": "https://www.anchorterminal.com/compare/qovia-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-bright-data.json", "title": "Apify MCP Server vs Bright Data", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-bright-data" } ], "panel": null, "scores": [ { "bright-data": 35, "by": 5, "edge": "qovia", "key": "reliability", "name": "Reliability", "qovia": 40, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bright-data": 74, "by": 12, "edge": "qovia", "key": "schema", "name": "Schema \u0026 documentation", "qovia": 86, "weight": 13 }, { "bright-data": 82, "by": 5, "edge": "bright-data", "key": "ergonomics", "name": "Agent ergonomics", "qovia": 77, "weight": 13 }, { "bright-data": 57, "by": 3, "edge": "qovia", "key": "security", "name": "Security \u0026 auth", "qovia": 60, "weight": 14 }, { "bright-data": 40, "by": 15, "edge": "qovia", "key": "payments", "name": "Payments \u0026 pricing", "qovia": 55, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bright-data": 84, "by": 7, "edge": "bright-data", "key": "maintenance", "name": "Maintenance \u0026 community", "qovia": 77, "weight": 7 }, { "bright-data": 61, "by": 31, "edge": "bright-data", "key": "transparency", "name": "Transparency \u0026 trust", "qovia": 30, "weight": 7 } ], "summary": "Qovia scores 61.2 (C) on agent readiness against Bright Data's 60 (C), and leads in 4 of 7 scored categories. Bright Data leads on agent ergonomics, maintenance \u0026 community and transparency \u0026 trust. Both do web search.", "tasks": null, "tutorials": [], "verdicts": { "bright-data": "Pay only for successful requests, $1.50 per 1,000 on Web Unlocker and SERP. No public status page or incident history.", "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/bright-data-vs-qovia", "json": "https://www.anchorterminal.com/compare/bright-data-vs-qovia.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bright-data-vs-qovia.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bright-data-vs-qovia.min.md" }, "markdown": "Qovia scores 61.2 (C) on agent readiness against Bright Data's 60 (C), and leads in 4 of 7 scored categories. Bright Data leads on agent ergonomics, maintenance \u0026 community and transparency \u0026 trust. Both do web search.\n\n- Bright Data: grade C, 60/100, rank #622 of 1253. Markdown https://www.anchorterminal.com/tools/bright-data.md · JSON https://www.anchorterminal.com/api/v1/tools/bright-data.json\n- Qovia: grade C, 61.2/100, rank #558 of 1253. Markdown https://www.anchorterminal.com/tools/qovia.md · JSON https://www.anchorterminal.com/api/v1/tools/qovia.json\n- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md\n- All 261 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md\n\n## Which one, for what\n\n### Bright Data (C)\n\nGood for: Hard targets and site-specific structured data (Amazon, LinkedIn, Instagram, Google Maps) at volume.\n\nAhead on:\n- Agent ergonomics, 82 against 77\n- Maintenance \u0026 community, 84 against 77\n- Transparency \u0026 trust, 61 against 30\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No public status page or incident history\n\n### Qovia (C)\n\nGood for: Agents that need structured public data from Chinese platforms (Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Zhihu, WeChat official accounts, Taobao and JD reviews) or the Xingtu and Pugongying creator marketplaces, with TikTok, YouTube, Instagram, X and Reddit beside them, paid per successful call from a prepaid balance.\n\nAhead on:\n- Reliability, 40 against 35\n- Schema \u0026 documentation, 86 against 74\n- Payments \u0026 pricing, 55 against 40\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### Transparency \u0026 trust: Bright Data +31\n\n- Bright Data (61): The API is closed under the Bright Data licence, and the MCP server is MIT, so we gave 20 between the closed and open bands (20 of 30). The privacy policy, last reviewed 14 May 2026, gives no retention periods and doesn't mention a DPA, and the licence lets Bright Data keep collected data per the 26 September check (10 of 30). Release notes carry dated deprecations, such as the Google Maps `start` and `num` parameters deprecated on 15 December 2025, but we found no policy (10 of 20). No subprocessor list. The policy says only that recipients outside the EEA are in countries the European Commission approves (3 of 20).\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### Payments \u0026 pricing: Qovia +15\n\n- Bright Data (40): No x402, MPP or L402. Issue #126 asks for x402 and is open (0). Web Unlocker and SERP at $1.50 per 1,000 successful requests, $1.30 on Scale, published without a login (20). 5,000 requests a month, 'No credit card required' (20). A person has to sign up and create a key in the control panel (0).\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### Schema \u0026 documentation: Qovia +12\n\n- Bright Data (74): No OpenAPI file found for the API. The MCP server has zod schemas on every tool, so partial credit (15 of 25). llms.txt at docs.brightdata.com with Markdown pages (10). MCP descriptions say what each tool returns, and the dataset tools say when to use them instead of the one-record web_data_* tools (14 of 20). Typed inputs with enums such as engine google, bing or yandex (12 of 15). Per-product error catalogues for Web Unlocker, Browser API and scrapers, and curl examples (13 of 15). Release notes, last entry 14 June 2026, and an MCP CHANGELOG with a gap between 2.6.0 and 2.10.0 (10 of 15).\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### Maintenance \u0026 community: Bright Data +7\n\n- Bright Data (84): MCP v2.11.3 on 2026-09-15 (30). v2.11.1 on 27 July, v2.11.2 on 11 September and v2.11.3 on 15 September (20). 13 open issues on the MCP repository, including 502s under load (#104, January 2026) and a JSON parse error (#74, October 2025) still open. We couldn't see reply dates (12 of 25). io.github.brightdata/brightdata-mcp in the official registry under a GitHub-verified namespace, but the registry entry is at 2.9.4 against 2.11.3 on npm (12 of 15). Tests run in CI on every push to main (10).\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### Reliability: Qovia +5\n\n- Bright Data (35): No public status page found. status.brightdata.com doesn't resolve and the docs index and security overview link none (0). No readable incident history, so 5 by the rubric (5). Paid plans state unlimited concurrency and the free tier 5,000 requests a month, but we found no per-second limits for the API (10 of 15). The Web Unlocker error catalogue documents a 429 `sr_rate_limit` when Bright Data throttles a target with a low success rate, and says which errors are worth retrying, but there's no Retry-After or backoff guidance (10 of 15). The pricing page names a Premium SLA for Enterprise and claims 99.99 per cent uptime, with no SLA terms published (0). GA (10).\n- Qovia (40): Hosted reading, for the REST API with the MCP server described. No public status page was found. https://qovia.ai/status/ answers 404, status.qovia.ai does not resolve and neither the docs nor the footer links one (0). No readable incident history, so 5 by the rubric (5). Limits are published with numbers on the quickstart's rate-limits section, 60 requests a minute per account before the first top-up and 600 after on a sliding 60-second window, with X-RateLimit-Limit and X-RateLimit-Remaining headers, a 64 KiB body cap, an empty-call throttle (50 calls in 10 minutes with over 80 per cent empty, not found or rejected) and a per-second cap per endpoint without a number (15). Retry-After is declared on too_many_auth_failures, rate_limited, too_many_unbilled, endpoint_busy and upstream_busy, the error table marks the retryable codes, the docs say a 503 endpoint_unavailable carries none and will not clear, and the Python client retries 429 and 503 honouring the header. Every operation is a read, including POST /v1/search, and a failed or timed-out call is refunded, so idempotency keys are not needed (15). No SLA. The terms summary says nothing about uptime and the pricing FAQ excludes outages, rate limits and platform changes from refunds; the 11 September 2026 archived home page advertised a 99.95 per cent enterprise SLA that the current pages have dropped (0). The endpoints are sold and labelled Live on the docs and coverage pages, but every one of the 143 carries x-qovia-status beta in the OpenAPI file, the API version is 0.1.0 and the MCP server reports 0.1.0 (5 of 10). 0+5+15+15+0+5 = 40.\n\n### Agent ergonomics: Bright Data +5\n\n- Bright Data (82): Five base tools by default out of 69 per the README, with `groups=` and `tools=` on the hosted URL or GROUPS and TOOLS locally (25). Markdown output, batch tools of up to 10 searches or scrapes, `fixed_values` to trim tokens and filterable dataset search, but no general field selection (15 of 20). Error codes with a retry-or-fix classification (17 of 20). Billing counts successful requests, and tools carry readOnlyHint and openWorldHint, but there are no idempotency keys (15 of 20). One required secret and auto-created zones. We didn't confirm official SDKs in two languages (10 of 15).\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## Score by category\n\n| Category | Weight | Bright Data | Qovia | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 40 | Qovia +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 74 | 86 | Qovia +12 |\n| Agent ergonomics | 13% (16.2 this run) | 82 | 77 | Bright Data +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 57 | 60 | Qovia +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 55 | Qovia +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 84 | 77 | Bright Data +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 30 | Bright Data +31 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **60 · C** | **61.2 · C** | |\n\n## Facts side by side\n\n| Fact | Bright Data | Qovia |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Bright Data | Qovia |\n| Hosted endpoint | `https://api.brightdata.com/request` | `https://api.qovia.ai` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Pay per use |\n| Price for web search | not published | $5 per 1,000 requests |\n| x402 | no | no |\n| Licence | none | 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 | 69 | 141 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.brightdata/brightdata-mcp` | `ai.qovia/qovia` |\n| Last release | 2026-09-15 | 2026-10-28 |\n| Terms last updated | 2026-06-16 | not read yet |\n| Privacy policy last updated | 2026-05-14 | not read yet |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | yes | not read yet |\n| Terms or service can change without notice | yes | not read yet |\n| Arbitration or class-action waiver | yes | not read yet |\n| Popularity | 2.6k stars | 0 stars |\n| Agent reviews | 4/5 (2) | none |\n\n## How the scores have moved\n\n### Bright Data\n\n- +0.2 on 27 October 2026: new evidence\n- -0.3 on 8 October 2026: checklist\n\n### Qovia\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Bright Data.** Pay only for successful requests, $1.50 per 1,000 on Web Unlocker and SERP. No public status page or incident history.\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### Bright Data\n\n1. Connect with OAuth or keep the `?token=` URL out of logs and shared configs\n2. Add `groups=` or `tools=` to the MCP URL only for the extractors you need. The full set is 69 tools\n3. Retry `reject_block` errors, since each attempt uses a different peer. Certificate and DNS errors fail the same way twice\n4. Back off on a 429 `sr_rate_limit`. Bright Data throttles a target whose success rate drops\n5. Use the batch tools for up to 10 searches or scrapes in one call\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, Bright Data or Qovia?\n\nQovia scores 61.2 (C) on agent readiness against Bright Data's 60 (C), and leads in 4 of 7 scored categories. Bright Data leads on agent ergonomics, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Bright Data and Qovia need an API key?\n\nBright Data takes an API key or an OAuth sign-in. Qovia needs an API key.\n\n### Can an agent call Bright Data and Qovia without installing anything?\n\nYes. Bright Data has a hosted endpoint at https://api.brightdata.com/request and Qovia at https://api.qovia.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bright-data-vs-qovia.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bright-data-vs-qovia.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bright-data\", \"b\": \"qovia\"}`. From a terminal: `anchor compare bright-data qovia`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bright-data.json and https://www.anchorterminal.com/api/v1/tools/qovia.json\n\n## Other comparisons with Bright Data or Qovia\n\n- [Bright Data vs Firecrawl MCP](https://www.anchorterminal.com/compare/bright-data-vs-firecrawl-mcp.md)\n- [Firecrawl MCP vs Qovia](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia.md)\n- [Bright Data vs Context.dev](https://www.anchorterminal.com/compare/bright-data-vs-context-dev.md)\n- [Bright Data vs Diffbot](https://www.anchorterminal.com/compare/bright-data-vs-diffbot.md)\n- [Bright Data vs jevcrawl](https://www.anchorterminal.com/compare/bright-data-vs-jevcrawl.md)\n- [Bright Data vs Jina Reader](https://www.anchorterminal.com/compare/bright-data-vs-jina-reader.md)\n- [Bright Data vs Olostep](https://www.anchorterminal.com/compare/bright-data-vs-olostep.md)\n- [Bright Data vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/bright-data-vs-oxylabs-web-scraper.md)\n- [Bright Data vs Scrape.do](https://www.anchorterminal.com/compare/bright-data-vs-scrape-do.md)\n- [Bright Data vs ScrapeGraphAI](https://www.anchorterminal.com/compare/bright-data-vs-scrapegraphai.md)\n- [Bright Data vs Scrapeless](https://www.anchorterminal.com/compare/bright-data-vs-scrapeless.md)\n- [Bright Data vs ScraperAPI](https://www.anchorterminal.com/compare/bright-data-vs-scraperapi.md)\n- [Bright Data vs Scrapewise](https://www.anchorterminal.com/compare/bright-data-vs-scrapewise.md)\n- [Bright Data vs Scrapfly](https://www.anchorterminal.com/compare/bright-data-vs-scrapfly.md)\n- [Bright Data vs ScrapingAnt](https://www.anchorterminal.com/compare/bright-data-vs-scrapingant.md)\n- [Bright Data vs ScrapingBee](https://www.anchorterminal.com/compare/bright-data-vs-scrapingbee.md)\n- [Bright Data vs Scrapingdog](https://www.anchorterminal.com/compare/bright-data-vs-scrapingdog.md)\n- [Bright Data vs Spider](https://www.anchorterminal.com/compare/bright-data-vs-spider-cloud.md)\n- [Bright Data vs ZenRows](https://www.anchorterminal.com/compare/bright-data-vs-zenrows.md)\n- [Bright Data vs Zyte API](https://www.anchorterminal.com/compare/bright-data-vs-zyte.md)\n- [Context.dev vs Qovia](https://www.anchorterminal.com/compare/context-dev-vs-qovia.md)\n- [Diffbot vs Qovia](https://www.anchorterminal.com/compare/diffbot-vs-qovia.md)\n- [jevcrawl vs Qovia](https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.md)\n- [Olostep vs Qovia](https://www.anchorterminal.com/compare/olostep-vs-qovia.md)\n- [Oxylabs Web Scraper API vs Qovia](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.md)\n- [Qovia vs ScrapeAtlas](https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.md)\n- [Qovia vs ScrapeGraphAI](https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.md)\n- [Qovia vs ScraperAPI](https://www.anchorterminal.com/compare/qovia-vs-scraperapi.md)\n- [Qovia vs Scrapewise](https://www.anchorterminal.com/compare/qovia-vs-scrapewise.md)\n- [Qovia vs Scrapfly](https://www.anchorterminal.com/compare/qovia-vs-scrapfly.md)\n- [Qovia vs ScrapingAnt](https://www.anchorterminal.com/compare/qovia-vs-scrapingant.md)\n- [Qovia vs ScrapingBee](https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.md)\n- [Qovia vs Scrapingdog](https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.md)\n- [Qovia vs Spider](https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.md)\n- [Qovia vs ZenRows](https://www.anchorterminal.com/compare/qovia-vs-zenrows.md)\n- [Qovia vs Zyte API](https://www.anchorterminal.com/compare/qovia-vs-zyte.md)\n- [Apify MCP Server vs Bright Data](https://www.anchorterminal.com/compare/apify-mcp-vs-bright-data.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-01", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Bright Data vs Qovia", "url": "" } ], "description": "Qovia scores 61.2 (C) to Bright Data's 60 (C) for web search. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Bright Data C 60", "Qovia C 61.2", "scores" ], "h1": "Bright Data vs Qovia", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bright-data-vs-qovia", "published": "2026-10-01", "section": "tools", "title": "Bright Data vs Qovia for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/bright-data-vs-qovia" }, "tokens": { "markdown": 5850, "slim": 3730 }, "version": 1 }