{
  "data": {
    "a": {
      "slug": "outcrawl",
      "name": "Outcrawl",
      "vendor": "Aeonmind LLC (Outcrawl)",
      "vendorUrl": "https://outcrawl.ai",
      "kind": "http-api",
      "category": "web-scrapers",
      "summary": "Outcrawl is a hosted web layer for AI agents with scrape, crawl, search, cloud browsers over CDP and agent runs on one credit balance, reached through a REST API, TypeScript and Python SDKs, a CLI and a remote MCP server.",
      "url": "https://www.anchorterminal.com/tools/outcrawl",
      "markdownUrl": "https://www.anchorterminal.com/tools/outcrawl.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/outcrawl.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/outcrawl.json",
      "dns": "outcrawl.grade.anchorterminal.com",
      "repo": "https://github.com/outcrawlai/scout",
      "license": "Proprietary hosted service under Aeonmind LLC's terms of service (last updated 1 November 2026). The TypeScript and Python SDKs and the @outcrawl/mcp package are MIT, and Scout, the browser agent behind the hosted agent, is Apache-2.0 in a read-only GitHub mirror",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.outcrawl.ai/v1",
      "packages": [
        {
          "registry": "npm",
          "name": "@outcrawl/sdk"
        },
        {
          "registry": "pypi",
          "name": "outcrawl"
        }
      ],
      "auth": "mixed",
      "authNotes": "Two bearer credentials. An API key shaped `ock_\u003ckeyId\u003e.\u003csecret\u003e` is minted in the console, shown once, stored as a digest, scoped to one workspace and revocable within a minute; it works on the REST API and the MCP server as `Authorization: Bearer`, with no per-key scopes or read-only keys documented. An OAuth 2.1 access token `oat_...` comes from signing in, through the authorization code flow with PKCE S256 and dynamic client registration for MCP clients (the server at https://api.outcrawl.ai/mcp answers 401 with protected-resource metadata naming https://outcrawl.ai/api/auth) or the RFC 8628 device flow for the CLI, with scopes `api` and `offline_access`, access tokens of one hour and refresh for 30 days while in use; removing a member from a workspace cuts their tokens off at once. Console sign-in is Google, GitHub, an email code or a magic link behind reCAPTCHA.",
      "pricing": "freemium",
      "pricingNotes": "Free plan with 1,000 credits a month, no card, 2 concurrent browsers and 120 requests a minute, on a person's first workspace only. Builder $49 a month for 10,000 credits (5 browsers, 300 requests a minute), Pro $199 for 50,000 (25, 1,500), Scale $799 for 250,000 (100, 6,000), Enterprise custom with a 99.9 per cent monthly uptime SLA. Rates in credits are the same on every plan, 1 a page for scrape, crawl and rendered search results, 5 per 10 search results, 1 a minute of browser time, 2,000 a GB of proxy traffic, 1 a monitor check, and agent runs at model usage plus browser time plus proxy usage, about 15 credits a minute as the vendor's estimate. Extra credits cost $49.00 per 10,000 on Builder and Free, $39.80 on Pro and $31.96 on Scale, never expire, and auto top-up is capped monthly. Every response carries a `usage` object with its cost; a cached scrape answer bills the same credit as a live fetch, a cancelled crawl keeps billing the pages it fetched, and a search every engine refuses bills nothing (https://outcrawl.ai/pricing and https://outcrawl.ai/docs/billing/pricing, checked 2026-11-02).",
      "priceSummary": "$4.90 / 1k pages",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the OpenAPI file, llms-full.txt, the pricing pages or the terms (checked 2026-11-02). Plans and top-ups are paid by card through Stripe in the console.",
        "endpoints": []
      },
      "toolCount": 29,
      "popularity": {
        "githubStars": 948,
        "npmWeekly": 53,
        "pypiWeekly": null,
        "asOf": "2026-11-02"
      },
      "docsUrl": "https://outcrawl.ai/docs",
      "llmsTxt": "https://outcrawl.ai/docs/llms.txt",
      "openapi": "https://outcrawl.ai/docs/api-reference/openapi.json",
      "capabilities": [
        "web.scrape",
        "web.crawl",
        "web.extract",
        "web.search",
        "browser.hosted",
        "browser.control",
        "scraping.proxies",
        "scraping.js-render",
        "scraping.anti-bot",
        "scraping.screenshot"
      ],
      "tags": [
        "hosted",
        "official",
        "closed-source",
        "openapi",
        "llms-txt",
        "mcp",
        "remote-mcp",
        "oauth",
        "api-key",
        "cli",
        "python",
        "typescript",
        "proxies",
        "browser",
        "agents",
        "credits",
        "free-tier",
        "no-card",
        "freemium",
        "no-status-page",
        "new"
      ],
      "lastRelease": "2026-10-20",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.4,
        "grade": "B",
        "agentReady": false,
        "rank": 456,
        "ranked": true,
        "rankOf": 1268,
        "categoryRank": 13,
        "methodology": "0.7",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 83,
          "maintenance": 79,
          "payments": 40,
          "reliability": 45,
          "schema": 71,
          "security": 66,
          "transparency": 56
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-02"
        },
        "negative": 0,
        "verdict": "One credit balance over scrape, crawl, search, cloud browsers and agent runs, with published per-unit rates, a 1,000-credit free month, OAuth 2.1 for MCP and the CLI, and a closed error union with retry guidance. No status page, changelog or security.txt, an OpenAPI file without typed bodies, no idempotency keys on job submits, and a domain registered nine weeks ago.",
        "bestFor": "Agents that want one key and one balance for reading pages, walking a site, searching with rendered results and handing a signed-in or multi-step task to a hosted browser agent with a hard budget, and teams on TypeScript that want a residential-exit browser over CDP with a replay of every session.",
        "strengths": [
          "Per-unit rates published without a login, 1 credit a page or browser minute and 5 credits per 10 search results, with the dollar cost per plan and every response carrying its own `usage`",
          "Free plan of 1,000 credits a month with no card, 2 concurrent browsers and 120 requests a minute, usable over the API, the SDKs, the CLI and MCP",
          "OAuth 2.1 with PKCE S256, dynamic client registration, device code for the CLI, a revocation endpoint and one-hour access tokens, beside workspace-scoped keys shown once and stored as a digest",
          "A closed error union in one envelope with a documented list of codes safe to retry, `retryAfterSeconds` on the per-minute quota error, and MCP errors that carry a `recovery` string and a `retryable` flag",
          "MCP tool descriptions that each name what the tool is not for and which tool is, with secrets and integrations kept off the MCP surface and agent runs capped by a required or defaulted budget",
          "Scout, the agent behind the hosted agent, is published under Apache-2.0 with its tests, and the SDKs and MCP package are MIT"
        ],
        "weaknesses": [
          "No status page, incident history, SLA below Enterprise or security.txt; /status and status.outcrawl.ai do not answer",
          "The OpenAPI file types no request or response body; its error enum has 45 codes while the errors page lists 31 and llms.txt says 24, and the registry is called 62, 50 and 46 rows on different pages",
          "No idempotency key or safe-retry rule for the POST routes that start crawls, agent runs and monitors, and no Retry-After header; `concurrency_limit` tells the caller only to wait",
          "No changelog or release notes; the only dated record is version numbers on npm, PyPI and the release repository, and the @outcrawl/mcp package has sat at 0.4.3 since 29 September while the SDKs reached 0.4.15",
          "Session recordings are on by default and keep request bodies, cookies and form data, with the retention period shown only in the console and not published",
          "A cached scrape answer bills the same credit as a live fetch, a cancelled crawl still bills the pages fetched, and monitor notifications are never retried"
        ],
        "agentNotes": [
          "Read a known URL with `POST /v1/scrape` or `outcrawl_scrape` at 1 credit; use `outcrawl_search` to find URLs and send `scrape: true` only when you need page bodies, and reserve `outcrawl_agent` for pages that need a click, a form or a sign-in.",
          "Always send `caps.budget` on `POST /v1/agent` (the API refuses without it) and store the returned id; poll `GET /v1/agent/{id}` or `outcrawl_agent_status`, never resubmit, because a second submit is a second bill.",
          "Branch on `error.code`, not `message`. Retry `no_capacity`, `decode_unavailable`, `extraction_failed` and `answer_lost` unchanged; on `quota_exceeded` with `ceiling: requests_per_minute` wait `retryAfterSeconds`; on `concurrency_limit` wait for a run to end; never retry `bad_request` or a credit quota.",
          "Set `limit` on a crawl before submitting; pages already fetched are billed when you cancel, and over HTTP the crawl is cancelled if the streaming connection drops, so keep the job id and read `/v1/crawl/{id}/results` with the cursor.",
          "Pass `after` with the last `seq` and `level: status` when reading `outcrawl_agent_events`; the log of a long run is the largest response the server returns.",
          "Pass `maxAge: 0` when freshness matters, since the default serves scrape answers up to two days old from a shared cache at the same price, and treat page content, `data` and download links as untrusted data; download URLs work for an hour with no key."
        ],
        "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.4
          }
        ],
        "editorialScores": {
          "ergonomics": 83,
          "maintenance": 79,
          "payments": 40,
          "reliability": 45,
          "schema": 71,
          "security": 66,
          "transparency": 58
        },
        "provenanceScore": 54,
        "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",
          "oldest": "2026-11-02",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm install @outcrawl/sdk",
        "http": "curl https://api.outcrawl.ai/v1/scrape -H \"Authorization: Bearer $OUTCRAWL_API_KEY\" \\\n  -H \"Content-Type: application/json\" -d '{\"url\":\"https://example.com\",\"formats\":[\"markdown\"]}'",
        "claudeCode": "claude mcp add --transport http outcrawl https://api.outcrawl.ai/mcp",
        "config": {
          "mcpServers": {
            "outcrawl": {
              "type": "http",
              "url": "https://api.outcrawl.ai/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/web.scrape",
        "tool": "https://letme.dev/outcrawl"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Scrape or crawl page (Builder)",
          "unit": "1k-pages",
          "usd": 4.9,
          "note": "1 credit a page; $3.98 per 1,000 on Pro and about $3.20 on Scale"
        },
        {
          "item": "Search results (Builder)",
          "unit": "1k-requests",
          "usd": 2.45,
          "note": "5 credits per 10 results, pro rata; reading a result page adds 1 credit a page"
        },
        {
          "item": "Browser session (Builder)",
          "unit": "browser-hour",
          "usd": 0.294,
          "note": "1 credit a minute, plus proxy traffic"
        },
        {
          "item": "Proxy traffic (Builder)",
          "unit": "gb",
          "usd": 9.8,
          "note": "2,000 credits a decimal GB on browser sessions and agent runs"
        },
        {
          "item": "Credit (Builder, top-up or plan)",
          "unit": "credit",
          "usd": 0.0049,
          "note": "$49.00 per 10,000; $0.00398 on Pro and $0.003196 on Scale; agent runs cost about 15 credits a minute as the vendor's estimate"
        },
        {
          "item": "Builder plan",
          "unit": "month",
          "usd": 49,
          "note": "10,000 credits, 5 concurrent browsers, 300 requests a minute"
        },
        {
          "item": "Pro plan",
          "unit": "month",
          "usd": 199,
          "note": "50,000 credits, 25 concurrent browsers, 1,500 requests a minute"
        },
        {
          "item": "Scale plan",
          "unit": "month",
          "usd": 799,
          "note": "250,000 credits, 100 concurrent browsers, 6,000 requests a minute"
        }
      ],
      "provenance": {
        "legalEntity": "Aeonmind LLC (trading as Outcrawl)",
        "domain": "outcrawl.ai",
        "domainRegistered": "2026-08-28",
        "endpointOnVendorDomain": true,
        "terms": "https://outcrawl.ai/legal/terms",
        "privacy": "https://outcrawl.ai/legal/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-02",
        "notes": [
          "The terms of service and the privacy policy, both last updated 1 November 2026, name Aeonmind LLC, trading as Outcrawl, governed by Delaware law with disputes in Delaware courts; the privacy policy calls it a United States company. No postal address is given. The footer reads © 2026 Aeonmind LLC and Scout's licence notice names the same company.",
          "RDAP at rdap.identitydigital.services gives a registration date of 2026-08-28 for outcrawl.ai, last changed 2026-09-02, with Cloudflare nameservers. The REST API and the MCP server are on api.outcrawl.ai and the OAuth authorization server on outcrawl.ai.",
          "firstReleased is 2026-09-08, the first npm publish of @outcrawl/sdk 0.1.0, which is also the day the outcrawlai GitHub organisation was created; PyPI's first release followed on 22 September 2026 and the Wayback Machine's first copy of the home page is 15 October 2026. lastRelease is 2026-10-20, version 0.4.15 on npm and PyPI.",
          "https://outcrawl.ai/.well-known/security.txt and https://api.outcrawl.ai/.well-known/security.txt answer 404. The security page has a responsible disclosure section with security@outcrawl.ai, a 90-day window and a no-legal-action statement for good-faith reports. /status, /changelog, /blog and /about on outcrawl.ai answer 404 and status.outcrawl.ai does not answer; no changelog or release notes exist on either host.",
          "robots.txt on outcrawl.ai allows every named crawler and `*`, disallows /console, /admin, /api/ and /og/ (except PNG and JPG files), and carries `Content-Signal: ai-train=yes, search=yes, ai-input=yes`. api.outcrawl.ai disallows /play/, /replay/, /v1/, /mcp, /connect, /agent, /internal/ and /operator/; none of those paths was fetched, and the OAuth metadata documents were read as the listing check allowed.",
          "The vendor's own benchmark claim of 92.5 per cent pages reached, the 'orders of magnitude' cost language in tool descriptions and the human input model measurements are the vendor's claims. No MCP registry entry exists for outcrawl (search answers an empty list)."
        ],
        "score": 54
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/outcrawl.json",
      "live": {
        "slug": "outcrawl",
        "probe": {
          "target": "https://api.outcrawl.ai/v1",
          "method": "get",
          "lastAt": "2026-11-02T21:16:12.60527246Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 326,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 415,
          "p95ms24h": 695,
          "samples24h": 33,
          "samples30d": 33,
          "days": [
            {
              "date": "2026-11-02",
              "probes": 33,
              "ok": 33
            }
          ]
        },
        "versions": [
          {
            "registry": "npm",
            "name": "@outcrawl/sdk",
            "version": "0.4.15",
            "seenAt": "2026-11-02T19:40:27.502289569Z"
          },
          {
            "registry": "pypi",
            "name": "outcrawl",
            "version": "0.4.15",
            "released": "2026-10-20",
            "seenAt": "2026-11-02T19:40:28.458855358Z"
          }
        ],
        "githubStars": 948,
        "npmWeekly": 54,
        "pypiWeekly": 36,
        "updatedAt": "2026-11-02T21:16:12.60527246Z"
      }
    },
    "answer": "ScrapeAtlas and Outcrawl score within a point of each other on agent readiness, 62.8 (B) and 62.4 (B). Outcrawl leads on agent ergonomics, 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": 444,
        "ranked": true,
        "rankOf": 1268,
        "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-11-02"
        },
        "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 six 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-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-30",
          "oldest": "2026-11-02",
          "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-02T21:16:17.861875147Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 150,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 159,
          "p95ms24h": 231,
          "samples24h": 250,
          "samples30d": 849,
          "days": [
            {
              "date": "2026-10-30",
              "probes": 127,
              "ok": 127
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 222,
              "ok": 222
            }
          ]
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "io.github.OnlineDopamine/scrapeatlas",
            "version": "1.0.0",
            "seenAt": "2026-11-02T16:30:45.916990424Z"
          },
          {
            "registry": "npm",
            "name": "@scrapeatlas/cli",
            "version": "0.26.0",
            "seenAt": "2026-11-02T19:48:54.219004923Z"
          },
          {
            "registry": "npm",
            "name": "n8n-nodes-scrapeatlas",
            "version": "0.1.0",
            "seenAt": "2026-11-02T19:48:56.191874975Z"
          }
        ],
        "npmWeekly": 301,
        "securityTxt": {
          "url": "https://scrapeatlas.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-02T15:44:57.469615317Z"
        },
        "llmsTxt": {
          "url": "https://scrapeatlas.com/docs/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-02T15:17:58.305811945Z"
        },
        "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-02T07:24:51.53540625Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "5407765a3690"
          },
          {
            "url": "https://scrapeatlas.com/privacy/",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-11-02T07:24:53.643715959Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "d2a68672ac0a"
          },
          {
            "url": "https://scrapeatlas.com/terms/",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-11-02T07:24:55.606781793Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "ae5e8551869f"
          }
        ],
        "updatedAt": "2026-11-02T21:16:17.861875147Z"
      }
    },
    "edges": [
      {
        "by": 17,
        "category": "schema",
        "leads": "scrapeatlas",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "API reading, with the MCP server described. An OpenAPI 3.1 document at https://outcrawl.ai/docs/api-reference/openapi.json lists 62 operations over 51 paths with a summary each and the same 11 status codes, generated from the vendor's capability registry, but every request body is an untyped object marked `additionalProperties: true` with a pointer to the docs, every 200 response is an untyped object, and `Error` is the only schema; the typed shapes live in the SDK declarations and in the MCP server's zod schemas, which were read in the 0.4.3 npm package rather than from the hosted server (15 of 25). llms.txt and a 525 KB llms-full.txt on the docs, a Markdown twin of every page and an llms.txt on the site (10). The MCP descriptions each end with a `Not for:` clause naming the better tool and most with a `Cost:` clause, the OpenAPI summaries say when not to use a route, and the capability pages say which neighbour to use instead (18 of 20). Scrape formats are an enum of eight, event levels and record kinds are enums, `caps.budget` is required, and the SDK types bound every option, while the OpenAPI bodies carry none of it (10 of 15). curl, TypeScript and Python examples on every page, 20 worked programs, a 31-row error table with meanings and a retryable list, and MCP errors with a `recovery` string, though the closed union is sized 24, 31, 45 and 22 on different pages (13 of 15). `/v1` in the path and 1.0.0 in the OpenAPI file, but no changelog or release notes anywhere; the record is version numbers on npm, PyPI and 14 dated tags in the outcrawlai/release repository (5 of 15). 15+10+18+10+13+5 = 71.",
          "b": "An OpenAPI 3.1.0 file (version 0.1.0, 34 MB) is public at scrapeatlas.com/docs/openapi.json with 384 paths and 386 operations, a per-platform x-api-key security scheme on each, response schemas for 200 and every documented error, and 931 component schemas (25). llms.txt at scrapeatlas.com/docs/llms.txt lists all 373 endpoints with one-line descriptions and schema links, and endpoint pages carry a copy-as-Markdown action (10). 386 operations have a summary and 373 a description, median 39 words, saying what public page is read, what the response holds, how to page and what it costs. llms.txt says not to assume one normalised JSON shape. Guidance on when not to call an endpoint is thin, with 9 descriptions using only and 2 instead (14 of 20). 1,390 parameters, 304 with enums, most with minLength, maxLength or a pattern, 232 operations needing one required parameter and 143 none; the 12 POST bodies are typed (14 of 15). A response example on 373 operations and examples on 508 parameters, HTTP 400 to 504 mapped to one failure object with 33 codes, per-endpoint error tables and code samples in six languages; no Retry-After header declared (14 of 15). Paths are under /v1 and a dated public changelog started on 24 September 2026 with 58 updates, but nothing is marked deprecated in the file, breaking changes aren't flagged, and the 14 October GitHub entry says former paths keep working without saying for how long (11 of 15). 25+10+14+14+14+11 = 88."
        },
        "scores": {
          "a": 71,
          "b": 88
        }
      },
      {
        "by": 15,
        "category": "payments",
        "leads": "scrapeatlas",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No x402, MPP or L402 in the OpenAPI file, the docs, the pricing pages or the terms (0). Per-unit rates published without a login, 1 credit a page, 5 credits per 10 search results, 1 credit a browser minute, 2,000 credits a GB and 1 credit a monitor check, with the dollar rate per plan ($4.90 per 1,000 credits on Builder down to about $3.20 on Scale), top-up prices per 10,000 and an estimate of about 15 credits a minute for agent runs (20). Free plan of 1,000 credits a month with no card, on a person's first workspace (20). A person signs in with Google, GitHub, an email code or a magic link behind reCAPTCHA, and MCP's OAuth consent needs that browser sign-in; no keyless route, no programmatic key creation (0). 0+20+20+0 = 40.",
          "b": "No x402, MPP or L402 on ScrapeAtlas's own endpoints. The vendor's eight Actors on the Apify Store, covering TikTok, Instagram, Meetup and Couchsurfing at $1.98 per 1,000 successful requests, 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-unit prices are on the home page without a login, 1 credit per successful request and packs at $1.90, $1.78 and $1.25 per 1,000, with the 2-credit endpoints named (20). 100 free credits at signup, no card (20). A person signs up in a browser and creates a key; the Apify route reaches four platforms without a ScrapeAtlas account (5 of 20). 10+20+20+5 = 55."
        },
        "scores": {
          "a": 40,
          "b": 55
        }
      },
      {
        "by": 11,
        "category": "security",
        "leads": "outcrawl",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "OAuth 2.1 for MCP clients and the CLI with authorization code, PKCE S256, dynamic public-client registration, device code, one-hour access tokens, 30-day refresh, introspection and revocation endpoints and private_key_jwt, but one functional scope, `api`; API keys shaped `ock_\u003ckeyId\u003e.\u003csecret\u003e` are shown once, stored as a digest, scoped to a workspace and revoked within a minute, with no per-key scopes, expiry or read-only keys; nothing documents a secret in a query string (25 of 30). No read-only key or scope. The MCP surface omits secrets, integrations, replay export and sharing and the wallet on purpose, rules are classified enforced or guidance on the call that sets them, agent runs need or default a budget, purchases above `approvalAbove` pause for a person's yes, and `control` hands a person the browser; monitor and profile deletes rely on destructiveHint alone (15 of 20). Every tool returns untrusted page content. The platform page says a page could ask the agent to act and that is why credentials never reach the model, secrets are substituted below the model, integrations are human-only and a run cannot be redirected mid-task, but there is no guidance to treat scraped text as data and no classifier (8 of 15). Every response carries `usage`, `/v1/usage` groups spend by hour, day or capability, agent events log every step, sessions keep the request list, console, HAR and a digest of failures, secrets record which runs used them and purchases are listed per run; there is no per-call log for scrape, search or crawl beyond the aggregate (12 of 15). No security.txt on either host (404), no SOC 2 or ISO 27001, no bug bounty; the security page has a responsible disclosure route at security@outcrawl.ai with a 90-day window and a no-legal-action statement (6 of 20). 25+15+8+12+6 = 66.",
          "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": 66,
          "b": 55
        }
      },
      {
        "by": 9,
        "category": "maintenance",
        "leads": "outcrawl",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "@outcrawl/sdk and the PyPI package outcrawl both reached 0.4.15 on 20 October 2026, 13 days before the check, and the Scout mirror was synced on 1 November (30). 21 npm versions since 8 September and 17 PyPI releases since 22 September 2026, with 14 dated tags in outcrawlai/release (20). Scout's pull request #1 of 13 October was answered the same day with an import note and closed, while three pull requests and one issue opened on 18 October had no reply after 15 days; the service has no changelog, support is one email address, and no community channel exists (8 of 25). Not in the official MCP registry; official SDKs in TypeScript and Python current at 0.4.15, with a CLI (15). The three npm packages are published from GitHub Actions with trusted publishing, the TypeScript SDK has zero runtime dependencies and the Python SDK one, and Scout has tests per package, but the mirror has no CI workflows and @outcrawl/mcp has sat at 0.4.3 since 29 September with a tool list that differs from the hosted docs (6 of 10). 30+20+8+15+6 = 79.",
          "b": "The newest change is CLI 0.26.0 on 28 October 2026 per the 30 October npm reading, not re-read on 2 November, after the StockX endpoints on 27 October, still the changelog's newest entry on 2 November (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": 79,
          "b": 70
        }
      },
      {
        "by": 7,
        "category": "ergonomics",
        "leads": "outcrawl",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "API reading. Scrape returns main content only by default with `formats` picking markdown, html, rawHtml, links, screenshots or schema JSON, search renders page bodies only on request, agent events take a `level` and an `after` cursor, the MCP server shows request bodies up to a character limit and says when it truncated, and the MCP surface is 29 tools with no toolsets (20 of 25). Cursor pagination on crawl results, agent results and downloads, `limit`, depth and path filters on crawl, status, outcome, task and age filters on sessions, and usage grouped by hour, day, month or capability (20). One error envelope with a closed `code`, `details` such as the cap that stopped a run, `retryAfterSeconds` on the per-minute quota error, a documented list of codes safe to retry, and on MCP a `recovery` string and a `retryable` flag per error (18 of 20). No idempotency key on any route, a repeated agent, crawl or monitor submit runs twice, and `concurrency_limit` carries no retry hint; cancel is idempotent, `integration_changed` (409) guards updates, and the npm MCP package sets readOnlyHint on GET tools, destructiveHint on DELETE tools and idempotentHint on either, which the hosted server was not read to confirm (10 of 20). Scrape needs a URL alone, agent runs need `caps.budget` on the API and SDKs with the MCP server defaulting it, and official SDKs exist in TypeScript and Python beside a CLI (15). 20+20+18+10+15 = 83.",
          "b": "API reading. Responses are bounded by limit on 93 operations, by per-body caps, by format on 19 and view on 14 operations, and by since and until on about 60; Instagram and Twitch have reduced basic-profile endpoints. No field selection was found. The MCP server loads 373 tool definitions with no documented subset, which on the MCP reading would score 5 (15 of 25). Cursor pagination on 130 operations, sort on 28, date windows, and coverage.order reported on every list since 2 October 2026 (20). One failure object with code and message, a requestId on every response, retryable codes named, and an HTTP status table (19 of 20). All data reads are GET, failed requests aren't charged, and the docs say which codes to retry; no idempotency key on the 12 POST batch reads and MCP annotations weren't read (14 of 20). Median one required parameter and defaults on limits, but no official SDK in any language. The npm CLI, the n8n node and six-language samples stand in (8 of 15). 15+20+19+14+8 = 76."
        },
        "scores": {
          "a": 83,
          "b": 76
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Aeonmind LLC (Outcrawl)",
        "b": "OD. Media \u0026 Technology LLC",
        "name": "Vendor"
      },
      {
        "a": "https://api.outcrawl.ai/v1",
        "b": "https://api.scrapeatlas.com",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, Streamable HTTP",
        "b": "HTTP, Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary hosted service under Aeonmind LLC's terms of service (last updated 1 November 2026). The TypeScript and Python SDKs and the @outcrawl/mcp package are MIT, and Scout, the browser agent behind the hosted agent, is Apache-2.0 in a read-only GitHub mirror",
        "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": "29",
        "b": "373",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "io.github.OnlineDopamine/scrapeatlas",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-20",
        "b": "2026-10-28",
        "name": "Last release"
      },
      {
        "a": "2026-11-01",
        "b": "2026-09-29",
        "name": "Terms last updated"
      },
      {
        "a": "2026-11-01",
        "b": "2026-10-19",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "948 stars, 53 npm/wk",
        "b": "none",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "ScrapeAtlas and Outcrawl score within a point of each other on agent readiness, 62.8 (B) and 62.4 (B). Outcrawl leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community.",
        "question": "Which is better for AI agents, Outcrawl or ScrapeAtlas?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do Outcrawl and ScrapeAtlas need an API key?"
      },
      {
        "answer": "Yes. Outcrawl has a hosted endpoint at https://api.outcrawl.ai/v1 and ScrapeAtlas at https://api.scrapeatlas.com.",
        "question": "Can an agent call Outcrawl and ScrapeAtlas without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Agent ergonomics, 83 against 76",
          "Security \u0026 auth, 66 against 55",
          "Maintenance \u0026 community, 79 against 70"
        ],
        "also": null,
        "goodFor": "Agents that want one key and one balance for reading pages, walking a site, searching with rendered results and handing a signed-in or multi-step task to a hosted browser agent with a hard budget, and teams on TypeScript that want a residential-exit browser over CDP with a replay of every session.",
        "slug": "outcrawl",
        "watchFor": "No status page, incident history, SLA below Enterprise or security.txt; /status and status.outcrawl.ai do not answer"
      },
      {
        "aheadOn": [
          "Schema \u0026 documentation, 88 against 71",
          "Payments \u0026 pricing, 55 against 40"
        ],
        "also": null,
        "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": {
      "outcrawl": 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-outcrawl.json",
        "title": "Bright Data vs Outcrawl",
        "url": "https://www.anchorterminal.com/compare/bright-data-vs-outcrawl"
      },
      {
        "json": "https://www.anchorterminal.com/compare/context-dev-vs-outcrawl.json",
        "title": "Context.dev vs Outcrawl",
        "url": "https://www.anchorterminal.com/compare/context-dev-vs-outcrawl"
      },
      {
        "json": "https://www.anchorterminal.com/compare/jina-reader-vs-outcrawl.json",
        "title": "Jina Reader vs Outcrawl",
        "url": "https://www.anchorterminal.com/compare/jina-reader-vs-outcrawl"
      },
      {
        "json": "https://www.anchorterminal.com/compare/olostep-vs-outcrawl.json",
        "title": "Olostep vs Outcrawl",
        "url": "https://www.anchorterminal.com/compare/olostep-vs-outcrawl"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-oxylabs-web-scraper.json",
        "title": "Outcrawl vs Oxylabs Web Scraper API",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-oxylabs-web-scraper"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-scrape-do.json",
        "title": "Outcrawl vs Scrape.do",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-scrape-do"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapegraphai.json",
        "title": "Outcrawl vs ScrapeGraphAI",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapegraphai"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapeless.json",
        "title": "Outcrawl vs Scrapeless",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapeless"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-scraperapi.json",
        "title": "Outcrawl vs ScraperAPI",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-scraperapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapewise.json",
        "title": "Outcrawl vs Scrapewise",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapewise"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapfly.json",
        "title": "Outcrawl vs Scrapfly",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapfly"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapingant.json",
        "title": "Outcrawl vs ScrapingAnt",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapingant"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapingbee.json",
        "title": "Outcrawl vs ScrapingBee",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapingbee"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapingdog.json",
        "title": "Outcrawl vs Scrapingdog",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapingdog"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-spider-cloud.json",
        "title": "Outcrawl vs Spider",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-spider-cloud"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-zenrows.json",
        "title": "Outcrawl vs ZenRows",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-zenrows"
      },
      {
        "json": "https://www.anchorterminal.com/compare/outcrawl-vs-zyte.json",
        "title": "Outcrawl vs Zyte API",
        "url": "https://www.anchorterminal.com/compare/outcrawl-vs-zyte"
      },
      {
        "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-outcrawl.json",
        "title": "Firecrawl MCP vs Outcrawl",
        "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-outcrawl"
      },
      {
        "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-outcrawl.json",
        "title": "Diffbot vs Outcrawl",
        "url": "https://www.anchorterminal.com/compare/diffbot-vs-outcrawl"
      },
      {
        "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-scrapeatlas.json",
        "title": "jevcrawl vs ScrapeAtlas",
        "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapeatlas"
      },
      {
        "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/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-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-scrapeatlas.json",
        "title": "Qovia vs ScrapeAtlas",
        "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas"
      },
      {
        "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"
      },
      {
        "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-outcrawl.json",
        "title": "Apify MCP Server vs Outcrawl",
        "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-outcrawl"
      },
      {
        "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-outcrawl.json",
        "title": "jevcrawl vs Outcrawl",
        "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-outcrawl"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 3,
        "edge": "outcrawl",
        "key": "reliability",
        "name": "Reliability",
        "outcrawl": 45,
        "scrapeatlas": 42,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 17,
        "edge": "scrapeatlas",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "outcrawl": 71,
        "scrapeatlas": 88,
        "weight": 13
      },
      {
        "by": 7,
        "edge": "outcrawl",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "outcrawl": 83,
        "scrapeatlas": 76,
        "weight": 13
      },
      {
        "by": 11,
        "edge": "outcrawl",
        "key": "security",
        "name": "Security \u0026 auth",
        "outcrawl": 66,
        "scrapeatlas": 55,
        "weight": 14
      },
      {
        "by": 15,
        "edge": "scrapeatlas",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "outcrawl": 40,
        "scrapeatlas": 55,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 9,
        "edge": "outcrawl",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "outcrawl": 79,
        "scrapeatlas": 70,
        "weight": 7
      },
      {
        "by": 3,
        "edge": "scrapeatlas",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "outcrawl": 56,
        "scrapeatlas": 59,
        "weight": 7
      }
    ],
    "summary": "ScrapeAtlas and Outcrawl score within a point of each other on agent readiness, 62.8 (B) and 62.4 (B). Outcrawl leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community. Both do extraction.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "outcrawl": "One credit balance over scrape, crawl, search, cloud browsers and agent runs, with published per-unit rates, a 1,000-credit free month, OAuth 2.1 for MCP and the CLI, and a closed error union with retry guidance. No status page, changelog or security.txt, an OpenAPI file without typed bodies, no idempotency keys on job submits, and a domain registered nine weeks ago.",
      "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 six weeks old."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapeatlas",
    "json": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapeatlas.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapeatlas.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapeatlas.min.md"
  },
  "markdown": "ScrapeAtlas and Outcrawl score within a point of each other on agent readiness, 62.8 (B) and 62.4 (B). Outcrawl leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community. Both do extraction.\n\n- Outcrawl: grade B, 62.4/100, rank #456 of 1268. Markdown https://www.anchorterminal.com/tools/outcrawl.md · JSON https://www.anchorterminal.com/api/v1/tools/outcrawl.json\n- ScrapeAtlas: grade B, 62.8/100, rank #444 of 1268. 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 284 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md\n\n## Which one, for what\n\n### Outcrawl (B)\n\nGood for: Agents that want one key and one balance for reading pages, walking a site, searching with rendered results and handing a signed-in or multi-step task to a hosted browser agent with a hard budget, and teams on TypeScript that want a residential-exit browser over CDP with a replay of every session.\n\nAhead on:\n- Agent ergonomics, 83 against 76\n- Security \u0026 auth, 66 against 55\n- Maintenance \u0026 community, 79 against 70\n\nWatch for: No status page, incident history, SLA below Enterprise or security.txt; /status and status.outcrawl.ai do not answer\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- Schema \u0026 documentation, 88 against 71\n- Payments \u0026 pricing, 55 against 40\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### Schema \u0026 documentation: ScrapeAtlas +17\n\n- Outcrawl (71): API reading, with the MCP server described. An OpenAPI 3.1 document at https://outcrawl.ai/docs/api-reference/openapi.json lists 62 operations over 51 paths with a summary each and the same 11 status codes, generated from the vendor's capability registry, but every request body is an untyped object marked `additionalProperties: true` with a pointer to the docs, every 200 response is an untyped object, and `Error` is the only schema; the typed shapes live in the SDK declarations and in the MCP server's zod schemas, which were read in the 0.4.3 npm package rather than from the hosted server (15 of 25). llms.txt and a 525 KB llms-full.txt on the docs, a Markdown twin of every page and an llms.txt on the site (10). The MCP descriptions each end with a `Not for:` clause naming the better tool and most with a `Cost:` clause, the OpenAPI summaries say when not to use a route, and the capability pages say which neighbour to use instead (18 of 20). Scrape formats are an enum of eight, event levels and record kinds are enums, `caps.budget` is required, and the SDK types bound every option, while the OpenAPI bodies carry none of it (10 of 15). curl, TypeScript and Python examples on every page, 20 worked programs, a 31-row error table with meanings and a retryable list, and MCP errors with a `recovery` string, though the closed union is sized 24, 31, 45 and 22 on different pages (13 of 15). `/v1` in the path and 1.0.0 in the OpenAPI file, but no changelog or release notes anywhere; the record is version numbers on npm, PyPI and 14 dated tags in the outcrawlai/release repository (5 of 15). 15+10+18+10+13+5 = 71.\n- ScrapeAtlas (88): An OpenAPI 3.1.0 file (version 0.1.0, 34 MB) is public at scrapeatlas.com/docs/openapi.json with 384 paths and 386 operations, a per-platform x-api-key security scheme on each, response schemas for 200 and every documented error, and 931 component schemas (25). llms.txt at scrapeatlas.com/docs/llms.txt lists all 373 endpoints with one-line descriptions and schema links, and endpoint pages carry a copy-as-Markdown action (10). 386 operations have a summary and 373 a description, median 39 words, saying what public page is read, what the response holds, how to page and what it costs. llms.txt says not to assume one normalised JSON shape. Guidance on when not to call an endpoint is thin, with 9 descriptions using only and 2 instead (14 of 20). 1,390 parameters, 304 with enums, most with minLength, maxLength or a pattern, 232 operations needing one required parameter and 143 none; the 12 POST bodies are typed (14 of 15). A response example on 373 operations and examples on 508 parameters, HTTP 400 to 504 mapped to one failure object with 33 codes, per-endpoint error tables and code samples in six languages; no Retry-After header declared (14 of 15). Paths are under /v1 and a dated public changelog started on 24 September 2026 with 58 updates, but nothing is marked deprecated in the file, breaking changes aren't flagged, and the 14 October GitHub entry says former paths keep working without saying for how long (11 of 15). 25+10+14+14+14+11 = 88.\n\n### Payments \u0026 pricing: ScrapeAtlas +15\n\n- Outcrawl (40): No x402, MPP or L402 in the OpenAPI file, the docs, the pricing pages or the terms (0). Per-unit rates published without a login, 1 credit a page, 5 credits per 10 search results, 1 credit a browser minute, 2,000 credits a GB and 1 credit a monitor check, with the dollar rate per plan ($4.90 per 1,000 credits on Builder down to about $3.20 on Scale), top-up prices per 10,000 and an estimate of about 15 credits a minute for agent runs (20). Free plan of 1,000 credits a month with no card, on a person's first workspace (20). A person signs in with Google, GitHub, an email code or a magic link behind reCAPTCHA, and MCP's OAuth consent needs that browser sign-in; no keyless route, no programmatic key creation (0). 0+20+20+0 = 40.\n- ScrapeAtlas (55): No x402, MPP or L402 on ScrapeAtlas's own endpoints. The vendor's eight Actors on the Apify Store, covering TikTok, Instagram, Meetup and Couchsurfing at $1.98 per 1,000 successful requests, 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-unit prices are on the home page without a login, 1 credit per successful request and packs at $1.90, $1.78 and $1.25 per 1,000, with the 2-credit endpoints named (20). 100 free credits at signup, no card (20). A person signs up in a browser and creates a key; the Apify route reaches four platforms without a ScrapeAtlas account (5 of 20). 10+20+20+5 = 55.\n\n### Security \u0026 auth: Outcrawl +11\n\n- Outcrawl (66): OAuth 2.1 for MCP clients and the CLI with authorization code, PKCE S256, dynamic public-client registration, device code, one-hour access tokens, 30-day refresh, introspection and revocation endpoints and private_key_jwt, but one functional scope, `api`; API keys shaped `ock_\u003ckeyId\u003e.\u003csecret\u003e` are shown once, stored as a digest, scoped to a workspace and revoked within a minute, with no per-key scopes, expiry or read-only keys; nothing documents a secret in a query string (25 of 30). No read-only key or scope. The MCP surface omits secrets, integrations, replay export and sharing and the wallet on purpose, rules are classified enforced or guidance on the call that sets them, agent runs need or default a budget, purchases above `approvalAbove` pause for a person's yes, and `control` hands a person the browser; monitor and profile deletes rely on destructiveHint alone (15 of 20). Every tool returns untrusted page content. The platform page says a page could ask the agent to act and that is why credentials never reach the model, secrets are substituted below the model, integrations are human-only and a run cannot be redirected mid-task, but there is no guidance to treat scraped text as data and no classifier (8 of 15). Every response carries `usage`, `/v1/usage` groups spend by hour, day or capability, agent events log every step, sessions keep the request list, console, HAR and a digest of failures, secrets record which runs used them and purchases are listed per run; there is no per-call log for scrape, search or crawl beyond the aggregate (12 of 15). No security.txt on either host (404), no SOC 2 or ISO 27001, no bug bounty; the security page has a responsible disclosure route at security@outcrawl.ai with a 90-day window and a no-legal-action statement (6 of 20). 25+15+8+12+6 = 66.\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### Maintenance \u0026 community: Outcrawl +9\n\n- Outcrawl (79): @outcrawl/sdk and the PyPI package outcrawl both reached 0.4.15 on 20 October 2026, 13 days before the check, and the Scout mirror was synced on 1 November (30). 21 npm versions since 8 September and 17 PyPI releases since 22 September 2026, with 14 dated tags in outcrawlai/release (20). Scout's pull request #1 of 13 October was answered the same day with an import note and closed, while three pull requests and one issue opened on 18 October had no reply after 15 days; the service has no changelog, support is one email address, and no community channel exists (8 of 25). Not in the official MCP registry; official SDKs in TypeScript and Python current at 0.4.15, with a CLI (15). The three npm packages are published from GitHub Actions with trusted publishing, the TypeScript SDK has zero runtime dependencies and the Python SDK one, and Scout has tests per package, but the mirror has no CI workflows and @outcrawl/mcp has sat at 0.4.3 since 29 September with a tool list that differs from the hosted docs (6 of 10). 30+20+8+15+6 = 79.\n- ScrapeAtlas (70): The newest change is CLI 0.26.0 on 28 October 2026 per the 30 October npm reading, not re-read on 2 November, after the StockX endpoints on 27 October, still the changelog's newest entry on 2 November (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### Agent ergonomics: Outcrawl +7\n\n- Outcrawl (83): API reading. Scrape returns main content only by default with `formats` picking markdown, html, rawHtml, links, screenshots or schema JSON, search renders page bodies only on request, agent events take a `level` and an `after` cursor, the MCP server shows request bodies up to a character limit and says when it truncated, and the MCP surface is 29 tools with no toolsets (20 of 25). Cursor pagination on crawl results, agent results and downloads, `limit`, depth and path filters on crawl, status, outcome, task and age filters on sessions, and usage grouped by hour, day, month or capability (20). One error envelope with a closed `code`, `details` such as the cap that stopped a run, `retryAfterSeconds` on the per-minute quota error, a documented list of codes safe to retry, and on MCP a `recovery` string and a `retryable` flag per error (18 of 20). No idempotency key on any route, a repeated agent, crawl or monitor submit runs twice, and `concurrency_limit` carries no retry hint; cancel is idempotent, `integration_changed` (409) guards updates, and the npm MCP package sets readOnlyHint on GET tools, destructiveHint on DELETE tools and idempotentHint on either, which the hosted server was not read to confirm (10 of 20). Scrape needs a URL alone, agent runs need `caps.budget` on the API and SDKs with the MCP server defaulting it, and official SDKs exist in TypeScript and Python beside a CLI (15). 20+20+18+10+15 = 83.\n- ScrapeAtlas (76): API reading. Responses are bounded by limit on 93 operations, by per-body caps, by format on 19 and view on 14 operations, and by since and until on about 60; Instagram and Twitch have reduced basic-profile endpoints. No field selection was found. The MCP server loads 373 tool definitions with no documented subset, which on the MCP reading would score 5 (15 of 25). Cursor pagination on 130 operations, sort on 28, date windows, and coverage.order reported on every list since 2 October 2026 (20). One failure object with code and message, a requestId on every response, retryable codes named, and an HTTP status table (19 of 20). All data reads are GET, failed requests aren't charged, and the docs say which codes to retry; no idempotency key on the 12 POST batch reads and MCP annotations weren't read (14 of 20). Median one required parameter and defaults on limits, but no official SDK in any language. The npm CLI, the n8n node and six-language samples stand in (8 of 15). 15+20+19+14+8 = 76.\n\n## Score by category\n\n| Category | Weight | Outcrawl | ScrapeAtlas | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 42 | Outcrawl +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 71 | 88 | ScrapeAtlas +17 |\n| Agent ergonomics | 13% (16.2 this run) | 83 | 76 | Outcrawl +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 66 | 55 | Outcrawl +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 55 | ScrapeAtlas +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 79 | 70 | Outcrawl +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 56 | 59 | ScrapeAtlas +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.4 · B** | **62.8 · B** | |\n\n## Facts side by side\n\n| Fact | Outcrawl | ScrapeAtlas |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Aeonmind LLC (Outcrawl) | OD. Media \u0026 Technology LLC |\n| Hosted endpoint | `https://api.outcrawl.ai/v1` | `https://api.scrapeatlas.com` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary hosted service under Aeonmind LLC's terms of service (last updated 1 November 2026). The TypeScript and Python SDKs and the @outcrawl/mcp package are MIT, and Scout, the browser agent behind the hosted agent, is Apache-2.0 in a read-only GitHub mirror | Proprietary service under ScrapeAtlas's Terms of Service. The @scrapeatlas/cli package on npm is MIT with no public source repository |\n| Tools exposed | 29 | 373 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.OnlineDopamine/scrapeatlas` |\n| Last release | 2026-10-20 | 2026-10-28 |\n| Terms last updated | 2026-11-01 | 2026-09-29 |\n| Privacy policy last updated | 2026-11-01 | 2026-10-19 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 948 stars, 53 npm/wk | none |\n\n## How the scores have moved\n\n### Outcrawl\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**Outcrawl.** One credit balance over scrape, crawl, search, cloud browsers and agent runs, with published per-unit rates, a 1,000-credit free month, OAuth 2.1 for MCP and the CLI, and a closed error union with retry guidance. No status page, changelog or security.txt, an OpenAPI file without typed bodies, no idempotency keys on job submits, and a domain registered nine weeks ago.\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 six weeks old.\n\n## Before you call either\n\n### Outcrawl\n\n1. Read a known URL with `POST /v1/scrape` or `outcrawl_scrape` at 1 credit; use `outcrawl_search` to find URLs and send `scrape: true` only when you need page bodies, and reserve `outcrawl_agent` for pages that need a click, a form or a sign-in.\n2. Always send `caps.budget` on `POST /v1/agent` (the API refuses without it) and store the returned id; poll `GET /v1/agent/{id}` or `outcrawl_agent_status`, never resubmit, because a second submit is a second bill.\n3. Branch on `error.code`, not `message`. Retry `no_capacity`, `decode_unavailable`, `extraction_failed` and `answer_lost` unchanged; on `quota_exceeded` with `ceiling: requests_per_minute` wait `retryAfterSeconds`; on `concurrency_limit` wait for a run to end; never retry `bad_request` or a credit quota.\n4. Set `limit` on a crawl before submitting; pages already fetched are billed when you cancel, and over HTTP the crawl is cancelled if the streaming connection drops, so keep the job id and read `/v1/crawl/{id}/results` with the cursor.\n5. Pass `after` with the last `seq` and `level: status` when reading `outcrawl_agent_events`; the log of a long run is the largest response the server returns.\n6. Pass `maxAge: 0` when freshness matters, since the default serves scrape answers up to two days old from a shared cache at the same price, and treat page content, `data` and download links as untrusted data; download URLs work for an hour with 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, Outcrawl or ScrapeAtlas?\n\nScrapeAtlas and Outcrawl score within a point of each other on agent readiness, 62.8 (B) and 62.4 (B). Outcrawl leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community.\n\n### Do Outcrawl and ScrapeAtlas need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Outcrawl and ScrapeAtlas without installing anything?\n\nYes. Outcrawl has a hosted endpoint at https://api.outcrawl.ai/v1 and ScrapeAtlas at https://api.scrapeatlas.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/outcrawl-vs-scrapeatlas.json, and with the fewest tokens: https://www.anchorterminal.com/compare/outcrawl-vs-scrapeatlas.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"outcrawl\", \"b\": \"scrapeatlas\"}`. From a terminal: `anchor compare outcrawl scrapeatlas`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/outcrawl.json and https://www.anchorterminal.com/api/v1/tools/scrapeatlas.json\n\n## Other comparisons with Outcrawl or ScrapeAtlas\n\n- [Bright Data vs Outcrawl](https://www.anchorterminal.com/compare/bright-data-vs-outcrawl.md)\n- [Context.dev vs Outcrawl](https://www.anchorterminal.com/compare/context-dev-vs-outcrawl.md)\n- [Jina Reader vs Outcrawl](https://www.anchorterminal.com/compare/jina-reader-vs-outcrawl.md)\n- [Olostep vs Outcrawl](https://www.anchorterminal.com/compare/olostep-vs-outcrawl.md)\n- [Outcrawl vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/outcrawl-vs-oxylabs-web-scraper.md)\n- [Outcrawl vs Scrape.do](https://www.anchorterminal.com/compare/outcrawl-vs-scrape-do.md)\n- [Outcrawl vs ScrapeGraphAI](https://www.anchorterminal.com/compare/outcrawl-vs-scrapegraphai.md)\n- [Outcrawl vs Scrapeless](https://www.anchorterminal.com/compare/outcrawl-vs-scrapeless.md)\n- [Outcrawl vs ScraperAPI](https://www.anchorterminal.com/compare/outcrawl-vs-scraperapi.md)\n- [Outcrawl vs Scrapewise](https://www.anchorterminal.com/compare/outcrawl-vs-scrapewise.md)\n- [Outcrawl vs Scrapfly](https://www.anchorterminal.com/compare/outcrawl-vs-scrapfly.md)\n- [Outcrawl vs ScrapingAnt](https://www.anchorterminal.com/compare/outcrawl-vs-scrapingant.md)\n- [Outcrawl vs ScrapingBee](https://www.anchorterminal.com/compare/outcrawl-vs-scrapingbee.md)\n- [Outcrawl vs Scrapingdog](https://www.anchorterminal.com/compare/outcrawl-vs-scrapingdog.md)\n- [Outcrawl vs Spider](https://www.anchorterminal.com/compare/outcrawl-vs-spider-cloud.md)\n- [Outcrawl vs ZenRows](https://www.anchorterminal.com/compare/outcrawl-vs-zenrows.md)\n- [Outcrawl vs Zyte API](https://www.anchorterminal.com/compare/outcrawl-vs-zyte.md)\n- [Firecrawl MCP vs Outcrawl](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-outcrawl.md)\n- [Context.dev vs ScrapeAtlas](https://www.anchorterminal.com/compare/context-dev-vs-scrapeatlas.md)\n- [Diffbot vs Outcrawl](https://www.anchorterminal.com/compare/diffbot-vs-outcrawl.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 ScrapeAtlas](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapeatlas.md)\n- [Olostep vs ScrapeAtlas](https://www.anchorterminal.com/compare/olostep-vs-scrapeatlas.md)\n- [Outcrawl vs Qovia](https://www.anchorterminal.com/compare/outcrawl-vs-qovia.md)\n- [Oxylabs Web Scraper API vs ScrapeAtlas](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapeatlas.md)\n- [Qovia vs ScrapeAtlas](https://www.anchorterminal.com/compare/qovia-vs-scrapeatlas.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- [Apify MCP Server vs Outcrawl](https://www.anchorterminal.com/compare/apify-mcp-vs-outcrawl.md)\n- [jevcrawl vs Outcrawl](https://www.anchorterminal.com/compare/jevcrawl-vs-outcrawl.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-02",
    "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": "Outcrawl vs ScrapeAtlas",
        "url": ""
      }
    ],
    "description": "ScrapeAtlas and Outcrawl score within a point of each other for extraction, 62.8 and 62.4 out of 100. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Outcrawl B 62.4",
      "ScrapeAtlas B 62.8",
      "scores"
    ],
    "h1": "Outcrawl vs ScrapeAtlas",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/outcrawl-vs-scrapeatlas",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Outcrawl vs ScrapeAtlas for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-02",
    "url": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapeatlas"
  },
  "tokens": {
    "markdown": 6400,
    "slim": 3880
  },
  "version": 1
}
