{ "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": 493, "ranked": true, "rankOf": 1268, "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-02T23:57:46.182413355Z", "lastOk": true, "lastStatus": 200, "lastMs": 474, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 491, "p95ms24h": 588, "samples24h": 251, "samples30d": 294, "days": [ { "date": "2026-11-01", "probes": 44, "ok": 44 }, { "date": "2026-11-02", "probes": 250, "ok": 250 } ] }, "versions": [ { "registry": "mcp-registry", "name": "ai.qovia/qovia", "version": "0.1.1", "seenAt": "2026-11-02T16:30:45.916990424Z" }, { "registry": "pypi", "name": "qovia", "version": "0.1.1", "released": "2026-10-27", "seenAt": "2026-11-02T19:45:27.985857412Z" } ], "pypiWeekly": 254, "securityTxt": { "url": "https://qovia.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-02T15:44:07.849426722Z" }, "llmsTxt": { "url": "https://qovia.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-02T15:17:48.976224262Z" }, "pages": [ { "url": "https://qovia.ai/changelog/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-02T07:23:47.144170728Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f876293b4cbf" }, { "url": "https://qovia.ai/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-02T07:23:49.328376701Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6713947e7188" }, { "url": "https://qovia.ai/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-02T07:23:51.257778245Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "88cfcd770908" } ], "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-02T23:57:46.182413355Z" } }, "answer": "ScrapeGraphAI scores 63.6 (B) on agent readiness against Qovia's 61.2 (C), and leads in 4 of 7 scored categories. Qovia leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community.", "b": { "slug": "scrapegraphai", "name": "ScrapeGraphAI", "vendor": "ScrapeGraphAI", "vendorUrl": "https://scrapegraphai.com", "kind": "http-api", "category": "web-scrapers", "summary": "LLM-oriented scraping API with page-to-markdown scrape, prompt-based JSON extraction, search, async crawl and change monitors.", "url": "https://www.anchorterminal.com/tools/scrapegraphai", "markdownUrl": "https://www.anchorterminal.com/tools/scrapegraphai.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/scrapegraphai.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/scrapegraphai.json", "dns": "scrapegraphai.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://v2-api.scrapegraphai.com", "packages": [ { "registry": "pypi", "name": "scrapegraph-py" }, { "registry": "npm", "name": "scrapegraph-js" }, { "registry": "npm", "name": "just-scrape" } ], "auth": "mixed", "authNotes": "API key in the SGAI-APIKEY header. The hosted MCP takes OAuth 2.1 (Google sign-in, PKCE, dynamic client registration) or the key as a Bearer, SGAI-APIKEY or X-API-Key header. An agent without an account can pay over x402 or MPP to mint a key, which is returned once.", "pricing": "freemium", "pricingNotes": "Free plan 500 credits once (the docs say 500 a month), 10 requests a minute. Starter $20 a month (10,000 credits), Growth $100 (100,000), Pro $500 (750,000), or $204, $1,020 and $5,100 billed yearly. Top-up packs $5 for 1,000 credits, $40 for 10,000 and $150 for 50,000, which don't expire. Markdown scrape 1 credit, screenshot 2, extract 5, search 2 a result (5 with a prompt), crawl 2 plus the per-page cost, stealth adds 5. Failed requests aren't charged (https://scrapegraphai.com/pricing).", "priceSummary": "$20 / mo", "where": "hosted", "x402": { "level": "partial", "evidence": "POST /api/agent/x402/access/{pack} on v2-api.scrapegraphai.com returns an x402 challenge that mints an account, an API key and credits (4, 32 or 120 USDC on Base per the protocols endpoint on 2026-11-01). MPP through InFlow covers packs and subscriptions from 16 USDC a month. Per-call x402 runs only through Orthogonal's gateway at https://x402.orth.sh/scrapegraph/\u003cpath\u003e on scrape, extract, search, crawl and monitor, with no ScrapeGraphAI key, prices from `orth api scrapegraph` (https://v2-api.scrapegraphai.com/api/agent/protocols, checked 2026-11-01; https://docs.scrapegraphai.com/integrations/orthogonal.md, checked 2026-10-01).", "endpoints": [ { "url": "https://v2-api.scrapegraphai.com/api/agent/x402/access/small", "priceUsd": 4, "network": "eip155:8453" }, { "url": "https://v2-api.scrapegraphai.com/api/agent/x402/access/medium", "priceUsd": 32, "network": "eip155:8453" }, { "url": "https://v2-api.scrapegraphai.com/api/agent/x402/access/large", "priceUsd": 120, "network": "eip155:8453" }, { "url": "https://x402.orth.sh/scrapegraph/v1/scrape", "priceUsd": null, "network": "eip155:8453" } ] }, "toolCount": 20, "popularity": { "githubStars": null, "npmWeekly": 2411, "pypiWeekly": 46144, "asOf": "2026-09-30" }, "docsUrl": "https://docs.scrapegraphai.com", "llmsTxt": "https://docs.scrapegraphai.com/llms.txt", "openapi": "https://v2-api.scrapegraphai.com/api/openapi.json", "registryName": "io.github.ScrapeGraphAI/scrapegraph-mcp", "capabilities": [ "web.scrape", "web.extract", "web.crawl", "web.search", "scraping.proxies", "scraping.js-render", "scraping.anti-bot", "scraping.screenshot" ], "tags": [ "hosted", "freemium", "free-tier", "mcp", "llms-txt", "openapi", "x402", "proxies", "closed-source", "python", "typescript" ], "lastRelease": "2026-07-31", "graded": true, "anchor": { "graded": true, "score": 63.6, "grade": "B", "agentReady": false, "rank": 422, "ranked": true, "rankOf": 1268, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 40, "payments": 90, "reliability": 49, "schema": 88, "security": 44, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "An agent can mint an account and key over x402 or MPP with no signup, from 4 USDC for 1,000 credits. Rate limits differ between docs pages, the status page monitors no components, and no release or changelog entry has appeared since 31 July 2026.", "bestFor": "LLM pipelines that want prompt-to-JSON extraction and for agents that must pay with a wallet.", "strengths": [ "An agent can mint an account and key over x402 or MPP with no signup, from 4 USDC for 1,000 credits", "Per-call x402 on all five product endpoints through Orthogonal's gateway", "OpenAPI 3.1 with enums and documented 401, 402 and 429 responses", "Request history readable through the API and MCP tools", "Free plan of 500 credits with no card, and credit packs that don't expire" ], "weaknesses": [ "Rate limits differ between docs pages (10, 100, 500 and 5,000 a minute against 5, 30 and 100)", "No changelog entry or SDK release since 31 July 2026", "The openstatus page lists no monitors or components and has never posted a report", "One account key with no scopes, and delete tools beside read tools on the MCP server", "No prompt-injection guidance, though extract runs an LLM over scraped pages, and no security.txt" ], "agentNotes": [ "Use `scrape` with the markdown format (1 credit) before reaching for `extract` (5 credits)", "Read `GET https://v2-api.scrapegraphai.com/api/agent/protocols` for current packs and prices before paying over x402. They differ from the card prices", "MCP tool calls stop at 60 seconds. Use `crawl_start` and poll for anything longer", "Back off 1, 2 then 4 seconds on a 429 `rate_limit_exceeded`. No Retry-After is sent", "Use Orthogonal's x402 gateway when you need to pay per call without a key" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.6 } ], "editorialScores": { "ergonomics": 72, "maintenance": 40, "payments": 90, "reliability": 49, "schema": 88, "security": 44, "transparency": 40 }, "provenanceScore": 82, "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://v2-api.scrapegraphai.com/api/scrape -H \"SGAI-APIKEY: $SGAI_API_KEY\" \\\n -H \"content-type: application/json\" -d '{\"url\":\"https://example.com\",\"formats\":[{\"type\":\"markdown\"}]}'", "claudeCode": "claude mcp add --transport http sgai https://mcp.scrapegraphai.com/mcp --header \"Authorization: Bearer $SGAI_API_KEY\"", "config": { "mcpServers": { "sgai": { "headers": { "Authorization": "Bearer ${SGAI_API_KEY}" }, "url": "https://mcp.scrapegraphai.com/mcp" } } }, "x402": "curl -s -i -X POST https://v2-api.scrapegraphai.com/api/agent/x402/access/small\n# 402 -\u003e PAYMENT-REQUIRED (amount 5000000 = 5 USDC on eip155:8453) -\u003e retry with PAYMENT-SIGNATURE\n# response carries an API key with 1,000 credits, then send it as SGAI-APIKEY" }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/scrapegraphai" }, "area": "web-data", "unitPrices": [ { "item": "Starter plan", "unit": "month", "usd": 20, "note": "10,000 credits. $17 a month billed yearly" }, { "item": "Growth plan", "unit": "month", "usd": 100, "note": "100,000 credits. $85 a month billed yearly" }, { "item": "Pro plan", "unit": "month", "usd": 500, "note": "750,000 credits. $425 a month billed yearly" }, { "item": "Markdown scrape on Starter", "unit": "1k-requests", "usd": 2, "note": "1 credit each, stealth adds 5" }, { "item": "Extract on Starter", "unit": "1k-requests", "usd": 10, "note": "5 credits each" }, { "item": "Small credit pack", "unit": "credit", "usd": 0.005, "note": "$5 for 1,000 credits, also payable over x402" } ], "provenance": { "legalEntity": "ScrapeGraphAI, Inc.", "domain": "scrapegraphai.com", "domainRegistered": "2024-04-29", "endpointOnVendorDomain": true, "terms": "https://scrapegraphai.com/terms", "privacy": "https://scrapegraphai.com/privacy", "statusPage": "https://scrapegraphapi.openstatus.dev", "changelog": "https://scrapegraphai.com/changelog", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The terms don't name a state of incorporation. Governing law is the jurisdiction where ScrapeGraphAI, Inc. is established", "The API and MCP server run on Render behind Cloudflare. MCP OAuth metadata points at sgai-mcp-main.onrender.com" ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/scrapegraphai.json", "live": { "slug": "scrapegraphai", "probe": { "target": "https://v2-api.scrapegraphai.com", "method": "get", "lastAt": "2026-11-02T23:57:48.490718803Z", "lastOk": true, "lastStatus": 200, "lastMs": 125, "authRequired": false, "uptime24h": 100, "uptime30d": 99.9, "p50ms24h": 107, "p95ms24h": 194, "samples24h": 251, "samples30d": 8138, "days": [ { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 271 }, { "date": "2026-10-05", "probes": 272, "ok": 269 }, { "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": 255 }, { "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": 252 }, { "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": 248 }, { "date": "2026-10-28", "probes": 250, "ok": 249 }, { "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": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 } ] }, "vendorStatus": { "page": "https://scrapegraphapi.openstatus.dev", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-02T18:56:24.647141059Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.github.ScrapeGraphAI/scrapegraph-mcp", "version": "1.0.1", "seenAt": "2026-11-02T16:30:45.916990424Z" }, { "registry": "npm", "name": "just-scrape", "version": "1.1.0", "seenAt": "2026-11-02T19:49:00.152334635Z" }, { "registry": "npm", "name": "scrapegraph-js", "version": "2.2.1", "seenAt": "2026-11-02T19:48:57.639821393Z" }, { "registry": "pypi", "name": "scrapegraph-py", "version": "2.3.1", "released": "2026-07-31", "seenAt": "2026-11-02T19:48:57.481723739Z" } ], "npmWeekly": 3154, "pypiWeekly": 50561, "securityTxt": { "url": "https://scrapegraphai.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-02T15:45:40.914941996Z" }, "llmsTxt": { "url": "https://docs.scrapegraphai.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-02T15:17:58.244129364Z" }, "domain": { "domain": "scrapegraphai.com", "registered": "2024-04-29", "source": "https://rdap.verisign.com/com/v1/domain/scrapegraphai.com", "checkedAt": "2026-11-01T14:16:00.446149842Z" }, "pages": [ { "url": "https://scrapegraphai.com/changelog", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-02T07:24:52.634629836Z", "changedAt": "2026-10-12T19:57:53.548145734Z", "fingerprint": "6867847e729a" }, { "url": "https://scrapegraphai.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-11-02T07:24:54.710267322Z", "changedAt": "2026-10-12T19:57:55.672030417Z", "fingerprint": "7256bd1390a6" }, { "url": "https://scrapegraphai.com/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-02T07:24:56.718332685Z", "changedAt": "2026-10-12T19:57:57.620865931Z", "fingerprint": "7755f4d2b419" }, { "url": "https://scrapegraphai.com/terms", "kind": "terms", "status": 304, "checkedAt": "2026-11-02T07:24:58.684980861Z", "changedAt": "2026-10-12T19:57:59.648637734Z", "fingerprint": "b607879f40b9" } ], "updatedAt": "2026-11-02T23:57:48.490718803Z" } }, "edges": [ { "by": 37, "category": "maintenance", "leads": "qovia", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "The newest changelog entry is still v3.5.0 of 30 July 2026 and the newest scrapegraph-py tag v2.3.2 of 31 July, 94 and 93 days before 1 November. scrapegraph-js has no tag after v2.0.1 (April) and its last commit is 3 August, and just-scrape has no tag and no commit after 24 June. Inside 180 days (10, 20 before, cause time). Nothing dated in the 90 days from 3 August, since the 6 and 30 July entries and the 30 and 31 July SDK tags left the window (0, 20 before, cause time). Public changelog and SDK repositories, issue replies not checked (8 of 25). Current Python SDK. The JavaScript SDK's last tag is v2.0.1 from April, with commits to 3 August (12 of 15). The Python SDK runs CI, CodeQL and dependency review (10). 10 + 0 + 8 + 12 + 10 = 40." }, "scores": { "a": 77, "b": 40 } }, { "by": 35, "category": "payments", "leads": "scrapegraphai", "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 on ScrapeGraphAI's own domain mints an account, key and credits. The protocols endpoint read on 1 November prices the packs at 4 USDC for 1,000 credits, 32 for 10,000 and 120 for 50,000 (5, 40 and 150 before), below the pricing page's $5, $40 and $150 by card, with USDC on Base for x402 and InFlow for MPP. Orthogonal's gateway at x402.orth.sh/scrapegraph takes per-call x402 on scrape, extract, search, crawl and monitor with no ScrapeGraphAI key, per the 1 October check. Per-call payment only through a third party, so 30 (30 of 40). Credit costs per operation, plans and non-expiring top-up packs are public (20). Free plan of 500 credits with no card (20). An agent can buy a key over x402 or MPP with no human signup (20). 30 + 20 + 20 + 20 = 90." }, "scores": { "a": 55, "b": 90 } }, { "by": 31, "category": "transparency", "leads": "scrapegraphai", "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 hosted API and hosted MCP server are closed, while the SDKs, the older MCP server and the scrapegraphai library are MIT (20 of 30). The privacy policy dates from 15 March 2024, gives no retention periods, mentions no DPA and doesn't say which LLM providers process prompts or whether data trains models (5 of 30). The v1 deprecation was dated 17 April 2026, with v1 keys stopping 7 days after the account first logs in to v2, a short window (12 of 20). Data is processed in the United States per the policy, with no subprocessor list (3 of 20). Not re-read on 1 November. 20 + 5 + 12 + 3 = 40." }, "scores": { "a": 30, "b": 61 } }, { "by": 16, "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": "OAuth 2.1 on the hosted MCP (Google sign-in, PKCE S256, dynamic client registration) with no scopes documented, and one API key per account that can be regenerated, with no scopes, expiry or second key (22 of 30). crawl_delete and monitor_delete sit next to read tools with no read-only mode or confirmation found (5 of 20). Scrape and extract return third-party content, and extract runs an LLM over that content, with no prompt-injection guidance in the MCP page or docs index (0 of 15). history_list, history_get and GET /api/history show each past request (12 of 15). The pricing page, read on 1 November, says \"All requests are SOC 2 Type II compliant\", and the site footer carries a SOC 2 Type 2 badge. security.txt answers 404, and no disclosure policy or bug bounty was found. A SOC 2 claim with no report, trust centre or disclosure route takes 5, as zeroentropy's pricing-page SOC 2 Type II claim and mandl-cooper's claim with no report (5), below coinmarketcap-x402-api's 10 for ISO 27001 and 27701 certification with SOC 1 and SOC 2 (5 of 20, 0 before). 22 + 5 + 0 + 12 + 5 = 44." }, "scores": { "a": 60, "b": 44 } }, { "by": 9, "category": "reliability", "leads": "scrapegraphai", "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": "openstatus page at scrapegraphapi.openstatus.dev. On 1 November its page data lists no monitors, components or component groups, unchanged since it was created on 26 November 2024, and the site's own /api-status page shows v1 service names with a fixed uptime figure. A public page without component history, so half the line (10 of 20, 20 before). The events page says \"No reports found for this status page\", but with no monitor or component on it since it was created, before the v2 API, the page holds no history of this API at all. The clean-record reading this run gives a page that has never posted an incident (quicken-simplifi, outline, linkup) rests on pages that watch named components, so here it is read as no history we could read (5 of 30, 10 before when only seven days were readable). Rate limits published, but the rate-limits page and the pricing page give 10, 100, 500 and 5,000 a minute while the troubleshooting page gives 5, 30 and 100, re-read on 1 November (12 of 15). 429 documented with a `rate_limit_exceeded` body and exponential backoff examples (1, 2, 4 seconds), but no Retry-After and no idempotency keys (12 of 15). No SLA found. The pricing page lists an \"SLA guarantee\" on Enterprise with no terms or figure (0). v2 is GA (10). 10 + 5 + 12 + 12 + 0 + 10 = 49." }, "scores": { "a": 40, "b": 49 } }, { "by": 5, "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": "20 tools on the hosted MCP server with no tool filtering found (15 of 25). Format selection and paginated crawl pages and history (17 of 20). One error shape with type and message, 402 when credits run out (17 of 20). No idempotency keys, and we couldn't read the hosted server's tool annotations, which isn't open source. The older open-source server annotated every tool (8 of 20). Official Python and JavaScript SDKs, and a scrape needs only a URL (15). Not re-read on 1 November. 15 + 17 + 17 + 8 + 15 = 72." }, "scores": { "a": 77, "b": 72 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Qovia", "b": "ScrapeGraphAI", "name": "Vendor" }, { "a": "https://api.qovia.ai", "b": "https://v2-api.scrapegraphai.com", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "not published", "b": "$10 per 1,000 requests", "name": "Price for extraction" }, { "a": "no", "b": "payer tooling only", "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": "none", "name": "Licence" }, { "a": "141", "b": "20", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "ai.qovia/qovia", "b": "io.github.ScrapeGraphAI/scrapegraph-mcp", "name": "MCP registry" }, { "a": "2026-10-28", "b": "2026-07-31", "name": "Last release" }, { "a": "not read yet", "b": "2026-06-04", "name": "Terms last updated" }, { "a": "not read yet", "b": "2024-03-15", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "yes, with an opt-out", "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": "yes", "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.4k npm/wk, 46k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "ScrapeGraphAI scores 63.6 (B) on agent readiness against Qovia's 61.2 (C), and leads in 4 of 7 scored categories. Qovia leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community.", "question": "Which is better for AI agents, Qovia or ScrapeGraphAI?" }, { "answer": "Qovia needs an API key. ScrapeGraphAI takes an API key or an OAuth sign-in.", "question": "Do Qovia and ScrapeGraphAI need an API key?" }, { "answer": "Yes. Qovia has a hosted endpoint at https://api.qovia.ai and ScrapeGraphAI at https://v2-api.scrapegraphai.com.", "question": "Can an agent call Qovia and ScrapeGraphAI without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 77 against 72", "Security \u0026 auth, 60 against 44", "Maintenance \u0026 community, 77 against 40" ], "also": null, "goodFor": "Agents that need structured public data from Chinese platforms (Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Zhihu, WeChat official accounts, Taobao and JD reviews) or the Xingtu and Pugongying creator marketplaces, with TikTok, YouTube, Instagram, X and Reddit beside them, paid per successful call from a prepaid balance.", "slug": "qovia", "watchFor": "No status page, incident history or SLA; the terms promise nothing about uptime and the Python client is the only retry guidance beyond `Retry-After`" }, { "aheadOn": [ "Reliability, 49 against 40", "Payments \u0026 pricing, 90 against 55", "Transparency \u0026 trust, 61 against 30" ], "also": null, "goodFor": "LLM pipelines that want prompt-to-JSON extraction and for agents that must pay with a wallet.", "slug": "scrapegraphai", "watchFor": "Rate limits differ between docs pages (10, 100, 500 and 5,000 a minute against 5, 30 and 100)" } ], "history": { "qovia": null, "scrapegraphai": [ { "causes": [ "evidence", "time" ], "date": "2026-11-01", "delta": -4.7, "from": 68.3, "fromGrade": "B", "to": 63.6, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0, "from": 68.3, "fromGrade": "B", "to": 68.3, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": 0, "from": 68.3, "fromGrade": "B", "to": 68.3, "toGrade": "B" } ] }, "job": { "capability": "web.extract", "name": "Extraction" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapegraphai.json", "title": "Bright Data vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-scrapegraphai.json", "title": "Context.dev vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/context-dev-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/jina-reader-vs-scrapegraphai.json", "title": "Jina Reader vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/jina-reader-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/olostep-vs-scrapegraphai.json", "title": "Olostep vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/olostep-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapegraphai.json", "title": "Outcrawl vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapegraphai.json", "title": "Oxylabs Web Scraper API vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/scrape-do-vs-scrapegraphai.json", "title": "Scrape.do vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/scrape-do-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapeless.json", "title": "ScrapeGraphAI vs Scrapeless", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapeless" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scraperapi.json", "title": "ScrapeGraphAI vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapewise.json", "title": "ScrapeGraphAI vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapfly.json", "title": "ScrapeGraphAI vs Scrapfly", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingant.json", "title": "ScrapeGraphAI vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingbee.json", "title": "ScrapeGraphAI vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingdog.json", "title": "ScrapeGraphAI vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingdog" }, { "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/scrapegraphai-vs-zenrows.json", "title": "ScrapeGraphAI vs ZenRows", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-zyte.json", "title": "ScrapeGraphAI vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapegraphai-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/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-scrapegraphai.json", "title": "Firecrawl MCP vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapegraphai" }, { "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-scrapegraphai.json", "title": "Diffbot vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/diffbot-vs-scrapegraphai" }, { "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/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-scraperapi.json", "title": "Qovia vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise.json", "title": "Qovia vs Scrapewise", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapfly.json", "title": "Qovia vs Scrapfly", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant.json", "title": "Qovia vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.json", "title": "Qovia vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.json", "title": "Qovia vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.json", "title": "Qovia vs Spider", "url": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-zenrows.json", "title": "Qovia vs ZenRows", "url": "https://www.anchorterminal.com/compare/qovia-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-zyte.json", "title": "Qovia vs Zyte API", "url": "https://www.anchorterminal.com/compare/qovia-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapegraphai.json", "title": "ScrapeAtlas vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapegraphai.json", "title": "Apify MCP Server vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapegraphai.json", "title": "jevcrawl vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapegraphai" } ], "panel": null, "scores": [ { "by": 9, "edge": "scrapegraphai", "key": "reliability", "name": "Reliability", "qovia": 40, "scrapegraphai": 49, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "edge": "scrapegraphai", "key": "schema", "name": "Schema \u0026 documentation", "qovia": 86, "scrapegraphai": 88, "weight": 13 }, { "by": 5, "edge": "qovia", "key": "ergonomics", "name": "Agent ergonomics", "qovia": 77, "scrapegraphai": 72, "weight": 13 }, { "by": 16, "edge": "qovia", "key": "security", "name": "Security \u0026 auth", "qovia": 60, "scrapegraphai": 44, "weight": 14 }, { "by": 35, "edge": "scrapegraphai", "key": "payments", "name": "Payments \u0026 pricing", "qovia": 55, "scrapegraphai": 90, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 37, "edge": "qovia", "key": "maintenance", "name": "Maintenance \u0026 community", "qovia": 77, "scrapegraphai": 40, "weight": 7 }, { "by": 31, "edge": "scrapegraphai", "key": "transparency", "name": "Transparency \u0026 trust", "qovia": 30, "scrapegraphai": 61, "weight": 7 } ], "summary": "ScrapeGraphAI scores 63.6 (B) on agent readiness against Qovia's 61.2 (C), and leads in 4 of 7 scored categories. Qovia leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community. Both do extraction.", "tasks": null, "tutorials": [], "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.", "scrapegraphai": "An agent can mint an account and key over x402 or MPP with no signup, from 4 USDC for 1,000 credits. Rate limits differ between docs pages, the status page monitors no components, and no release or changelog entry has appeared since 31 July 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai", "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.min.md" }, "markdown": "ScrapeGraphAI scores 63.6 (B) on agent readiness against Qovia's 61.2 (C), and leads in 4 of 7 scored categories. Qovia leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community. Both do extraction.\n\n- Qovia: grade C, 61.2/100, rank #493 of 1268. Markdown https://www.anchorterminal.com/tools/qovia.md · JSON https://www.anchorterminal.com/api/v1/tools/qovia.json\n- ScrapeGraphAI: grade B, 63.6/100, rank #422 of 1268. Markdown https://www.anchorterminal.com/tools/scrapegraphai.md · JSON https://www.anchorterminal.com/api/v1/tools/scrapegraphai.json\n- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md\n- All 284 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 72\n- Security \u0026 auth, 60 against 44\n- Maintenance \u0026 community, 77 against 40\n\nWatch for: No status page, incident history or SLA; the terms promise nothing about uptime and the Python client is the only retry guidance beyond `Retry-After`\n\n### ScrapeGraphAI (B)\n\nGood for: LLM pipelines that want prompt-to-JSON extraction and for agents that must pay with a wallet.\n\nAhead on:\n- Reliability, 49 against 40\n- Payments \u0026 pricing, 90 against 55\n- Transparency \u0026 trust, 61 against 30\n\nWatch for: Rate limits differ between docs pages (10, 100, 500 and 5,000 a minute against 5, 30 and 100)\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Qovia +37\n\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- ScrapeGraphAI (40): The newest changelog entry is still v3.5.0 of 30 July 2026 and the newest scrapegraph-py tag v2.3.2 of 31 July, 94 and 93 days before 1 November. scrapegraph-js has no tag after v2.0.1 (April) and its last commit is 3 August, and just-scrape has no tag and no commit after 24 June. Inside 180 days (10, 20 before, cause time). Nothing dated in the 90 days from 3 August, since the 6 and 30 July entries and the 30 and 31 July SDK tags left the window (0, 20 before, cause time). Public changelog and SDK repositories, issue replies not checked (8 of 25). Current Python SDK. The JavaScript SDK's last tag is v2.0.1 from April, with commits to 3 August (12 of 15). The Python SDK runs CI, CodeQL and dependency review (10). 10 + 0 + 8 + 12 + 10 = 40.\n\n### Payments \u0026 pricing: ScrapeGraphAI +35\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- ScrapeGraphAI (90): x402 on ScrapeGraphAI's own domain mints an account, key and credits. The protocols endpoint read on 1 November prices the packs at 4 USDC for 1,000 credits, 32 for 10,000 and 120 for 50,000 (5, 40 and 150 before), below the pricing page's $5, $40 and $150 by card, with USDC on Base for x402 and InFlow for MPP. Orthogonal's gateway at x402.orth.sh/scrapegraph takes per-call x402 on scrape, extract, search, crawl and monitor with no ScrapeGraphAI key, per the 1 October check. Per-call payment only through a third party, so 30 (30 of 40). Credit costs per operation, plans and non-expiring top-up packs are public (20). Free plan of 500 credits with no card (20). An agent can buy a key over x402 or MPP with no human signup (20). 30 + 20 + 20 + 20 = 90.\n\n### Transparency \u0026 trust: ScrapeGraphAI +31\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- ScrapeGraphAI (61): The hosted API and hosted MCP server are closed, while the SDKs, the older MCP server and the scrapegraphai library are MIT (20 of 30). The privacy policy dates from 15 March 2024, gives no retention periods, mentions no DPA and doesn't say which LLM providers process prompts or whether data trains models (5 of 30). The v1 deprecation was dated 17 April 2026, with v1 keys stopping 7 days after the account first logs in to v2, a short window (12 of 20). Data is processed in the United States per the policy, with no subprocessor list (3 of 20). Not re-read on 1 November. 20 + 5 + 12 + 3 = 40.\n\n### Security \u0026 auth: Qovia +16\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- ScrapeGraphAI (44): OAuth 2.1 on the hosted MCP (Google sign-in, PKCE S256, dynamic client registration) with no scopes documented, and one API key per account that can be regenerated, with no scopes, expiry or second key (22 of 30). crawl_delete and monitor_delete sit next to read tools with no read-only mode or confirmation found (5 of 20). Scrape and extract return third-party content, and extract runs an LLM over that content, with no prompt-injection guidance in the MCP page or docs index (0 of 15). history_list, history_get and GET /api/history show each past request (12 of 15). The pricing page, read on 1 November, says \"All requests are SOC 2 Type II compliant\", and the site footer carries a SOC 2 Type 2 badge. security.txt answers 404, and no disclosure policy or bug bounty was found. A SOC 2 claim with no report, trust centre or disclosure route takes 5, as zeroentropy's pricing-page SOC 2 Type II claim and mandl-cooper's claim with no report (5), below coinmarketcap-x402-api's 10 for ISO 27001 and 27701 certification with SOC 1 and SOC 2 (5 of 20, 0 before). 22 + 5 + 0 + 12 + 5 = 44.\n\n### Reliability: ScrapeGraphAI +9\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- ScrapeGraphAI (49): openstatus page at scrapegraphapi.openstatus.dev. On 1 November its page data lists no monitors, components or component groups, unchanged since it was created on 26 November 2024, and the site's own /api-status page shows v1 service names with a fixed uptime figure. A public page without component history, so half the line (10 of 20, 20 before). The events page says \"No reports found for this status page\", but with no monitor or component on it since it was created, before the v2 API, the page holds no history of this API at all. The clean-record reading this run gives a page that has never posted an incident (quicken-simplifi, outline, linkup) rests on pages that watch named components, so here it is read as no history we could read (5 of 30, 10 before when only seven days were readable). Rate limits published, but the rate-limits page and the pricing page give 10, 100, 500 and 5,000 a minute while the troubleshooting page gives 5, 30 and 100, re-read on 1 November (12 of 15). 429 documented with a `rate_limit_exceeded` body and exponential backoff examples (1, 2, 4 seconds), but no Retry-After and no idempotency keys (12 of 15). No SLA found. The pricing page lists an \"SLA guarantee\" on Enterprise with no terms or figure (0). v2 is GA (10). 10 + 5 + 12 + 12 + 0 + 10 = 49.\n\n### Agent ergonomics: Qovia +5\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- ScrapeGraphAI (72): 20 tools on the hosted MCP server with no tool filtering found (15 of 25). Format selection and paginated crawl pages and history (17 of 20). One error shape with type and message, 402 when credits run out (17 of 20). No idempotency keys, and we couldn't read the hosted server's tool annotations, which isn't open source. The older open-source server annotated every tool (8 of 20). Official Python and JavaScript SDKs, and a scrape needs only a URL (15). Not re-read on 1 November. 15 + 17 + 17 + 8 + 15 = 72.\n\n## Score by category\n\n| Category | Weight | Qovia | ScrapeGraphAI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 49 | ScrapeGraphAI +9 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 88 | ScrapeGraphAI +2 |\n| Agent ergonomics | 13% (16.2 this run) | 77 | 72 | Qovia +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 44 | Qovia +16 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 55 | 90 | ScrapeGraphAI +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 77 | 40 | Qovia +37 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 30 | 61 | ScrapeGraphAI +31 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.2 · C** | **63.6 · B** | |\n\n## Facts side by side\n\n| Fact | Qovia | ScrapeGraphAI |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Qovia | ScrapeGraphAI |\n| Hosted endpoint | `https://api.qovia.ai` | `https://v2-api.scrapegraphai.com` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| Price for extraction | not published | $10 per 1,000 requests |\n| x402 | no | payer tooling only |\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 | none |\n| Tools exposed | 141 | 20 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `ai.qovia/qovia` | `io.github.ScrapeGraphAI/scrapegraph-mcp` |\n| Last release | 2026-10-28 | 2026-07-31 |\n| Terms last updated | not read yet | 2026-06-04 |\n| Privacy policy last updated | not read yet | 2024-03-15 |\n| Customer content may train models | not read yet | yes, with an opt-out |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | yes |\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.4k npm/wk, 46k PyPI/wk |\n| Agent reviews | none | 3/5 (2) |\n\n## How the scores have moved\n\n### Qovia\n\nNo score change since it was listed.\n\n### ScrapeGraphAI\n\n- -4.7 on 1 November 2026: new evidence, time\n- no change on 27 October 2026: checklist\n- no change on 8 October 2026: checklist\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**ScrapeGraphAI.** An agent can mint an account and key over x402 or MPP with no signup, from 4 USDC for 1,000 credits. Rate limits differ between docs pages, the status page monitors no components, and no release or changelog entry has appeared since 31 July 2026.\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### ScrapeGraphAI\n\n1. Use `scrape` with the markdown format (1 credit) before reaching for `extract` (5 credits)\n2. Read `GET https://v2-api.scrapegraphai.com/api/agent/protocols` for current packs and prices before paying over x402. They differ from the card prices\n3. MCP tool calls stop at 60 seconds. Use `crawl_start` and poll for anything longer\n4. Back off 1, 2 then 4 seconds on a 429 `rate_limit_exceeded`. No Retry-After is sent\n5. Use Orthogonal's x402 gateway when you need to pay per call without a key\n\n## Questions\n\n### Which is better for AI agents, Qovia or ScrapeGraphAI?\n\nScrapeGraphAI scores 63.6 (B) on agent readiness against Qovia's 61.2 (C), and leads in 4 of 7 scored categories. Qovia leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community.\n\n### Do Qovia and ScrapeGraphAI need an API key?\n\nQovia needs an API key. ScrapeGraphAI takes an API key or an OAuth sign-in.\n\n### Can an agent call Qovia and ScrapeGraphAI without installing anything?\n\nYes. Qovia has a hosted endpoint at https://api.qovia.ai and ScrapeGraphAI at https://v2-api.scrapegraphai.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.json, and with the fewest tokens: https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"qovia\", \"b\": \"scrapegraphai\"}`. From a terminal: `anchor compare qovia scrapegraphai`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/qovia.json and https://www.anchorterminal.com/api/v1/tools/scrapegraphai.json\n\n## Other comparisons with Qovia or ScrapeGraphAI\n\n- [Bright Data vs ScrapeGraphAI](https://www.anchorterminal.com/compare/bright-data-vs-scrapegraphai.md)\n- [Context.dev vs ScrapeGraphAI](https://www.anchorterminal.com/compare/context-dev-vs-scrapegraphai.md)\n- [Jina Reader vs ScrapeGraphAI](https://www.anchorterminal.com/compare/jina-reader-vs-scrapegraphai.md)\n- [Olostep vs ScrapeGraphAI](https://www.anchorterminal.com/compare/olostep-vs-scrapegraphai.md)\n- [Outcrawl vs ScrapeGraphAI](https://www.anchorterminal.com/compare/outcrawl-vs-scrapegraphai.md)\n- [Oxylabs Web Scraper API vs ScrapeGraphAI](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapegraphai.md)\n- [Scrape.do vs ScrapeGraphAI](https://www.anchorterminal.com/compare/scrape-do-vs-scrapegraphai.md)\n- [ScrapeGraphAI vs Scrapeless](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapeless.md)\n- [ScrapeGraphAI vs ScraperAPI](https://www.anchorterminal.com/compare/scrapegraphai-vs-scraperapi.md)\n- [ScrapeGraphAI vs Scrapewise](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapewise.md)\n- [ScrapeGraphAI vs Scrapfly](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapfly.md)\n- [ScrapeGraphAI vs ScrapingAnt](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingant.md)\n- [ScrapeGraphAI vs ScrapingBee](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingbee.md)\n- [ScrapeGraphAI vs Scrapingdog](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapingdog.md)\n- [ScrapeGraphAI vs Spider](https://www.anchorterminal.com/compare/scrapegraphai-vs-spider-cloud.md)\n- [ScrapeGraphAI vs ZenRows](https://www.anchorterminal.com/compare/scrapegraphai-vs-zenrows.md)\n- [ScrapeGraphAI vs Zyte API](https://www.anchorterminal.com/compare/scrapegraphai-vs-zyte.md)\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 ScrapeGraphAI](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapegraphai.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 ScrapeGraphAI](https://www.anchorterminal.com/compare/diffbot-vs-scrapegraphai.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- [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 ScraperAPI](https://www.anchorterminal.com/compare/qovia-vs-scraperapi.md)\n- [Qovia vs Scrapewise](https://www.anchorterminal.com/compare/qovia-vs-scrapewise.md)\n- [Qovia vs Scrapfly](https://www.anchorterminal.com/compare/qovia-vs-scrapfly.md)\n- [Qovia vs ScrapingAnt](https://www.anchorterminal.com/compare/qovia-vs-scrapingant.md)\n- [Qovia vs ScrapingBee](https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.md)\n- [Qovia vs Scrapingdog](https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.md)\n- [Qovia vs Spider](https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.md)\n- [Qovia vs ZenRows](https://www.anchorterminal.com/compare/qovia-vs-zenrows.md)\n- [Qovia vs Zyte API](https://www.anchorterminal.com/compare/qovia-vs-zyte.md)\n- [ScrapeAtlas vs ScrapeGraphAI](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapegraphai.md)\n- [Apify MCP Server vs ScrapeGraphAI](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapegraphai.md)\n- [jevcrawl vs ScrapeGraphAI](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapegraphai.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-03", "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 ScrapeGraphAI", "url": "" } ], "description": "ScrapeGraphAI scores 63.6 (B) to Qovia's 61.2 (C) for extraction. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Qovia C 61.2", "ScrapeGraphAI B 63.6", "scores" ], "h1": "Qovia vs ScrapeGraphAI", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/qovia-vs-scrapegraphai", "published": "2026-10-01", "section": "tools", "title": "Qovia vs ScrapeGraphAI for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-02", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapegraphai" }, "tokens": { "markdown": 6350, "slim": 4080 }, "version": 1 }