# ScrapeAtlas > 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. - Canonical: https://www.anchorterminal.com/tools/scrapeatlas - Pricing: https://www.anchorterminal.com/tools/scrapeatlas#pricing - Reviews: https://www.anchorterminal.com/tools/scrapeatlas#reviews - Markdown: https://www.anchorterminal.com/tools/scrapeatlas.md (~9,800 tokens) - Slim: https://www.anchorterminal.com/tools/scrapeatlas.min.md (~2,430 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/scrapeatlas.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-10-30 ## Overview **Grade B · 63/100 · rank #481 of 1226 · #12 in Web scraping & crawling · not agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | OD. Media & Technology LLC (https://scrapeatlas.com) | | Kind | HTTP API | | Category | Web scraping & crawling (https://www.anchorterminal.com/categories/web-scrapers) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://api.scrapeatlas.com` | | Auth | OAuth or key · 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 | Pay per use ($1.90 / 1k req) · 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. | | x402 | No · 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. | | Licence | Proprietary service under ScrapeAtlas's Terms of Service. The @scrapeatlas/cli package on npm is MIT with no public source repository | | Tools exposed | 373 | | Packages | npm: `@scrapeatlas/cli`; npm: `n8n-nodes-scrapeatlas` | | MCP registry name | `io.github.OnlineDopamine/scrapeatlas` | | Docs | https://scrapeatlas.com/docs/ | | llms.txt | https://scrapeatlas.com/docs/llms.txt | | Last release | 2026-10-28 | | Surface listed | The REST API at https://api.scrapeatlas.com, the @scrapeatlas/cli command-line tool and the hosted MCP server at https://api.scrapeatlas.com/mcp, read from the docs, the OpenAPI file, llms.txt, the MCP page, the changelog, the legal pages, npm, the MCP registry and the Apify Store on 30 October 2026. No account was created, no API call or MCP session was made, and the OAuth metadata on api.scrapeatlas.com was the only thing read from that host | | API | OpenAPI 3.1.0, version 0.1.0, 384 paths and 386 operations (374 GET, 12 POST). 371 platform data operations across 49 platforms, from 18 on TikTok and 17 on YouTube to 1 each on Kick, Komi, Linkme, Lnk.Bio and Pillar; 2 account operations; 10 MCP OAuth and 3 dashboard operations. The file is 34 MB | | Response envelope | `success`, `status` (success, partial, failed, challenged), `requestId`, `accounting` {upstreamRequests, responseBytes, durationMs}, `sourceUrl`, `fetchedAt` and `coverage` {source, complete, warnings, order, window}. Unknown metrics are `null` | | Credentials | Customer key with prefix `sa_live_` in `x-api-key` or `Authorization: Bearer`. Several keys per account on one balance, expiry dates, revocation within 60 seconds, stored as hashes. No scopes. Keys can't start a checkout or create keys. MCP also takes OAuth authorization code with PKCE S256, dynamic client registration, refresh-token rotation, revocation, scope `scrapeatlas`; access tokens last one hour and grants 30 days per the privacy policy | | Rate limits | 120 requests a minute and 4 concurrent requests per account. 429 with `retry-after` when the account or a source platform rate-limits; 503 `busy` when retrieval slots are full or a platform is unavailable. Per-worker caps such as a 60-second deadline and 24 MiB of decoded responses per operation on LinkedIn, 90 seconds on TikTok | | Pagination | `cursor` on 130 operations, `limit` on 93, `since` on 60 and `until` on 57, `sort` on 28, `format` on 19 and `view` on 14. Platform-native tokens elsewhere (`pageToken`, `next_max_id`, `pagination_token`). Lists report `coverage.order` since 2 October 2026 | | Errors | HTTP 400, 401, 402, 403, 404, 408, 413, 422, 429, 502, 503 and 504 mapped to one `failure` {code, message} object with 33 codes, 13 of them on every worker. The docs say to retry only on `upstream_rate_limited`, `timeout` and `busy`. No Retry-After header is declared in the OpenAPI file | | MCP | Streamable HTTP at https://api.scrapeatlas.com/mcp, labelled Preview. 373 tools generated from the endpoint catalogue, each with inputSchema and outputSchema; results carry httpStatus, the endpoint body and credit metadata in structuredContent and text. Listed in the official MCP registry as io.github.OnlineDopamine/scrapeatlas 1.0.0 (5 October 2026). Tool annotations not checked | | CLI and integrations | @scrapeatlas/cli 0.26.0 on npm (28 October 2026, MIT, Node 22 or newer), 18 versions since 0.1.0 on 12 September. `scrapeatlas ` or `scrapeatlas call `, a bundled endpoint catalogue with `list --json`, no automatic retries or pagination, keys stored in plaintext in the config file. n8n-nodes-scrapeatlas 0.1.0 (30 September). Eight Actors on the Apify Store (TikTok, Instagram, Meetup, Couchsurfing). No SDKs; code samples in six languages | | Credits | 100 free at signup, no card. Packs of 10,000 for $19, 50,000 for $89 and 200,000 for $249, one-time, never expiring. 1 credit per successful request including partial results and valid empty collections; 2 on `/v1/linkedin/search/posts`, the six Quora search endpoints and `/v1/threads/search/users`. Failed requests, account utilities and internal retries cost 0. The OpenAPI checkout operation and the affiliate page name only the 10,000 and 50,000 packs | | SLA | None. The terms (29 September 2026) say ScrapeAtlas does not promise a particular uptime, throughput, response time, data accuracy or continued availability of an endpoint unless a separate signed agreement says otherwise | | Data handling | Retrieval workers keep no cache or archive of results. Raw usage, activity and proxy-performance records expire within 90 days, inactive key metadata 30 days after expiry or revocation. Usage records exclude search text, handles, URLs and response content. Providers named are Supabase, Tinybird, PostHog, Stripe, Google (fonts, analytics), OpenAI (ad measurement) and Affonso (referrals). The operator is in the UAE and infrastructure can process in other countries; no DPA is published | | Status | No status page found. https://scrapeatlas.com/status/ answers 404 and the docs and footer link none | | 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 | | JSON | https://www.anchorterminal.com/api/v1/tools/scrapeatlas.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-10-30 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 42 | 8.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 88 | 14.3 | | Agent ergonomics | 13% | 16.2 | 76 | 12.3 | | Security & auth | 14% | 17.5 | 55 | 9.6 | | Payments & pricing | 10% | 12.5 | 55 | 6.9 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 70 | 6.1 | | Transparency & trust (editorial 54, provenance 67) | 7% | 8.8 | 61 | 5.3 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **63 → B** | ### Why each score - Reliability 42 (checked 2026-10-30): Hosted reading, for the REST API with the MCP server described. No public status page was found. https://scrapeatlas.com/status/ answers 404 and neither the docs nor the footer links one (0). No readable incident history, so 5 by the rubric (5). Limits are published with numbers on the authentication page, 120 requests a minute and 4 concurrent requests per account, with per-worker deadlines and byte caps on the platform pages (15). A 429 is documented for account and upstream limits with a retry-after to respect, 503 busy for full capacity, and the responses page says to retry only on upstream_rate_limited, timeout or busy. No Retry-After header is declared in the OpenAPI file and the CLI does no automatic retries. Writes don't exist, the 12 POST operations are batch reads, so idempotency keys aren't needed (12 of 15). No SLA. The terms (29 September 2026) say no particular uptime, throughput or continued availability is promised unless a separate signed agreement says otherwise (0). The API is sold and listed as available on every platform page, with 15 of 386 operations saying preview in their descriptions; the MCP server is labelled Preview and scored under the API (10). 0+5+15+12+0+10 = 42. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 88 (checked 2026-10-30): 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. - Agent ergonomics 76 (checked 2026-10-30): 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. - Security & auth 55 (checked 2026-10-30): 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. - Payments & pricing 55 (checked 2026-10-30): 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. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 70 (checked 2026-10-30): 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. - Transparency & trust 61 (checked 2026-10-30): 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. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (22 items): https://www.anchorterminal.com/fixes/scrapeatlas.md (JSON https://www.anchorterminal.com/fixes/scrapeatlas.json) ### What we couldn't check - unchecked: MCP tool annotations (readOnlyHint and the rest), the tool list's size in tokens and whether tools/list is paged. No MCP session was opened, so the 373-tool count is the MCP page's figure, which matches the 371 platform and 2 account operations in the OpenAPI file. - unchecked: whether the Apify Store Actors are Pay Per Event Actors payable by direct x402, and whether Apify's prepaid token covers them. The payments score gives 10 of 40 for that third-party route on the vendor's own Apify profile, which says no ScrapeAtlas account or key is needed. - unchecked: the OAuth consent flow in practice. The MCP page says OAuth-only connectors are unsupported in the preview, while llms.txt and the privacy policy describe browser OAuth consent for ChatGPT and other clients, and the authorization server metadata publishes registration, authorization, token and revocation endpoints with PKCE S256. - The 200,000-credit pack at $249 is on the home page, but the OpenAPI checkout operation and the affiliate page name only the 10,000 and 50,000 packs. Recorded, not deducted. - No Retry-After header is declared in the OpenAPI file; the docs say to respect retry-after and the CLI envelope has a retryAfter field. Whether the header is sent wasn't observed. - The Apify profile reports 15 total users and 84.9 per cent of runs succeeded, read on 30 October 2026; no success rate for the API itself is published. - The vendor's 373 endpoint tools and 50 catalogued platforms on the MCP page count the two account operations and the account-usage group; the home page says 49 platforms and 371 endpoints, and both agree with the OpenAPI file. The registry entry's 'about 40 platforms' is stale. - firstReleased is set to 21 September 2026, the changelog's first entry and the day CLI 0.10.0 shipped every endpoint as a command and an MCP tool. The domain was registered on 10 September and the 11 September capture says self-service access wasn't open, so a signup date between 11 and 21 September is possible but not shown. - The product is about five weeks old, so the maintenance and transparency scores rest on a short record by the checklist, not on guesswork about where it goes. - The MCP registry namespace and the npm packages are published from a personal GitHub account rather than a company organisation. Recorded in provenance notes; no deduction. - ScrapeAtlas doesn't do LocalGhost's or letme's job. It returns platform data for an agent to use; it neither hides an agent's identity nor chooses tools for a task. ### Sources - home page with pricing and FAQ: (seen 2026-10-30) - docs overview and platform index: (seen 2026-10-30) - OpenAPI 3.1 file: (seen 2026-10-30) - llms.txt: (seen 2026-10-30) - authentication, limits and credit headers: (seen 2026-10-30) - errors and responses: (seen 2026-10-30) - CLI guide: (seen 2026-10-30) - n8n guide: (seen 2026-10-30) - MCP page: (seen 2026-10-30) - LinkedIn platform page (worker limits): (seen 2026-10-30) - LinkedIn post search endpoint (2 credits): (seen 2026-10-30) - TikTok profile endpoint: (seen 2026-10-30) - playground: (seen 2026-10-30) - changelog: (seen 2026-10-30) - about page: (seen 2026-10-30) - contact page: (seen 2026-10-30) - careers page: (seen 2026-10-30) - affiliate page: (seen 2026-10-30) - Terms of Service: (seen 2026-10-30) - privacy policy: (seen 2026-10-30) - Public Data Notice: (seen 2026-10-30) - sitemap: (seen 2026-10-30) - OAuth protected resource metadata: (seen 2026-10-30) - OAuth authorization server metadata: (seen 2026-10-30) - npm, @scrapeatlas/cli: (seen 2026-10-30) - npm search, n8n node: (seen 2026-10-30) - official MCP registry: (seen 2026-10-30) - Apify Store profile: (seen 2026-10-30) - RDAP for scrapeatlas.com: (seen 2026-10-30) - Wayback Machine capture of 11 September 2026: (seen 2026-10-30) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/scrapeatlas/history.json - 2026-10-30: graded 63 B (methodology 0.7) ## Who's behind it (provenance 67/100, checked 2026-10-30) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | OD. Media & Technology LLC | 20/20 | | Domain age | scrapeatlas.com, registered 2026-09-10 (under a year) | 0/15 | | Endpoint on the vendor's domain | api.scrapeatlas.com | 15/15 | | Terms of service | published | 10/10 | | Privacy policy | published | 10/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | | People named | 2 named with their role, none with a public profile | 7/10 | | Support route | a support address, help pages, a community | 5/5 | 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 & 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://scrapeatlas.com/terms/), not read yet. **Privacy policy** (https://scrapeatlas.com/privacy/), not read yet. ## Humans behind the project (researched 2026-10-30 from public pages, not part of the grade) ### Key people - Viktor, Co-founder - Fekri, Co-founder - Note: the about page names the founders as viktor and fekri, first names only, and no page on scrapeatlas.com gives a surname, so none is recorded. the careers page gives a scrapeatlas.com mailbox for viktor for job applications, not listed here. no linkedin or x account for either person is linked from the site. the npm packages (@scrapeatlas/cli, n8n-nodes-scrapeatlas) and the official mcp registry entry are published from a personal github account whose profile name is viktor and which holds a scrapeatlas example repository, but the site doesn't link it, so it isn't attached to a person. genviral.io's home page names nobody. no company linkedin, x or github organisation was found; the site links a youtube channel. investors were looked for on scrapeatlas.com (about, careers, affiliate, contact, changelog, terms, privacy, the sitemap, which has no blog or press section), on genviral.io's home page, and in web searches for scrapeatlas funding and for the legal entity, which returned only directory pages and nothing on a round. the roster of two founders comes from the company's own page and may be complete; the careers page lists three open roles. ### Getting support - Support email: admin@fddigital.net - Help: https://scrapeatlas.com/contact/ - Help: https://scrapeatlas.com/docs/ - Community (YouTube channel): https://www.youtube.com/@ScrapeAtlas - Sources: https://scrapeatlas.com/about/, https://scrapeatlas.com/careers/, https://scrapeatlas.com/contact/, https://scrapeatlas.com/terms/, https://scrapeatlas.com/privacy/, https://scrapeatlas.com/affiliate/, https://scrapeatlas.com/sitemap.xml, https://scrapeatlas.com/, https://www.genviral.io/, https://registry.npmjs.org/@scrapeatlas%2Fcli, https://registry.modelcontextprotocol.io/v0/servers?search=scrapeatlas ## Live (updated 2026-10-30 13:20 UTC) - Right now: up, HTTP 404, 159 ms, checked 2026-10-30 13:20 UTC (get on `https://api.scrapeatlas.com`) - Uptime 24h 100.0% (17 probes) · 30 days 100.0% (17 probes) · p50 162 ms · p95 243 ms - Always current: https://www.anchorterminal.com/api/v1/live/scrapeatlas.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | 10,000-credit pack | $1.90 | per 1,000 requests | $19 one-time, 1 credit per successful request, home page checked 30 October 2026 | | 50,000-credit pack | $1.78 | per 1,000 requests | $89 one-time | | 200,000-credit pack | $1.25 | per 1,000 requests | $249 one-time; not named in the OpenAPI checkout operation or on the affiliate page | | Apify Store Actors | $1.98 | per 1,000 requests | successful requests, paid through Apify, no ScrapeAtlas account; TikTok, Instagram, Meetup and Couchsurfing only | Across all listings: https://www.anchorterminal.com/prices/index.md ## 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 ## Before you call it (notes for agents) 1. 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`. 2. 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. 3. 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. 4. Each platform has its own response schema, so read the endpoint's response fields before mapping; unknown values are `null`, never 0. 5. 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. ## Connect Install: ```bash npm install -g @scrapeatlas/cli ``` First request: ```bash curl "https://api.scrapeatlas.com/v1/bluesky/profile?handle=bsky.app" -H "x-api-key: $SCRAPEATLAS_API_KEY" ``` Through letme: https://letme.dev/scrapeatlas. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Browser Use | A | 80.3 | 7 | web.extract | yes | https://www.anchorterminal.com/tools/browser-use.md | | ZenRows | A | 78.9 | 13 | web.extract | no | https://www.anchorterminal.com/tools/zenrows.md | | Context.dev | A | 78.3 | 19 | web.extract | no | https://www.anchorterminal.com/tools/context-dev.md | | Firecrawl MCP | A | 78 | 22 | web.extract | no | https://www.anchorterminal.com/tools/firecrawl-mcp.md | | Tavily API + MCP | BB | 77 | 36 | web.extract | no | https://www.anchorterminal.com/tools/tavily-mcp.md | | You.com APIs | BB | 75.9 | 48 | web.extract | no | https://www.anchorterminal.com/tools/you-com-api.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The OpenAPI 3.1 file has 384 paths and 386 operations, 374 GET and 12 POST. 371 read platform data across 49 platforms, 2 report account usage and activity, 10 describe the MCP OAuth flow and 3 the dashboard. Each platform has its own `x-api-key` security scheme (source: ) - Every response carries `success`, `status` (success, partial, failed or challenged), `requestId`, `accounting` (upstream requests, bytes, milliseconds) and `coverage` with warnings, and failures share one `failure.code` vocabulary of 33 codes (source: ) - Limits are 120 requests a minute and 4 concurrent requests per account, with 429 and a `retry-after` to respect, and 503 `busy` when capacity or a platform is unavailable. Responses carry `x-credits-charged` and `x-credits-remaining` (source: ) - `GET /v1/usage` and `GET /v1/activity` return daily totals and per-request metadata (endpoint, time, status) for the account at 0 credits, filterable by window, platform, operation and status (source: ) - The hosted MCP server at api.scrapeatlas.com/mcp is labelled Preview and lists 373 tools, one per endpoint plus the two account tools, each with inputSchema and outputSchema; no toolsets or subsets are documented (source: ) - The changelog runs from 21 September to 27 October 2026, 58 updates on 15 release days, and the domain was registered on 10 September 2026, so the product is about five weeks old (source: ) - No status page was found (/status answers 404 and none is linked), no security.txt, and the terms promise no uptime, throughput or continued availability of an endpoint (source: ) - The privacy policy (19 October 2026) keeps raw usage records at most 90 days and no archive of retrieved content, and names Supabase, Tinybird, PostHog, Stripe, Google, OpenAI and Affonso as providers (source: ) - #12 of 22 in Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md - All 242 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md ## Compare - [Context.dev vs ScrapeAtlas](https://www.anchorterminal.com/compare/context-dev-vs-scrapeatlas.md): A 78.3 vs B 63 - [Diffbot vs ScrapeAtlas](https://www.anchorterminal.com/compare/diffbot-vs-scrapeatlas.md): C 54.3 vs B 63 - [Firecrawl MCP vs ScrapeAtlas](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapeatlas.md): A 78 vs B 63 - [jevcrawl vs ScrapeAtlas](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapeatlas.md): B 64.3 vs B 63 - [Olostep vs ScrapeAtlas](https://www.anchorterminal.com/compare/olostep-vs-scrapeatlas.md): B 63.1 vs B 63 - [Oxylabs Web Scraper API vs ScrapeAtlas](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapeatlas.md): B 63.1 vs B 63 - [ScrapeAtlas vs ScrapeGraphAI](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapegraphai.md): B 63 vs B 68.3 - [ScrapeAtlas vs ScraperAPI](https://www.anchorterminal.com/compare/scrapeatlas-vs-scraperapi.md): B 63 vs D 52.1 - [ScrapeAtlas vs Scrapewise](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapewise.md): B 63 vs B 62.6 - [ScrapeAtlas vs Scrapfly](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapfly.md): B 63 vs B 69.6 - [ScrapeAtlas vs ScrapingAnt](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingant.md): B 63 vs F 35.8 - [ScrapeAtlas vs ScrapingBee](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingbee.md): B 63 vs C 59.4 - [ScrapeAtlas vs Scrapingdog](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapingdog.md): B 63 vs E 39.3 - [ScrapeAtlas vs Spider](https://www.anchorterminal.com/compare/scrapeatlas-vs-spider-cloud.md): B 63 vs BB 75.4 - [ScrapeAtlas vs ZenRows](https://www.anchorterminal.com/compare/scrapeatlas-vs-zenrows.md): B 63 vs A 78.9 - [ScrapeAtlas vs Zyte API](https://www.anchorterminal.com/compare/scrapeatlas-vs-zyte.md): B 63 vs B 69.7 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on scrapeatlas.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "scrapeatlas", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html ScrapeAtlas on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![ScrapeAtlas on Anchor Terminal](https://www.anchorterminal.com/badges/scrapeatlas.svg)](https://www.anchorterminal.com/tools/scrapeatlas) ``` Plain link: ```html ScrapeAtlas on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say ScrapeAtlas is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/scrapeatlas-dark.png - Light: https://www.anchorterminal.com/assets/share/scrapeatlas-light.png - Create a video and download its frames: https://www.anchorterminal.com/assets/listing-video/index.html?listing=scrapeatlas --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp