{ "data": { "a": { "slug": "crw", "name": "fastCRW", "vendor": "Nanofy OÜ", "vendorUrl": "https://fastcrw.com", "kind": "http-api", "category": "web-scrapers", "summary": "fastCRW is a Firecrawl-compatible scraping engine in Rust from Nanofy OÜ in Estonia. It turns pages into Markdown or JSON and searches, maps and crawls sites, as an AGPL-3.0 self-hosted binary or a hosted API with an MCP server.", "url": "https://www.anchorterminal.com/tools/crw", "markdownUrl": "https://www.anchorterminal.com/tools/crw.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/crw.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/crw.json", "dns": "crw.grade.anchorterminal.com", "repo": "https://github.com/fastcrw/crw", "license": "AGPL-3.0", "transports": [ "stdio", "streamable-http" ], "remoteUrl": "https://fastcrw.com/mcp", "packages": [ { "registry": "npm", "name": "crw-mcp" }, { "registry": "npm", "name": "crw-sdk" }, { "registry": "pypi", "name": "crw" }, { "registry": "cargo", "name": "crw-server" }, { "registry": "oci", "name": "ghcr.io/fastcrw/crw" } ], "auth": "mixed", "authNotes": "Hosted API at api.fastcrw.com takes `Authorization: Bearer crw_live_...` keys from the fastcrw.com dashboard after a browser signup (GitHub or email). The hosted MCP server at fastcrw.com/mcp takes OAuth 2.1 (PKCE S256, dynamic client registration, one scope `mcp:tools`) or the key in the URL path as fastcrw.com/mcp/\u003cAPI_KEY\u003e. No key scopes found. A self-hosted engine needs no key unless `[auth] api_keys` is set.", "pricing": "freemium", "pricingNotes": "500 one-off credits with no card, plus up to 500 more from onboarding tasks. Hobby $13 a month for 5,000 credits, Standard $69 for 100,000, Growth $279 for 500,000, Scale $549 for 1,000,000 (less with yearly billing). One credit a page on any renderer, search 2. Failed pages refunded, top-ups never expire. Self-hosting is free.", "priceSummary": "$13 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page, the credit-costs and agent-onboarding docs, or the OpenAPI spec (checked 2026-11-06). A 402 on the hosted API means an exhausted credit balance (`errorCode: insufficient_credits`) with an upgrade URL header, not a payment requirement.", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": 1200, "npmWeekly": 881, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.fastcrw.com", "llmsTxt": "https://docs.fastcrw.com/llms.txt", "openapi": "https://github.com/fastcrw/crw/blob/main/docs/openapi.json", "registryName": "io.github.fastcrw/crw", "capabilities": [ "web.scrape", "web.crawl", "web.extract", "scraping.js-render", "scraping.proxies", "web.search", "web.fetch" ], "tags": [ "hosted", "local", "open-source", "self-hosted", "freemium", "no-card", "mcp", "remote-mcp", "mcp-registry", "llms-txt", "openapi", "rust", "eu" ], "lastRelease": "2026-11-04", "graded": true, "anchor": { "graded": true, "score": 64.3, "grade": "B", "agentReady": false, "rank": 478, "ranked": true, "rankOf": 1486, "categoryRank": 11, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 91, "maintenance": 93, "payments": 35, "reliability": 50, "schema": 91, "security": 40, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Agents get 11 compact, annotated MCP tools with bounded output, a public OpenAPI spec, refunds on failed pages and a free self-hosted engine. The hosted service has no status history, publishes no SLA terms, names its operator only on the support page, and documents an MCP address with the API key in the URL path.", "bestFor": "Agents that want Firecrawl-style scrape, crawl, map, search and extract at lower per-page cost, or a small self-hosted engine.", "strengths": [ "11 MCP tools, each annotated readOnlyHint, destructiveHint and idempotentHint, with output capped near 15,000 characters and a resume offset", "Public OpenAPI 3.1 spec, llms.txt and an error page that says which codes to retry and which to stop on", "Failed and blocked pages are refunded, every renderer costs 1 credit, and top-up credits never expire", "Released 16 times in the 90 days to 6 November 2026, with five open issues on GitHub", "AGPL-3.0 engine runs self-hosted with no account, and MIT Python and TypeScript SDKs" ], "weaknesses": [ "The status page shows a live check and an uptime objective but no incident history", "The hosted MCP address fastcrw.com/mcp/\u003cAPI_KEY\u003e puts the key in the URL path as a documented option", "Terms and privacy policy name no legal entity, give no retention periods and name no DPA; only the support page names Nanofy OÜ", "No SLA terms beyond an Enterprise mention, no security.txt and no certification found", "No machine payment protocol, and hosted keys need a person to sign up in a browser" ], "agentNotes": [ "Connect to https://fastcrw.com/mcp with OAuth rather than the /mcp/\u003cAPI_KEY\u003e address, so the key stays out of URLs and logs", "Branch on `errorCode`. Stop on 402 insufficient_credits or llm_not_available, and on 429 wait for Retry-After before retrying", "Check `success` as well as the HTTP status, since an anti-bot wall answers 200 with `success: false` and `errorCode: anti_bot`", "Pass `startIndex` from a truncated result to read the rest of a long page instead of setting `maxLength: 0`", "Use native /v1 routes for new work; /firecrawl/v2 is for Firecrawl SDK migrations and keeps the older 429 for empty balances" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.3 } ], "editorialScores": { "ergonomics": 91, "maintenance": 93, "payments": 35, "reliability": 50, "schema": 91, "security": 40, "transparency": 53 }, "provenanceScore": 67, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx -y crw-mcp@latest install", "http": "curl -X POST https://api.fastcrw.com/v1/scrape -H \"Authorization: Bearer YOUR_API_KEY\" -H \"Content-Type: application/json\" -d '{\"url\":\"https://example.com\",\"formats\":[\"markdown\"]}'" }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/crw" }, "area": "web-data", "unitPrices": [ { "item": "Hobby plan", "unit": "month", "usd": 13, "note": "5,000 credits; $11 a month billed yearly" }, { "item": "Standard plan", "unit": "month", "usd": 69, "note": "100,000 credits; $59 a month billed yearly" }, { "item": "Hobby top-up", "unit": "1k-pages", "usd": 9, "note": "one credit scrapes one page on any renderer" }, { "item": "Scale top-up", "unit": "1k-pages", "usd": 0.6, "note": "$299 for 500,000 credits" } ], "provenance": { "legalEntity": "Nanofy OÜ", "domain": "fastcrw.com", "domainRegistered": "2026-03-05", "endpointOnVendorDomain": true, "terms": "https://fastcrw.com/terms", "privacy": "https://fastcrw.com/privacy", "statusPage": "https://fastcrw.com/status", "changelog": "https://github.com/fastcrw/crw/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "Nanofy OÜ (registry code 17365846, Sepapaja tn 6, Tallinn) is named as operator on fastcrw.com/support. The terms (last updated 4 April 2026) and the privacy policy (undated) name only fastCRW and 'the jurisdiction in which fastCRW operates'.", "The terms forbid crawling sites against their terms or robots.txt and put responsibility for targets on the customer. No clause forbids automated access to fastcrw.com itself.", "fastcrw.com/robots.txt allows all crawlers except account, API and login paths; docs.fastcrw.com/robots.txt allows all.", "RDAP gives fastcrw.com a registration date of 5 March 2026.", "fastcrw.com/.well-known/security.txt answers 404. SECURITY.md in the repository names security@fastcrw.com and GitHub private vulnerability reporting." ], "score": 67 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/crw.json", "live": { "slug": "crw", "probe": { "target": "https://fastcrw.com/mcp", "method": "get", "lastAt": "2026-11-07T18:20:19.526009674Z", "lastOk": true, "lastStatus": 401, "lastMs": 156, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 80, "p95ms24h": 153, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://fastcrw.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:35.720864858Z" }, "versions": [ { "registry": "github", "name": "fastcrw/crw", "version": "v0.42.1", "released": "2026-11-06", "seenAt": "2026-11-06T23:18:48.669809831Z" }, { "registry": "mcp-registry", "name": "io.github.fastcrw/crw", "version": "0.42.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "crw-mcp", "version": "0.42.1", "seenAt": "2026-11-06T23:18:46.329470936Z" }, { "registry": "npm", "name": "crw-sdk", "version": "0.42.1", "seenAt": "2026-11-06T23:18:46.739900633Z" }, { "registry": "pypi", "name": "crw", "version": "0.42.1", "released": "2026-11-06", "seenAt": "2026-11-06T23:18:48.550796676Z" } ], "githubStars": 1230, "npmWeekly": 881, "pypiWeekly": 441, "securityTxt": { "url": "https://fastcrw.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:50.596126033Z" }, "llmsTxt": { "url": "https://docs.fastcrw.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:13.945191217Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/fastcrw/crw/main/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:20:49.992321515Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "572aa4127341" }, { "url": "https://fastcrw.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:09:41.233044196Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "56adab90a2ac" }, { "url": "https://fastcrw.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:09:43.278176432Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4f55b83dc108" } ], "updatedAt": "2026-11-07T18:20:19.526009674Z" } }, "answer": "fastCRW scores 64.3 (B) on agent readiness against Qovia's 61.2 (C), and leads in 5 of 7 scored categories. Qovia leads on security \u0026 auth and payments \u0026 pricing.", "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": 621, "ranked": true, "rankOf": 1486, "categoryRank": 18, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 77, "payments": 55, "reliability": 40, "schema": 86, "security": 60, "transparency": 30 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "An OpenAPI 3.1 file with 144 operations, one envelope and 20 error codes, per-endpoint prices with failed and empty calls refunded, scoped keys and a four-tool MCP server that keeps the catalogue out of context. No status page, no legal entity, one-paragraph terms and privacy pages, and a product ten days old at the check.", "bestFor": "Agents that need structured public data from Chinese platforms (Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Zhihu, WeChat official accounts, Taobao and JD reviews) or the Xingtu and Pugongying creator marketplaces, with TikTok, YouTube, Instagram, X and Reddit beside them, paid per successful call from a prepaid balance.", "strengths": [ "A public OpenAPI 3.1 file with 144 operations, patterns or enums on parameters, a response example on every operation and the error responses declared on each", "One envelope on every call, `request_id`, `data` and `meta` with the charge and balance, and 20 error codes sorted into not charged and refunded, with `Retry-After` on the retryable ones", "Only HTTP 200 with a non-empty result is charged; empty results, 404s, timeouts and upstream failures are refunded, and 50 trial calls come with a new account", "API keys carry per-platform scopes and an optional expiry, are read from headers only, and the docs tell users to give AI tools a separate scoped key", "The MCP server loads four tools by default and lets an agent find, read and call any of 137 endpoints, with `?tools=` subsets for direct tools; listed in the official registry under ai.qovia/qovia", "Published limits of 60 and 600 requests a minute with `X-RateLimit-*` headers, and a documented empty-call throttle" ], "weaknesses": [ "No status page, incident history or SLA; the terms promise nothing about uptime and the Python client is the only retry guidance beyond `Retry-After`", "The terms and privacy policy are one paragraph each, name no legal entity, address, retention period or subprocessor, and say a signed agreement governs", "Every endpoint is marked `beta` in the OpenAPI file while the docs call it Live, and the API version is 0.1.0", "No security.txt, disclosure policy beyond a SECURITY.md, bug bounty or certification; the only support channels are Telegram, WhatsApp, WeChat and one mailbox", "Every response is third-party platform content and the docs carry no guidance on treating it as untrusted; four endpoint groups read login-gated creator marketplaces", "The changelog has two dated days, the domain is four months old, and the GitHub account was created the week of the request with nine forked lists beside the one repository" ], "agentNotes": [ "Send `Authorization: Bearer sk-qovia-...` to https://api.qovia.ai and check `meta.empty` on every HTTP 200; `data` may be `null` or an empty structure and nothing is charged for it.", "Branch on `error.code`, never on `message`. Retry only `rate_limited`, `too_many_unbilled`, `endpoint_busy`, `upstream_busy` and `too_many_auth_failures` after `Retry-After`; `endpoint_unavailable` has none and will not clear.", "Stay under 60 requests a minute (600 after the first top-up) across every key on the account, and keep empty or not-found calls under 80 per cent of the last 10 minutes or expect 429 `too_many_unbilled`.", "Pass the previous page's `cursor` (and `search_id` on Douyin and Zhihu search) back unchanged and stop when `has_more` is false; each page is a separate charge, and unknown parameters answer 400.", "For MCP, connect to https://api.qovia.ai/mcp over Streamable HTTP; call `search_endpoints` then `get_endpoint` before `call_endpoint`, or add `?tools=douyin,kuaishou` for typed direct tools. Catalogue tools need no key." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.2 } ], "editorialScores": { "ergonomics": 77, "maintenance": 77, "payments": 55, "reliability": 40, "schema": 86, "security": 60, "transparency": 23 }, "provenanceScore": 36, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install qovia", "http": "curl \"https://api.qovia.ai/v1/raw/weibo/hot_search\" -H \"Authorization: Bearer $QOVIA_API_KEY\"", "claudeCode": "claude mcp add --transport http qovia https://api.qovia.ai/mcp --header \"Authorization: Bearer $QOVIA_API_KEY\"" }, "letme": { "capability": "https://letme.dev/web.extract", "tool": "https://letme.dev/qovia" }, "area": "web-data", "unitPrices": [ { "item": "Cross-platform search", "unit": "1k-requests", "usd": 5, "note": "POST /v1/search, successful non-empty calls only, pricing page and OpenAPI file checked 1 November 2026" }, { "item": "Lowest raw endpoints (Douyin, Bilibili, Xingtu keywords)", "unit": "1k-requests", "usd": 0.5, "note": "15 fixed-price endpoints at $0.0005 a successful call" }, { "item": "Most raw endpoints (TikTok, YouTube, X, Reddit, Weibo, Zhihu, Kuaishou and others)", "unit": "1k-requests", "usd": 1, "note": "61 fixed-price endpoints at $0.001 a successful call" }, { "item": "Tiered raw endpoints (Tieba, Fliggy, coming-soon platforms)", "unit": "1k-requests", "usd": 1.5, "note": "$1 per 1,000 after 5,000,000 billed calls in a calendar month" }, { "item": "Xiaohongshu and WeChat endpoints", "unit": "1k-requests", "usd": 5, "note": "11 fixed-price endpoints at $0.005 a successful call" }, { "item": "Xingtu and Pugongying creator marketplace endpoints", "unit": "1k-requests", "usd": 10, "note": "21 fixed-price endpoints at $0.01 a successful call" }, { "item": "JD.com product reviews", "unit": "1k-requests", "usd": 19.5, "note": "the dearest endpoint; Taobao and Tmall reviews are $13.5" }, { "item": "Apify Store, Xingtu Actor premium section", "unit": "record", "usd": 0.06, "note": "per creator per section, paid through Apify with no Qovia account; basic sections $0.01, video sections $0.03" } ], "provenance": { "legalEntity": "", "domain": "qovia.ai", "domainRegistered": "2026-07-04", "endpointOnVendorDomain": true, "terms": "https://qovia.ai/terms/", "privacy": "https://qovia.ai/privacy/", "statusPage": "", "changelog": "https://qovia.ai/changelog/", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "No legal entity is named anywhere read. The terms and privacy pages are one paragraph each, say Delaware law governs and that the signed agreement governs where it differs, and name no company, address or jurisdiction beyond the state. The footer reads © 2026 QoviaAI, a brand name, not an entity, so legalEntity is left empty.", "RDAP for qovia.ai gives a registration date of 2026-07-04 through GoDaddy with a Domains By Proxy registrant and Cloudflare nameservers. The Wayback Machine's only capture before the check is the home page of 11 September 2026, which advertised sign-up with a free 1,000 calls a month, 25+ platforms, a 99.95 per cent enterprise SLA and a team@ mailbox; none of those claims is on the current site.", "firstReleased is the changelog's first dated entry, 21 October 2026, when the search, Xiaohongshu, WeChat, Taobao and JD endpoints are recorded as live; the remaining platforms are dated 22 October, the registry entry is 22 October and the GitHub account and repository were created on 23 October 2026. The 11 September page sold an API key but dates nothing live.", "https://qovia.ai/.well-known/security.txt, https://qovia.ai/security.txt and https://api.qovia.ai/.well-known/security.txt answer 404. The repository's SECURITY.md gives a Telegram handle and a mailbox for reports and says it covers qovia.ai and api.qovia.ai.", "api.qovia.ai has no robots.txt (404); only its OAuth metadata (404) and /mcp (405 on GET) were touched, both by the 1 November listing check. qovia.ai's robots.txt disallows /console/, /account/, /order/ and /admin/ and their /zh/ twins, which were not fetched." ], "score": 36 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/qovia.json", "live": { "slug": "qovia", "probe": { "target": "https://api.qovia.ai", "method": "get", "lastAt": "2026-11-07T18:20:49.254264522Z", "lastOk": true, "lastStatus": 200, "lastMs": 556, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 487, "p95ms24h": 589, "samples24h": 239, "samples30d": 1401, "days": [ { "date": "2026-11-01", "probes": 44, "ok": 44 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "versions": [ { "registry": "mcp-registry", "name": "ai.qovia/qovia", "version": "0.1.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "pypi", "name": "qovia", "version": "0.1.1", "released": "2026-10-27", "seenAt": "2026-11-06T23:59:37.730213111Z" } ], "pypiWeekly": 23, "securityTxt": { "url": "https://qovia.ai/.well-known/security.txt", "state": "valid", "expires": "2027-11-06T00:00:00.000Z", "checkedAt": "2026-11-07T15:59:29.845298165Z" }, "llmsTxt": { "url": "https://qovia.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:42.782081127Z" }, "pages": [ { "url": "https://qovia.ai/changelog/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:17:43.796156022Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f876293b4cbf" }, { "url": "https://qovia.ai/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:17:46.065253467Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6713947e7188" }, { "url": "https://qovia.ai/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:17:47.901511472Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "88cfcd770908" } ], "mcpTools": { "url": "https://api.qovia.ai/mcp", "checkedAt": "2026-11-07T01:47:04.314060831Z", "status": "ok", "protocol": "2025-11-25", "tools": [ { "name": "search_endpoints", "title": "Search Qovia Endpoints", "description": "Search Qovia's data endpoints by keyword (Chinese or English) and/or platform slug (douyin, tiktok, xiaohongshu, pgy, bilibili, tieba, wechat, taobao, jd, fliggy, xingtu, huahuo, cljx, ...). Returns ids, titles, price per call and whether each endpoint is live. Free; no sign-in required.", "inputSchema": { "additionalProperties": false, "properties": { "include_unavailable": { "default": false, "description": "Also list endpoints that are not live yet", "type": "boolean" }, "platform": { "description": "Platform slug", "maxLength": 50, "type": "string" }, "query": { "description": "Words in the id, path or title", "maxLength": 100, "type": "string" } }, "type": "object" }, "annotations": { "destructiveHint": false, "readOnlyHint": true, "title": "Search Qovia Endpoints" } }, { "name": "get_endpoint", "title": "Get Endpoint Details", "description": "Show one endpoint: what it returns, its parameters (JSON Schema), example parameters, a response example and the price. Free; no sign-in required.", "inputSchema": { "additionalProperties": false, "properties": { "endpoint_id": { "description": "e.g. raw.douyin.video", "type": "string" } }, "required": [ "endpoint_id" ], "type": "object" }, "annotations": { "destructiveHint": false, "readOnlyHint": true, "title": "Get Endpoint Details" } }, { "name": "call_endpoint", "title": "Call Qovia Endpoint", "description": "Run an endpoint and return its data plus billing info (charged_usd and remaining credit). Requires a Qovia account connected to this MCP server; billed only when data is returned, so empty results and failures are free.", "inputSchema": { "additionalProperties": false, "properties": { "endpoint_id": { "description": "e.g. raw.douyin.video", "type": "string" }, "params": { "description": "The endpoint's parameters (see get_endpoint)", "type": "object" } }, "required": [ "endpoint_id" ], "type": "object" }, "annotations": { "destructiveHint": false, "openWorldHint": true, "readOnlyHint": true, "title": "Call Qovia Endpoint" } }, { "name": "get_account", "title": "Get Qovia Account", "description": "Show the connected Qovia account's credit, plan and rate limit. Free; counts toward the rate limit.", "inputSchema": { "additionalProperties": false, "properties": {}, "type": "object" }, "annotations": { "destructiveHint": false, "readOnlyHint": true, "title": "Get Qovia Account" } } ], "schemaTokens": 653, "changedAt": "2026-11-07T01:47:04.314060831Z", "check": { "checker": "anchor-check/1.0", "totalTokens": 653, "counts": { "error": 0, "note": 1, "warn": 1 }, "findings": [ { "rule": "TC13", "severity": "warn", "tool": "call_endpoint", "message": "params (object with no properties)", "fix": "Declare the properties (or additionalProperties with a schema) and the array's items." }, { "rule": "TC24", "severity": "note", "message": "4 of 4 tools have no outputSchema", "fix": "Declare outputSchema for tools that return structured data, and return structuredContent that matches it." } ] } }, "github": { "repo": "qovia/qovia-mcp", "checkedAt": "2026-11-02T08:22:59.675177389Z", "stars": 0, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-01T09:41:18Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0 }, "updatedAt": "2026-11-07T18:20:49.254264522Z" } }, "edges": [ { "by": 30, "category": "transparency", "leads": "crw", "name": "Transparency \u0026 trust", "reasons": { "a": "The engine and MCP server are AGPL-3.0 and the SDKs MIT, while the hosted control plane is closed under terms that name no legal entity (25 of 30). The terms say crawled data is handled transiently with zero data retention for approved accounts, but the privacy policy is undated, names no controller, gives no retention periods and mentions no DPA (10 of 30). The CHANGELOG flags breaking changes, deprecated v2 extract routes return a warning on every response, and the October 2026 402 change is dated in the docs, with no standing notice policy (10 of 20). Local data-source telemetry is disclosed with an opt-out. The privacy policy names Stripe, Google Analytics, Google Ads and an X pixel, but infrastructure and search providers are unnamed and no data location is given (8 of 20). 25 + 10 + 10 + 8 = 53.", "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": 60, "b": 30 } }, { "by": 20, "category": "security", "leads": "qovia", "name": "Security \u0026 auth", "reasons": { "a": "The hosted MCP server publishes RFC 9728 metadata naming its own authorisation server, with PKCE S256, dynamic client registration and one scope, `mcp:tools`, and the API takes revocable Bearer keys from the dashboard. No key scopes or second scope found (22). The authentication page documents fastcrw.com/mcp/\u003cAPI_KEY\u003e as a way in, a key in the URL path, so less 10 (12 of 30). Tools mostly read, and data-source calls check approvals, but there is no read-only key or confirmation step for monitors (8 of 20). Managed LLM extraction, summaries and answers wrap scraped text in a nonce fence (crates/crw-extract/src/untrusted.rs), and the hardening guide treats pages as untrusted, but the MCP docs give agents no guidance on scraped content (7 of 15). Each response reports `creditsUsed`; no per-call log in the docs (5 of 15). SECURITY.md names security@fastcrw.com and GitHub private reporting with a 48-hour acknowledgement, and CI runs CodeQL and OpenSSF Scorecard. security.txt answers 404, and no bounty or certification found (8 of 20). 12 + 8 + 7 + 5 + 8 = 40.", "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": 40, "b": 60 } }, { "by": 20, "category": "payments", "leads": "qovia", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Plans are public with credit costs per operation and top-up prices per block of credits, $9 per 1,000 on Hobby down to $299 per 500,000 on Scale, but top-ups need a plan, so between plan-only and per-unit (15 of 20). 500 one-off credits with no card, plus up to 500 from onboarding tasks (20). Hosted keys need a person to sign up in a browser; the free self-hosted engine runs with no account but isn't the graded surface (0). 0 + 15 + 20 + 0 = 35.", "b": "No x402, MPP or L402 on Qovia's own endpoints; USDT on TRC-20 is a top-up method from a console session, not a machine payment protocol. The vendor's five Actors on the Apify Store under the profile qovia (Qovia Data, the same Telegram handle and mailbox as the site), such as the Xingtu Actor at $0.01 to $0.06 a section, can be paid through Apify, whose prepaid token is sold over x402, so partial credit for a third-party route on part of the catalogue (10 of 40). Per-call prices are published without a login, per endpoint in the OpenAPI file, llms.txt and the docs, search at $5 and raw endpoints from $0.5 to $19.5 per 1,000, with the tier rule and payment fees stated (20). 50 trial calls for a new account, counted only when a call returns data; the quickstart says to top up when they run out and the docs ask for no card at sign-up, though no account was created to confirm it (20). A person signs up in a browser and creates a key; the MCP catalogue tools work without a key but data calls do not, and the Apify route reaches four platforms without a Qovia account (5 of 20). 10+20+20+5 = 55." }, "scores": { "a": 35, "b": 55 } }, { "by": 16, "category": "maintenance", "leads": "crw", "name": "Maintenance \u0026 community", "reasons": { "a": "v0.41.0 on 4 November 2026, matching the registry and npm (30). 16 dated releases in the 90 days from 8 August, from 0.37.0 to 0.41.0 (20). Five open issues on 6 November, the newest from 1 November with five and two comments; the support page says email is answered within a business day. Reply authors weren't read (18 of 25). In the official MCP registry as io.github.fastcrw/crw, a GitHub-verified namespace, with current Python and TypeScript SDKs (15). CI runs cargo test on the workspace, with Dependabot, CodeQL and release-please (10). 30 + 20 + 18 + 15 + 10 = 93.", "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": 93, "b": 77 } }, { "by": 14, "category": "ergonomics", "leads": "crw", "name": "Agent ergonomics", "reasons": { "a": "11 compact MCP tools, two of them the data-source tools added in 0.41.0. Content is capped near 15,000 characters with `truncated: true` and a resume offset, and map returns at most 100 URLs by default (20 of 25). Formats, main-content filtering, include and exclude selectors, maxLength, startIndex, limit and crawl depth and page caps (20). Errors carry `errorCode` values such as anti_bot, insufficient_credits and llm_not_available with a retry table, though an anti-bot wall answers HTTP 200 with `success: false` (19 of 20). Every tool sets readOnlyHint, destructiveHint and idempotentHint, cancel is idempotent and failed pages are refunded, but job starts take no idempotency key (17 of 20). Only `url` is required, with official Python and TypeScript SDKs (15). 20 + 20 + 19 + 17 + 15 = 91.", "b": "API reading. Responses come in fixed page sizes per endpoint, from about 5 comments on Xiaohongshu to 100 Fliggy reviews, with limit only on Bilibili danmaku and no field selection; the record shape is compact and shared across posts, notes and videos. The MCP server loads four tools by default, keeps the catalogue out of context until search_endpoints and get_endpoint are called, and ?tools= selects platforms or everything, which on the MCP reading would score 25 (18 of 25). Cursor pagination with has_more on most lists, search_id on Douyin and Zhihu search, page numbers on Weibo, Xiaohongshu and Bilibili, sort options on several, and the cross-platform search filters by platform, content type, sentiment and whole-day date windows up to 90 days (17 of 20). One error object with 20 codes, request_id on every answer, the retryable set marked, refunded codes separated from never-charged ones, and MCP tool errors carrying error.code, the HTTP status and retry_after_seconds (19 of 20). All calls are reads, failed and empty calls are refunded, Retry-After is declared and the Python client retries; no readOnlyHint or other annotation appears in the vendor's 28 October tools/list snapshot (14 of 20). One required parameter on 117 of 144 operations and defaults set on the server, but the only official SDK is the Python client; Node and curl are examples (9 of 15). 18+17+19+14+9 = 77." }, "scores": { "a": 91, "b": 77 } }, { "by": 10, "category": "reliability", "leads": "crw", "name": "Reliability", "reasons": { "a": "Graded on the hosted lines, for the hosted API and MCP server an agent would call; the self-hosted engine would read higher on the local lines. fastcrw.com/status is a first-party page with a live health check and a 99.9% monthly uptime objective, but no components with history (10 of 20). It lists no incidents and keeps no history we could read (5). Concurrency per plan is published, 3 on Free to 150 on Scale, while the request-rate guard above it is deliberately unpublished (12 of 15). The rate-limits page documents Retry-After and X-RateLimit headers, gives exponential backoff code, and separates 429 (retry) from 402 (stop). No idempotency keys for crawl, extract or monitor starts (13 of 15). Pricing mentions an SLA only as 'Premier + SLA' on Enterprise, with no terms, and the terms promise no uptime (0). The hosted service is sold on paid plans with no beta label, though the engine is at 0.41.0 (10). 10 + 5 + 12 + 13 + 0 + 10 = 50.", "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": 50, "b": 40 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Nanofy OÜ", "b": "Qovia", "name": "Vendor" }, { "a": "https://fastcrw.com/mcp", "b": "https://api.qovia.ai", "name": "Hosted endpoint" }, { "a": "stdio, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "AGPL-3.0", "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": "11", "b": "141", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.fastcrw/crw", "b": "ai.qovia/qovia", "name": "MCP registry" }, { "a": "2026-11-04", "b": "2026-10-28", "name": "Last release" }, { "a": "2026-04-04", "b": "not read yet", "name": "Terms last updated" }, { "a": "no date given", "b": "not read yet", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not read yet", "name": "Customer content may train models" }, { "a": "yes", "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": "not found in the text", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "1.2k stars, 881 npm/wk", "b": "0 stars", "name": "Popularity" } ], "faq": [ { "answer": "fastCRW scores 64.3 (B) on agent readiness against Qovia's 61.2 (C), and leads in 5 of 7 scored categories. Qovia leads on security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, fastCRW or Qovia?" }, { "answer": "fastCRW takes an API key or an OAuth sign-in. Qovia needs an API key.", "question": "Do fastCRW and Qovia need an API key?" }, { "answer": "Yes. fastCRW has a hosted endpoint at https://fastcrw.com/mcp and Qovia at https://api.qovia.ai.", "question": "Can an agent call fastCRW and Qovia without installing anything?" }, { "answer": "fastCRW is open source (AGPL-3.0). No open-source release is listed for Qovia.", "question": "Are fastCRW and Qovia open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 50 against 40", "Schema \u0026 documentation, 91 against 86", "Agent ergonomics, 91 against 77", "Maintenance \u0026 community, 93 against 77", "Transparency \u0026 trust, 60 against 30" ], "also": [ "Runs on your own machine", "Free to start without a card", "Open source" ], "goodFor": "Agents that want Firecrawl-style scrape, crawl, map, search and extract at lower per-page cost, or a small self-hosted engine.", "slug": "crw", "watchFor": "The status page shows a live check and an uptime objective but no incident history" }, { "aheadOn": [ "Security \u0026 auth, 60 against 40", "Payments \u0026 pricing, 55 against 35" ], "also": null, "goodFor": "Agents that need structured public data from Chinese platforms (Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Zhihu, WeChat official accounts, Taobao and JD reviews) or the Xingtu and Pugongying creator marketplaces, with TikTok, YouTube, Instagram, X and Reddit beside them, paid per successful call from a prepaid balance.", "slug": "qovia", "watchFor": "No status page, incident history or SLA; the terms promise nothing about uptime and the Python client is the only retry guidance beyond `Retry-After`" } ], "history": null, "job": { "capability": "web.extract", "name": "Extraction" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bright-data-vs-crw.json", "title": "Bright Data vs fastCRW", "url": "https://www.anchorterminal.com/compare/bright-data-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/browseract-vs-crw.json", "title": "BrowserAct vs fastCRW", "url": "https://www.anchorterminal.com/compare/browseract-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-crw.json", "title": "Context.dev vs fastCRW", "url": "https://www.anchorterminal.com/compare/context-dev-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/crawl4ai-vs-crw.json", "title": "Crawl4AI vs fastCRW", "url": "https://www.anchorterminal.com/compare/crawl4ai-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-decodo.json", "title": "fastCRW vs Decodo Web Data API", "url": "https://www.anchorterminal.com/compare/crw-vs-decodo" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-diffbot.json", "title": "fastCRW vs Diffbot", "url": "https://www.anchorterminal.com/compare/crw-vs-diffbot" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-jevcrawl.json", "title": "fastCRW vs jevcrawl", "url": "https://www.anchorterminal.com/compare/crw-vs-jevcrawl" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-jina-reader.json", "title": "fastCRW vs Jina Reader", "url": "https://www.anchorterminal.com/compare/crw-vs-jina-reader" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-microlink.json", "title": "fastCRW vs Microlink", "url": "https://www.anchorterminal.com/compare/crw-vs-microlink" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-olostep.json", "title": "fastCRW vs Olostep", "url": "https://www.anchorterminal.com/compare/crw-vs-olostep" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-outcrawl.json", "title": "fastCRW vs Outcrawl", "url": "https://www.anchorterminal.com/compare/crw-vs-outcrawl" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-oxylabs-web-scraper.json", "title": "fastCRW vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/crw-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrape-do.json", "title": "fastCRW vs Scrape.do", "url": "https://www.anchorterminal.com/compare/crw-vs-scrape-do" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapegraphai.json", "title": "fastCRW vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapeless.json", "title": "fastCRW vs Scrapeless", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapeless" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapeops.json", "title": "fastCRW vs ScrapeOps Proxy API Aggregator", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapeops" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scraperapi.json", "title": "fastCRW vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/crw-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapewise.json", "title": "fastCRW vs Scrapewise", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapfly.json", "title": "fastCRW vs Scrapfly", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapingant.json", "title": "fastCRW vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapingbee.json", "title": "fastCRW vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapingdog.json", "title": "fastCRW vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-spider-cloud.json", "title": "fastCRW vs Spider", "url": "https://www.anchorterminal.com/compare/crw-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-webscraping-ai.json", "title": "fastCRW vs WebScraping.AI", "url": "https://www.anchorterminal.com/compare/crw-vs-webscraping-ai" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-zenrows.json", "title": "fastCRW vs ZenRows", "url": "https://www.anchorterminal.com/compare/crw-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-zyte.json", "title": "fastCRW vs Zyte API", "url": "https://www.anchorterminal.com/compare/crw-vs-zyte" }, { "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/crw-vs-firecrawl-mcp.json", "title": "fastCRW vs Firecrawl MCP", "url": "https://www.anchorterminal.com/compare/crw-vs-firecrawl-mcp" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia.json", "title": "Firecrawl MCP vs Qovia", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/browseract-vs-qovia.json", "title": "BrowserAct vs Qovia", "url": "https://www.anchorterminal.com/compare/browseract-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-qovia.json", "title": "Context.dev vs Qovia", "url": "https://www.anchorterminal.com/compare/context-dev-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/crawl4ai-vs-qovia.json", "title": "Crawl4AI vs Qovia", "url": "https://www.anchorterminal.com/compare/crawl4ai-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapeatlas.json", "title": "fastCRW vs ScrapeAtlas", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapeatlas" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-soldfetch.json", "title": "fastCRW vs SoldFetch", "url": "https://www.anchorterminal.com/compare/crw-vs-soldfetch" }, { "json": "https://www.anchorterminal.com/compare/decodo-vs-qovia.json", "title": "Decodo Web Data API vs Qovia", "url": "https://www.anchorterminal.com/compare/decodo-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/diffbot-vs-qovia.json", "title": "Diffbot vs Qovia", "url": "https://www.anchorterminal.com/compare/diffbot-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.json", "title": "jevcrawl vs Qovia", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/microlink-vs-qovia.json", "title": "Microlink vs Qovia", "url": "https://www.anchorterminal.com/compare/microlink-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/outcrawl-vs-qovia.json", "title": "Outcrawl vs Qovia", "url": "https://www.anchorterminal.com/compare/outcrawl-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.json", "title": "Oxylabs Web Scraper API vs Qovia", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.json", "title": "Qovia vs ScrapeAtlas", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.json", "title": "Qovia vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapeops.json", "title": "Qovia vs ScrapeOps Proxy API Aggregator", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapeops" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi.json", "title": "Qovia vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise.json", "title": "Qovia vs Scrapewise", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapfly.json", "title": "Qovia vs Scrapfly", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant.json", "title": "Qovia vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.json", "title": "Qovia vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.json", "title": "Qovia vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-soldfetch.json", "title": "Qovia vs SoldFetch", "url": "https://www.anchorterminal.com/compare/qovia-vs-soldfetch" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.json", "title": "Qovia vs Spider", "url": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-webscraping-ai.json", "title": "Qovia vs WebScraping.AI", "url": "https://www.anchorterminal.com/compare/qovia-vs-webscraping-ai" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-zenrows.json", "title": "Qovia vs ZenRows", "url": "https://www.anchorterminal.com/compare/qovia-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-zyte.json", "title": "Qovia vs Zyte API", "url": "https://www.anchorterminal.com/compare/qovia-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-crw.json", "title": "Apify MCP Server vs fastCRW", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-crw" } ], "panel": null, "scores": [ { "by": 10, "crw": 50, "edge": "crw", "key": "reliability", "name": "Reliability", "qovia": 40, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "crw": 91, "edge": "crw", "key": "schema", "name": "Schema \u0026 documentation", "qovia": 86, "weight": 13 }, { "by": 14, "crw": 91, "edge": "crw", "key": "ergonomics", "name": "Agent ergonomics", "qovia": 77, "weight": 13 }, { "by": 20, "crw": 40, "edge": "qovia", "key": "security", "name": "Security \u0026 auth", "qovia": 60, "weight": 14 }, { "by": 20, "crw": 35, "edge": "qovia", "key": "payments", "name": "Payments \u0026 pricing", "qovia": 55, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 16, "crw": 93, "edge": "crw", "key": "maintenance", "name": "Maintenance \u0026 community", "qovia": 77, "weight": 7 }, { "by": 30, "crw": 60, "edge": "crw", "key": "transparency", "name": "Transparency \u0026 trust", "qovia": 30, "weight": 7 } ], "summary": "fastCRW scores 64.3 (B) on agent readiness against Qovia's 61.2 (C), and leads in 5 of 7 scored categories. Qovia leads on security \u0026 auth and payments \u0026 pricing. Both do extraction.", "tasks": null, "tutorials": [], "verdicts": { "crw": "Agents get 11 compact, annotated MCP tools with bounded output, a public OpenAPI spec, refunds on failed pages and a free self-hosted engine. The hosted service has no status history, publishes no SLA terms, names its operator only on the support page, and documents an MCP address with the API key in the URL path.", "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/crw-vs-qovia", "json": "https://www.anchorterminal.com/compare/crw-vs-qovia.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/crw-vs-qovia.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/crw-vs-qovia.min.md" }, "markdown": "fastCRW scores 64.3 (B) on agent readiness against Qovia's 61.2 (C), and leads in 5 of 7 scored categories. Qovia leads on security \u0026 auth and payments \u0026 pricing. Both do extraction.\n\n- fastCRW: grade B, 64.3/100, rank #478 of 1486. Markdown https://www.anchorterminal.com/tools/crw.md · JSON https://www.anchorterminal.com/api/v1/tools/crw.json\n- Qovia: grade C, 61.2/100, rank #621 of 1486. 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 501 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md\n\n## Which one, for what\n\n### fastCRW (B)\n\nGood for: Agents that want Firecrawl-style scrape, crawl, map, search and extract at lower per-page cost, or a small self-hosted engine.\n\nAhead on:\n- Reliability, 50 against 40\n- Schema \u0026 documentation, 91 against 86\n- Agent ergonomics, 91 against 77\n- Maintenance \u0026 community, 93 against 77\n- Transparency \u0026 trust, 60 against 30\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n- Open source\n\nWatch for: The status page shows a live check and an uptime objective but no incident history\n\n### Qovia (C)\n\nGood for: Agents that need structured public data from Chinese platforms (Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Zhihu, WeChat official accounts, Taobao and JD reviews) or the Xingtu and Pugongying creator marketplaces, with TikTok, YouTube, Instagram, X and Reddit beside them, paid per successful call from a prepaid balance.\n\nAhead on:\n- Security \u0026 auth, 60 against 40\n- Payments \u0026 pricing, 55 against 35\n\nWatch for: No status page, incident history or SLA; the terms promise nothing about uptime and the Python client is the only retry guidance beyond `Retry-After`\n\n\n## Why the edge\n\n### Transparency \u0026 trust: fastCRW +30\n\n- fastCRW (60): The engine and MCP server are AGPL-3.0 and the SDKs MIT, while the hosted control plane is closed under terms that name no legal entity (25 of 30). The terms say crawled data is handled transiently with zero data retention for approved accounts, but the privacy policy is undated, names no controller, gives no retention periods and mentions no DPA (10 of 30). The CHANGELOG flags breaking changes, deprecated v2 extract routes return a warning on every response, and the October 2026 402 change is dated in the docs, with no standing notice policy (10 of 20). Local data-source telemetry is disclosed with an opt-out. The privacy policy names Stripe, Google Analytics, Google Ads and an X pixel, but infrastructure and search providers are unnamed and no data location is given (8 of 20). 25 + 10 + 10 + 8 = 53.\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### Security \u0026 auth: Qovia +20\n\n- fastCRW (40): The hosted MCP server publishes RFC 9728 metadata naming its own authorisation server, with PKCE S256, dynamic client registration and one scope, `mcp:tools`, and the API takes revocable Bearer keys from the dashboard. No key scopes or second scope found (22). The authentication page documents fastcrw.com/mcp/\u003cAPI_KEY\u003e as a way in, a key in the URL path, so less 10 (12 of 30). Tools mostly read, and data-source calls check approvals, but there is no read-only key or confirmation step for monitors (8 of 20). Managed LLM extraction, summaries and answers wrap scraped text in a nonce fence (crates/crw-extract/src/untrusted.rs), and the hardening guide treats pages as untrusted, but the MCP docs give agents no guidance on scraped content (7 of 15). Each response reports `creditsUsed`; no per-call log in the docs (5 of 15). SECURITY.md names security@fastcrw.com and GitHub private reporting with a 48-hour acknowledgement, and CI runs CodeQL and OpenSSF Scorecard. security.txt answers 404, and no bounty or certification found (8 of 20). 12 + 8 + 7 + 5 + 8 = 40.\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### Payments \u0026 pricing: Qovia +20\n\n- fastCRW (35): No x402, MPP or L402 (0). Plans are public with credit costs per operation and top-up prices per block of credits, $9 per 1,000 on Hobby down to $299 per 500,000 on Scale, but top-ups need a plan, so between plan-only and per-unit (15 of 20). 500 one-off credits with no card, plus up to 500 from onboarding tasks (20). Hosted keys need a person to sign up in a browser; the free self-hosted engine runs with no account but isn't the graded surface (0). 0 + 15 + 20 + 0 = 35.\n- Qovia (55): No x402, MPP or L402 on Qovia's own endpoints; USDT on TRC-20 is a top-up method from a console session, not a machine payment protocol. The vendor's five Actors on the Apify Store under the profile qovia (Qovia Data, the same Telegram handle and mailbox as the site), such as the Xingtu Actor at $0.01 to $0.06 a section, can be paid through Apify, whose prepaid token is sold over x402, so partial credit for a third-party route on part of the catalogue (10 of 40). Per-call prices are published without a login, per endpoint in the OpenAPI file, llms.txt and the docs, search at $5 and raw endpoints from $0.5 to $19.5 per 1,000, with the tier rule and payment fees stated (20). 50 trial calls for a new account, counted only when a call returns data; the quickstart says to top up when they run out and the docs ask for no card at sign-up, though no account was created to confirm it (20). A person signs up in a browser and creates a key; the MCP catalogue tools work without a key but data calls do not, and the Apify route reaches four platforms without a Qovia account (5 of 20). 10+20+20+5 = 55.\n\n### Maintenance \u0026 community: fastCRW +16\n\n- fastCRW (93): v0.41.0 on 4 November 2026, matching the registry and npm (30). 16 dated releases in the 90 days from 8 August, from 0.37.0 to 0.41.0 (20). Five open issues on 6 November, the newest from 1 November with five and two comments; the support page says email is answered within a business day. Reply authors weren't read (18 of 25). In the official MCP registry as io.github.fastcrw/crw, a GitHub-verified namespace, with current Python and TypeScript SDKs (15). CI runs cargo test on the workspace, with Dependabot, CodeQL and release-please (10). 30 + 20 + 18 + 15 + 10 = 93.\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### Agent ergonomics: fastCRW +14\n\n- fastCRW (91): 11 compact MCP tools, two of them the data-source tools added in 0.41.0. Content is capped near 15,000 characters with `truncated: true` and a resume offset, and map returns at most 100 URLs by default (20 of 25). Formats, main-content filtering, include and exclude selectors, maxLength, startIndex, limit and crawl depth and page caps (20). Errors carry `errorCode` values such as anti_bot, insufficient_credits and llm_not_available with a retry table, though an anti-bot wall answers HTTP 200 with `success: false` (19 of 20). Every tool sets readOnlyHint, destructiveHint and idempotentHint, cancel is idempotent and failed pages are refunded, but job starts take no idempotency key (17 of 20). Only `url` is required, with official Python and TypeScript SDKs (15). 20 + 20 + 19 + 17 + 15 = 91.\n- Qovia (77): API reading. Responses come in fixed page sizes per endpoint, from about 5 comments on Xiaohongshu to 100 Fliggy reviews, with limit only on Bilibili danmaku and no field selection; the record shape is compact and shared across posts, notes and videos. The MCP server loads four tools by default, keeps the catalogue out of context until search_endpoints and get_endpoint are called, and ?tools= selects platforms or everything, which on the MCP reading would score 25 (18 of 25). Cursor pagination with has_more on most lists, search_id on Douyin and Zhihu search, page numbers on Weibo, Xiaohongshu and Bilibili, sort options on several, and the cross-platform search filters by platform, content type, sentiment and whole-day date windows up to 90 days (17 of 20). One error object with 20 codes, request_id on every answer, the retryable set marked, refunded codes separated from never-charged ones, and MCP tool errors carrying error.code, the HTTP status and retry_after_seconds (19 of 20). All calls are reads, failed and empty calls are refunded, Retry-After is declared and the Python client retries; no readOnlyHint or other annotation appears in the vendor's 28 October tools/list snapshot (14 of 20). One required parameter on 117 of 144 operations and defaults set on the server, but the only official SDK is the Python client; Node and curl are examples (9 of 15). 18+17+19+14+9 = 77.\n\n### Reliability: fastCRW +10\n\n- fastCRW (50): Graded on the hosted lines, for the hosted API and MCP server an agent would call; the self-hosted engine would read higher on the local lines. fastcrw.com/status is a first-party page with a live health check and a 99.9% monthly uptime objective, but no components with history (10 of 20). It lists no incidents and keeps no history we could read (5). Concurrency per plan is published, 3 on Free to 150 on Scale, while the request-rate guard above it is deliberately unpublished (12 of 15). The rate-limits page documents Retry-After and X-RateLimit headers, gives exponential backoff code, and separates 429 (retry) from 402 (stop). No idempotency keys for crawl, extract or monitor starts (13 of 15). Pricing mentions an SLA only as 'Premier + SLA' on Enterprise, with no terms, and the terms promise no uptime (0). The hosted service is sold on paid plans with no beta label, though the engine is at 0.41.0 (10). 10 + 5 + 12 + 13 + 0 + 10 = 50.\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## Score by category\n\n| Category | Weight | fastCRW | Qovia | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 50 | 40 | fastCRW +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 91 | 86 | fastCRW +5 |\n| Agent ergonomics | 13% (16.2 this run) | 91 | 77 | fastCRW +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 40 | 60 | Qovia +20 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 55 | Qovia +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 93 | 77 | fastCRW +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 30 | fastCRW +30 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **64.3 · B** | **61.2 · C** | |\n\n## Facts side by side\n\n| Fact | fastCRW | Qovia |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Nanofy OÜ | Qovia |\n| Hosted endpoint | `https://fastcrw.com/mcp` | `https://api.qovia.ai` |\n| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | AGPL-3.0 | 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 | 11 | 141 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.fastcrw/crw` | `ai.qovia/qovia` |\n| Last release | 2026-11-04 | 2026-10-28 |\n| Terms last updated | 2026-04-04 | not read yet |\n| Privacy policy last updated | no date given | not read yet |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | yes | 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 | not found in the text | not read yet |\n| Popularity | 1.2k stars, 881 npm/wk | 0 stars |\n\n## Verdicts\n\n**fastCRW.** Agents get 11 compact, annotated MCP tools with bounded output, a public OpenAPI spec, refunds on failed pages and a free self-hosted engine. The hosted service has no status history, publishes no SLA terms, names its operator only on the support page, and documents an MCP address with the API key in the URL path.\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### fastCRW\n\n1. Connect to https://fastcrw.com/mcp with OAuth rather than the /mcp/\u003cAPI_KEY\u003e address, so the key stays out of URLs and logs\n2. Branch on `errorCode`. Stop on 402 insufficient_credits or llm_not_available, and on 429 wait for Retry-After before retrying\n3. Check `success` as well as the HTTP status, since an anti-bot wall answers 200 with `success: false` and `errorCode: anti_bot`\n4. Pass `startIndex` from a truncated result to read the rest of a long page instead of setting `maxLength: 0`\n5. Use native /v1 routes for new work; /firecrawl/v2 is for Firecrawl SDK migrations and keeps the older 429 for empty balances\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, fastCRW or Qovia?\n\nfastCRW scores 64.3 (B) on agent readiness against Qovia's 61.2 (C), and leads in 5 of 7 scored categories. Qovia leads on security \u0026 auth and payments \u0026 pricing.\n\n### Do fastCRW and Qovia need an API key?\n\nfastCRW takes an API key or an OAuth sign-in. Qovia needs an API key.\n\n### Can an agent call fastCRW and Qovia without installing anything?\n\nYes. fastCRW has a hosted endpoint at https://fastcrw.com/mcp and Qovia at https://api.qovia.ai.\n\n### Are fastCRW and Qovia open source?\n\nfastCRW is open source (AGPL-3.0). No open-source release is listed for Qovia.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/crw-vs-qovia.json, and with the fewest tokens: https://www.anchorterminal.com/compare/crw-vs-qovia.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"crw\", \"b\": \"qovia\"}`. From a terminal: `anchor compare crw qovia`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/crw.json and https://www.anchorterminal.com/api/v1/tools/qovia.json\n\n## Other comparisons with fastCRW or Qovia\n\n- [Bright Data vs fastCRW](https://www.anchorterminal.com/compare/bright-data-vs-crw.md)\n- [BrowserAct vs fastCRW](https://www.anchorterminal.com/compare/browseract-vs-crw.md)\n- [Context.dev vs fastCRW](https://www.anchorterminal.com/compare/context-dev-vs-crw.md)\n- [Crawl4AI vs fastCRW](https://www.anchorterminal.com/compare/crawl4ai-vs-crw.md)\n- [fastCRW vs Decodo Web Data API](https://www.anchorterminal.com/compare/crw-vs-decodo.md)\n- [fastCRW vs Diffbot](https://www.anchorterminal.com/compare/crw-vs-diffbot.md)\n- [fastCRW vs jevcrawl](https://www.anchorterminal.com/compare/crw-vs-jevcrawl.md)\n- [fastCRW vs Jina Reader](https://www.anchorterminal.com/compare/crw-vs-jina-reader.md)\n- [fastCRW vs Microlink](https://www.anchorterminal.com/compare/crw-vs-microlink.md)\n- [fastCRW vs Olostep](https://www.anchorterminal.com/compare/crw-vs-olostep.md)\n- [fastCRW vs Outcrawl](https://www.anchorterminal.com/compare/crw-vs-outcrawl.md)\n- [fastCRW vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/crw-vs-oxylabs-web-scraper.md)\n- [fastCRW vs Scrape.do](https://www.anchorterminal.com/compare/crw-vs-scrape-do.md)\n- [fastCRW vs ScrapeGraphAI](https://www.anchorterminal.com/compare/crw-vs-scrapegraphai.md)\n- [fastCRW vs Scrapeless](https://www.anchorterminal.com/compare/crw-vs-scrapeless.md)\n- [fastCRW vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/crw-vs-scrapeops.md)\n- [fastCRW vs ScraperAPI](https://www.anchorterminal.com/compare/crw-vs-scraperapi.md)\n- [fastCRW vs Scrapewise](https://www.anchorterminal.com/compare/crw-vs-scrapewise.md)\n- [fastCRW vs Scrapfly](https://www.anchorterminal.com/compare/crw-vs-scrapfly.md)\n- [fastCRW vs ScrapingAnt](https://www.anchorterminal.com/compare/crw-vs-scrapingant.md)\n- [fastCRW vs ScrapingBee](https://www.anchorterminal.com/compare/crw-vs-scrapingbee.md)\n- [fastCRW vs Scrapingdog](https://www.anchorterminal.com/compare/crw-vs-scrapingdog.md)\n- [fastCRW vs Spider](https://www.anchorterminal.com/compare/crw-vs-spider-cloud.md)\n- [fastCRW vs WebScraping.AI](https://www.anchorterminal.com/compare/crw-vs-webscraping-ai.md)\n- [fastCRW vs ZenRows](https://www.anchorterminal.com/compare/crw-vs-zenrows.md)\n- [fastCRW vs Zyte API](https://www.anchorterminal.com/compare/crw-vs-zyte.md)\n- [Bright Data vs Qovia](https://www.anchorterminal.com/compare/bright-data-vs-qovia.md)\n- [fastCRW vs Firecrawl MCP](https://www.anchorterminal.com/compare/crw-vs-firecrawl-mcp.md)\n- [Firecrawl MCP vs Qovia](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia.md)\n- [BrowserAct vs Qovia](https://www.anchorterminal.com/compare/browseract-vs-qovia.md)\n- [Context.dev vs Qovia](https://www.anchorterminal.com/compare/context-dev-vs-qovia.md)\n- [Crawl4AI vs Qovia](https://www.anchorterminal.com/compare/crawl4ai-vs-qovia.md)\n- [fastCRW vs ScrapeAtlas](https://www.anchorterminal.com/compare/crw-vs-scrapeatlas.md)\n- [fastCRW vs SoldFetch](https://www.anchorterminal.com/compare/crw-vs-soldfetch.md)\n- [Decodo Web Data API vs Qovia](https://www.anchorterminal.com/compare/decodo-vs-qovia.md)\n- [Diffbot vs Qovia](https://www.anchorterminal.com/compare/diffbot-vs-qovia.md)\n- [jevcrawl vs Qovia](https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.md)\n- [Microlink vs Qovia](https://www.anchorterminal.com/compare/microlink-vs-qovia.md)\n- [Olostep vs Qovia](https://www.anchorterminal.com/compare/olostep-vs-qovia.md)\n- [Outcrawl vs Qovia](https://www.anchorterminal.com/compare/outcrawl-vs-qovia.md)\n- [Oxylabs Web Scraper API vs Qovia](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.md)\n- [Qovia vs ScrapeAtlas](https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.md)\n- [Qovia vs ScrapeGraphAI](https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.md)\n- [Qovia vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/qovia-vs-scrapeops.md)\n- [Qovia vs ScraperAPI](https://www.anchorterminal.com/compare/qovia-vs-scraperapi.md)\n- [Qovia vs Scrapewise](https://www.anchorterminal.com/compare/qovia-vs-scrapewise.md)\n- [Qovia vs Scrapfly](https://www.anchorterminal.com/compare/qovia-vs-scrapfly.md)\n- [Qovia vs ScrapingAnt](https://www.anchorterminal.com/compare/qovia-vs-scrapingant.md)\n- [Qovia vs ScrapingBee](https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.md)\n- [Qovia vs Scrapingdog](https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.md)\n- [Qovia vs SoldFetch](https://www.anchorterminal.com/compare/qovia-vs-soldfetch.md)\n- [Qovia vs Spider](https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.md)\n- [Qovia vs WebScraping.AI](https://www.anchorterminal.com/compare/qovia-vs-webscraping-ai.md)\n- [Qovia vs ZenRows](https://www.anchorterminal.com/compare/qovia-vs-zenrows.md)\n- [Qovia vs Zyte API](https://www.anchorterminal.com/compare/qovia-vs-zyte.md)\n- [Apify MCP Server vs fastCRW](https://www.anchorterminal.com/compare/apify-mcp-vs-crw.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-07", "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": "fastCRW vs Qovia", "url": "" } ], "description": "fastCRW scores 64.3 (B) to Qovia's 61.2 (C) for extraction. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "fastCRW B 64.3", "Qovia C 61.2", "scores" ], "h1": "fastCRW vs Qovia", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/crw-vs-qovia", "published": "2026-10-01", "section": "tools", "title": "fastCRW vs Qovia for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/crw-vs-qovia" }, "tokens": { "markdown": 6500, "slim": 3980 }, "version": 1 }