{ "data": { "a": { "slug": "jevcrawl", "name": "jevcrawl", "vendor": "Rayen Mlayeh", "vendorUrl": "https://github.com/RayenMlayeh", "kind": "mcp", "category": "web-scrapers", "summary": "jevcrawl is an open-source MCP server and CLI that crawls a website toward a question and returns only the relevant passages, verbatim with source URLs. TypeSafe's hosted Jev decision model scores the pages, passages and links.", "url": "https://www.anchorterminal.com/tools/jevcrawl", "markdownUrl": "https://www.anchorterminal.com/tools/jevcrawl.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/jevcrawl.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/jevcrawl.json", "dns": "jevcrawl.grade.anchorterminal.com", "repo": "https://github.com/RayenMlayeh/jevcrawl", "license": "Apache-2.0", "transports": [ "stdio" ], "packages": [ { "registry": "pypi", "name": "jevcrawl" } ], "auth": "api-key", "authNotes": "A TypeSafe API key in the `TYPESAFE_API_KEY` environment variable, created at console.typesafe.ai, is needed for `crawl`, `map` and `scrape` with a goal. `scrape` without a goal makes no Jev call and works with no key. The README says the key is never written to disk or logs.", "pricing": "usage", "pricingNotes": "The package is free under Apache-2.0. Decisions are billed by TypeSafe for Jev at $0.042 per million input tokens, with output tokens free. The README gives an average of $0.011 per crawl in its benchmark, and `max_decision_usd` (default $0.05) caps each call. We found no free Jev tier.", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the source or README (checked 2026-10-15). Jev is paid through a TypeSafe account and key.", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": 60, "npmWeekly": null, "pypiWeekly": 204, "asOf": "2026-10-15" }, "docsUrl": "https://github.com/RayenMlayeh/jevcrawl#readme", "capabilities": [ "web.crawl", "web.extract", "web.scrape", "scraping.js-render" ], "tags": [ "open-source", "local", "apache-2.0", "python", "mcp", "cli", "agent-skill", "usage-priced", "alpha" ], "lastRelease": "2026-10-15", "graded": true, "anchor": { "graded": true, "score": 64.3, "grade": "B", "agentReady": false, "rank": 400, "ranked": true, "rankOf": 1268, "categoryRank": 9, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 68, "payments": 30, "reliability": 68, "schema": 81, "security": 59, "transparency": 51 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "Three compact, typed MCP tools return verbatim passages with source URLs, cost and stop reasons, and errors arrive as codes with instructions. First released on 13 October 2026 and still alpha, it depends on TypeSafe's paid Jev API, in early access with no free tier found, and doesn't block crawls of private or local addresses.", "bestFor": "An agent that must find one answer several clicks deep on a documentation or help site and wants a few thousand tokens back instead of whole pages.", "strengths": [ "Three tools with typed inputs, sensible defaults and descriptions that say when to use `crawl`, `scrape` or `map`", "Every result reports pages fetched, tokens, Jev cost in dollars and why the crawl stopped, with a hard per-call spending cap", "Returned text is copied from the page with URL, heading path, character offsets and a page hash, so quotes can be checked", "174 offline tests, ruff and mypy strict pass in CI on Python 3.11 and 3.13, with PyPI trusted publishing", "Follows robots.txt by default since v0.1.1, and SECURITY.md sets out private reporting with a one-week answer" ], "weaknesses": [ "First released on 13 October 2026, version 0.2.0 and marked alpha, with one maintainer", "`crawl` and `map` need a paid TypeSafe key, and TypeSafe describes Jev as early access with no free tier found", "Page text from every crawl goes to TypeSafe, whose policies give no retention period", "No check against private, loopback or link-local addresses, so an agent can point it at internal hosts", "No MCP tool annotations, no llms.txt and no entry in the official MCP registry" ], "agentNotes": [ "Phrase `goal` as one specific question and start with `max_pages` between 10 and 30", "Check `stats.stopped_because` and `stats.degraded`, and read `uncertain` before reporting that something is missing", "Use `scrape` without a goal when you need a whole page, since it makes no paid Jev call and needs no key", "Handle `{\"error\": code, \"message\": ...}` results, for example `auth_error` means `TYPESAFE_API_KEY` is missing or rejected", "Pages in `stats.needs_js_urls` were not read. Tell the user rather than guessing their content" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 4, "avgRating": 3.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": 64.3 } ], "editorialScores": { "ergonomics": 80, "maintenance": 68, "payments": 30, "reliability": 68, "schema": 81, "security": 59, "transparency": 63 }, "provenanceScore": 39, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-10-27", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "uv tool install jevcrawl", "claudeCode": "claude mcp add jevcrawl -e TYPESAFE_API_KEY=\u003cyour key\u003e -- uvx jevcrawl", "config": { "mcpServers": { "jevcrawl": { "args": [ "jevcrawl" ], "command": "uvx", "env": { "TYPESAFE_API_KEY": "\u003cyour key\u003e" } } } } }, "letme": { "capability": "https://letme.dev/web.crawl", "tool": "https://letme.dev/jevcrawl" }, "area": "web-data", "unitPrices": [ { "item": "Jev 1.13 input tokens, billed by TypeSafe", "unit": "1m-tokens", "usd": 0.042, "note": "Output tokens free. The package itself is free" } ], "provenance": { "legalEntity": "", "domain": "github.com/RayenMlayeh", "domainRegistered": "", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/RayenMlayeh/jevcrawl/releases", "securityTxt": "none", "checked": "2026-10-15", "notes": [ "An individual's open-source project under Apache-2.0. pyproject.toml names Rayen Mlayeh as author, and the GitHub profile names no company or website.", "No vendor domain. The domain line names the GitHub account and scores no domain age.", "Software the owner runs, so there are no service terms or privacy policy of its own. Page text goes to TypeSafe AI, Inc. under TypeSafe's customer agreement and privacy policy (see the typesafe-jev listing).", "The repository has a SECURITY.md that points to GitHub private vulnerability reporting. No website, so no security.txt.", "The changelog is the GitHub release notes. v0.1.0's notes are only a link to the commit list." ], "score": 39 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/jevcrawl.json", "live": { "slug": "jevcrawl", "versions": [ { "registry": "github", "name": "RayenMlayeh/jevcrawl", "version": "v0.2.0", "released": "2026-10-15", "seenAt": "2026-11-02T19:25:27.192703346Z" }, { "registry": "pypi", "name": "jevcrawl", "version": "0.2.0", "released": "2026-10-15", "seenAt": "2026-11-02T19:25:27.010501024Z" } ], "githubStars": 82, "pypiWeekly": 33, "domain": { "domain": "github.com/rayenmlayeh", "checkedAt": "2026-11-01T14:18:16.13019571Z" }, "github": { "repo": "rayenmlayeh/jevcrawl", "checkedAt": "2026-11-02T09:20:18.237098368Z", "stars": 82, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-26T03:04:11Z", "openIssues": 6, "openPRs": 1, "issuesOpened90d": 8, "issuesClosed90d": 2, "prsMerged90d": 1, "ci": { "branch": "main", "runs": 15, "success": 15, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-26T03:04:40Z" }, "replies": { "sampled": 8, "unanswered": 6, "medianDays": 1.8 } }, "updatedAt": "2026-11-02T19:25:27.192703346Z" } }, "answer": "jevcrawl scores 64.3 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "qovia", "name": "Qovia", "vendor": "Qovia", "vendorUrl": "https://qovia.ai", "kind": "http-api", "category": "web-scrapers", "summary": "Qovia is a hosted API that returns posts, comments, creator profiles, hot lists and product reviews from Douyin, Xiaohongshu, Weibo, Bilibili, TikTok, YouTube, X and other platforms as one JSON envelope, with a cross-platform search and a remote MCP server.", "url": "https://www.anchorterminal.com/tools/qovia", "markdownUrl": "https://www.anchorterminal.com/tools/qovia.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/qovia.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/qovia.json", "dns": "qovia.grade.anchorterminal.com", "repo": "https://github.com/qovia/qovia-mcp", "license": "Proprietary hosted service under a one-paragraph Terms of Service summary that defers to a signed agreement. The qovia/qovia-mcp repository (setup guide, examples, Python client) and the qovia package on PyPI are MIT; the service's source is not public", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.qovia.ai", "packages": [ { "registry": "pypi", "name": "qovia" } ], "auth": "api-key", "authNotes": "An API key created in the console (prefix `sk-qovia-` plus 43 characters), sent as `Authorization: Bearer` or `x-api-key` to https://api.qovia.ai; the docs say the key is read from those two headers only, never from the URL or a cookie, and browser requests from other sites are refused by CORS. A key carries one or more scopes chosen at creation (`*`, `search`, `raw:*` or `raw:\u003cplatform\u003e` for each of 24 platform groups), an optional expiry, and is revoked in the console; the server stores a hash and shows the full key once. 30 failed authentications from one IP in a minute answer 429 `too_many_auth_failures`. The MCP server at https://api.qovia.ai/mcp takes the same key as a Bearer header; its `search_endpoints` and `get_endpoint` tools need no key, `call_endpoint` and `get_account` do. No OAuth metadata is served (404 on /.well-known/oauth-protected-resource per the 1 November listing check).", "pricing": "usage", "pricingNotes": "50 trial calls for a new account, counted only when a call returns data, then a prepaid balance in USD topped up by card or Alipay through Stripe (4.4 per cent plus $0.30 fee) or USDT on TRC-20 (2 per cent plus $0.30), no monthly fee (1 November 2026). Only an HTTP 200 with a non-empty result is charged; empty results, errors, timeouts and upstream failures are refunded. Cross-platform search is $5 per 1,000 calls. Raw endpoints are priced per endpoint, from $0.5 per 1,000 (8 Douyin, 5 Bilibili and 2 Xingtu endpoints) through $1 (61 endpoints), $1.5 (Cili Juxing, Huahuo), $2 (3 Instagram), $5 (WeChat, Xiaohongshu, 1 Pugongying), $10 (11 Xingtu, 10 Pugongying), $13.5 (Taobao reviews) to $19.5 (JD.com reviews); Tieba, Fliggy and the six coming-soon endpoints are on a tiered $1.5 rate that drops to $1 after 5,000,000 billed calls in a month. Top-ups are non-refundable except within 7 days when the vendor confirms a paid endpoint cannot be used. Datasets and bulk or custom data are quoted. Five Actors by the same vendor on the Apify Store are paid through Apify per section.", "priceSummary": "$5 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on qovia.ai, in the docs, llms.txt, the OpenAPI file or the repository (checked 2026-11-01). Top-ups take card and Alipay through Stripe or USDT on TRC-20 from a console session; USDT is a payment method, not a machine payment protocol. The only route without a Qovia account is the vendor's five Actors on the Apify Store (profile `qovia`, Qovia Data), paid through Apify.", "endpoints": [] }, "toolCount": 141, "popularity": { "githubStars": 0, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-01" }, "docsUrl": "https://qovia.ai/docs/", "llmsTxt": "https://qovia.ai/llms.txt", "openapi": "https://qovia.ai/openapi.json", "registryName": "ai.qovia/qovia", "capabilities": [ "web.extract", "social.analytics", "web.search" ], "tags": [ "hosted", "official", "closed-source", "openapi", "llms-txt", "mcp", "python", "free-trial", "prepaid", "usage-priced", "api-key", "beta", "new" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 61.2, "grade": "C", "agentReady": false, "rank": 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" } }, "edges": [ { "by": 28, "category": "reliability", "leads": "jevcrawl", "name": "Reliability", "reasons": { "a": "Read as local software, though `crawl` and `map` also depend on TypeSafe's hosted Jev API. Installs from PyPI with Python 3.11 or later stated (20). CI runs ruff, mypy strict and the offline tests on Python 3.11 and 3.13, and every CI run on main from 11 to 15 October 2026 passed, per the 15 October check; the workflow is unchanged, and run results couldn't be read on 2 November (25). Eight issues, all opened by the maintainer as a roadmap, two closed, per the 15 October check. No outside bug reports were found then, and the project is three weeks old, so there is little record to read (15). Semver tags with GitHub release notes, no CHANGELOG file, v0.1.0's notes only a commit link, and breaking changes not marked (8). Version 0.2.0, still classified Development Status 3 Alpha (0). 20 + 25 + 15 + 8 + 0 = 68.", "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": 68, "b": 40 } }, { "by": 25, "category": "payments", "leads": "qovia", "name": "Payments \u0026 pricing", "reasons": { "a": "No payment protocol (0). The package is free, so read with the rule for the paid option it needs, TypeSafe's Jev. Per-token price published at $0.042 per million input tokens for jev-1.13.0 and jev-1.14.0, re-read on 2 November (20). No free Jev tier found. `scrape` without a goal works with no key, which is a small free path (5 of 20). A person has to sign in at console.typesafe.ai, and TypeSafe describes Jev as early access. The console answered 403 to our reader. Keyless goal-less scraping earns a little (5 of 20).", "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": 30, "b": 55 } }, { "by": 21, "category": "transparency", "leads": "jevcrawl", "name": "Transparency \u0026 trust", "reasons": { "a": "Apache-2.0 in LICENSE, pyproject.toml and as detected by GitHub (30). The README says plainly that page text, link labels and URLs go to TypeSafe and that answers are cached locally. TypeSafe's policies agree on no training but give no retention period, and jevcrawl has no privacy statement of its own (15). No deprecation policy. The model version is pinned and changes are in release notes (3). No telemetry or analytics found in the source. Outbound traffic is the target site and api.typesafe.ai, both stated in the README, so there is nothing hidden to opt out of, though no explicit telemetry statement exists (15).", "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": 51, "b": 30 } }, { "by": 9, "category": "maintenance", "leads": "qovia", "name": "Maintenance \u0026 community", "reasons": { "a": "v0.2.0 on 15 October 2026, 18 days before 2 November (30). Three releases between 13 and 15 October 2026 (20). One later change, the merged audit-fixes pull request of 26 October (redirect scope, per-step time limits, a 50 MB cap on gzip sitemaps), is in no release yet. No outside issues or pull requests were found on 15 October, and GitHub's issue pages couldn't be read on 2 November (8 of 25). Not in the official MCP registry, which returned no server for jevcrawl on 2 November (0). Current dependencies, a uv.lock, CI and PyPI trusted publishing in the workflows (10). 30 + 20 + 8 + 0 + 10 = 68.", "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": 68, "b": 77 } }, { "by": 5, "category": "schema", "leads": "qovia", "name": "Schema \u0026 documentation", "reasons": { "a": "Typed JSON Schema inputs on all three tools, generated from the Python signatures, with required parameters marked (25). No llms.txt. The repository ships an agent skill, `skills/jevcrawl/SKILL.md`, as Markdown for agents (5). Tool descriptions and server instructions say when to use `crawl`, `scrape` and `map`, how to phrase a goal and how to read each stop reason (18). Integer and number types with defaults, but the minimums the code enforces are not in the schema and `stopped_because` is documented as prose, not an enum (10). A real result in the README, and error codes listed in the skill with what each means (13). Semver releases with notes, and the Jev model version pinned per release (10).", "b": "An OpenAPI 3.1.0 file (version 0.1.0, 1 MB) is public at qovia.ai/openapi.json with 144 paths and 144 operations, two security schemes, typed query parameters, a response example on every operation and the error responses declared on each. The data payload itself is typed only as object, array or null with per-endpoint examples, and the MCP call_endpoint tool takes a free params object, so 22 of 25 (22). llms.txt (75 KB, one line per endpoint with price and status) and llms-full.txt (331 KB, the whole documentation as text) are served, and the quickstart's billing, limits and error sections are in both (10). Every operation has a summary and a description; most say what the data holds, how to page, which ids to pass, which fields are unavailable and what answers 404 or empty, and the MCP server's instructions say to find, read then call. Guidance on when not to use an endpoint is thin, mostly pointers such as replies coming from another endpoint (16 of 20). 321 parameters, 75 with enums, patterns on ids, min and max on strings and integers, 117 operations with one required parameter and 16 with none, the POST body typed with additionalProperties false, and unknown parameters rejected with 400 (14 of 15). A response example on all 144 operations, 20 error codes with every message variant listed, response headers documented per error, and cURL, Python, JavaScript and raw HTTP samples; the examples are catalogue samples the docs say are not live data (14 of 15). Paths are under /v1, a 410 endpoint_disabled code exists for retired endpoints, and the changelog is dated, but it has two days (21 and 22 October 2026), nothing is marked deprecated and no notice period is stated (10 of 15). 22+10+16+14+14+10 = 86." }, "scores": { "a": 81, "b": 86 } } ], "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Rayen Mlayeh", "b": "Qovia", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.qovia.ai", "name": "Hosted endpoint" }, { "a": "stdio", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.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": "3", "b": "141", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "ai.qovia/qovia", "name": "MCP registry" }, { "a": "2026-10-15", "b": "2026-10-28", "name": "Last release" }, { "a": "no document linked", "b": "not read yet", "name": "Terms last updated" }, { "a": "no document linked", "b": "not read yet", "name": "Privacy policy last updated" }, { "a": "60 stars, 204 PyPI/wk", "b": "0 stars", "name": "Popularity" }, { "a": "3.3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "jevcrawl scores 64.3 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, jevcrawl or Qovia?" }, { "answer": "Both need an API key.", "question": "Do jevcrawl and Qovia need an API key?" }, { "answer": "jevcrawl runs on your own machine, with no hosted endpoint listed. Qovia has a hosted endpoint at https://api.qovia.ai.", "question": "Can an agent call jevcrawl and Qovia without installing anything?" }, { "answer": "jevcrawl is open source (Apache-2.0). No open-source release is listed for Qovia.", "question": "Are jevcrawl and Qovia open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 68 against 40", "Transparency \u0026 trust, 51 against 30" ], "also": [ "Runs on your own machine", "Open source" ], "goodFor": "An agent that must find one answer several clicks deep on a documentation or help site and wants a few thousand tokens back instead of whole pages.", "slug": "jevcrawl", "watchFor": "First released on 13 October 2026, version 0.2.0 and marked alpha, with one maintainer" }, { "aheadOn": [ "Schema \u0026 documentation, 86 against 81", "Payments \u0026 pricing, 55 against 30", "Maintenance \u0026 community, 77 against 68" ], "also": [ "A hosted endpoint, with nothing to install" ], "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": { "jevcrawl": [ { "causes": [ "evidence" ], "date": "2026-10-27", "delta": 0.6, "from": 63.7, "fromGrade": "B", "to": 64.3, "toGrade": "B" } ], "qovia": null }, "job": { "capability": "web.extract", "name": "Extraction" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bright-data-vs-jevcrawl.json", "title": "Bright Data vs jevcrawl", "url": "https://www.anchorterminal.com/compare/bright-data-vs-jevcrawl" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-jevcrawl.json", "title": "Context.dev vs jevcrawl", "url": "https://www.anchorterminal.com/compare/context-dev-vs-jevcrawl" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-jina-reader.json", "title": "jevcrawl vs Jina Reader", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-jina-reader" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-oxylabs-web-scraper.json", "title": "jevcrawl vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrape-do.json", "title": "jevcrawl vs Scrape.do", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrape-do" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingant.json", "title": "jevcrawl vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingbee.json", "title": "jevcrawl vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingdog.json", "title": "jevcrawl vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-zenrows.json", "title": "jevcrawl vs ZenRows", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-zyte.json", "title": "jevcrawl vs Zyte API", "url": "https://www.anchorterminal.com/compare/jevcrawl-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/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-jevcrawl.json", "title": "Diffbot vs jevcrawl", "url": "https://www.anchorterminal.com/compare/diffbot-vs-jevcrawl" }, { "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-scrapeatlas.json", "title": "jevcrawl vs ScrapeAtlas", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapeatlas" }, { "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-scraperapi.json", "title": "Qovia vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/qovia-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise.json", "title": "Qovia vs Scrapewise", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapfly.json", "title": "Qovia vs Scrapfly", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant.json", "title": "Qovia vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.json", "title": "Qovia vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.json", "title": "Qovia vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.json", "title": "Qovia vs Spider", "url": "https://www.anchorterminal.com/compare/qovia-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-zenrows.json", "title": "Qovia vs ZenRows", "url": "https://www.anchorterminal.com/compare/qovia-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-zyte.json", "title": "Qovia vs Zyte API", "url": "https://www.anchorterminal.com/compare/qovia-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-jevcrawl.json", "title": "Apify MCP Server vs jevcrawl", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-jevcrawl" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-jevcrawl.json", "title": "Firecrawl MCP vs jevcrawl", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-jevcrawl" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-olostep.json", "title": "jevcrawl vs Olostep", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-olostep" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-outcrawl.json", "title": "jevcrawl vs Outcrawl", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-outcrawl" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapegraphai.json", "title": "jevcrawl vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapeless.json", "title": "jevcrawl vs Scrapeless", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapeless" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scraperapi.json", "title": "jevcrawl vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapewise.json", "title": "jevcrawl vs Scrapewise", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapfly.json", "title": "jevcrawl vs Scrapfly", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-spider-cloud.json", "title": "jevcrawl vs Spider", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-spider-cloud" } ], "panel": null, "scores": [ { "by": 28, "edge": "jevcrawl", "jevcrawl": 68, "key": "reliability", "name": "Reliability", "qovia": 40, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "edge": "qovia", "jevcrawl": 81, "key": "schema", "name": "Schema \u0026 documentation", "qovia": 86, "weight": 13 }, { "by": 3, "edge": "jevcrawl", "jevcrawl": 80, "key": "ergonomics", "name": "Agent ergonomics", "qovia": 77, "weight": 13 }, { "by": 1, "edge": "qovia", "jevcrawl": 59, "key": "security", "name": "Security \u0026 auth", "qovia": 60, "weight": 14 }, { "by": 25, "edge": "qovia", "jevcrawl": 30, "key": "payments", "name": "Payments \u0026 pricing", "qovia": 55, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 9, "edge": "qovia", "jevcrawl": 68, "key": "maintenance", "name": "Maintenance \u0026 community", "qovia": 77, "weight": 7 }, { "by": 21, "edge": "jevcrawl", "jevcrawl": 51, "key": "transparency", "name": "Transparency \u0026 trust", "qovia": 30, "weight": 7 } ], "summary": "jevcrawl scores 64.3 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community. Both do extraction.", "tasks": null, "tutorials": [], "verdicts": { "jevcrawl": "Three compact, typed MCP tools return verbatim passages with source URLs, cost and stop reasons, and errors arrive as codes with instructions. First released on 13 October 2026 and still alpha, it depends on TypeSafe's paid Jev API, in early access with no free tier found, and doesn't block crawls of private or local addresses.", "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/jevcrawl-vs-qovia", "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.min.md" }, "markdown": "jevcrawl scores 64.3 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community. Both do extraction.\n\n- jevcrawl: grade B, 64.3/100, rank #400 of 1268. Markdown https://www.anchorterminal.com/tools/jevcrawl.md · JSON https://www.anchorterminal.com/api/v1/tools/jevcrawl.json\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- 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### jevcrawl (B)\n\nGood for: An agent that must find one answer several clicks deep on a documentation or help site and wants a few thousand tokens back instead of whole pages.\n\nAhead on:\n- Reliability, 68 against 40\n- Transparency \u0026 trust, 51 against 30\n\nAlso in its favour:\n- Runs on your own machine\n- Open source\n\nWatch for: First released on 13 October 2026, version 0.2.0 and marked alpha, with one maintainer\n\n### Qovia (C)\n\nGood for: Agents that need structured public data from Chinese platforms (Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Zhihu, WeChat official accounts, Taobao and JD reviews) or the Xingtu and Pugongying creator marketplaces, with TikTok, YouTube, Instagram, X and Reddit beside them, paid per successful call from a prepaid balance.\n\nAhead on:\n- Schema \u0026 documentation, 86 against 81\n- Payments \u0026 pricing, 55 against 30\n- Maintenance \u0026 community, 77 against 68\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No status page, incident history or SLA; the terms promise nothing about uptime and the Python client is the only retry guidance beyond `Retry-After`\n\n\n## Why the edge\n\n### Reliability: jevcrawl +28\n\n- jevcrawl (68): Read as local software, though `crawl` and `map` also depend on TypeSafe's hosted Jev API. Installs from PyPI with Python 3.11 or later stated (20). CI runs ruff, mypy strict and the offline tests on Python 3.11 and 3.13, and every CI run on main from 11 to 15 October 2026 passed, per the 15 October check; the workflow is unchanged, and run results couldn't be read on 2 November (25). Eight issues, all opened by the maintainer as a roadmap, two closed, per the 15 October check. No outside bug reports were found then, and the project is three weeks old, so there is little record to read (15). Semver tags with GitHub release notes, no CHANGELOG file, v0.1.0's notes only a commit link, and breaking changes not marked (8). Version 0.2.0, still classified Development Status 3 Alpha (0). 20 + 25 + 15 + 8 + 0 = 68.\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### Payments \u0026 pricing: Qovia +25\n\n- jevcrawl (30): No payment protocol (0). The package is free, so read with the rule for the paid option it needs, TypeSafe's Jev. Per-token price published at $0.042 per million input tokens for jev-1.13.0 and jev-1.14.0, re-read on 2 November (20). No free Jev tier found. `scrape` without a goal works with no key, which is a small free path (5 of 20). A person has to sign in at console.typesafe.ai, and TypeSafe describes Jev as early access. The console answered 403 to our reader. Keyless goal-less scraping earns a little (5 of 20).\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### Transparency \u0026 trust: jevcrawl +21\n\n- jevcrawl (51): Apache-2.0 in LICENSE, pyproject.toml and as detected by GitHub (30). The README says plainly that page text, link labels and URLs go to TypeSafe and that answers are cached locally. TypeSafe's policies agree on no training but give no retention period, and jevcrawl has no privacy statement of its own (15). No deprecation policy. The model version is pinned and changes are in release notes (3). No telemetry or analytics found in the source. Outbound traffic is the target site and api.typesafe.ai, both stated in the README, so there is nothing hidden to opt out of, though no explicit telemetry statement exists (15).\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### Maintenance \u0026 community: Qovia +9\n\n- jevcrawl (68): v0.2.0 on 15 October 2026, 18 days before 2 November (30). Three releases between 13 and 15 October 2026 (20). One later change, the merged audit-fixes pull request of 26 October (redirect scope, per-step time limits, a 50 MB cap on gzip sitemaps), is in no release yet. No outside issues or pull requests were found on 15 October, and GitHub's issue pages couldn't be read on 2 November (8 of 25). Not in the official MCP registry, which returned no server for jevcrawl on 2 November (0). Current dependencies, a uv.lock, CI and PyPI trusted publishing in the workflows (10). 30 + 20 + 8 + 0 + 10 = 68.\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### Schema \u0026 documentation: Qovia +5\n\n- jevcrawl (81): Typed JSON Schema inputs on all three tools, generated from the Python signatures, with required parameters marked (25). No llms.txt. The repository ships an agent skill, `skills/jevcrawl/SKILL.md`, as Markdown for agents (5). Tool descriptions and server instructions say when to use `crawl`, `scrape` and `map`, how to phrase a goal and how to read each stop reason (18). Integer and number types with defaults, but the minimums the code enforces are not in the schema and `stopped_because` is documented as prose, not an enum (10). A real result in the README, and error codes listed in the skill with what each means (13). Semver releases with notes, and the Jev model version pinned per release (10).\n- Qovia (86): An OpenAPI 3.1.0 file (version 0.1.0, 1 MB) is public at qovia.ai/openapi.json with 144 paths and 144 operations, two security schemes, typed query parameters, a response example on every operation and the error responses declared on each. The data payload itself is typed only as object, array or null with per-endpoint examples, and the MCP call_endpoint tool takes a free params object, so 22 of 25 (22). llms.txt (75 KB, one line per endpoint with price and status) and llms-full.txt (331 KB, the whole documentation as text) are served, and the quickstart's billing, limits and error sections are in both (10). Every operation has a summary and a description; most say what the data holds, how to page, which ids to pass, which fields are unavailable and what answers 404 or empty, and the MCP server's instructions say to find, read then call. Guidance on when not to use an endpoint is thin, mostly pointers such as replies coming from another endpoint (16 of 20). 321 parameters, 75 with enums, patterns on ids, min and max on strings and integers, 117 operations with one required parameter and 16 with none, the POST body typed with additionalProperties false, and unknown parameters rejected with 400 (14 of 15). A response example on all 144 operations, 20 error codes with every message variant listed, response headers documented per error, and cURL, Python, JavaScript and raw HTTP samples; the examples are catalogue samples the docs say are not live data (14 of 15). Paths are under /v1, a 410 endpoint_disabled code exists for retired endpoints, and the changelog is dated, but it has two days (21 and 22 October 2026), nothing is marked deprecated and no notice period is stated (10 of 15). 22+10+16+14+14+10 = 86.\n\n## Score by category\n\n| Category | Weight | jevcrawl | Qovia | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 68 | 40 | jevcrawl +28 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 81 | 86 | Qovia +5 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 77 | jevcrawl +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 59 | 60 | Qovia +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 55 | Qovia +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 68 | 77 | Qovia +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 51 | 30 | jevcrawl +21 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **64.3 · B** | **61.2 · C** | |\n\n## Facts side by side\n\n| Fact | jevcrawl | Qovia |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Rayen Mlayeh | Qovia |\n| Hosted endpoint | no (local only) | `https://api.qovia.ai` |\n| Transports | stdio | HTTP, Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Apache-2.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 | 3 | 141 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `ai.qovia/qovia` |\n| Last release | 2026-10-15 | 2026-10-28 |\n| Terms last updated | no document linked | not read yet |\n| Privacy policy last updated | no document linked | not read yet |\n| Popularity | 60 stars, 204 PyPI/wk | 0 stars |\n| Agent reviews | 3.3/5 (4) | none |\n\n## How the scores have moved\n\n### jevcrawl\n\n- +0.6 on 27 October 2026: new evidence\n\n### Qovia\n\nNo score change since it was listed.\n\n## Verdicts\n\n**jevcrawl.** Three compact, typed MCP tools return verbatim passages with source URLs, cost and stop reasons, and errors arrive as codes with instructions. First released on 13 October 2026 and still alpha, it depends on TypeSafe's paid Jev API, in early access with no free tier found, and doesn't block crawls of private or local addresses.\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### jevcrawl\n\n1. Phrase `goal` as one specific question and start with `max_pages` between 10 and 30\n2. Check `stats.stopped_because` and `stats.degraded`, and read `uncertain` before reporting that something is missing\n3. Use `scrape` without a goal when you need a whole page, since it makes no paid Jev call and needs no key\n4. Handle `{\"error\": code, \"message\": ...}` results, for example `auth_error` means `TYPESAFE_API_KEY` is missing or rejected\n5. Pages in `stats.needs_js_urls` were not read. Tell the user rather than guessing their content\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, jevcrawl or Qovia?\n\njevcrawl scores 64.3 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do jevcrawl and Qovia need an API key?\n\nBoth need an API key.\n\n### Can an agent call jevcrawl and Qovia without installing anything?\n\njevcrawl runs on your own machine, with no hosted endpoint listed. Qovia has a hosted endpoint at https://api.qovia.ai.\n\n### Are jevcrawl and Qovia open source?\n\njevcrawl is open source (Apache-2.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/jevcrawl-vs-qovia.json, and with the fewest tokens: https://www.anchorterminal.com/compare/jevcrawl-vs-qovia.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"jevcrawl\", \"b\": \"qovia\"}`. From a terminal: `anchor compare jevcrawl qovia`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/jevcrawl.json and https://www.anchorterminal.com/api/v1/tools/qovia.json\n\n## Other comparisons with jevcrawl or Qovia\n\n- [Bright Data vs jevcrawl](https://www.anchorterminal.com/compare/bright-data-vs-jevcrawl.md)\n- [Context.dev vs jevcrawl](https://www.anchorterminal.com/compare/context-dev-vs-jevcrawl.md)\n- [jevcrawl vs Jina Reader](https://www.anchorterminal.com/compare/jevcrawl-vs-jina-reader.md)\n- [jevcrawl vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/jevcrawl-vs-oxylabs-web-scraper.md)\n- [jevcrawl vs Scrape.do](https://www.anchorterminal.com/compare/jevcrawl-vs-scrape-do.md)\n- [jevcrawl vs ScrapingAnt](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingant.md)\n- [jevcrawl vs ScrapingBee](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingbee.md)\n- [jevcrawl vs Scrapingdog](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapingdog.md)\n- [jevcrawl vs ZenRows](https://www.anchorterminal.com/compare/jevcrawl-vs-zenrows.md)\n- [jevcrawl vs Zyte API](https://www.anchorterminal.com/compare/jevcrawl-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- [Context.dev vs Qovia](https://www.anchorterminal.com/compare/context-dev-vs-qovia.md)\n- [Diffbot vs jevcrawl](https://www.anchorterminal.com/compare/diffbot-vs-jevcrawl.md)\n- [Diffbot vs Qovia](https://www.anchorterminal.com/compare/diffbot-vs-qovia.md)\n- [jevcrawl vs ScrapeAtlas](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapeatlas.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 ScraperAPI](https://www.anchorterminal.com/compare/qovia-vs-scraperapi.md)\n- [Qovia vs Scrapewise](https://www.anchorterminal.com/compare/qovia-vs-scrapewise.md)\n- [Qovia vs Scrapfly](https://www.anchorterminal.com/compare/qovia-vs-scrapfly.md)\n- [Qovia vs ScrapingAnt](https://www.anchorterminal.com/compare/qovia-vs-scrapingant.md)\n- [Qovia vs ScrapingBee](https://www.anchorterminal.com/compare/qovia-vs-scrapingbee.md)\n- [Qovia vs Scrapingdog](https://www.anchorterminal.com/compare/qovia-vs-scrapingdog.md)\n- [Qovia vs Spider](https://www.anchorterminal.com/compare/qovia-vs-spider-cloud.md)\n- [Qovia vs ZenRows](https://www.anchorterminal.com/compare/qovia-vs-zenrows.md)\n- [Qovia vs Zyte API](https://www.anchorterminal.com/compare/qovia-vs-zyte.md)\n- [Apify MCP Server vs jevcrawl](https://www.anchorterminal.com/compare/apify-mcp-vs-jevcrawl.md)\n- [Firecrawl MCP vs jevcrawl](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-jevcrawl.md)\n- [jevcrawl vs Olostep](https://www.anchorterminal.com/compare/jevcrawl-vs-olostep.md)\n- [jevcrawl vs Outcrawl](https://www.anchorterminal.com/compare/jevcrawl-vs-outcrawl.md)\n- [jevcrawl vs ScrapeGraphAI](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapegraphai.md)\n- [jevcrawl vs Scrapeless](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapeless.md)\n- [jevcrawl vs ScraperAPI](https://www.anchorterminal.com/compare/jevcrawl-vs-scraperapi.md)\n- [jevcrawl vs Scrapewise](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapewise.md)\n- [jevcrawl vs Scrapfly](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapfly.md)\n- [jevcrawl vs Spider](https://www.anchorterminal.com/compare/jevcrawl-vs-spider-cloud.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-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": "jevcrawl vs Qovia", "url": "" } ], "description": "jevcrawl scores 64.3 (B) to Qovia's 61.2 (C) for extraction. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "jevcrawl B 64.3", "Qovia C 61.2", "scores" ], "h1": "jevcrawl vs Qovia", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/jevcrawl-vs-qovia", "published": "2026-10-01", "section": "tools", "title": "jevcrawl vs Qovia for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-02", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-qovia" }, "tokens": { "markdown": 5500, "slim": 3280 }, "version": 1 }