{ "data": { "a": { "slug": "oxylabs-web-scraper", "name": "Oxylabs Web Scraper API", "vendor": "oxylabs, UAB", "vendorUrl": "https://oxylabs.io", "kind": "http-api", "category": "web-scrapers", "summary": "Hosted scraping API from Oxylabs that fetches public pages through its proxy pool with optional JavaScript rendering and returns HTML, Markdown or parsed JSON, with dedicated sources for Google, Amazon and other large sites.", "url": "https://www.anchorterminal.com/tools/oxylabs-web-scraper", "markdownUrl": "https://www.anchorterminal.com/tools/oxylabs-web-scraper.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/oxylabs-web-scraper.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/oxylabs-web-scraper.json", "dns": "oxylabs-web-scraper.grade.anchorterminal.com", "repo": "https://github.com/oxylabs/oxylabs-mcp", "license": "Proprietary service under the Oxylabs General Conditions. The MCP server and the Python SDK on GitHub are MIT", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://realtime.oxylabs.io/v1/queries", "packages": [ { "registry": "pypi", "name": "oxylabs" }, { "registry": "pypi", "name": "oxylabs-mcp" }, { "registry": "go", "name": "github.com/oxylabs/oxylabs-sdk-go" } ], "auth": "api-key", "authNotes": "HTTP Basic with the username and password of a product instance created in the Oxylabs dashboard. The password can be edited, an instance can take whitelisted IPs and a spending limit, and no scopes were found. The hosted MCP server takes the same pair in an `Authorization: Basic` header or in `X-Oxylabs-Username` and `X-Oxylabs-Password`. The Classic overview page says to contact the team for credentials, while the MCP page says they come from the dashboard, whose product list now shows only Web API under data collection.", "pricing": "usage", "pricingNotes": "A one-time $5 welcome credit with no payment details, then a monthly plan of $30, $100 or $500 whose amount becomes a credit balance shared across Oxylabs products and expires each cycle. On Starter, other targets cost $1.00 per 1,000 results without rendering and $1.50 with it, Amazon $0.50, Google $1.00 or $1.35 rendered, and LLM sources $1.50 (https://oxylabs.io/products/scraper-api/web/pricing, which now redirects to the Web API /Scrape pricing page, checked 2026-10-08). Purchases are non-refundable.", "priceSummary": "$30 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the pricing page, the docs index, the Web Scraper API pages or the MCP repository (checked 2026-10-08).", "endpoints": [] }, "toolCount": 10, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": 17594, "asOf": "2026-10-08" }, "docsUrl": "https://developers.oxylabs.io/products/web-scraper-api", "llmsTxt": "https://developers.oxylabs.io/llms.txt", "registryName": "io.oxylabs/oxylabs-mcp", "capabilities": [ "web.scrape", "web.extract", "scraping.proxies", "scraping.js-render", "scraping.anti-bot", "search.serp" ], "tags": [ "hosted", "no-card", "mcp", "llms-txt", "proxies", "python", "go", "closed-source", "status-page", "soc2" ], "lastRelease": "2026-09-07", "graded": true, "anchor": { "graded": true, "score": 63.1, "grade": "B", "agentReady": false, "rank": 463, "ranked": true, "rankOf": 1253, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 72, "payments": 40, "reliability": 80, "schema": 68, "security": 53, "transparency": 64 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": -3, "negativeNotes": [ "2026-03-18. The changelog announced that the `domain` parameter for Google sources was no longer available, with no earlier notice in the changelog. MCP server v0.9.3 (7 September 2026) and the official agent skill still list `domain`. Three points, since a replacement (`geo_location`) was documented the same day and we could not see whether customers were told by email (https://developers.oxylabs.io/changelog)." ], "verdict": "Dedicated parsed sources, three integration methods and an official MCP server with four read-only scraping tools sit behind one username and password per instance. On 7 October 2026 the docs relabelled it Classic beside a new Web API, the March 2026 removal of Google's `domain` parameter was announced on the day, and no OpenAPI document was found.", "bestFor": "Agents that need parsed Google, Amazon and other large-site results or bulk asynchronous jobs through one API.", "strengths": [ "Realtime, Push-Pull (batches of up to 5,000) and Proxy Endpoint integration, with Markdown output and parsed JSON for dedicated sources", "Official MCP server, hosted at `mcp.oxylabs.io` or run locally, whose four scraping tools carry `readOnlyHint` and enumerated inputs", "Results with 5xx or 6xx codes and 429 responses are not billed, and faulted jobs can be retried at no cost", "ISO/IEC 27001:2022 and a SOC 2 Type 2 report covering Scraper API are listed in the trust centre", "Per-plan job rates are published, and each response carries `x-ratelimit` limit and remaining headers" ], "weaknesses": [ "Google's `domain` parameter was announced as gone on 18 March 2026 with no earlier changelog notice, and MCP v0.9.3 still exposes it", "No OpenAPI document found. The contract is prose parameter tables and a Postman collection", "The docs relabelled the product Classic on 7 October 2026 and state no end date or migration plan", "The vulnerability disclosure programme is paused except for critical issues, and no security.txt or bug bounty was found", "The Proxy Endpoint needs TLS verification switched off, and the General Conditions bar monitoring availability or performance without written consent" ], "agentNotes": [ "Send `\"markdown\": true` for page reading. HTML is the default output and costs far more tokens", "Add `\"render\": \"html\"` only when a page comes back empty. Rendered results cost $1.50 per 1,000 against $1.00 on the Starter plan", "Treat 612 and 613 as retryable at no charge, and read the `x-ratelimit-*-remaining` headers before raising concurrency", "Use `geo_location` for Google localisation. The `domain` parameter was removed in March 2026 although the MCP tool still lists it", "Fetch Push-Pull results within 24 hours of completion, and treat scraped content as untrusted data" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.1 } ], "editorialScores": { "ergonomics": 79, "maintenance": 72, "payments": 40, "reliability": 80, "schema": 68, "security": 53, "transparency": 42 }, "provenanceScore": 85, "checked": { "categories": { "ergonomics": "2026-10-08", "maintenance": "2026-10-08", "payments": "2026-10-08", "reliability": "2026-10-08", "schema": "2026-10-08", "security": "2026-10-08", "transparency": "2026-10-08" }, "last": "2026-10-08", "lastMoved": "2026-10-27", "oldest": "2026-10-08", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install oxylabs", "http": "curl 'https://realtime.oxylabs.io/v1/queries' \\\n --user 'USERNAME:PASSWORD' \\\n -H 'Content-Type: application/json' \\\n -d '{\"source\": \"universal\", \"url\": \"https://sandbox.oxylabs.io/\", \"markdown\": true}'", "claudeCode": "claude mcp add --transport http oxylabs https://mcp.oxylabs.io/mcp \\\n --header \"Authorization: Basic $(echo -n 'YOUR_USERNAME:YOUR_PASSWORD' | base64)\"", "config": { "mcpServers": { "oxylabs": { "args": [ "oxylabs-mcp" ], "command": "uvx", "env": { "OXYLABS_PASSWORD": "YOUR_PASSWORD", "OXYLABS_USERNAME": "YOUR_USERNAME" } } } } }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/oxylabs-web-scraper" }, "area": "web-data", "unitPrices": [ { "item": "Starter plan", "unit": "month", "usd": 30, "note": "Credit balance shared across Oxylabs products, expires each cycle, VAT may apply" }, { "item": "Other targets without rendering, Starter", "unit": "1k-requests", "usd": 1, "note": "Per 1,000 billable results" }, { "item": "Other targets with JavaScript rendering, Starter", "unit": "1k-requests", "usd": 1.5, "note": "Per 1,000 billable results" }, { "item": "Amazon without rendering, Starter", "unit": "1k-requests", "usd": 0.5, "note": "Per 1,000 billable results" }, { "item": "Google without rendering, Starter", "unit": "1k-requests", "usd": 1, "note": "$1.35 with rendering" } ], "provenance": { "legalEntity": "oxylabs, UAB", "domain": "oxylabs.io", "domainRegistered": "2015-11-30", "endpointOnVendorDomain": true, "terms": "https://oxylabs.io/legal/v1-oxylabs-general-conditions", "privacy": "https://oxylabs.io/legal/privacy", "statusPage": "https://uptime.oxylabs.io", "changelog": "https://developers.oxylabs.io/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The General Conditions of the oxylabs, UAB Services Agreement name a Lithuanian company registered at Švitrigailos str. 32, Vilnius, and were last updated on 5 October 2026. They are linked from the trust centre, not from the site footer.", "The privacy policy was last updated on 14 October 2024 and does not name the controlling entity. It covers registration and self-service use as well as the website.", "https://oxylabs.io/.well-known/security.txt returns 404. The vulnerability disclosure policy gives security@oxylabs.io and says the programme is paused except for critical issues.", "RDAP gives a registration date of 2015-11-30 for oxylabs.io.", "The API answers on realtime.oxylabs.io and data.oxylabs.io, and the hosted MCP server on mcp.oxylabs.io." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/oxylabs-web-scraper.json", "live": { "slug": "oxylabs-web-scraper", "probe": { "target": "https://realtime.oxylabs.io/v1/queries", "method": "get", "lastAt": "2026-11-01T22:08:41.164899031Z", "lastOk": true, "lastStatus": 404, "lastMs": 100, "authRequired": false, "uptime24h": 100, "uptime30d": 99.93, "p50ms24h": 112, "p95ms24h": 168, "samples24h": 250, "samples30d": 5913, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 246 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 230, "ok": 230 } ], "outages": [ { "start": "2026-10-28T06:38:25.688447591Z", "end": "2026-10-28T06:55:00.16149851Z", "note": "timed out" } ] }, "vendorStatus": { "page": "https://uptime.oxylabs.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-01T22:09:52.176709637Z" }, "versions": [ { "registry": "github", "name": "oxylabs/oxylabs-mcp", "version": "v0.10.2", "released": "2026-10-29", "seenAt": "2026-11-01T17:22:53.739945052Z" }, { "registry": "mcp-registry", "name": "io.oxylabs/oxylabs-mcp", "version": "0.10.2", "seenAt": "2026-11-01T16:10:44.053973489Z" }, { "registry": "pypi", "name": "oxylabs", "version": "3.0.0", "released": "2026-03-09", "seenAt": "2026-11-01T17:22:51.724582374Z" }, { "registry": "pypi", "name": "oxylabs-mcp", "version": "0.10.2", "released": "2026-10-29", "seenAt": "2026-11-01T17:22:51.930613302Z" } ], "githubStars": 104, "pypiWeekly": 30170, "securityTxt": { "url": "https://oxylabs.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:42:09.20933986Z" }, "llmsTxt": { "url": "https://developers.oxylabs.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:14:40.111143848Z" }, "domain": { "domain": "oxylabs.io", "checkedAt": "2026-11-01T14:26:42.02839894Z" }, "pages": [ { "url": "https://developers.oxylabs.io/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-01T06:40:07.900998627Z", "changedAt": "2026-10-30T05:35:48.388829901Z", "fingerprint": "48f0807509ae" }, { "url": "https://oxylabs.io/products/scraper-api/web/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-11-01T06:49:13.991485612Z", "changedAt": "2026-10-28T04:39:54.019970924Z", "fingerprint": "b1734b60f0b1" }, { "url": "https://oxylabs.io/legal/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-01T06:49:09.795101324Z", "changedAt": "2026-10-24T02:22:23.189234723Z", "fingerprint": "67a7ec9f4ace" }, { "url": "https://oxylabs.io/legal/v1-oxylabs-general-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-01T06:49:11.819699221Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "12d31ffc465f" } ], "github": { "repo": "oxylabs/oxylabs-mcp", "checkedAt": "2026-10-26T07:53:45.638172075Z", "stars": 104, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-15T07:48:32Z", "openIssues": 2, "openPRs": 0, "issuesOpened90d": 1, "issuesClosed90d": 0, "prsMerged90d": 9, "ci": { "branch": "main", "runs": 30, "success": 30, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-15T07:48:35Z" }, "replies": { "sampled": 5, "unanswered": 2, "medianDays": 8.2 } }, "updatedAt": "2026-11-01T22:09:52.176709637Z" } }, "answer": "Oxylabs Web Scraper API scores 63.1 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.", "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": 40, "category": "reliability", "leads": "oxylabs-web-scraper", "name": "Reliability", "reasons": { "a": "Graded on the Web Scraper API (Classic) surface. Status page at uptime.oxylabs.io on incident.io with separate components for Scraper APIs Push-Pull and Real-Time (20). Both show 100 per cent uptime for July to October 2026 and the page reported no current issue, but the incident list is drawn by script and its history URL returned 404 to our reader, so we scored below clean (25 of 30). Job rates per plan are published, from 10 a second on the trial to 100 on Business, with rendered-job limits (15). 429 is not billed, responses carry `x-ratelimit` limit and remaining headers, and 612 and 613 faults can be retried at no cost. No Retry-After or backoff guidance was found for this API (10 of 15). No SLA is published. The product page claims 99.9 per cent API uptime and the General Conditions promise reasonable efforts (0). Generally available (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": 80, "b": 40 } }, { "by": 34, "category": "transparency", "leads": "oxylabs-web-scraper", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under public General Conditions naming oxylabs, UAB of Vilnius, last updated 5 October 2026, with MIT clients (15 of 30). The privacy policy dates from 14 October 2024, does not name the controller and says nothing about scraped content. Clause 4.3.9 of the General Conditions lets Oxylabs keep data gathered through Web API and Web Unblocker and use it at its discretion, and it is unclear whether Web API there includes this Classic API. A DPA is published and Push-Pull results are kept for at least 24 hours (14 of 30). No deprecation policy. Removals appear in the changelog on the day they take effect, and the General Conditions give 14 days' notice of contract changes (6 of 20). The DPA says the sub-processor list is available on request. The privacy policy names some vendors, and data locations are given only as the EEA and the US (7 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": 64, "b": 30 } }, { "by": 18, "category": "schema", "leads": "qovia", "name": "Schema \u0026 documentation", "reasons": { "a": "No OpenAPI document was found. The contract is parameter tables per source plus a Postman collection, and the MCP server types every input (10 of 25). llms.txt indexes the docs and every page is served as Markdown by adding `.md` (10). Each source page states its parameters and defaults, and the MCP `output_format` description says when to choose links, Markdown or HTML, though tool descriptions are two lines (13 of 20). MCP inputs use enumerations for rendering, user agent and output format. The REST API takes `context` as a list of key and value pairs and free-form parsing instructions (10 of 15). Request examples in several languages, sample outputs, and a response code table covering HTTP, parser, storage and session codes (13 of 15). Paths are versioned at `/v1` and the public changelog is dated, while the MCP repository's CHANGELOG.md stops at 0.2.2 in May 2025 although v0.9.3 shipped in September 2026 (12 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": 68, "b": 86 } }, { "by": 15, "category": "payments", "leads": "qovia", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-1,000-result prices by target and plan are public (20). A one-time $5 welcome credit needs no payment details (20). A person registers in the dashboard and creates the product instance (0). The Classic overview page says to contact the team for credentials, which conflicts with the dashboard instructions elsewhere, so the trial route for this surface is unconfirmed.", "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": 7, "category": "security", "leads": "qovia", "name": "Security \u0026 auth", "reasons": { "a": "A username and password per product instance over HTTP Basic, with an editable password, optional IP whitelisting and several instances per account. No scopes (20 of 30). The Proxy Endpoint puts the pair in the proxy URL and needs TLS verification switched off, which we note without the query-string deduction. Scraping is read-only apart from POST requests to targets, callbacks and uploads to the customer's bucket, each instance can take a spending limit that disables it, and every MCP tool is marked read-only (10 of 20). No guidance on untrusted page content was found in the Web Scraper API docs, the MCP README or the agent skill (2 of 15). `GET /v2/stats` and the dashboard report usage by day and source, and jobs accept client notes. No per-request access log was found (7 of 15). ISO/IEC 27001:2022, SOC 2 Type 2 for Scraper API and yearly penetration tests per the trust centre, but the disclosure programme is paused except for critical issues, security.txt returns 404 and no bug bounty was found (14 of 20).", "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": 53, "b": 60 } }, { "by": 5, "category": "maintenance", "leads": "qovia", "name": "Maintenance \u0026 community", "reasons": { "a": "The last dated change to this API is the Google Travel hotels parser on 24 August 2026, and MCP server v0.9.3 followed on 7 September, both within 90 days (20 of 30). Eleven changelog entries tagged for this API between 13 July and 24 August 2026 (20). Dated public changelog, support by email and round-the-clock live chat per the docs. GitHub issues were unread because the API refused us (10 of 15). The MCP server is in the official registry as `io.oxylabs/oxylabs-mcp`, where the latest entry is 0.9.1 against 0.9.3 on PyPI, and official Python and Go SDKs exist (15). The MCP repository runs lint and test workflows. The Python SDK's last release is 3.0.0 on 9 March 2026 (7 of 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": 72, "b": 77 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "oxylabs, UAB", "b": "Qovia", "name": "Vendor" }, { "a": "https://realtime.oxylabs.io/v1/queries", "b": "https://api.qovia.ai", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, stdio", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Oxylabs General Conditions. The MCP server and the Python SDK on GitHub are MIT", "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": "10", "b": "141", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.oxylabs/oxylabs-mcp", "b": "ai.qovia/qovia", "name": "MCP registry" }, { "a": "2026-09-07", "b": "2026-10-28", "name": "Last release" }, { "a": "2026-10-05", "b": "not read yet", "name": "Terms last updated" }, { "a": "2024-10-14", "b": "not read yet", "name": "Privacy policy last updated" }, { "a": "yes", "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": "not found in the text", "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": "18k PyPI/wk", "b": "0 stars", "name": "Popularity" }, { "a": "3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Oxylabs Web Scraper API scores 63.1 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Oxylabs Web Scraper API or Qovia?" }, { "answer": "Both need an API key.", "question": "Do Oxylabs Web Scraper API and Qovia need an API key?" }, { "answer": "Yes. Oxylabs Web Scraper API has a hosted endpoint at https://realtime.oxylabs.io/v1/queries and Qovia at https://api.qovia.ai.", "question": "Can an agent call Oxylabs Web Scraper API and Qovia without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 80 against 40", "Transparency \u0026 trust, 64 against 30" ], "also": [ "Runs on your own machine", "Free to start without a card" ], "goodFor": "Agents that need parsed Google, Amazon and other large-site results or bulk asynchronous jobs through one API.", "slug": "oxylabs-web-scraper", "watchFor": "Google's `domain` parameter was announced as gone on 18 March 2026 with no earlier changelog notice, and MCP v0.9.3 still exposes it" }, { "aheadOn": [ "Schema \u0026 documentation, 86 against 68", "Security \u0026 auth, 60 against 53", "Payments \u0026 pricing, 55 against 40", "Maintenance \u0026 community, 77 against 72" ], "also": [ "No incidents deducted, where Oxylabs Web Scraper API loses 3 points for them" ], "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": { "oxylabs-web-scraper": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 63, "fromGrade": "B", "to": 63.1, "toGrade": "B" } ], "qovia": 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/apify-mcp-vs-oxylabs-web-scraper.json", "title": "Apify MCP Server vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-oxylabs-web-scraper" }, { "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/context-dev-vs-oxylabs-web-scraper.json", "title": "Context.dev vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/context-dev-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-oxylabs-web-scraper.json", "title": "jevcrawl vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/jina-reader-vs-oxylabs-web-scraper.json", "title": "Jina Reader vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/jina-reader-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/olostep-vs-oxylabs-web-scraper.json", "title": "Olostep vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/olostep-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrape-do.json", "title": "Oxylabs Web Scraper API vs Scrape.do", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrape-do" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapegraphai.json", "title": "Oxylabs Web Scraper API vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapeless.json", "title": "Oxylabs Web Scraper API vs Scrapeless", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapeless" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scraperapi.json", "title": "Oxylabs Web Scraper API vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapewise.json", "title": "Oxylabs Web Scraper API vs Scrapewise", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapfly.json", "title": "Oxylabs Web Scraper API vs Scrapfly", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingant.json", "title": "Oxylabs Web Scraper API vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingbee.json", "title": "Oxylabs Web Scraper API vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingdog.json", "title": "Oxylabs Web Scraper API vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-spider-cloud.json", "title": "Oxylabs Web Scraper API vs Spider", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-zenrows.json", "title": "Oxylabs Web Scraper API vs ZenRows", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-zyte.json", "title": "Oxylabs Web Scraper API vs Zyte API", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-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-oxylabs-web-scraper.json", "title": "Diffbot vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/diffbot-vs-oxylabs-web-scraper" }, { "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-oxylabs-web-scraper.json", "title": "Firecrawl MCP vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-oxylabs-web-scraper" }, { "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-scrapeatlas.json", "title": "Oxylabs Web Scraper API vs ScrapeAtlas", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapeatlas" }, { "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" } ], "panel": null, "scores": [ { "by": 40, "edge": "oxylabs-web-scraper", "key": "reliability", "name": "Reliability", "oxylabs-web-scraper": 80, "qovia": 40, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 18, "edge": "qovia", "key": "schema", "name": "Schema \u0026 documentation", "oxylabs-web-scraper": 68, "qovia": 86, "weight": 13 }, { "by": 2, "edge": "oxylabs-web-scraper", "key": "ergonomics", "name": "Agent ergonomics", "oxylabs-web-scraper": 79, "qovia": 77, "weight": 13 }, { "by": 7, "edge": "qovia", "key": "security", "name": "Security \u0026 auth", "oxylabs-web-scraper": 53, "qovia": 60, "weight": 14 }, { "by": 15, "edge": "qovia", "key": "payments", "name": "Payments \u0026 pricing", "oxylabs-web-scraper": 40, "qovia": 55, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 5, "edge": "qovia", "key": "maintenance", "name": "Maintenance \u0026 community", "oxylabs-web-scraper": 72, "qovia": 77, "weight": 7 }, { "by": 34, "edge": "oxylabs-web-scraper", "key": "transparency", "name": "Transparency \u0026 trust", "oxylabs-web-scraper": 64, "qovia": 30, "weight": 7 } ], "summary": "Oxylabs Web Scraper API scores 63.1 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community. Both do extraction.", "tasks": null, "tutorials": [], "verdicts": { "oxylabs-web-scraper": "Dedicated parsed sources, three integration methods and an official MCP server with four read-only scraping tools sit behind one username and password per instance. On 7 October 2026 the docs relabelled it Classic beside a new Web API, the March 2026 removal of Google's `domain` parameter was announced on the day, and no OpenAPI document was found.", "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/oxylabs-web-scraper-vs-qovia", "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.min.md" }, "markdown": "Oxylabs Web Scraper API scores 63.1 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community. Both do extraction.\n\n- Oxylabs Web Scraper API: grade B, 63.1/100, rank #463 of 1253. Markdown https://www.anchorterminal.com/tools/oxylabs-web-scraper.md · JSON https://www.anchorterminal.com/api/v1/tools/oxylabs-web-scraper.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### Oxylabs Web Scraper API (B)\n\nGood for: Agents that need parsed Google, Amazon and other large-site results or bulk asynchronous jobs through one API.\n\nAhead on:\n- Reliability, 80 against 40\n- Transparency \u0026 trust, 64 against 30\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Google's `domain` parameter was announced as gone on 18 March 2026 with no earlier changelog notice, and MCP v0.9.3 still exposes it\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 68\n- Security \u0026 auth, 60 against 53\n- Payments \u0026 pricing, 55 against 40\n- Maintenance \u0026 community, 77 against 72\n\nAlso in its favour:\n- No incidents deducted, where Oxylabs Web Scraper API loses 3 points for them\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### Reliability: Oxylabs Web Scraper API +40\n\n- Oxylabs Web Scraper API (80): Graded on the Web Scraper API (Classic) surface. Status page at uptime.oxylabs.io on incident.io with separate components for Scraper APIs Push-Pull and Real-Time (20). Both show 100 per cent uptime for July to October 2026 and the page reported no current issue, but the incident list is drawn by script and its history URL returned 404 to our reader, so we scored below clean (25 of 30). Job rates per plan are published, from 10 a second on the trial to 100 on Business, with rendered-job limits (15). 429 is not billed, responses carry `x-ratelimit` limit and remaining headers, and 612 and 613 faults can be retried at no cost. No Retry-After or backoff guidance was found for this API (10 of 15). No SLA is published. The product page claims 99.9 per cent API uptime and the General Conditions promise reasonable efforts (0). Generally available (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### Transparency \u0026 trust: Oxylabs Web Scraper API +34\n\n- Oxylabs Web Scraper API (64): Closed service under public General Conditions naming oxylabs, UAB of Vilnius, last updated 5 October 2026, with MIT clients (15 of 30). The privacy policy dates from 14 October 2024, does not name the controller and says nothing about scraped content. Clause 4.3.9 of the General Conditions lets Oxylabs keep data gathered through Web API and Web Unblocker and use it at its discretion, and it is unclear whether Web API there includes this Classic API. A DPA is published and Push-Pull results are kept for at least 24 hours (14 of 30). No deprecation policy. Removals appear in the changelog on the day they take effect, and the General Conditions give 14 days' notice of contract changes (6 of 20). The DPA says the sub-processor list is available on request. The privacy policy names some vendors, and data locations are given only as the EEA and the US (7 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### Schema \u0026 documentation: Qovia +18\n\n- Oxylabs Web Scraper API (68): No OpenAPI document was found. The contract is parameter tables per source plus a Postman collection, and the MCP server types every input (10 of 25). llms.txt indexes the docs and every page is served as Markdown by adding `.md` (10). Each source page states its parameters and defaults, and the MCP `output_format` description says when to choose links, Markdown or HTML, though tool descriptions are two lines (13 of 20). MCP inputs use enumerations for rendering, user agent and output format. The REST API takes `context` as a list of key and value pairs and free-form parsing instructions (10 of 15). Request examples in several languages, sample outputs, and a response code table covering HTTP, parser, storage and session codes (13 of 15). Paths are versioned at `/v1` and the public changelog is dated, while the MCP repository's CHANGELOG.md stops at 0.2.2 in May 2025 although v0.9.3 shipped in September 2026 (12 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### Payments \u0026 pricing: Qovia +15\n\n- Oxylabs Web Scraper API (40): No x402, MPP or L402 (0). Per-1,000-result prices by target and plan are public (20). A one-time $5 welcome credit needs no payment details (20). A person registers in the dashboard and creates the product instance (0). The Classic overview page says to contact the team for credentials, which conflicts with the dashboard instructions elsewhere, so the trial route for this surface is unconfirmed.\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 +7\n\n- Oxylabs Web Scraper API (53): A username and password per product instance over HTTP Basic, with an editable password, optional IP whitelisting and several instances per account. No scopes (20 of 30). The Proxy Endpoint puts the pair in the proxy URL and needs TLS verification switched off, which we note without the query-string deduction. Scraping is read-only apart from POST requests to targets, callbacks and uploads to the customer's bucket, each instance can take a spending limit that disables it, and every MCP tool is marked read-only (10 of 20). No guidance on untrusted page content was found in the Web Scraper API docs, the MCP README or the agent skill (2 of 15). `GET /v2/stats` and the dashboard report usage by day and source, and jobs accept client notes. No per-request access log was found (7 of 15). ISO/IEC 27001:2022, SOC 2 Type 2 for Scraper API and yearly penetration tests per the trust centre, but the disclosure programme is paused except for critical issues, security.txt returns 404 and no bug bounty was found (14 of 20).\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 +5\n\n- Oxylabs Web Scraper API (72): The last dated change to this API is the Google Travel hotels parser on 24 August 2026, and MCP server v0.9.3 followed on 7 September, both within 90 days (20 of 30). Eleven changelog entries tagged for this API between 13 July and 24 August 2026 (20). Dated public changelog, support by email and round-the-clock live chat per the docs. GitHub issues were unread because the API refused us (10 of 15). The MCP server is in the official registry as `io.oxylabs/oxylabs-mcp`, where the latest entry is 0.9.1 against 0.9.3 on PyPI, and official Python and Go SDKs exist (15). The MCP repository runs lint and test workflows. The Python SDK's last release is 3.0.0 on 9 March 2026 (7 of 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## Score by category\n\n| Category | Weight | Oxylabs Web Scraper API | Qovia | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 40 | Oxylabs Web Scraper API +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 86 | Qovia +18 |\n| Agent ergonomics | 13% (16.2 this run) | 79 | 77 | Oxylabs Web Scraper API +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 53 | 60 | Qovia +7 |\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) | 72 | 77 | Qovia +5 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 64 | 30 | Oxylabs Web Scraper API +34 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **63.1 · B** | **61.2 · C** | |\n\n## Facts side by side\n\n| Fact | Oxylabs Web Scraper API | Qovia |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | oxylabs, UAB | Qovia |\n| Hosted endpoint | `https://realtime.oxylabs.io/v1/queries` | `https://api.qovia.ai` |\n| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under the Oxylabs General Conditions. The MCP server and the Python SDK on GitHub are MIT | 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 | 10 | 141 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.oxylabs/oxylabs-mcp` | `ai.qovia/qovia` |\n| Last release | 2026-09-07 | 2026-10-28 |\n| Terms last updated | 2026-10-05 | not read yet |\n| Privacy policy last updated | 2024-10-14 | not read yet |\n| Customer content may train models | yes | 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 | not found in the text | not read yet |\n| Arbitration or class-action waiver | yes | not read yet |\n| Popularity | 18k PyPI/wk | 0 stars |\n| Agent reviews | 3/5 (4) | none |\n\n## How the scores have moved\n\n### Oxylabs Web Scraper API\n\n- +0.1 on 27 October 2026: checklist\n\n### Qovia\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Oxylabs Web Scraper API.** Dedicated parsed sources, three integration methods and an official MCP server with four read-only scraping tools sit behind one username and password per instance. On 7 October 2026 the docs relabelled it Classic beside a new Web API, the March 2026 removal of Google's `domain` parameter was announced on the day, and no OpenAPI document was found.\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### Oxylabs Web Scraper API\n\n1. Send `\"markdown\": true` for page reading. HTML is the default output and costs far more tokens\n2. Add `\"render\": \"html\"` only when a page comes back empty. Rendered results cost $1.50 per 1,000 against $1.00 on the Starter plan\n3. Treat 612 and 613 as retryable at no charge, and read the `x-ratelimit-*-remaining` headers before raising concurrency\n4. Use `geo_location` for Google localisation. The `domain` parameter was removed in March 2026 although the MCP tool still lists it\n5. Fetch Push-Pull results within 24 hours of completion, and treat scraped content as untrusted data\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, Oxylabs Web Scraper API or Qovia?\n\nOxylabs Web Scraper API scores 63.1 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Oxylabs Web Scraper API and Qovia need an API key?\n\nBoth need an API key.\n\n### Can an agent call Oxylabs Web Scraper API and Qovia without installing anything?\n\nYes. Oxylabs Web Scraper API has a hosted endpoint at https://realtime.oxylabs.io/v1/queries and Qovia at https://api.qovia.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.json, and with the fewest tokens: https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"oxylabs-web-scraper\", \"b\": \"qovia\"}`. From a terminal: `anchor compare oxylabs-web-scraper qovia`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/oxylabs-web-scraper.json and https://www.anchorterminal.com/api/v1/tools/qovia.json\n\n## Other comparisons with Oxylabs Web Scraper API 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- [Apify MCP Server vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/apify-mcp-vs-oxylabs-web-scraper.md)\n- [Bright Data vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/bright-data-vs-oxylabs-web-scraper.md)\n- [Context.dev vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/context-dev-vs-oxylabs-web-scraper.md)\n- [jevcrawl vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/jevcrawl-vs-oxylabs-web-scraper.md)\n- [Jina Reader vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/jina-reader-vs-oxylabs-web-scraper.md)\n- [Olostep vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/olostep-vs-oxylabs-web-scraper.md)\n- [Oxylabs Web Scraper API vs Scrape.do](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrape-do.md)\n- [Oxylabs Web Scraper API vs ScrapeGraphAI](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapegraphai.md)\n- [Oxylabs Web Scraper API vs Scrapeless](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapeless.md)\n- [Oxylabs Web Scraper API vs ScraperAPI](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scraperapi.md)\n- [Oxylabs Web Scraper API vs Scrapewise](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapewise.md)\n- [Oxylabs Web Scraper API vs Scrapfly](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapfly.md)\n- [Oxylabs Web Scraper API vs ScrapingAnt](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingant.md)\n- [Oxylabs Web Scraper API vs ScrapingBee](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingbee.md)\n- [Oxylabs Web Scraper API vs Scrapingdog](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapingdog.md)\n- [Oxylabs Web Scraper API vs Spider](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-spider-cloud.md)\n- [Oxylabs Web Scraper API vs ZenRows](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-zenrows.md)\n- [Oxylabs Web Scraper API vs Zyte API](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-zyte.md)\n- [Context.dev vs Qovia](https://www.anchorterminal.com/compare/context-dev-vs-qovia.md)\n- [Diffbot vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/diffbot-vs-oxylabs-web-scraper.md)\n- [Diffbot vs Qovia](https://www.anchorterminal.com/compare/diffbot-vs-qovia.md)\n- [Firecrawl MCP vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-oxylabs-web-scraper.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 ScrapeAtlas](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapeatlas.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", "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": "Oxylabs Web Scraper API vs Qovia", "url": "" } ], "description": "Oxylabs Web Scraper scores 63.1 (B) to Qovia's 61.2 (C) for extraction. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Oxylabs Web Scraper API B 63.1", "Qovia C 61.2", "scores" ], "h1": "Oxylabs Web Scraper API vs Qovia", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/oxylabs-web-scraper-vs-qovia", "published": "2026-10-01", "section": "tools", "title": "Oxylabs Web Scraper vs Qovia for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia" }, "tokens": { "markdown": 6550, "slim": 4180 }, "version": 1 }