{ "data": { "a": { "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" } }, "answer": "Spider scores 74.6 (BB) on agent readiness against Qovia's 61.2 (C), and leads in 4 of 7 scored categories. Qovia leads on agent ergonomics and security \u0026 auth.", "b": { "slug": "spider-cloud", "name": "Spider", "vendor": "Spider (BAGELMEN LLC)", "vendorUrl": "https://spider.cloud", "kind": "http-api", "category": "web-scrapers", "summary": "Hosted crawl, scrape, search, links and screenshot API built on the open-source Rust spider crate, plus a cloud browser and proxy pool.", "url": "https://www.anchorterminal.com/tools/spider-cloud", "markdownUrl": "https://www.anchorterminal.com/tools/spider-cloud.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/spider-cloud.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/spider-cloud.json", "dns": "spider-cloud.grade.anchorterminal.com", "repo": "https://github.com/spider-rs/spider", "license": "MIT", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.spider.cloud", "packages": [ { "registry": "npm", "name": "@spider-cloud/spider-client" }, { "registry": "pypi", "name": "spider_client" }, { "registry": "npm", "name": "spider-cloud-mcp" } ], "auth": "mixed", "authNotes": "Bearer key in the Authorization header. POST /scrape also works with no key at 4 requests a minute. Every core route accepts x402 in place of a key. The hosted MCP server takes a Bearer key or runs OAuth (PKCE, dynamic client registration, a single mcp scope) on first connect.", "pricing": "usage", "pricingNotes": "Pay as you go at $1 per 10,000 credits, metered as $1 per GB of fetched content plus $0.0001 per CPU minute. No subscription and the balance doesn't expire. Top-ups of $500 or more get a 5 per cent bonus, $2,000 or more 12 per cent. Unlimited plans bill by concurrency, self-serve from $40 a month for 2 to $19,994 for 1,538 ($350 for 25), the price per seat falling from $20 to $13. Zero data retention bills at 2.5 times credits. AI Studio routes need a plan from $6 a month (https://spider.cloud/pricing).", "priceSummary": "$0.0005 / call", "where": "both", "x402": { "level": "yes", "evidence": "x402 v2 on all core routes, exact scheme, USDC on Base (eip155:8453), priced 1 to 1 with credits. Estimates are /scrape $0.0005, /crawl $0.005, /search $0.002, /links $0.0002 (https://spider.cloud/docs/integrations/x402). Our unpaid POST to /crawl on 2026-09-30 returned 402 with a PAYMENT-REQUIRED header and an x402Version 2 body.", "endpoints": [ { "url": "https://api.spider.cloud/scrape", "priceUsd": 0.0005, "network": "eip155:8453" }, { "url": "https://api.spider.cloud/crawl", "priceUsd": 0.005, "network": "eip155:8453" }, { "url": "https://api.spider.cloud/search", "priceUsd": 0.002, "network": "eip155:8453" }, { "url": "https://api.spider.cloud/links", "priceUsd": 0.0002, "network": "eip155:8453" } ] }, "toolCount": 21, "popularity": { "githubStars": 2748, "npmWeekly": 2745, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://spider.cloud/docs/overview", "llmsTxt": "https://spider.cloud/llms.txt", "openapi": "https://spider.cloud/openapi.yaml", "registryName": "cloud.spider/mcp", "capabilities": [ "web.scrape", "web.extract", "web.crawl", "web.search", "web.fetch", "browser.hosted", "scraping.proxies", "scraping.js-render", "scraping.anti-bot", "scraping.screenshot" ], "tags": [ "hosted", "mcp", "llms-txt", "proxies", "open-source", "python", "typescript", "openapi", "x402", "no-key" ], "lastRelease": "2026-09-05", "graded": true, "anchor": { "graded": true, "score": 74.6, "grade": "BB", "agentReady": true, "rank": 66, "ranked": true, "rankOf": 1253, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 75, "payments": 96, "reliability": 85, "schema": 87, "security": 42, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "Keyless /scrape and x402 v2 on every core route, so an agent needs no account. Operated by BAGELMEN LLC with no security.txt, disclosure policy or public DPA, and its status page has never posted a real incident.", "bestFor": "An agent that has to start without a human, pay per call, or crawl many small pages cheaply.", "strengths": [ "Keyless /scrape and x402 v2 on every core route, so an agent needs no account", "Metered by bytes and CPU, so small pages cost a fraction of a cent", "Published rate limits, 10,000 requests a minute rising with usage, with RateLimit and Retry-After headers and a backoff example", "Stated retention, request logs up to 30 days and cached pages up to 48 hours, with a zero data retention option", "The Rust crawler, clients and MCP are MIT and can be self-hosted" ], "weaknesses": [ "No security.txt, disclosure policy, certification or prompt-injection guidance found", "A DPA only for Enterprise customers who sign one, and the privacy policy no longer names its service providers", "Invalid parameter values fall back silently instead of returning 400", "Errored attempts are billed for the bytes and compute they used, despite the pricing page's failed requests cost $0", "No dated release or changelog entry since 1 October 2026, and the status page has posted no real incident since it opened in June 2024" ], "agentNotes": [ "Every content route returns a JSON array, even /scrape. The status field is the page's, not the API call's", "Leave request on smart and set return_format to markdown for LLM input", "Set limit on /crawl. Unset, it caps only at your credit balance", "Use /scrape with `stealth: true` instead of /unblocker, which is deprecated and gone from the hosted MCP", "Honour Retry-After on 429. Keyless use allows 4 requests a minute" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 74.6 } ], "editorialScores": { "ergonomics": 70, "maintenance": 75, "payments": 96, "reliability": 85, "schema": 87, "security": 42, "transparency": 61 }, "provenanceScore": 79, "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", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -X POST https://api.spider.cloud/scrape -H \"Authorization: Bearer $SPIDER_API_KEY\" \\\n -H \"Content-Type: application/json\" -d '{\"url\":\"https://example.com\",\"return_format\":\"markdown\"}'", "claudeCode": "claude mcp add spider --transport http https://mcp.spider.cloud/mcp -H \"Authorization: Bearer $SPIDER_API_KEY\"", "config": { "mcpServers": { "spider": { "headers": { "Authorization": "Bearer ${SPIDER_API_KEY}" }, "url": "https://mcp.spider.cloud/mcp" } } } }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/spider-cloud" }, "area": "web-data", "unitPrices": [ { "item": "Credits", "unit": "credit", "usd": 0.0001, "note": "$1 per 10,000" }, { "item": "Bandwidth", "unit": "gb", "usd": 1, "note": "pre-transformation content" }, { "item": "Compute", "unit": "vcpu-hour", "usd": 0.006, "note": "billed at $0.0001 per CPU minute" }, { "item": "Scrape via x402", "unit": "1k-requests", "usd": 0.5, "note": "published estimate of 5 credits a scrape. Small pages cost far less" }, { "item": "Unlimited, 25 concurrent", "unit": "month", "usd": 350 }, { "item": "Unlimited, 2 concurrent", "unit": "month", "usd": 40 } ], "provenance": { "legalEntity": "BAGELMEN LLC", "domain": "spider.cloud", "domainRegistered": "2024-04-22", "domainNote": "spider.cloud dates from 2024, but the spider crate it runs on has been on GitHub since January 2018.", "endpointOnVendorDomain": true, "terms": "https://spider.cloud/eula", "privacy": "https://spider.cloud/privacy", "statusPage": "https://spidercloud.statuspage.io", "changelog": "https://spider.cloud/changelog", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "The EULA and privacy policy both name BAGELMEN LLC as operator. The October 2026 privacy policy gives its address, 1600 Polk Way, Sanford, FL 32773, United States", "security.txt returned 404 at spider.cloud/.well-known/security.txt and spider.cloud/security.txt on 2026-11-01", "The EULA and the privacy policy both read 'Last updated · October 2026' on 2026-11-01" ], "score": 79 }, "requirements": { "agentAlone": true, "card": "unknown", "minutes": 5, "credential": "mixed", "hosting": [ "US" ], "euResidency": "unknown", "trainsOnData": "no", "zeroRetention": "yes", "selfHost": "no" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/spider-cloud.json", "live": { "slug": "spider-cloud", "probe": { "target": "https://api.spider.cloud", "method": "get", "lastAt": "2026-11-01T22:08:48.503884518Z", "lastOk": true, "lastStatus": 402, "lastMs": 288, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 284, "p95ms24h": 359, "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": 272 }, { "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": 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": 250 }, { "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 } ] }, "vendorStatus": { "page": "https://spidercloud.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-01T22:10:08.847762608Z" }, "versions": [ { "registry": "github", "name": "spider-rs/spider", "version": "v2.53.9", "released": "2026-10-30", "seenAt": "2026-11-01T17:35:05.46452311Z" }, { "registry": "mcp-registry", "name": "cloud.spider/mcp", "version": "1.0.0", "seenAt": "2026-11-01T16:10:44.053973489Z" }, { "registry": "npm", "name": "@spider-cloud/spider-client", "version": "0.2.5", "seenAt": "2026-11-01T17:35:03.108888082Z" }, { "registry": "npm", "name": "spider-cloud-mcp", "version": "1.2.2", "seenAt": "2026-11-01T17:35:03.769749431Z" }, { "registry": "pypi", "name": "spider_client", "version": "0.1.93", "released": "2026-07-18", "seenAt": "2026-11-01T17:35:03.579453327Z" } ], "githubStars": 2814, "npmWeekly": 2642, "pypiWeekly": 115906, "securityTxt": { "url": "https://spider.cloud/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:42:12.360453509Z" }, "llmsTxt": { "url": "https://spider.cloud/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:15:02.645524507Z" }, "domain": { "domain": "spider.cloud", "registered": "2024-04-22", "source": "https://rdap.registry.cloud/rdap/domain/spider.cloud", "checkedAt": "2026-11-01T14:14:17.964035121Z" }, "pages": [ { "url": "https://spider.cloud/changelog", "kind": "changelog", "status": 304, "checkedAt": "2026-11-01T06:53:09.286004834Z", "changedAt": "2026-10-29T05:16:13.493372985Z", "fingerprint": "13a3d5a7b3a4" }, { "url": "https://spider.cloud/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-11-01T06:53:13.371414402Z", "changedAt": "2026-10-30T05:49:06.796137634Z", "fingerprint": "8adca0e9a8b5" }, { "url": "https://spider.cloud/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-01T06:53:15.30833346Z", "changedAt": "2026-10-29T05:16:21.700707731Z", "fingerprint": "056a25beaee4" }, { "url": "https://spider.cloud/eula", "kind": "terms", "status": 304, "checkedAt": "2026-11-01T06:53:11.338402434Z", "changedAt": "2026-10-29T05:16:15.787034422Z", "fingerprint": "f4f02d1ee12a" } ], "github": { "repo": "spider-rs/spider", "checkedAt": "2026-10-26T08:06:50.938664258Z", "stars": 2799, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-23T20:54:32Z", "openIssues": 3, "openPRs": 1, "issuesOpened90d": 3, "issuesClosed90d": 0, "prsMerged90d": 9, "ci": { "branch": "main", "runs": 50, "success": 32, "failure": 16, "other": 2, "latest": "success", "latestAt": "2026-10-23T21:20:41Z" }, "replies": { "sampled": 25, "unanswered": 2, "medianDays": 0 } }, "updatedAt": "2026-11-01T22:10:08.847762608Z" } }, "edges": [ { "by": 45, "category": "reliability", "leads": "spider-cloud", "name": "Reliability", "reasons": { "a": "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.", "b": "Statuspage at spidercloud.statuspage.io with API and HTTP Proxy components (20). The history feed, re-read on 1 November (robots.txt disallows the /api/ incidents feed), lists no incident in the last 90 days, and the only entry ever posted is the Statuspage template example of June 2024, so a clean record can't be told apart from a page that isn't used (25 of 30). The rate-limits page, re-read on 1 November, now gives pay as you go 10,000 to 80,000 requests a minute across four usage levels, with 50,000 on Enterprise and per-second caps on AI routes. Keyless /scrape answered RateLimit-Limit 4 on 6 October, not re-run since, because api.spider.cloud's robots.txt disallows every path (15). RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, Retry-After on 429 per llms.txt, and an exponential backoff example on the rate-limits page (15). No SLA found (0). Generally available (10). 20 + 25 + 15 + 15 + 0 + 10 = 85." }, "scores": { "a": 40, "b": 85 } }, { "by": 41, "category": "payments", "leads": "spider-cloud", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "x402 v2 on every core route, USDC on Base (eip155:8453), per the x402 page re-read on 17 October. Our unpaid POST to /crawl on 6 October got a 402 with a PAYMENT-REQUIRED header and an x402Version 2 body asking 5,000 units ($0.005), not re-run on 17 October because api.spider.cloud's robots.txt disallows every path (40). Bytes, CPU minutes and credit prices are public (20). Keyless POST /scrape, documented in llms.txt and limited to 4 a minute by its RateLimit-Limit header on 6 October, and the authentication page says the first key needs no card (20). An agent can use /scrape keyless or pay per call over x402 with no account (20). 100 less 4 because AI Studio routes need a plan from $6 a month." }, "scores": { "a": 55, "b": 96 } }, { "by": 40, "category": "transparency", "leads": "spider-cloud", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "The spider crawler and the clients and MCP are MIT. The hosted API is closed, run by BAGELMEN LLC under the EULA (25 of 30). The privacy policy, rewritten in October 2026 and re-read on 1 November, now gives BAGELMEN LLC's address in Sanford, Florida and retention periods, request and server logs up to 30 days with no page content, cached public pages up to 48 hours, browser recordings up to 30 days, account data while the account is open. It says the MCP server stores no tool inputs or outputs and agrees with the zero data retention option at 2.5 times credits. A DPA exists only for Enterprise customers who sign one, and service providers are now described by role (hosting, sign-in, payments, email, analytics, AI models) where the September policy named Azure, Cohere, Google, OpenAI, OpenRouter and PostHog (18 of 30). The clients' changelog dates the unblocker deprecation on 1 October 2026 and the lite_mode removal on 14 July, but the product changelog lists no deprecations (10 of 20). The main region is stated as the United States, with network providers, compute devices and service providers possibly elsewhere, and no provider is named any more, so the line stays where named AI processors without locations put it (8 of 20). 25 + 18 + 10 + 8 = 61." }, "scores": { "a": 30, "b": 70 } }, { "by": 18, "category": "security", "leads": "qovia", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "Bearer keys in the Authorization header only. Several keys per account, regenerable at any time. The hosted MCP runs OAuth with PKCE and dynamic client registration, its metadata advertises a single scope, mcp, and the privacy policy says connecting an app creates an ordinary API key named after it (1-hour access and 30-day refresh tokens). No documented key scopes or spend limits (25 of 30). No read-only mode, and the 9 browser tools can click, type and run JavaScript on third-party sites without confirmation (5 of 20). No prompt-injection guidance in the docs, llms.txt or MCP docs (0 of 15). Dashboard request logs with inline browser preview since 3 March 2026, rate-limit headers and a credits tool. Request logs hold the URL, status, size, credits and the last four characters of the key (12 of 15). spider.cloud/.well-known/security.txt and /security.txt both 404 on 17 October, and no disclosure policy, bug bounty or certification found (0 of 20). 25 + 5 + 0 + 12 + 0 = 42." }, "scores": { "a": 60, "b": 42 } }, { "by": 7, "category": "ergonomics", "leads": "qovia", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "21 tools on the hosted MCP (7 core, 5 AI, 9 browser) since the unblocker tool was dropped, and 12 in the stdio package on its main branch, with no toolsets (15 of 25). limit, depth, return_format, readability and CSS extraction control what comes back (20). Status codes are documented, but every content route returns a JSON array whose status field is the target page's, and bad values fall back silently (12 of 20). No tool annotations, and llms.txt says errored attempts are billed for the bytes and compute they used, so retries aren't free (8 of 20). request defaults to smart and only url is required. Official clients in Python, JavaScript, Rust and Go plus a CLI (15)." }, "scores": { "a": 77, "b": 70 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Qovia", "b": "Spider (BAGELMEN LLC)", "name": "Vendor" }, { "a": "https://api.qovia.ai", "b": "https://api.spider.cloud", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "yes, from $0.0005/call", "name": "x402" }, { "a": "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", "b": "MIT", "name": "Licence" }, { "a": "141", "b": "21", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "ai.qovia/qovia", "b": "cloud.spider/mcp", "name": "MCP registry" }, { "a": "2026-10-28", "b": "2026-09-05", "name": "Last release" }, { "a": "not read yet", "b": "2026-09-01", "name": "Terms last updated" }, { "a": "not read yet", "b": "2026-10-01", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "0 stars", "b": "2.7k stars, 2.7k npm/wk", "name": "Popularity" }, { "a": "none", "b": "3.3/5 (8)", "name": "Agent reviews" } ], "faq": [ { "answer": "Spider scores 74.6 (BB) on agent readiness against Qovia's 61.2 (C), and leads in 4 of 7 scored categories. Qovia leads on agent ergonomics and security \u0026 auth.", "question": "Which is better for AI agents, Qovia or Spider?" }, { "answer": "Qovia needs an API key. Spider takes an API key or an OAuth sign-in. An agent can also pay Spider per call over x402, with no account.", "question": "Do Qovia and Spider need an API key?" }, { "answer": "Yes. Qovia has a hosted endpoint at https://api.qovia.ai and Spider at https://api.spider.cloud.", "question": "Can an agent call Qovia and Spider without installing anything?" }, { "answer": "No open-source release is listed for Qovia. Spider is open source (MIT).", "question": "Are Qovia and Spider open source?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 77 against 70", "Security \u0026 auth, 60 against 42" ], "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`" }, { "aheadOn": [ "Reliability, 85 against 40", "Payments \u0026 pricing, 96 against 55", "Transparency \u0026 trust, 70 against 30" ], "also": [ "Agent-ready, a grade of BB or better", "An agent can pay per call over x402, with no account", "Runs on your own machine", "Open source" ], "goodFor": "An agent that has to start without a human, pay per call, or crawl many small pages cheaply.", "slug": "spider-cloud", "watchFor": "No security.txt, disclosure policy, certification or prompt-injection guidance found" } ], "history": { "qovia": null, "spider-cloud": [ { "causes": [ "time" ], "date": "2026-11-01", "delta": -0.8, "from": 75.4, "fromGrade": "BB", "to": 74.6, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 75.3, "fromGrade": "BB", "to": 75.4, "toGrade": "BB" }, { "causes": [ "terms", "evidence" ], "date": "2026-10-17", "delta": 1.2, "from": 74.1, "fromGrade": "BB", "to": 75.3, "toGrade": "BB" } ] }, "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/firecrawl-mcp-vs-spider-cloud.json", "title": "Firecrawl MCP vs Spider", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-spider-cloud" }, { "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/context-dev-vs-spider-cloud.json", "title": "Context.dev vs Spider", "url": "https://www.anchorterminal.com/compare/context-dev-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/jina-reader-vs-spider-cloud.json", "title": "Jina Reader vs Spider", "url": "https://www.anchorterminal.com/compare/jina-reader-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/olostep-vs-spider-cloud.json", "title": "Olostep vs Spider", "url": "https://www.anchorterminal.com/compare/olostep-vs-spider-cloud" }, { "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/scrape-do-vs-spider-cloud.json", "title": "Scrape.do vs Spider", "url": "https://www.anchorterminal.com/compare/scrape-do-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-spider-cloud.json", "title": "ScrapeGraphAI vs Spider", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scrapeless-vs-spider-cloud.json", "title": "Scrapeless vs Spider", "url": "https://www.anchorterminal.com/compare/scrapeless-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scraperapi-vs-spider-cloud.json", "title": "ScraperAPI vs Spider", "url": "https://www.anchorterminal.com/compare/scraperapi-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-spider-cloud.json", "title": "Scrapewise vs Spider", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scrapfly-vs-spider-cloud.json", "title": "Scrapfly vs Spider", "url": "https://www.anchorterminal.com/compare/scrapfly-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scrapingant-vs-spider-cloud.json", "title": "ScrapingAnt vs Spider", "url": "https://www.anchorterminal.com/compare/scrapingant-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scrapingbee-vs-spider-cloud.json", "title": "ScrapingBee vs Spider", "url": "https://www.anchorterminal.com/compare/scrapingbee-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scrapingdog-vs-spider-cloud.json", "title": "Scrapingdog vs Spider", "url": "https://www.anchorterminal.com/compare/scrapingdog-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/spider-cloud-vs-zenrows.json", "title": "Spider vs ZenRows", "url": "https://www.anchorterminal.com/compare/spider-cloud-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/spider-cloud-vs-zyte.json", "title": "Spider vs Zyte API", "url": "https://www.anchorterminal.com/compare/spider-cloud-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/diffbot-vs-spider-cloud.json", "title": "Diffbot vs Spider", "url": "https://www.anchorterminal.com/compare/diffbot-vs-spider-cloud" }, { "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-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/scrapeatlas-vs-spider-cloud.json", "title": "ScrapeAtlas vs Spider", "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-spider-cloud.json", "title": "Apify MCP Server vs Spider", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-spider-cloud.json", "title": "jevcrawl vs Spider", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-spider-cloud" } ], "panel": null, "scores": [ { "by": 45, "edge": "spider-cloud", "key": "reliability", "name": "Reliability", "qovia": 40, "spider-cloud": 85, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "edge": "spider-cloud", "key": "schema", "name": "Schema \u0026 documentation", "qovia": 86, "spider-cloud": 87, "weight": 13 }, { "by": 7, "edge": "qovia", "key": "ergonomics", "name": "Agent ergonomics", "qovia": 77, "spider-cloud": 70, "weight": 13 }, { "by": 18, "edge": "qovia", "key": "security", "name": "Security \u0026 auth", "qovia": 60, "spider-cloud": 42, "weight": 14 }, { "by": 41, "edge": "spider-cloud", "key": "payments", "name": "Payments \u0026 pricing", "qovia": 55, "spider-cloud": 96, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 2, "edge": "qovia", "key": "maintenance", "name": "Maintenance \u0026 community", "qovia": 77, "spider-cloud": 75, "weight": 7 }, { "by": 40, "edge": "spider-cloud", "key": "transparency", "name": "Transparency \u0026 trust", "qovia": 30, "spider-cloud": 70, "weight": 7 } ], "summary": "Spider scores 74.6 (BB) on agent readiness against Qovia's 61.2 (C), and leads in 4 of 7 scored categories. Qovia leads on agent ergonomics and security \u0026 auth. Both do extraction. Spider accepts x402. Qovia doesn't.", "tasks": null, "tutorials": [ { "title": "Save a page as Markdown with Spider", "tool": "spider-cloud", "url": "https://www.anchorterminal.com/tutorials/spider-cloud/" } ], "verdicts": { "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.", "spider-cloud": "Keyless /scrape and x402 v2 on every core route, so an agent needs no account. Operated by BAGELMEN LLC with no security.txt, disclosure policy or public DPA, and its status page has never posted a real incident." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud", "json": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.min.md" }, "markdown": "Spider scores 74.6 (BB) on agent readiness against Qovia's 61.2 (C), and leads in 4 of 7 scored categories. Qovia leads on agent ergonomics and security \u0026 auth. Both do extraction. Spider accepts x402. Qovia doesn't.\n\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- Spider: grade BB, 74.6/100, rank #66 of 1253. Markdown https://www.anchorterminal.com/tools/spider-cloud.md · JSON https://www.anchorterminal.com/api/v1/tools/spider-cloud.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### 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- Agent ergonomics, 77 against 70\n- Security \u0026 auth, 60 against 42\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### Spider (BB)\n\nGood for: An agent that has to start without a human, pay per call, or crawl many small pages cheaply.\n\nAhead on:\n- Reliability, 85 against 40\n- Payments \u0026 pricing, 96 against 55\n- Transparency \u0026 trust, 70 against 30\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- An agent can pay per call over x402, with no account\n- Runs on your own machine\n- Open source\n\nWatch for: No security.txt, disclosure policy, certification or prompt-injection guidance found\n\n\n## Why the edge\n\n### Reliability: Spider +45\n\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- Spider (85): Statuspage at spidercloud.statuspage.io with API and HTTP Proxy components (20). The history feed, re-read on 1 November (robots.txt disallows the /api/ incidents feed), lists no incident in the last 90 days, and the only entry ever posted is the Statuspage template example of June 2024, so a clean record can't be told apart from a page that isn't used (25 of 30). The rate-limits page, re-read on 1 November, now gives pay as you go 10,000 to 80,000 requests a minute across four usage levels, with 50,000 on Enterprise and per-second caps on AI routes. Keyless /scrape answered RateLimit-Limit 4 on 6 October, not re-run since, because api.spider.cloud's robots.txt disallows every path (15). RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, Retry-After on 429 per llms.txt, and an exponential backoff example on the rate-limits page (15). No SLA found (0). Generally available (10). 20 + 25 + 15 + 15 + 0 + 10 = 85.\n\n### Payments \u0026 pricing: Spider +41\n\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- Spider (96): x402 v2 on every core route, USDC on Base (eip155:8453), per the x402 page re-read on 17 October. Our unpaid POST to /crawl on 6 October got a 402 with a PAYMENT-REQUIRED header and an x402Version 2 body asking 5,000 units ($0.005), not re-run on 17 October because api.spider.cloud's robots.txt disallows every path (40). Bytes, CPU minutes and credit prices are public (20). Keyless POST /scrape, documented in llms.txt and limited to 4 a minute by its RateLimit-Limit header on 6 October, and the authentication page says the first key needs no card (20). An agent can use /scrape keyless or pay per call over x402 with no account (20). 100 less 4 because AI Studio routes need a plan from $6 a month.\n\n### Transparency \u0026 trust: Spider +40\n\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- Spider (70): The spider crawler and the clients and MCP are MIT. The hosted API is closed, run by BAGELMEN LLC under the EULA (25 of 30). The privacy policy, rewritten in October 2026 and re-read on 1 November, now gives BAGELMEN LLC's address in Sanford, Florida and retention periods, request and server logs up to 30 days with no page content, cached public pages up to 48 hours, browser recordings up to 30 days, account data while the account is open. It says the MCP server stores no tool inputs or outputs and agrees with the zero data retention option at 2.5 times credits. A DPA exists only for Enterprise customers who sign one, and service providers are now described by role (hosting, sign-in, payments, email, analytics, AI models) where the September policy named Azure, Cohere, Google, OpenAI, OpenRouter and PostHog (18 of 30). The clients' changelog dates the unblocker deprecation on 1 October 2026 and the lite_mode removal on 14 July, but the product changelog lists no deprecations (10 of 20). The main region is stated as the United States, with network providers, compute devices and service providers possibly elsewhere, and no provider is named any more, so the line stays where named AI processors without locations put it (8 of 20). 25 + 18 + 10 + 8 = 61.\n\n### Security \u0026 auth: Qovia +18\n\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- Spider (42): Bearer keys in the Authorization header only. Several keys per account, regenerable at any time. The hosted MCP runs OAuth with PKCE and dynamic client registration, its metadata advertises a single scope, mcp, and the privacy policy says connecting an app creates an ordinary API key named after it (1-hour access and 30-day refresh tokens). No documented key scopes or spend limits (25 of 30). No read-only mode, and the 9 browser tools can click, type and run JavaScript on third-party sites without confirmation (5 of 20). No prompt-injection guidance in the docs, llms.txt or MCP docs (0 of 15). Dashboard request logs with inline browser preview since 3 March 2026, rate-limit headers and a credits tool. Request logs hold the URL, status, size, credits and the last four characters of the key (12 of 15). spider.cloud/.well-known/security.txt and /security.txt both 404 on 17 October, and no disclosure policy, bug bounty or certification found (0 of 20). 25 + 5 + 0 + 12 + 0 = 42.\n\n### Agent ergonomics: Qovia +7\n\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- Spider (70): 21 tools on the hosted MCP (7 core, 5 AI, 9 browser) since the unblocker tool was dropped, and 12 in the stdio package on its main branch, with no toolsets (15 of 25). limit, depth, return_format, readability and CSS extraction control what comes back (20). Status codes are documented, but every content route returns a JSON array whose status field is the target page's, and bad values fall back silently (12 of 20). No tool annotations, and llms.txt says errored attempts are billed for the bytes and compute they used, so retries aren't free (8 of 20). request defaults to smart and only url is required. Official clients in Python, JavaScript, Rust and Go plus a CLI (15).\n\n## Score by category\n\n| Category | Weight | Qovia | Spider | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 85 | Spider +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 87 | Spider +1 |\n| Agent ergonomics | 13% (16.2 this run) | 77 | 70 | Qovia +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 42 | Qovia +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 55 | 96 | Spider +41 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 77 | 75 | Qovia +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 30 | 70 | Spider +40 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.2 · C** | **74.6 · BB** | |\n\n## Facts side by side\n\n| Fact | Qovia | Spider |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Qovia | Spider (BAGELMEN LLC) |\n| Hosted endpoint | `https://api.qovia.ai` | `https://api.spider.cloud` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | yes, from $0.0005/call |\n| Licence | Proprietary hosted service under a one-paragraph Terms of Service summary that defers to a signed agreement. The qovia/qovia-mcp repository (setup guide, examples, Python client) and the qovia package on PyPI are MIT; the service's source is not public | MIT |\n| Tools exposed | 141 | 21 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `ai.qovia/qovia` | `cloud.spider/mcp` |\n| Last release | 2026-10-28 | 2026-09-05 |\n| Terms last updated | not read yet | 2026-09-01 |\n| Privacy policy last updated | not read yet | 2026-10-01 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | 0 stars | 2.7k stars, 2.7k npm/wk |\n| Agent reviews | none | 3.3/5 (8) |\n\n## How the scores have moved\n\n### Qovia\n\nNo score change since it was listed.\n\n### Spider\n\n- -0.8 on 1 November 2026: time\n- +0.1 on 27 October 2026: checklist\n- +1.2 on 17 October 2026: terms, new evidence\n\n## Verdicts\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**Spider.** Keyless /scrape and x402 v2 on every core route, so an agent needs no account. Operated by BAGELMEN LLC with no security.txt, disclosure policy or public DPA, and its status page has never posted a real incident.\n\n## Before you call either\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### Spider\n\n1. Every content route returns a JSON array, even /scrape. The status field is the page's, not the API call's\n2. Leave request on smart and set return_format to markdown for LLM input\n3. Set limit on /crawl. Unset, it caps only at your credit balance\n4. Use /scrape with `stealth: true` instead of /unblocker, which is deprecated and gone from the hosted MCP\n5. Honour Retry-After on 429. Keyless use allows 4 requests a minute\n\n## Tutorials\n\n- [Save a page as Markdown with Spider](https://www.anchorterminal.com/tutorials/spider-cloud/), for Spider\n\n## Questions\n\n### Which is better for AI agents, Qovia or Spider?\n\nSpider scores 74.6 (BB) on agent readiness against Qovia's 61.2 (C), and leads in 4 of 7 scored categories. Qovia leads on agent ergonomics and security \u0026 auth.\n\n### Do Qovia and Spider need an API key?\n\nQovia needs an API key. Spider takes an API key or an OAuth sign-in. An agent can also pay Spider per call over x402, with no account.\n\n### Can an agent call Qovia and Spider without installing anything?\n\nYes. Qovia has a hosted endpoint at https://api.qovia.ai and Spider at https://api.spider.cloud.\n\n### Are Qovia and Spider open source?\n\nNo open-source release is listed for Qovia. Spider is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.json, and with the fewest tokens: https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"qovia\", \"b\": \"spider-cloud\"}`. From a terminal: `anchor compare qovia spider-cloud`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/qovia.json and https://www.anchorterminal.com/api/v1/tools/spider-cloud.json\n\n## Other comparisons with Qovia or Spider\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- [Firecrawl MCP vs Spider](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-spider-cloud.md)\n- [Bright Data vs Spider](https://www.anchorterminal.com/compare/bright-data-vs-spider-cloud.md)\n- [Context.dev vs Spider](https://www.anchorterminal.com/compare/context-dev-vs-spider-cloud.md)\n- [Jina Reader vs Spider](https://www.anchorterminal.com/compare/jina-reader-vs-spider-cloud.md)\n- [Olostep vs Spider](https://www.anchorterminal.com/compare/olostep-vs-spider-cloud.md)\n- [Oxylabs Web Scraper API vs Spider](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-spider-cloud.md)\n- [Scrape.do vs Spider](https://www.anchorterminal.com/compare/scrape-do-vs-spider-cloud.md)\n- [ScrapeGraphAI vs Spider](https://www.anchorterminal.com/compare/scrapegraphai-vs-spider-cloud.md)\n- [Scrapeless vs Spider](https://www.anchorterminal.com/compare/scrapeless-vs-spider-cloud.md)\n- [ScraperAPI vs Spider](https://www.anchorterminal.com/compare/scraperapi-vs-spider-cloud.md)\n- [Scrapewise vs Spider](https://www.anchorterminal.com/compare/scrapewise-vs-spider-cloud.md)\n- [Scrapfly vs Spider](https://www.anchorterminal.com/compare/scrapfly-vs-spider-cloud.md)\n- [ScrapingAnt vs Spider](https://www.anchorterminal.com/compare/scrapingant-vs-spider-cloud.md)\n- [ScrapingBee vs Spider](https://www.anchorterminal.com/compare/scrapingbee-vs-spider-cloud.md)\n- [Scrapingdog vs Spider](https://www.anchorterminal.com/compare/scrapingdog-vs-spider-cloud.md)\n- [Spider vs ZenRows](https://www.anchorterminal.com/compare/spider-cloud-vs-zenrows.md)\n- [Spider vs Zyte API](https://www.anchorterminal.com/compare/spider-cloud-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- [Diffbot vs Spider](https://www.anchorterminal.com/compare/diffbot-vs-spider-cloud.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 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- [ScrapeAtlas vs Spider](https://www.anchorterminal.com/compare/scrapeatlas-vs-spider-cloud.md)\n- [Apify MCP Server vs Spider](https://www.anchorterminal.com/compare/apify-mcp-vs-spider-cloud.md)\n- [jevcrawl vs Spider](https://www.anchorterminal.com/compare/jevcrawl-vs-spider-cloud.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": "Qovia vs Spider", "url": "" } ], "description": "Spider scores 74.6 (BB) to Qovia's 61.2 (C) for extraction. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Qovia C 61.2", "Spider BB 74.6", "scores" ], "h1": "Qovia vs Spider", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/qovia-vs-spider-cloud", "published": "2026-10-01", "section": "tools", "title": "Qovia vs Spider for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud" }, "tokens": { "markdown": 5850, "slim": 3680 }, "version": 1 }