# ScraperAPI > Web scraping API that fetches a URL through rotating proxies with optional JavaScript rendering and anti-bot bypass, and returns HTML, Markdown, text or parsed JSON. It has async jobs, a crawler, structured data endpoints and an MCP server. - Canonical: https://www.anchorterminal.com/tools/scraperapi - Markdown: https://www.anchorterminal.com/tools/scraperapi.md (~7,000 tokens) - Slim: https://www.anchorterminal.com/tools/scraperapi.min.md (~1,530 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/scraperapi.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 - Updated: 2026-10-10 ## Overview **Grade D · 52.1/100 · rank #739 of 950 · #14 in Web scraping & crawling · not agent-ready · confidence medium** ## Assessment One GET request with a key and a URL returns a page, and the MCP server's 28 tools carry read-only and destructive hints. No status page, OpenAPI file, security.txt or certification was found, and the documented default puts the API key in the URL query string. ## Facts | Field | Value | | --- | --- | | Vendor | ScraperAPI (saas.group) (https://www.scraperapi.com) | | Kind | HTTP API | | Category | Web scraping & crawling (https://www.anchorterminal.com/categories/web-scrapers) | | Transport | HTTP, Streamable HTTP, stdio | | Endpoint | `https://api.scraperapi.com` | | Auth | API key · Self-serve API key from the dashboard after a browser signup. The sync API takes it as the `api_key` query parameter by default or as an `x-sapi-api_key` header. The async, crawler and AI parser APIs take it in the JSON body, and the remote MCP server takes `Authorization: Bearer`. One key per account, regenerated at most once every 24 hours, with no scopes. | | Pricing | Freemium ($49 / mo) · Free plan of 1,000 credits a month with 5 concurrent threads, and 5,000 credits for the first 7 days, no card. Hobby $49 a month (100,000 credits, 20 threads), Startup $149 (1 million, 50), Business $299 (3 million, 100), Scaling $475 (5 million, 200), Professional $975 (10.5 million, 300), Advanced $1,975 (21.5 million, 500), Enterprise custom. Annual billing takes 10% off. A plain request costs 1 credit, rendering or premium proxies 10, Google and Bing 25. Only 200 and 404 responses are charged. Pay-as-you-go overage starts at Scaling (https://www.scraperapi.com/pricing/). | | x402 | No · No x402, MPP or L402 in the docs index, the pricing page or llms.txt (checked 2026-10-09). | | Licence | unknown | | Tools exposed | 28 | | Packages | pypi: `scraperapi-mcp-server`; pypi: `scraperapi-sdk`; npm: `scraperapi-sdk`; npm: `scraperapi-cli` | | Docs | https://docs.scraperapi.com/ | | llms.txt | https://docs.scraperapi.com/llms.txt | | Last release | 2026-08-07 | | GitHub stars | 5 (as of 2026-10-09) | | Endpoints | `GET https://api.scraperapi.com` (sync), `POST https://async.scraperapi.com/jobs` (async, up to 50,000 URLs a batch), `https://api.scraperapi.com/structured//` (parsed JSON), `POST https://crawler.scraperapi.com/job` (crawler), an AI parser API and a proxy port | | MCP server | Remote at `https://mcp.scraperapi.com/mcp` with a Bearer header, or local from the `scraperapi-mcp-server` Python package or Docker. 28 tools covering scrape, Google, Amazon, Walmart, eBay, Redfin, the crawler and the AI parser | | Free tier | 1,000 credits a month, 5 concurrent threads, no card. 5,000 credits for the first 7 days | | Concurrency | 20 threads on Hobby, 50 Startup, 100 Business, 200 Scaling, 300 Professional, 500 Advanced. Over the limit returns 429 with no charge | | Retention | Activity logs 7 days, async results up to 72 hours, DataPipeline results 30 days | | Access | Self-serve key after a browser signup. No sales approval below Enterprise | | Capabilities | web.scrape, web.extract, web.crawl, scraping.proxies, scraping.js-render, scraping.anti-bot, scraping.screenshot, scraping.serp | | Tags | hosted, freemium, free-tier, no-card, api-key, mcp, llms-txt, proxies, async-jobs, webhooks, cli, python, javascript, php, ruby, java, closed-source | | JSON | https://www.anchorterminal.com/api/v1/tools/scraperapi.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 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 | 45 | 9.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 67 | 10.9 | | Agent ergonomics | 13% | 16.2 | 74 | 12.0 | | Security & auth | 14% | 17.5 | 29 | 5.1 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 61 | 5.3 | | Transparency & trust (editorial 35, provenance 72) | 7% | 8.8 | 54 | 4.7 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **52.1 → D** | ### Why each score - Reliability 45: No status page is linked from the home, pricing, support or docs pages we read (0). No readable incident history (5). Concurrency limits are published per plan, 5 threads on Free, 20 on Hobby, 50, 100, 200, 300 and 500 above it, and the local MCP server limits itself to 10 calls in 60 seconds (15). 429 is documented as a concurrency rejection with no charge, the API retries a target for up to 70 seconds before returning 500, and the docs tell clients to retry failed requests. No Retry-After header or idempotency key was found (10 of 15). The pricing page lists a 99.9% uptime guarantee on every plan, with no SLA document or credit terms found, and the Terms of Use were unread (5 of 10). The API, async service and crawler are generally available (10). - 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 67: No OpenAPI file found. The MCP server's source defines typed pydantic inputs for all 28 tools (12 of 25). The docs publish llms.txt, llms-full.txt and a Markdown twin of every page (10). MCP tool descriptions state when to use a tool and when not to, and the API reference describes each parameter with its credit cost (15 of 20). MCP inputs use enums for device type and output format. The HTTP API's parameters are query strings described in prose tables (10 of 15). Examples in cURL, Python, Node.js, PHP, Ruby and Java, a status code table that says which codes are billed, and an error table for the AI parser (12 of 15). Release notes are grouped by month without day dates, the HTTP API has no version, and the MCP server uses semver tags (8 of 15). - Agent ergonomics 74: 28 MCP tools with no toolsets or dynamic loading (15 of 25). `output_format` returns Markdown or text, `autoparse` returns JSON on supported domains, structured endpoints page their results, and `max_cost`, `crawl_budget` and `max_depth` cap a job (15 of 20). Errors are HTTP status codes with plain-text messages. No machine-readable error codes (13 of 20). All 28 MCP tools carry readOnlyHint, destructiveHint, idempotentHint and openWorldHint, failed requests are not charged, and async jobs return a status URL to poll (16 of 20). Only `api_key` and `url` are required, rendering is off by default, and SDKs are documented for Python, Node.js, PHP, Ruby and Java (15). - Security & auth 29: One API key per account, regenerated from the dashboard at most once every 24 hours. No scopes (20). The documented default puts the key in the URL query string, so less 10, although an `x-sapi-api_key` header and a Bearer header on the remote MCP server exist (10 of 30). No read-only or restricted keys. `max_cost`, a monthly pay-as-you-go spending cap and destructive hints on the two MCP delete tools limit damage (6 of 20). The API returns untrusted web content and no prompt-injection guidance was found in the docs, the MCP README or the skills (2 of 15). The dashboard has analytics with error logs, each response carries `sa-credit-cost`, and the privacy policy says activity logs are deleted after 7 days (9 of 15). `/.well-known/security.txt` returned 404, and no disclosure policy, bug bounty or certification was found. The home page claims CCPA and GDPR compliance (2 of 20). - Payments & pricing 40: No x402, MPP or L402 found in the docs index or pricing page (0). Plan prices and credit costs per request type are public without a login (20). Free plan of 1,000 credits a month and a 7-day trial of 5,000 credits, no card (20). A person signs up in a browser to get a key (0). - 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 61: The skills plugin was last updated on 7 August 2026, 63 days before the check, and the MCP server's v1.1.1 is from 17 July 2026 (20 of 30). MCP v1.1.0 and v1.1.1 on 17 July and the plugin update on 7 August fall within 90 days, with two July 2026 release notes dated by month only (20). Monthly release notes and support through the dashboard and email. We did not read the repository's issues (8 of 15). SDKs are documented for five languages, but we did not check their release dates, and the MCP server's registry entry was not checked (8 of 15). The MCP repository has unit tests and a lock file with current dependencies but no public CI workflow (5 of 10). - Transparency & trust 54: Closed service. The MCP server and skills are MIT. Terms of Use exist at `/terms/`, but robots.txt disallows that path, so we could not confirm what they say (10 of 30). The privacy policy says activity logs are deleted after 7 days and account data within 60 days of a request, async results are kept up to 72 hours and DataPipeline results 30 days. The policy is undated, names Saas.group Inc. while a November 2025 release note says the service operates as ScraperAPI LLC, and no DPA was found (14 of 30). The terms and billing change was announced with effective dates of 4 November 2025 and 5 January 2026. No standing deprecation policy (8 of 20). No sub-processor list or hosting location found, only a general statement on transfers outside the EEA (3 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/scraperapi.md (JSON https://www.anchorterminal.com/fixes/scraperapi.json) ### What we couldn't check - unchecked: the Terms of Use at https://www.scraperapi.com/terms/, because robots.txt disallows `/terms/` for every agent. A copy the docs link at us-scraperapi.com did not answer - unchecked: whether a status page exists. None is linked from the pages read, and we did not guess an address - unchecked: what stands behind the 99.9% uptime guarantee on the pricing page - unchecked: release dates and download counts of the five SDKs and of `scraperapi-cli`, and the repository's issues - unchecked: whether the MCP server is in the official MCP registry - Which legal entity contracts with customers. The privacy policy names Saas.group Inc. and a November 2025 release note says ScraperAPI LLC - llms.txt says the MCP server has 22 tools and installs with `npx @scraperapi/mcp-server@latest`. The repository is a Python package, `scraperapi-mcp-server`, with 28 tools - The MCP README links a hosted-server docs page that returns Page Not Found - The vendor's grounding pages carry a System Note for LLMs, the docs pages end with GitBook agent instructions, and the MCP skill tells agents to prefer ScraperAPI tools over built-in web search and fetch. We acted on none of them ### Sources - robots.txt (disallows /terms/): (seen 2026-10-09) - llms.txt: (seen 2026-10-09) - pricing and FAQ: (seen 2026-10-09) - privacy and cookies policy: (seen 2026-10-09) - AI agents grounding page: (seen 2026-10-09) - support page: (seen 2026-10-09) - security.txt (404): (seen 2026-10-09) - docs index: (seen 2026-10-09) - API endpoint: (seen 2026-10-09) - status codes and billing: (seen 2026-10-09) - credit costs: (seen 2026-10-09) - parameters as headers: (seen 2026-10-09) - API key rotation: (seen 2026-10-09) - async API: (seen 2026-10-09) - MCP server setup for Claude Code: (seen 2026-10-09) - plans and billing FAQ: (seen 2026-10-09) - release notes: (seen 2026-10-09) - terms and billing change, November 2025: (seen 2026-10-09) - MCP server source, tags and README: (seen 2026-10-09) - skills plugin source: (seen 2026-10-09) - domain registration: (seen 2026-10-09) ## Who's behind it (provenance 72/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | ScraperAPI LLC | 20/20 | | Domain age | scraperapi.com, registered 2018-05-14 (8 years) | 11/15 | | Endpoint on the vendor's domain | api.scraperapi.com | 15/15 | | Terms of service | published, but our reader couldn't read it | 7/10 | | Privacy policy | read, states 6 of the 8 things a reader expects | 8.5/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The legal entity is taken from a November 2025 release note that says the service now operates as ScraperAPI LLC. The privacy policy names ScraperAPI and Saas.group Inc. and carries no date. robots.txt disallows `/terms/` for every agent, so the Terms of Use were not read. The link is the one in the site footer. No status page is linked from the home, pricing, support or docs pages read on 9 October 2026. ### 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://www.scraperapi.com/terms/), read 2026-10-09. Our reader couldn't read it (robots.txt asks readers like ours not to fetch it). **Privacy policy** (https://www.scraperapi.com/privacy/), read 2026-10-09, gives no date, states 6 of the 8 things a reader expects. - Not found in the text. Gives the date it was last updated. - Says how long data is kept. Names a period of 60 days. - Not found in the text. Says whether personal data is sold or shared for advertising. - Gives a privacy contact. support@scraperapi.com. - Says where data is transferred or stored. Relies on standard contractual clauses. - Also in the text (2026-10-08). ScraperAPI automatically collects and stores information about use of its services, including page scraping activities. "ScraperAPI also automatically collects and stores information about our User’s use of the Platform and our Services, including page scraping activities, so that information gathered by a User through our Platform or Services can be served up each time a User logs in to the Platform." - Also in the text (2026-10-08). On request or account termination, personal data is deleted, destroyed or anonymised within 60 days, unless ScraperAPI ended the account for a breach of its Terms of Use. "upon your request or termination of your User account, delete, destroy, or anonymised your Personal Data that we have in our possession in accordance with our standard backup and retention policy (no later than 60 days)" ## Live (updated 2026-10-10 01:38 UTC) - Right now: up, HTTP 404, 277 ms, checked 2026-10-10 01:38 UTC (get on `https://api.scraperapi.com`) - Uptime 24h 100.0% (102 probes) · 30 days 100.0% (102 probes) · p50 292 ms · p95 420 ms - npm `scraperapi-cli` 1.0.0 - npm `scraperapi-sdk` 2.0.1 - pypi `scraperapi-mcp-server` 1.1.1, released 2026-07-17 - pypi `scraperapi-sdk` 1.6.1, released 2026-07-20 - Watching changelog - Watching pricing - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/scraperapi.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 | | --- | --- | --- | --- | | Hobby plan | $49 | per month (plan) | 100,000 credits, 20 concurrent threads | | Startup plan | $149 | per month (plan) | 1 million credits, 50 concurrent threads | | Business plan | $299 | per month (plan) | 3 million credits, 100 concurrent threads | | Plain request on Hobby | $0.49 | per 1,000 requests | 1 credit each, no rendering | | Rendered request on Hobby | $4.90 | per 1,000 requests | render=true, 10 credits each | | Google or Bing request on Hobby | $12.25 | per 1,000 requests | 25 credits each | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Only `api_key` and `url` are required, and JavaScript rendering is off by default, so a plain request costs 1 credit - Failed requests are not charged. Only 200 and 404 responses are billed, and each response carries an `sa-credit-cost` header - `max_cost` caps the credits one request may spend, and `/account/urlcost` returns the cost of a URL before it is scraped - The open-source MCP server (MIT) defines 28 typed tools, each with read-only, destructive and idempotent hints - Free plan of 1,000 credits a month with no card, plus 5,000 credits for the first 7 days ## Weaknesses - No status page is linked from the home, pricing, support or docs pages, although the pricing page lists a 99.9% uptime guarantee - The documented default sends the API key in the URL query string. A header alternative, `x-sapi-api_key`, exists - No OpenAPI file, security.txt, bug bounty, certification or sub-processor list was found - The site's robots.txt disallows `/terms/`, so the Terms of Use went unread by us - Google and Bing cost 25 credits a request and LinkedIn 30, and a bypassed anti-bot check adds 10 ## Before you call it (notes for agents) 1. Set the client timeout to 70 seconds. The API retries for that long before it returns 500, and a request cancelled earlier is still charged 2. Send the key as the `x-sapi-api_key` header to keep it out of URLs and logs 3. Pass `max_cost` on each request, or call `/account/urlcost` first, because domain and anti-bot surcharges vary from 1 to 75 credits 4. Use `output_format=markdown` or `text` to cut response size, and `autoparse=true` only on supported domains 5. On 429 reduce concurrency to the plan limit (5 on Free, 20 on Hobby). The request is rejected, not queued ## Connect Install: ```bash pip install scraperapi-mcp-server ``` First request: ```bash curl --request GET \ --url 'https://api.scraperapi.com?api_key=API_KEY&url=https://www.example.com' ``` Claude Code: ```bash claude mcp add scraperapi -- npx mcp-remote https://mcp.scraperapi.com/mcp --header "Authorization: Bearer {YOUR_API_KEY}" ``` MCP client configuration: ```json { "mcpServers": { "ScraperAPIRemote": { "args": [ "mcp-remote", "https://mcp.scraperapi.com/mcp", "--header", "Authorization: Bearer {YOUR_API_KEY}" ], "command": "npx" } } } ``` Through letme (picks today, calling later): https://letme.dev/scraperapi. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. 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 | | --- | --- | --- | --- | --- | --- | --- | | Olostep | B | 63 | 410 | web.scrape, web.extract, web.crawl, scraping.proxies, scraping.js-render, scraping.anti-bot, scraping.screenshot, scraping.serp | no | https://www.anchorterminal.com/tools/olostep.md | | Spider | BB | 74.1 | 76 | web.scrape, web.extract, web.crawl, scraping.proxies, scraping.js-render, scraping.anti-bot, scraping.screenshot | yes | https://www.anchorterminal.com/tools/spider-cloud.md | | Scrapfly | B | 69.6 | 176 | web.scrape, web.extract, web.crawl, scraping.proxies, scraping.js-render, scraping.anti-bot, scraping.screenshot | no | https://www.anchorterminal.com/tools/scrapfly.md | | ScrapeGraphAI | B | 68.3 | 221 | web.scrape, web.extract, web.crawl, scraping.proxies, scraping.js-render, scraping.anti-bot, scraping.screenshot | no | https://www.anchorterminal.com/tools/scrapegraphai.md | | ScrapingBee | C | 59.2 | 557 | web.scrape, web.extract, scraping.proxies, scraping.js-render, scraping.anti-bot, scraping.screenshot, scraping.serp | no | https://www.anchorterminal.com/tools/scrapingbee.md | | Scrapeless | C | 54.1 | 693 | web.scrape, web.crawl, scraping.proxies, scraping.js-render, scraping.anti-bot, scraping.screenshot, scraping.serp | no | https://www.anchorterminal.com/tools/scrapeless.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 site's robots.txt disallows `/terms/` for every agent, so the Terms of Use are closed to crawlers (source: ) - A November 2025 release note says the service now operates as ScraperAPI LLC, while the privacy policy names Saas.group Inc. (source: ) - The MCP server is a Python package under the MIT licence with 28 tools, v1.1.1 of 17 July 2026. llms.txt still says 22 tools (source: ) - The API retries a target for up to 70 seconds and charges only for 200 and 404 responses (source: ) - The MCP skill tells agents to prefer ScraperAPI tools over built-in web search and fetch, and the vendor's grounding pages carry a System Note for LLMs (source: ) - #14 of 18 in Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md - All 167 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md ## Compare - [Bright Data vs ScraperAPI](https://www.anchorterminal.com/compare/bright-data-vs-scraperapi.md): C 59.8 vs D 52.1 - [Jina Reader vs ScraperAPI](https://www.anchorterminal.com/compare/jina-reader-vs-scraperapi.md): E 45.1 vs D 52.1 - [Olostep vs ScraperAPI](https://www.anchorterminal.com/compare/olostep-vs-scraperapi.md): B 63 vs D 52.1 - [Oxylabs Web Scraper API vs ScraperAPI](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scraperapi.md): B 63 vs D 52.1 - [Scrape.do vs ScraperAPI](https://www.anchorterminal.com/compare/scrape-do-vs-scraperapi.md): E 43.7 vs D 52.1 - [ScrapeGraphAI vs ScraperAPI](https://www.anchorterminal.com/compare/scrapegraphai-vs-scraperapi.md): B 68.3 vs D 52.1 - [Scrapeless vs ScraperAPI](https://www.anchorterminal.com/compare/scrapeless-vs-scraperapi.md): C 54.1 vs D 52.1 - [ScraperAPI vs Scrapfly](https://www.anchorterminal.com/compare/scraperapi-vs-scrapfly.md): D 52.1 vs B 69.6 - [ScraperAPI vs ScrapingAnt](https://www.anchorterminal.com/compare/scraperapi-vs-scrapingant.md): D 52.1 vs F 35.5 - [ScraperAPI vs ScrapingBee](https://www.anchorterminal.com/compare/scraperapi-vs-scrapingbee.md): D 52.1 vs C 59.2 - [ScraperAPI vs Scrapingdog](https://www.anchorterminal.com/compare/scraperapi-vs-scrapingdog.md): D 52.1 vs E 39.2 - [ScraperAPI vs Spider](https://www.anchorterminal.com/compare/scraperapi-vs-spider-cloud.md): D 52.1 vs BB 74.1 - [ScraperAPI vs ZenRows](https://www.anchorterminal.com/compare/scraperapi-vs-zenrows.md): D 52.1 vs BB 74.8 - [ScraperAPI vs Zyte API](https://www.anchorterminal.com/compare/scraperapi-vs-zyte.md): D 52.1 vs B 69.7 - [Diffbot vs ScraperAPI](https://www.anchorterminal.com/compare/diffbot-vs-scraperapi.md): C 54.3 vs D 52.1 - [Firecrawl MCP vs ScraperAPI](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scraperapi.md): BB 75.3 vs D 52.1 - [Apify MCP Server vs ScraperAPI](https://www.anchorterminal.com/compare/apify-mcp-vs-scraperapi.md): BB 76.5 vs D 52.1 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on scraperapi.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": "scraperapi", "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 ScraperAPI on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![ScraperAPI on Anchor Terminal](https://www.anchorterminal.com/badges/scraperapi.svg)](https://www.anchorterminal.com/tools/scraperapi) ``` Plain link: ```html ScraperAPI on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say ScraperAPI 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/scraperapi-dark.png - Light: https://www.anchorterminal.com/assets/share/scraperapi-light.png