{
  "data": {
    "a": {
      "slug": "qovia",
      "name": "Qovia",
      "vendor": "Qovia",
      "vendorUrl": "https://qovia.ai",
      "kind": "http-api",
      "category": "web-scrapers",
      "summary": "Qovia is a hosted API that returns posts, comments, creator profiles, hot lists and product reviews from Douyin, Xiaohongshu, Weibo, Bilibili, TikTok, YouTube, X and other platforms as one JSON envelope, with a cross-platform search and a remote MCP server.",
      "url": "https://www.anchorterminal.com/tools/qovia",
      "markdownUrl": "https://www.anchorterminal.com/tools/qovia.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/qovia.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/qovia.json",
      "dns": "qovia.grade.anchorterminal.com",
      "repo": "https://github.com/qovia/qovia-mcp",
      "license": "Proprietary hosted service under a one-paragraph Terms of Service summary that defers to a signed agreement. The qovia/qovia-mcp repository (setup guide, examples, Python client) and the qovia package on PyPI are MIT; the service's source is not public",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.qovia.ai",
      "packages": [
        {
          "registry": "pypi",
          "name": "qovia"
        }
      ],
      "auth": "api-key",
      "authNotes": "An API key created in the console (prefix `sk-qovia-` plus 43 characters), sent as `Authorization: Bearer` or `x-api-key` to https://api.qovia.ai; the docs say the key is read from those two headers only, never from the URL or a cookie, and browser requests from other sites are refused by CORS. A key carries one or more scopes chosen at creation (`*`, `search`, `raw:*` or `raw:\u003cplatform\u003e` for each of 24 platform groups), an optional expiry, and is revoked in the console; the server stores a hash and shows the full key once. 30 failed authentications from one IP in a minute answer 429 `too_many_auth_failures`. The MCP server at https://api.qovia.ai/mcp takes the same key as a Bearer header; its `search_endpoints` and `get_endpoint` tools need no key, `call_endpoint` and `get_account` do. No OAuth metadata is served (404 on /.well-known/oauth-protected-resource per the 1 November listing check).",
      "pricing": "usage",
      "pricingNotes": "50 trial calls for a new account, counted only when a call returns data, then a prepaid balance in USD topped up by card or Alipay through Stripe (4.4 per cent plus $0.30 fee) or USDT on TRC-20 (2 per cent plus $0.30), no monthly fee (1 November 2026). Only an HTTP 200 with a non-empty result is charged; empty results, errors, timeouts and upstream failures are refunded. Cross-platform search is $5 per 1,000 calls. Raw endpoints are priced per endpoint, from $0.5 per 1,000 (8 Douyin, 5 Bilibili and 2 Xingtu endpoints) through $1 (61 endpoints), $1.5 (Cili Juxing, Huahuo), $2 (3 Instagram), $5 (WeChat, Xiaohongshu, 1 Pugongying), $10 (11 Xingtu, 10 Pugongying), $13.5 (Taobao reviews) to $19.5 (JD.com reviews); Tieba, Fliggy and the six coming-soon endpoints are on a tiered $1.5 rate that drops to $1 after 5,000,000 billed calls in a month. Top-ups are non-refundable except within 7 days when the vendor confirms a paid endpoint cannot be used. Datasets and bulk or custom data are quoted. Five Actors by the same vendor on the Apify Store are paid through Apify per section.",
      "priceSummary": "$5 / 1k req",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on qovia.ai, in the docs, llms.txt, the OpenAPI file or the repository (checked 2026-11-01). Top-ups take card and Alipay through Stripe or USDT on TRC-20 from a console session; USDT is a payment method, not a machine payment protocol. The only route without a Qovia account is the vendor's five Actors on the Apify Store (profile `qovia`, Qovia Data), paid through Apify.",
        "endpoints": []
      },
      "toolCount": 141,
      "popularity": {
        "githubStars": 0,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-01"
      },
      "docsUrl": "https://qovia.ai/docs/",
      "llmsTxt": "https://qovia.ai/llms.txt",
      "openapi": "https://qovia.ai/openapi.json",
      "registryName": "ai.qovia/qovia",
      "capabilities": [
        "web.extract",
        "social.analytics",
        "web.search"
      ],
      "tags": [
        "hosted",
        "official",
        "closed-source",
        "openapi",
        "llms-txt",
        "mcp",
        "python",
        "free-trial",
        "prepaid",
        "usage-priced",
        "api-key",
        "beta",
        "new"
      ],
      "lastRelease": "2026-10-28",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 61.2,
        "grade": "C",
        "agentReady": false,
        "rank": 558,
        "ranked": true,
        "rankOf": 1253,
        "categoryRank": 14,
        "methodology": "0.7",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 77,
          "maintenance": 77,
          "payments": 55,
          "reliability": 40,
          "schema": 86,
          "security": 60,
          "transparency": 30
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-01"
        },
        "negative": 0,
        "verdict": "An OpenAPI 3.1 file with 144 operations, one envelope and 20 error codes, per-endpoint prices with failed and empty calls refunded, scoped keys and a four-tool MCP server that keeps the catalogue out of context. No status page, no legal entity, one-paragraph terms and privacy pages, and a product ten days old at the check.",
        "bestFor": "Agents that need structured public data from Chinese platforms (Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Zhihu, WeChat official accounts, Taobao and JD reviews) or the Xingtu and Pugongying creator marketplaces, with TikTok, YouTube, Instagram, X and Reddit beside them, paid per successful call from a prepaid balance.",
        "strengths": [
          "A public OpenAPI 3.1 file with 144 operations, patterns or enums on parameters, a response example on every operation and the error responses declared on each",
          "One envelope on every call, `request_id`, `data` and `meta` with the charge and balance, and 20 error codes sorted into not charged and refunded, with `Retry-After` on the retryable ones",
          "Only HTTP 200 with a non-empty result is charged; empty results, 404s, timeouts and upstream failures are refunded, and 50 trial calls come with a new account",
          "API keys carry per-platform scopes and an optional expiry, are read from headers only, and the docs tell users to give AI tools a separate scoped key",
          "The MCP server loads four tools by default and lets an agent find, read and call any of 137 endpoints, with `?tools=` subsets for direct tools; listed in the official registry under ai.qovia/qovia",
          "Published limits of 60 and 600 requests a minute with `X-RateLimit-*` headers, and a documented empty-call throttle"
        ],
        "weaknesses": [
          "No status page, incident history or SLA; the terms promise nothing about uptime and the Python client is the only retry guidance beyond `Retry-After`",
          "The terms and privacy policy are one paragraph each, name no legal entity, address, retention period or subprocessor, and say a signed agreement governs",
          "Every endpoint is marked `beta` in the OpenAPI file while the docs call it Live, and the API version is 0.1.0",
          "No security.txt, disclosure policy beyond a SECURITY.md, bug bounty or certification; the only support channels are Telegram, WhatsApp, WeChat and one mailbox",
          "Every response is third-party platform content and the docs carry no guidance on treating it as untrusted; four endpoint groups read login-gated creator marketplaces",
          "The changelog has two dated days, the domain is four months old, and the GitHub account was created the week of the request with nine forked lists beside the one repository"
        ],
        "agentNotes": [
          "Send `Authorization: Bearer sk-qovia-...` to https://api.qovia.ai and check `meta.empty` on every HTTP 200; `data` may be `null` or an empty structure and nothing is charged for it.",
          "Branch on `error.code`, never on `message`. Retry only `rate_limited`, `too_many_unbilled`, `endpoint_busy`, `upstream_busy` and `too_many_auth_failures` after `Retry-After`; `endpoint_unavailable` has none and will not clear.",
          "Stay under 60 requests a minute (600 after the first top-up) across every key on the account, and keep empty or not-found calls under 80 per cent of the last 10 minutes or expect 429 `too_many_unbilled`.",
          "Pass the previous page's `cursor` (and `search_id` on Douyin and Zhihu search) back unchanged and stop when `has_more` is false; each page is a separate charge, and unknown parameters answer 400.",
          "For MCP, connect to https://api.qovia.ai/mcp over Streamable HTTP; call `search_endpoints` then `get_endpoint` before `call_endpoint`, or add `?tools=douyin,kuaishou` for typed direct tools. Catalogue tools need no key."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "0.7",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 61.2
          }
        ],
        "editorialScores": {
          "ergonomics": 77,
          "maintenance": 77,
          "payments": 55,
          "reliability": 40,
          "schema": 86,
          "security": 60,
          "transparency": 23
        },
        "provenanceScore": 36,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-01",
            "maintenance": "2026-11-01",
            "payments": "2026-11-01",
            "reliability": "2026-11-01",
            "schema": "2026-11-01",
            "security": "2026-11-01",
            "transparency": "2026-11-01"
          },
          "last": "2026-11-01",
          "oldest": "2026-11-01",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "pip install qovia",
        "http": "curl \"https://api.qovia.ai/v1/raw/weibo/hot_search\" -H \"Authorization: Bearer $QOVIA_API_KEY\"",
        "claudeCode": "claude mcp add --transport http qovia https://api.qovia.ai/mcp --header \"Authorization: Bearer $QOVIA_API_KEY\""
      },
      "letme": {
        "capability": "https://letme.dev/web.extract",
        "tool": "https://letme.dev/qovia"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Cross-platform search",
          "unit": "1k-requests",
          "usd": 5,
          "note": "POST /v1/search, successful non-empty calls only, pricing page and OpenAPI file checked 1 November 2026"
        },
        {
          "item": "Lowest raw endpoints (Douyin, Bilibili, Xingtu keywords)",
          "unit": "1k-requests",
          "usd": 0.5,
          "note": "15 fixed-price endpoints at $0.0005 a successful call"
        },
        {
          "item": "Most raw endpoints (TikTok, YouTube, X, Reddit, Weibo, Zhihu, Kuaishou and others)",
          "unit": "1k-requests",
          "usd": 1,
          "note": "61 fixed-price endpoints at $0.001 a successful call"
        },
        {
          "item": "Tiered raw endpoints (Tieba, Fliggy, coming-soon platforms)",
          "unit": "1k-requests",
          "usd": 1.5,
          "note": "$1 per 1,000 after 5,000,000 billed calls in a calendar month"
        },
        {
          "item": "Xiaohongshu and WeChat endpoints",
          "unit": "1k-requests",
          "usd": 5,
          "note": "11 fixed-price endpoints at $0.005 a successful call"
        },
        {
          "item": "Xingtu and Pugongying creator marketplace endpoints",
          "unit": "1k-requests",
          "usd": 10,
          "note": "21 fixed-price endpoints at $0.01 a successful call"
        },
        {
          "item": "JD.com product reviews",
          "unit": "1k-requests",
          "usd": 19.5,
          "note": "the dearest endpoint; Taobao and Tmall reviews are $13.5"
        },
        {
          "item": "Apify Store, Xingtu Actor premium section",
          "unit": "record",
          "usd": 0.06,
          "note": "per creator per section, paid through Apify with no Qovia account; basic sections $0.01, video sections $0.03"
        }
      ],
      "provenance": {
        "legalEntity": "",
        "domain": "qovia.ai",
        "domainRegistered": "2026-07-04",
        "endpointOnVendorDomain": true,
        "terms": "https://qovia.ai/terms/",
        "privacy": "https://qovia.ai/privacy/",
        "statusPage": "",
        "changelog": "https://qovia.ai/changelog/",
        "securityTxt": "none",
        "checked": "2026-11-01",
        "notes": [
          "No legal entity is named anywhere read. The terms and privacy pages are one paragraph each, say Delaware law governs and that the signed agreement governs where it differs, and name no company, address or jurisdiction beyond the state. The footer reads © 2026 QoviaAI, a brand name, not an entity, so legalEntity is left empty.",
          "RDAP for qovia.ai gives a registration date of 2026-07-04 through GoDaddy with a Domains By Proxy registrant and Cloudflare nameservers. The Wayback Machine's only capture before the check is the home page of 11 September 2026, which advertised sign-up with a free 1,000 calls a month, 25+ platforms, a 99.95 per cent enterprise SLA and a team@ mailbox; none of those claims is on the current site.",
          "firstReleased is the changelog's first dated entry, 21 October 2026, when the search, Xiaohongshu, WeChat, Taobao and JD endpoints are recorded as live; the remaining platforms are dated 22 October, the registry entry is 22 October and the GitHub account and repository were created on 23 October 2026. The 11 September page sold an API key but dates nothing live.",
          "https://qovia.ai/.well-known/security.txt, https://qovia.ai/security.txt and https://api.qovia.ai/.well-known/security.txt answer 404. The repository's SECURITY.md gives a Telegram handle and a mailbox for reports and says it covers qovia.ai and api.qovia.ai.",
          "api.qovia.ai has no robots.txt (404); only its OAuth metadata (404) and /mcp (405 on GET) were touched, both by the 1 November listing check. qovia.ai's robots.txt disallows /console/, /account/, /order/ and /admin/ and their /zh/ twins, which were not fetched."
        ],
        "score": 36
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/qovia.json",
      "live": {
        "slug": "qovia",
        "probe": {
          "target": "https://api.qovia.ai",
          "method": "get",
          "lastAt": "2026-11-01T22:08:43.664510387Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 491,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 521,
          "p95ms24h": 626,
          "samples24h": 25,
          "samples30d": 25,
          "days": [
            {
              "date": "2026-11-01",
              "probes": 25,
              "ok": 25
            }
          ]
        },
        "updatedAt": "2026-11-01T22:08:43.664510387Z"
      }
    },
    "answer": "ScrapeAtlas scores 62.8 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on security \u0026 auth and maintenance \u0026 community.",
    "b": {
      "slug": "scrapeatlas",
      "name": "ScrapeAtlas",
      "vendor": "OD. Media \u0026 Technology LLC",
      "vendorUrl": "https://scrapeatlas.com",
      "kind": "http-api",
      "category": "web-scrapers",
      "summary": "ScrapeAtlas is a hosted API that returns public profiles, posts, comments, videos, ads, products and market data from 49 social, video, forum, marketplace and prediction-market platforms as JSON, with a CLI, an n8n node and a hosted MCP server.",
      "url": "https://www.anchorterminal.com/tools/scrapeatlas",
      "markdownUrl": "https://www.anchorterminal.com/tools/scrapeatlas.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/scrapeatlas.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/scrapeatlas.json",
      "dns": "scrapeatlas.grade.anchorterminal.com",
      "license": "Proprietary service under ScrapeAtlas's Terms of Service. The @scrapeatlas/cli package on npm is MIT with no public source repository",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.scrapeatlas.com",
      "packages": [
        {
          "registry": "npm",
          "name": "@scrapeatlas/cli"
        },
        {
          "registry": "npm",
          "name": "n8n-nodes-scrapeatlas"
        }
      ],
      "auth": "mixed",
      "authNotes": "A customer API key (prefix `sa_live_`) created on the account page, sent as `x-api-key` or `Authorization: Bearer` to https://api.scrapeatlas.com. Several keys share one credit balance, keys carry an expiry date, and revocation takes effect within 60 seconds per the authentication page. No scopes or per-platform keys. The hosted MCP server at https://api.scrapeatlas.com/mcp takes the same key as a Bearer token, or an OAuth authorization-code flow with PKCE S256, dynamic client registration at /oauth/register and one scope, `scrapeatlas`; the MCP page calls OAuth-only connectors unsupported in the preview. Keys can't buy credits or manage the account, which need a dashboard session.",
      "pricing": "usage",
      "pricingNotes": "100 free credits at signup with no card, then one-time credit packs of 10,000 for $19 ($1.90 per 1,000), 50,000 for $89 ($1.78) and 200,000 for $249 ($1.25) on the home page (30 October 2026). One credit per successful request, partial results and valid empty collections included, 2 credits on LinkedIn post search, the six Quora search endpoints and Threads user search. Failed requests, account utilities and internal retries cost 0. Credits never expire, and there are no subscriptions. Eight Actors on the Apify Store cost $1.98 per 1,000 successful requests with no ScrapeAtlas account.",
      "priceSummary": "$1.90 / 1k req",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on scrapeatlas.com, in the docs, llms.txt or the OpenAPI file (checked 2026-10-30). Credit packs are bought through a hosted Stripe Checkout from a dashboard session. The only route without a ScrapeAtlas account is the vendor's eight Actors on the Apify Store, paid through Apify.",
        "endpoints": []
      },
      "toolCount": 373,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-30"
      },
      "docsUrl": "https://scrapeatlas.com/docs/",
      "llmsTxt": "https://scrapeatlas.com/docs/llms.txt",
      "openapi": "https://scrapeatlas.com/docs/openapi.json",
      "registryName": "io.github.OnlineDopamine/scrapeatlas",
      "capabilities": [
        "web.extract",
        "social.analytics",
        "data.markets"
      ],
      "tags": [
        "hosted",
        "official",
        "closed-source",
        "openapi",
        "llms-txt",
        "mcp",
        "cli",
        "free-tier",
        "no-card",
        "prepaid",
        "usage-priced",
        "new"
      ],
      "lastRelease": "2026-10-28",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.8,
        "grade": "B",
        "agentReady": false,
        "rank": 478,
        "ranked": true,
        "rankOf": 1253,
        "categoryRank": 12,
        "methodology": "0.7",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 76,
          "maintenance": 70,
          "payments": 55,
          "reliability": 42,
          "schema": 88,
          "security": 55,
          "transparency": 59
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-30"
        },
        "negative": 0,
        "verdict": "An OpenAPI 3.1 file with 386 operations, typed parameters and a uniform failure object, published limits of 120 requests a minute and 4 concurrent, and 1 credit per successful request with failed calls free. No status page, security.txt or SDKs, the MCP server is a preview with 373 tools, and the product is five weeks old.",
        "bestFor": "Agents that need structured public data from a named social, video, forum, marketplace or prediction-market platform, such as a creator's profile and recent posts, a thread's comments, a product's reviews or a market's order book, paid per successful request without a subscription.",
        "strengths": [
          "A public OpenAPI 3.1 file with 386 operations, enums or patterns on most parameters, a response example on 373 operations and error responses on every data endpoint",
          "One response envelope on every endpoint, with `status`, `coverage.warnings`, `requestId` and `accounting`, and 33 failure codes the docs sort into retryable and not",
          "Limits published as 120 requests a minute and 4 concurrent per account, with a `retry-after` on 429 and `x-credits-charged` and `x-credits-remaining` headers",
          "One credit per successful request, failed requests and internal retries free, 100 credits at signup without a card, and packs from $1.25 to $1.90 per 1,000",
          "Account usage and activity endpoints at 0 credits, with per-request metadata filterable by platform, operation and status"
        ],
        "weaknesses": [
          "No status page or incident history was found, and the terms promise no uptime, throughput or continued availability of an endpoint",
          "API keys have no scopes, and the MCP OAuth flow has a single scope, `scrapeatlas`",
          "No security.txt, disclosure policy, bug bounty or certification was found; keys are stored hashed per the privacy policy",
          "The MCP server is a preview that loads 373 tool definitions with no documented subset, and the registry entry under a personal GitHub namespace is at 1.0.0 from 5 October",
          "No official SDKs; the npm CLI has no public source repository, and support in the dashboard is for customers with a credit purchase",
          "Every response is third-party page content and the docs carry no guidance on treating it as untrusted"
        ],
        "agentNotes": [
          "Send the key as `x-api-key` on https://api.scrapeatlas.com and check `status` on every HTTP 200; `partial` is usable data with `coverage.warnings`, `failed` and `challenged` carry `failure.code`.",
          "Retry only on `upstream_rate_limited`, `timeout` and `busy`, after the `retry-after` on a 429. Stay under 120 requests a minute and 4 concurrent per account.",
          "Pass the returned `cursor` back unchanged for the next page, and use `since` and `until` (ISO 8601 or Unix seconds) where listed; each page costs another credit.",
          "Each platform has its own response schema, so read the endpoint's response fields before mapping; unknown values are `null`, never 0.",
          "For MCP, connect to https://api.scrapeatlas.com/mcp over Streamable HTTP with `Authorization: Bearer` and expect 373 tools; the two account tools and failed calls cost 0 credits."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.7",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.8
          }
        ],
        "editorialScores": {
          "ergonomics": 76,
          "maintenance": 70,
          "payments": 55,
          "reliability": 42,
          "schema": 88,
          "security": 55,
          "transparency": 54
        },
        "provenanceScore": 64,
        "checked": {
          "categories": {
            "ergonomics": "2026-10-30",
            "maintenance": "2026-10-30",
            "payments": "2026-10-30",
            "reliability": "2026-10-30",
            "schema": "2026-10-30",
            "security": "2026-10-30",
            "transparency": "2026-10-30"
          },
          "last": "2026-10-30",
          "lastMoved": "2026-10-30",
          "oldest": "2026-10-30",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm install -g @scrapeatlas/cli",
        "http": "curl \"https://api.scrapeatlas.com/v1/bluesky/profile?handle=bsky.app\" -H \"x-api-key: $SCRAPEATLAS_API_KEY\""
      },
      "letme": {
        "capability": "https://letme.dev/web.extract",
        "tool": "https://letme.dev/scrapeatlas"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "10,000-credit pack",
          "unit": "1k-requests",
          "usd": 1.9,
          "note": "$19 one-time, 1 credit per successful request, home page checked 30 October 2026"
        },
        {
          "item": "50,000-credit pack",
          "unit": "1k-requests",
          "usd": 1.78,
          "note": "$89 one-time"
        },
        {
          "item": "200,000-credit pack",
          "unit": "1k-requests",
          "usd": 1.25,
          "note": "$249 one-time; not named in the OpenAPI checkout operation or on the affiliate page"
        },
        {
          "item": "Apify Store Actors",
          "unit": "1k-requests",
          "usd": 1.98,
          "note": "successful requests, paid through Apify, no ScrapeAtlas account; TikTok, Instagram, Meetup and Couchsurfing only"
        }
      ],
      "provenance": {
        "legalEntity": "OD. Media \u0026 Technology LLC",
        "domain": "scrapeatlas.com",
        "domainRegistered": "2026-09-10",
        "endpointOnVendorDomain": true,
        "terms": "https://scrapeatlas.com/terms/",
        "privacy": "https://scrapeatlas.com/privacy/",
        "statusPage": "",
        "changelog": "https://scrapeatlas.com/changelog/",
        "securityTxt": "none",
        "checked": "2026-10-30",
        "notes": [
          "The Terms of Service (last updated 29 September 2026), the privacy policy (19 October 2026) and the Public Data Notice (29 September 2026) name OD. Media \u0026 Technology LLC, License No. 2431901.01, Sharjah Media City, Sharjah, United Arab Emirates, governed by UAE and Sharjah law. The contact address on all three is on a different domain, fddigital.net.",
          "RDAP for scrapeatlas.com gives a registration date of 2026-09-10 through NameCheap. The earliest Wayback Machine capture, 11 September 2026, lists ten platforms as live private services and says public self-service access is not open yet.",
          "firstReleased is the changelog's first entry, 21 September 2026, which also records CLI 0.10.0 with every endpoint as a CLI command and an MCP tool. The npm CLI's 0.1.0 is dated 12 September 2026, before self-service access opened. The changelog itself was published on 24 September.",
          "https://scrapeatlas.com/.well-known/security.txt and https://scrapeatlas.com/status/ answer 404. api.scrapeatlas.com answers robots.txt with a JSON error per the 30 October listing check, so only its two OAuth metadata documents were read.",
          "The MCP registry entry io.github.OnlineDopamine/scrapeatlas sits under a personal GitHub namespace, the account that also publishes the npm packages, not under a company organisation."
        ],
        "score": 64
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/scrapeatlas.json",
      "live": {
        "slug": "scrapeatlas",
        "probe": {
          "target": "https://api.scrapeatlas.com",
          "method": "get",
          "lastAt": "2026-11-01T22:08:45.788351622Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 159,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 160,
          "p95ms24h": 228,
          "samples24h": 250,
          "samples30d": 608,
          "days": [
            {
              "date": "2026-10-30",
              "probes": 127,
              "ok": 127
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 230,
              "ok": 230
            }
          ]
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "io.github.OnlineDopamine/scrapeatlas",
            "version": "1.0.0",
            "seenAt": "2026-11-01T16:10:44.053973489Z"
          },
          {
            "registry": "npm",
            "name": "@scrapeatlas/cli",
            "version": "0.26.0",
            "seenAt": "2026-11-01T17:31:19.20903345Z"
          },
          {
            "registry": "npm",
            "name": "n8n-nodes-scrapeatlas",
            "version": "0.1.0",
            "seenAt": "2026-11-01T17:31:21.109246455Z"
          }
        ],
        "npmWeekly": 434,
        "securityTxt": {
          "url": "https://scrapeatlas.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-01T15:42:53.870874539Z"
        },
        "llmsTxt": {
          "url": "https://scrapeatlas.com/docs/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-01T15:14:57.098776136Z"
        },
        "domain": {
          "domain": "scrapeatlas.com",
          "registered": "2026-09-10",
          "source": "https://rdap.verisign.com/com/v1/domain/scrapeatlas.com",
          "checkedAt": "2026-11-01T14:27:49.005315197Z"
        },
        "pages": [
          {
            "url": "https://scrapeatlas.com/changelog/",
            "kind": "changelog",
            "status": 304,
            "checkedAt": "2026-11-01T06:51:55.318054232Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "5407765a3690"
          },
          {
            "url": "https://scrapeatlas.com/privacy/",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-11-01T06:51:57.374715924Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "d2a68672ac0a"
          },
          {
            "url": "https://scrapeatlas.com/terms/",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-11-01T06:51:59.361248345Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "ae5e8551869f"
          }
        ],
        "updatedAt": "2026-11-01T22:08:45.788351622Z"
      }
    },
    "edges": [
      {
        "by": 29,
        "category": "transparency",
        "leads": "scrapeatlas",
        "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": "Closed service with clear terms dated 29 September 2026 naming the legal entity, governing law and liability cap; the CLI is MIT on npm with no source published (15 of 30). The privacy policy (19 October 2026) gives retention periods, 90 days for raw usage records, 30 days for inactive key metadata, 10 minutes to 30 days for OAuth artefacts, and says workers keep no archive of results, which the terms and the Public Data Notice repeat. Providers are named with their roles. No DPA is published; the terms say to arrange one before submitting such a workload (22 of 30). The terms promise reasonable notice of material changes when practicable, and the changelog records a Reddit retirement on 29 September and kept paths on 14 October, but there is no deprecation policy with periods and nothing in the OpenAPI file is marked deprecated (7 of 20). Supabase, Tinybird, PostHog, Stripe, Google, OpenAI and Affonso are named with purposes, but the only location statement is that the operator is in the UAE and infrastructure can process in other countries (10 of 20). 15+22+7+10 = 54."
        },
        "scores": {
          "a": 30,
          "b": 59
        }
      },
      {
        "by": 7,
        "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 change is CLI 0.26.0 on 28 October 2026, after the StockX endpoints on 27 October (30). 15 dated release days between 21 September and 27 October, 58 updates (20). Closed service with a public changelog. Support in the dashboard is for customers with a credit purchase, the contact form takes buying questions and privacy requests, and no Discord, forum or issue tracker was found; the careers page lists a customer support role (7 of 15). io.github.OnlineDopamine/scrapeatlas is in the official MCP registry under a GitHub-verified personal namespace, at 1.0.0 since 5 October and describing about 40 platforms against 49 now. The CLI is current on npm and an n8n node exists, but there are no SDKs (10 of 15). The CLI package has no repository field, no public source and no visible CI; it needs Node 22 or newer (3 of 10). 30+20+7+10+3 = 70."
        },
        "scores": {
          "a": 77,
          "b": 70
        }
      },
      {
        "by": 5,
        "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": "Customer keys with prefix sa_live_, several per account, each with an expiry date, revoked within 60 seconds and stored as hashes per the privacy policy, and keys can't start a checkout or create keys. No scopes or per-platform keys. The MCP server adds an authorization-code flow with PKCE S256, dynamic client registration, refresh-token rotation and revocation, but a single scope, scrapeatlas. No documented option to send a secret in a query string, and the MCP page says never to put the key in a prompt, argument or URL (22 of 30). The whole surface is read-only retrieval of public pages with no destructive action, and an OAuth grant covers retrieval plus the account's usage records only; nothing restricts a key to some platforms (16 of 20). Every response is third-party page content, and the only guidance found concerns keeping secrets out of tool arguments, nothing on treating returned text as untrusted (2 of 15). GET /v1/activity returns per-request metadata (endpoint, time, status, duration) newest first with filters, GET /v1/usage daily totals, responses carry x-credits-charged and x-credits-remaining, and the dashboard shows a credit history (13 of 15). No security.txt (404), no disclosure policy, bug bounty, SOC 2 or ISO 27001; the privacy policy describes access controls and incident notices and gives an abuse address (2 of 20). 22+16+2+13+2 = 55."
        },
        "scores": {
          "a": 60,
          "b": 55
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Qovia",
        "b": "OD. Media \u0026 Technology LLC",
        "name": "Vendor"
      },
      {
        "a": "https://api.qovia.ai",
        "b": "https://api.scrapeatlas.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": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "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": "Proprietary service under ScrapeAtlas's Terms of Service. The @scrapeatlas/cli package on npm is MIT with no public source repository",
        "name": "Licence"
      },
      {
        "a": "141",
        "b": "373",
        "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.OnlineDopamine/scrapeatlas",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-28",
        "b": "2026-10-28",
        "name": "Last release"
      },
      {
        "a": "not read yet",
        "b": "2026-09-29",
        "name": "Terms last updated"
      },
      {
        "a": "not read yet",
        "b": "2026-10-19",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "0 stars",
        "b": "none",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "ScrapeAtlas scores 62.8 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on security \u0026 auth and maintenance \u0026 community.",
        "question": "Which is better for AI agents, Qovia or ScrapeAtlas?"
      },
      {
        "answer": "Qovia needs an API key. ScrapeAtlas takes an API key or an OAuth sign-in.",
        "question": "Do Qovia and ScrapeAtlas need an API key?"
      },
      {
        "answer": "Yes. Qovia has a hosted endpoint at https://api.qovia.ai and ScrapeAtlas at https://api.scrapeatlas.com.",
        "question": "Can an agent call Qovia and ScrapeAtlas without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Security \u0026 auth, 60 against 55",
          "Maintenance \u0026 community, 77 against 70"
        ],
        "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": [
          "Transparency \u0026 trust, 59 against 30"
        ],
        "also": [
          "Free to start without a card"
        ],
        "goodFor": "Agents that need structured public data from a named social, video, forum, marketplace or prediction-market platform, such as a creator's profile and recent posts, a thread's comments, a product's reviews or a market's order book, paid per successful request without a subscription.",
        "slug": "scrapeatlas",
        "watchFor": "No status page or incident history was found, and the terms promise no uptime, throughput or continued availability of an endpoint"
      }
    ],
    "history": {
      "qovia": null,
      "scrapeatlas": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-30",
          "delta": -0.2,
          "from": 63,
          "fromGrade": "B",
          "to": 62.8,
          "toGrade": "B"
        }
      ]
    },
    "job": {
      "capability": "web.extract",
      "name": "Extraction"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/bright-data-vs-qovia.json",
        "title": "Bright Data vs Qovia",
        "url": "https://www.anchorterminal.com/compare/bright-data-vs-qovia"
      },
      {
        "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia.json",
        "title": "Firecrawl MCP vs Qovia",
        "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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/context-dev-vs-scrapeatlas.json",
        "title": "Context.dev vs ScrapeAtlas",
        "url": "https://www.anchorterminal.com/compare/context-dev-vs-scrapeatlas"
      },
      {
        "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-scrapeatlas.json",
        "title": "Diffbot vs ScrapeAtlas",
        "url": "https://www.anchorterminal.com/compare/diffbot-vs-scrapeatlas"
      },
      {
        "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapeatlas.json",
        "title": "Firecrawl MCP vs ScrapeAtlas",
        "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapeatlas"
      },
      {
        "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/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/olostep-vs-scrapeatlas.json",
        "title": "Olostep vs ScrapeAtlas",
        "url": "https://www.anchorterminal.com/compare/olostep-vs-scrapeatlas"
      },
      {
        "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/oxylabs-web-scraper-vs-scrapeatlas.json",
        "title": "Oxylabs Web Scraper API vs ScrapeAtlas",
        "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapeatlas"
      },
      {
        "json": "https://www.anchorterminal.com/compare/qovia-vs-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/scrapeatlas-vs-scrapegraphai.json",
        "title": "ScrapeAtlas vs ScrapeGraphAI",
        "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapegraphai"
      },
      {
        "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scraperapi.json",
        "title": "ScrapeAtlas vs ScraperAPI",
        "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scraperapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapewise.json",
        "title": "ScrapeAtlas vs Scrapewise",
        "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapewise"
      },
      {
        "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapfly.json",
        "title": "ScrapeAtlas vs Scrapfly",
        "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapfly"
      },
      {
        "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingant.json",
        "title": "ScrapeAtlas vs ScrapingAnt",
        "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingant"
      },
      {
        "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingbee.json",
        "title": "ScrapeAtlas vs ScrapingBee",
        "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingbee"
      },
      {
        "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingdog.json",
        "title": "ScrapeAtlas vs Scrapingdog",
        "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingdog"
      },
      {
        "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-spider-cloud.json",
        "title": "ScrapeAtlas vs Spider",
        "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-spider-cloud"
      },
      {
        "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-zenrows.json",
        "title": "ScrapeAtlas vs ZenRows",
        "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-zenrows"
      },
      {
        "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-zyte.json",
        "title": "ScrapeAtlas vs Zyte API",
        "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-zyte"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 2,
        "edge": "scrapeatlas",
        "key": "reliability",
        "name": "Reliability",
        "qovia": 40,
        "scrapeatlas": 42,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 2,
        "edge": "scrapeatlas",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "qovia": 86,
        "scrapeatlas": 88,
        "weight": 13
      },
      {
        "by": 1,
        "edge": "qovia",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "qovia": 77,
        "scrapeatlas": 76,
        "weight": 13
      },
      {
        "by": 5,
        "edge": "qovia",
        "key": "security",
        "name": "Security \u0026 auth",
        "qovia": 60,
        "scrapeatlas": 55,
        "weight": 14
      },
      {
        "by": 0,
        "edge": "",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "qovia": 55,
        "scrapeatlas": 55,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 7,
        "edge": "qovia",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "qovia": 77,
        "scrapeatlas": 70,
        "weight": 7
      },
      {
        "by": 29,
        "edge": "scrapeatlas",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "qovia": 30,
        "scrapeatlas": 59,
        "weight": 7
      }
    ],
    "summary": "ScrapeAtlas scores 62.8 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on 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.",
      "scrapeatlas": "An OpenAPI 3.1 file with 386 operations, typed parameters and a uniform failure object, published limits of 120 requests a minute and 4 concurrent, and 1 credit per successful request with failed calls free. No status page, security.txt or SDKs, the MCP server is a preview with 373 tools, and the product is five weeks old."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas",
    "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.min.md"
  },
  "markdown": "ScrapeAtlas scores 62.8 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on security \u0026 auth and maintenance \u0026 community. Both do extraction.\n\n- Qovia: grade C, 61.2/100, rank #558 of 1253. Markdown https://www.anchorterminal.com/tools/qovia.md · JSON https://www.anchorterminal.com/api/v1/tools/qovia.json\n- ScrapeAtlas: grade B, 62.8/100, rank #478 of 1253. Markdown https://www.anchorterminal.com/tools/scrapeatlas.md · JSON https://www.anchorterminal.com/api/v1/tools/scrapeatlas.json\n- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md\n- All 261 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md\n\n## Which one, for what\n\n### Qovia (C)\n\nGood for: Agents that need structured public data from Chinese platforms (Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Zhihu, WeChat official accounts, Taobao and JD reviews) or the Xingtu and Pugongying creator marketplaces, with TikTok, YouTube, Instagram, X and Reddit beside them, paid per successful call from a prepaid balance.\n\nAhead on:\n- Security \u0026 auth, 60 against 55\n- Maintenance \u0026 community, 77 against 70\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### ScrapeAtlas (B)\n\nGood for: Agents that need structured public data from a named social, video, forum, marketplace or prediction-market platform, such as a creator's profile and recent posts, a thread's comments, a product's reviews or a market's order book, paid per successful request without a subscription.\n\nAhead on:\n- Transparency \u0026 trust, 59 against 30\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No status page or incident history was found, and the terms promise no uptime, throughput or continued availability of an endpoint\n\n\n## Why the edge\n\n### Transparency \u0026 trust: ScrapeAtlas +29\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- ScrapeAtlas (59): Closed service with clear terms dated 29 September 2026 naming the legal entity, governing law and liability cap; the CLI is MIT on npm with no source published (15 of 30). The privacy policy (19 October 2026) gives retention periods, 90 days for raw usage records, 30 days for inactive key metadata, 10 minutes to 30 days for OAuth artefacts, and says workers keep no archive of results, which the terms and the Public Data Notice repeat. Providers are named with their roles. No DPA is published; the terms say to arrange one before submitting such a workload (22 of 30). The terms promise reasonable notice of material changes when practicable, and the changelog records a Reddit retirement on 29 September and kept paths on 14 October, but there is no deprecation policy with periods and nothing in the OpenAPI file is marked deprecated (7 of 20). Supabase, Tinybird, PostHog, Stripe, Google, OpenAI and Affonso are named with purposes, but the only location statement is that the operator is in the UAE and infrastructure can process in other countries (10 of 20). 15+22+7+10 = 54.\n\n### Maintenance \u0026 community: Qovia +7\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- ScrapeAtlas (70): The newest change is CLI 0.26.0 on 28 October 2026, after the StockX endpoints on 27 October (30). 15 dated release days between 21 September and 27 October, 58 updates (20). Closed service with a public changelog. Support in the dashboard is for customers with a credit purchase, the contact form takes buying questions and privacy requests, and no Discord, forum or issue tracker was found; the careers page lists a customer support role (7 of 15). io.github.OnlineDopamine/scrapeatlas is in the official MCP registry under a GitHub-verified personal namespace, at 1.0.0 since 5 October and describing about 40 platforms against 49 now. The CLI is current on npm and an n8n node exists, but there are no SDKs (10 of 15). The CLI package has no repository field, no public source and no visible CI; it needs Node 22 or newer (3 of 10). 30+20+7+10+3 = 70.\n\n### Security \u0026 auth: Qovia +5\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- ScrapeAtlas (55): Customer keys with prefix sa_live_, several per account, each with an expiry date, revoked within 60 seconds and stored as hashes per the privacy policy, and keys can't start a checkout or create keys. No scopes or per-platform keys. The MCP server adds an authorization-code flow with PKCE S256, dynamic client registration, refresh-token rotation and revocation, but a single scope, scrapeatlas. No documented option to send a secret in a query string, and the MCP page says never to put the key in a prompt, argument or URL (22 of 30). The whole surface is read-only retrieval of public pages with no destructive action, and an OAuth grant covers retrieval plus the account's usage records only; nothing restricts a key to some platforms (16 of 20). Every response is third-party page content, and the only guidance found concerns keeping secrets out of tool arguments, nothing on treating returned text as untrusted (2 of 15). GET /v1/activity returns per-request metadata (endpoint, time, status, duration) newest first with filters, GET /v1/usage daily totals, responses carry x-credits-charged and x-credits-remaining, and the dashboard shows a credit history (13 of 15). No security.txt (404), no disclosure policy, bug bounty, SOC 2 or ISO 27001; the privacy policy describes access controls and incident notices and gives an abuse address (2 of 20). 22+16+2+13+2 = 55.\n\n## Score by category\n\n| Category | Weight | Qovia | ScrapeAtlas | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 42 | ScrapeAtlas +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 88 | ScrapeAtlas +2 |\n| Agent ergonomics | 13% (16.2 this run) | 77 | 76 | Qovia +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 55 | Qovia +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 55 | 55 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 77 | 70 | Qovia +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 30 | 59 | ScrapeAtlas +29 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.2 · C** | **62.8 · B** | |\n\n## Facts side by side\n\n| Fact | Qovia | ScrapeAtlas |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Qovia | OD. Media \u0026 Technology LLC |\n| Hosted endpoint | `https://api.qovia.ai` | `https://api.scrapeatlas.com` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\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 | Proprietary service under ScrapeAtlas's Terms of Service. The @scrapeatlas/cli package on npm is MIT with no public source repository |\n| Tools exposed | 141 | 373 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `ai.qovia/qovia` | `io.github.OnlineDopamine/scrapeatlas` |\n| Last release | 2026-10-28 | 2026-10-28 |\n| Terms last updated | not read yet | 2026-09-29 |\n| Privacy policy last updated | not read yet | 2026-10-19 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | 0 stars | none |\n\n## How the scores have moved\n\n### Qovia\n\nNo score change since it was listed.\n\n### ScrapeAtlas\n\n- -0.2 on 30 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**ScrapeAtlas.** An OpenAPI 3.1 file with 386 operations, typed parameters and a uniform failure object, published limits of 120 requests a minute and 4 concurrent, and 1 credit per successful request with failed calls free. No status page, security.txt or SDKs, the MCP server is a preview with 373 tools, and the product is five weeks old.\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### ScrapeAtlas\n\n1. Send the key as `x-api-key` on https://api.scrapeatlas.com and check `status` on every HTTP 200; `partial` is usable data with `coverage.warnings`, `failed` and `challenged` carry `failure.code`.\n2. Retry only on `upstream_rate_limited`, `timeout` and `busy`, after the `retry-after` on a 429. Stay under 120 requests a minute and 4 concurrent per account.\n3. Pass the returned `cursor` back unchanged for the next page, and use `since` and `until` (ISO 8601 or Unix seconds) where listed; each page costs another credit.\n4. Each platform has its own response schema, so read the endpoint's response fields before mapping; unknown values are `null`, never 0.\n5. For MCP, connect to https://api.scrapeatlas.com/mcp over Streamable HTTP with `Authorization: Bearer` and expect 373 tools; the two account tools and failed calls cost 0 credits.\n\n## Questions\n\n### Which is better for AI agents, Qovia or ScrapeAtlas?\n\nScrapeAtlas scores 62.8 (B) on agent readiness against Qovia's 61.2 (C), and leads in 3 of 7 scored categories. Qovia leads on security \u0026 auth and maintenance \u0026 community.\n\n### Do Qovia and ScrapeAtlas need an API key?\n\nQovia needs an API key. ScrapeAtlas takes an API key or an OAuth sign-in.\n\n### Can an agent call Qovia and ScrapeAtlas without installing anything?\n\nYes. Qovia has a hosted endpoint at https://api.qovia.ai and ScrapeAtlas at https://api.scrapeatlas.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.json, and with the fewest tokens: https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"qovia\", \"b\": \"scrapeatlas\"}`. From a terminal: `anchor compare qovia scrapeatlas`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/qovia.json and https://www.anchorterminal.com/api/v1/tools/scrapeatlas.json\n\n## Other comparisons with Qovia or ScrapeAtlas\n\n- [Bright Data vs Qovia](https://www.anchorterminal.com/compare/bright-data-vs-qovia.md)\n- [Firecrawl MCP vs Qovia](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-qovia.md)\n- [Context.dev vs Qovia](https://www.anchorterminal.com/compare/context-dev-vs-qovia.md)\n- [Context.dev vs ScrapeAtlas](https://www.anchorterminal.com/compare/context-dev-vs-scrapeatlas.md)\n- [Diffbot vs Qovia](https://www.anchorterminal.com/compare/diffbot-vs-qovia.md)\n- [Diffbot vs ScrapeAtlas](https://www.anchorterminal.com/compare/diffbot-vs-scrapeatlas.md)\n- [Firecrawl MCP vs ScrapeAtlas](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapeatlas.md)\n- [jevcrawl vs Qovia](https://www.anchorterminal.com/compare/jevcrawl-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- [Olostep vs ScrapeAtlas](https://www.anchorterminal.com/compare/olostep-vs-scrapeatlas.md)\n- [Oxylabs Web Scraper API vs Qovia](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-qovia.md)\n- [Oxylabs Web Scraper API vs ScrapeAtlas](https://www.anchorterminal.com/compare/oxylabs-web-scraper-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- [ScrapeAtlas vs ScrapeGraphAI](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapegraphai.md)\n- [ScrapeAtlas vs ScraperAPI](https://www.anchorterminal.com/compare/scrapeatlas-vs-scraperapi.md)\n- [ScrapeAtlas vs Scrapewise](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapewise.md)\n- [ScrapeAtlas vs Scrapfly](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapfly.md)\n- [ScrapeAtlas vs ScrapingAnt](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingant.md)\n- [ScrapeAtlas vs ScrapingBee](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingbee.md)\n- [ScrapeAtlas vs Scrapingdog](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingdog.md)\n- [ScrapeAtlas vs Spider](https://www.anchorterminal.com/compare/scrapeatlas-vs-spider-cloud.md)\n- [ScrapeAtlas vs ZenRows](https://www.anchorterminal.com/compare/scrapeatlas-vs-zenrows.md)\n- [ScrapeAtlas vs Zyte API](https://www.anchorterminal.com/compare/scrapeatlas-vs-zyte.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-01",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.7",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Qovia vs ScrapeAtlas",
        "url": ""
      }
    ],
    "description": "ScrapeAtlas scores 62.8 (B) to Qovia's 61.2 (C) for extraction. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Qovia C 61.2",
      "ScrapeAtlas B 62.8",
      "scores"
    ],
    "h1": "Qovia vs ScrapeAtlas",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/qovia-vs-scrapeatlas",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Qovia vs ScrapeAtlas for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-01",
    "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas"
  },
  "tokens": {
    "markdown": 4750,
    "slim": 2580
  },
  "version": 1
}
