Head to head · Scraping · October 2026 research run

ScrapingAnt vs Scrapingdog

ScrapingAnt scores 42.5 (E) on agent readiness against Scrapingdog's 40.3 (E), and leads in 2 of 7 scored categories. Scrapingdog leads on reliability, schema & documentation and maintenance & community. Both do scraping.

Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons

Which one, for what

ScrapingAnt E

Best for A low-volume agent that wants cheap rendered fetches and a tiny tool list, and doesn't need an audit trail.

Ahead on

  • Agent ergonomics, 72 against 52
  • Security & auth, 20 against 5

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

API Basics puts the key in the query string, so it lands in logs

Scrapingdog E

Best for A budget agent that wants parsed Google, Amazon or LinkedIn results and can keep the key out of logs.

Ahead on

  • Reliability, 49 against 35
  • Schema & documentation, 53 against 46
  • Maintenance & community, 25 against 5

Also in its favour

  • Runs on your own machine

Watch for

The REST API takes the key only in the URL query string

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Agent ergonomics ScrapingAnt +20

ScrapingAnt 72

3 compact MCP tools (25). Markdown and text endpoints, AI extraction, wait-for-selector and a JSON extended response, but no output-size limit on the MCP tools (12 of 20). The errors page lists 7 statuses with exact detail messages, separates ScrapingAnt's status from the target's (Ant-page-status-code), and says for each whether to retry and what to fix (20, as scrapingdog). Requests are reads of third-party pages and failures aren't billed, but there are no idempotency keys or tool annotations (5 of 20). Only url is required, though browser defaults to true at 10 credits. Python and JavaScript clients exist but are stale (10 of 15). 25 + 12 + 20 + 5 + 10 = 72.

Scrapingdog 52

35 MCP tools with no toolsets or subsets (5 of 25). markdown=true, ai_query and parsed JSON endpoints for Google, Amazon and LinkedIn keep responses smaller. No documented pagination or size limits on the raw scrape (12 of 20). The docs list 8 status codes with meanings, and the agent onboarding guide gives each one an action (fix parameters on 400, check the key with /account on 401, a human upgrades on 403, lower concurrency and back off on 429, retry 410 once), with whether it's charged; the MCP passes the status and body back (20 of 20). Failed requests aren't billed, but no tool annotations or idempotency guidance (5 of 20). Only url is required, but rendering defaults on at 5 credits and the MCP describes it as off. Node and Python SDKs (10 of 15). Total 52.

Maintenance & community Scrapingdog +20

ScrapingAnt 5

No changelog or dated API change found. The newest dated release of any vendor package is the GitHub Action v1.0.0, tagged 3 April 2026 (222 days), and the newest SDK is Python 2.1.0, tagged 16 July 2024 (0). No releases in the last 90 days (0). No public changelog. Support by email (3 of 15). The JavaScript client was last tagged v0.2.1 on 6 May 2022, so the SDKs aren't current, and no registry page shows ScrapingAnt's own MCP server (0). The Python client has a code-check workflow, but neither SDK has moved in over two years (2 of 10). 0 + 0 + 3 + 0 + 2 = 5.

Scrapingdog 25

The newest dated releases are the SDKs and MCP server first published on 31 July and 1 August 2026, 102 days ago; no API changelog or later dated release found. The MCP repository became a hosted service at mcp.scrapingdog.com in commits of 25 and 26 October with no version bump, tag or changelog entry, so not a release (10 of 30). Nothing dated in the 90 days from 12 August (0 of 20). We couldn't read GitHub issues. The MCP repository has 13 commits, the last seven on 25 and 26 October, and support is by chat and email (5 of 25). Node and Python SDKs, current per the 1 October check; npm and PyPI weren't readable on 10 November (8 of 15). The MCP repository now runs typecheck, build and a smoke suite in CI before each deploy, with no tags or readable run results (2 of 10, the earlier partial held). Total 25.

Security & auth ScrapingAnt +15

ScrapingAnt 20

One account API key with no scopes. A new docs page explains how to regenerate it from the profile page, after which the old key answers 403 and an email confirms the change, so it is a plain revocable key (20). API Basics still tells you to send x-api-key as a query parameter, a documented option, so less 10 (10 of 30). The hosted MCP server now also accepts an OAuth sign-in bound to the active key. No read-only mode, and /v2/general can send POST, PUT and DELETE to target sites with no confirmation step; an IP allow-list can restrict where the key is used (5 of 20). No prompt-injection guidance found for the HTML, Markdown or text it returns (0 of 15). The Ant-credits-cost header and a subscription status endpoint show spend per call. No request log found (5 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). 10 + 5 + 0 + 5 + 0 = 20.

Scrapingdog 5

One account key with no scopes, and we found no rotation or revocation docs; team members get their own keys (10). The REST API takes the key only in the api_key query string, with no header option, so less 10 (0 of 30). The hosted MCP server takes the key as a bearer header, then passes it to the API in the query string. No read-only mode or least-privilege key. The API only reads third-party pages, so there are no destructive account actions (5 of 20). No prompt-injection guidance in the docs, the onboarding guide or the MCP README (0 of 15). No request log or per-call audit found; /account reports credits and concurrency only (0 of 15). No security.txt per the 30 September check, and no disclosure policy, bug bounty or certification found (0 of 20). Total 5.

Reliability Scrapingdog +14

ScrapingAnt 35

No status page linked from the site or docs (0). No readable incident history (5). The free plan allows 1 concurrent request and paid plans have no concurrency cap, with timeout settable from 5 to 60 seconds. No per-minute limits published (8 of 15). The rewritten errors page gives each status a retry rule, tells free-plan callers hitting the 409 concurrency limit to wait for the active request and queue, allows only bounded retries for 404, 423 and 500, and advises a small attempt cap with increasing delays and jitter for temporary failures on operations safe to repeat, and warns that a timed-out POST, PUT or DELETE may already have reached the target, with no idempotency keys and no 429 or Retry-After (12, backoff plus safe-retry guidance, as scrapingdog). No SLA found (0). The API is generally available (10). 0 + 5 + 8 + 12 + 0 + 10 = 35.

Scrapingdog 49

The footer still links an UptimeRobot status page. Its monitors load only from UptimeRobot's /api/ path, which robots.txt disallows, and the page itself shows "Loading..." and a fetch error, so no component could be read (0 of 20). No readable incident history (5). Concurrency per plan is published, 1 on Free up to 2,200 on the top plan, and over the limit returns 429 (15). The agent onboarding guide linked from llms.txt says to retry 410, 429 and occasional 400s with backoff, not to retry 401 or 403, and that failed requests aren't charged; requests time out after 60 seconds. No Retry-After or idempotency keys (12 of 15). A public SLA page says Scrapingdog aims for 99 per cent monthly uptime and compensates downtime in credits, with no measurement method or date, per the 1 October check, not re-read on 10 November (7 of 10, the earlier partial held). Generally available (10). Total 49.

Schema & documentation Scrapingdog +7

ScrapingAnt 46

No OpenAPI or Swagger spec found. The MCP docs give a typed parameter table for the 3 tools (8 of 25). docs.scrapingant.com/llms.txt still returns 404 and no Markdown twins were found (0). MCP descriptions are one line each, such as Fetch a URL and return raw HTML content, with no when-to-use guidance (8 of 20). Few parameters, typed, with proxy_type as an enum of datacenter or residential (10 of 15). Request examples on every docs page, and an errors page that now gives each status code its exact detail text, cause and retry rule, plus a separate SDK errors page (15). Versioned paths (v1 and v2) and no changelog (5 of 15). 8 + 0 + 8 + 10 + 15 + 5 = 46.

Scrapingdog 53

No OpenAPI spec found. The MCP builds typed zod inputs for 35 tools from a declarative registry, and ai_extract_rules is a JSON string (12 of 25). llms.txt at the site root, re-read on 10 November, links the docs and a Markdown onboarding guide for agents (10). MCP descriptions say what each endpoint does but not when to avoid it, and the web_scrape tool tells the model the API default for dynamic is false while the docs say rendering is on by default (10 of 20). Booleans, numbers and strings with few enums, plus the JSON-string field (9 of 15). Code examples on each docs page and 8 documented status codes (12 of 15). No changelog and no versioned API paths found (0). Total 53; the score published on 1 October was 43, ten below these lines, and is corrected to their sum.

Score by category

CategoryWeightScrapingAntScrapingdogEdge
Reliability16%3549Scrapingdog +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4653Scrapingdog +7
Agent ergonomics13%7252ScrapingAnt +20
Security & auth14%205ScrapingAnt +15
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%525Scrapingdog +20
Transparency & trust7%5656even
Negative events≤150-2
TotalE 42.5/100E 40.3/100

Facts side by side

FactScrapingAntScrapingdog
KindHTTP APIHTTP API
VendorScrapingAnt (DATAANT)Scrapingdog (OpenData Labs)
Hosted endpointhttps://api.scrapingant.com/v2/generalhttps://api.scrapingdog.com/scrape
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
Tools exposed335
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedio.github.Darshan972/scrapingdog-mcp
Last release2024-07-162026-07-31
Terms last updatedno date given2026-01-13
Privacy policy last updatedno date given2025-07-17
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone0 stars
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates ScrapingAnt higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

ScrapingAnt

10,000 free credits a month with no card, three compact MCP tools, and an errors reference that tells an agent when to retry and what to fix. API Basics still puts the key in the query string, there's no status page or changelog, and no vendor package has had a release in over 180 days.

Scrapingdog

A plain request is 1 credit, about $0.20 per 1,000 on Lite, and failed requests aren't charged. The REST API takes its key only in the URL query string, and the MCP server describes JavaScript rendering as off by default when the API turns it on at 5 credits.

Before you call either

ScrapingAnt

  1. Send the key in the x-api-key header rather than the query string
  2. Use /v2/markdown for LLM input, and set browser=false on static pages to pay 1 credit instead of 10
  3. Switch to proxy_type=residential only after a 423 (anti-bot) response. It raises a browser request from 10 to 125 credits
  4. On the free plan a second concurrent request gets 409. Queue requests and wait for the first to finish rather than retrying
  5. Google, Bing and Yandex result pages come back as raw HTML through /v2/general, so you parse them yourself

Scrapingdog

  1. Add dynamic=false unless the page needs JavaScript. It cuts the cost from 5 credits to 1, whatever the MCP description says
  2. Connect the hosted MCP with the key as a bearer header, and keep REST request URLs out of logs, since they carry api_key
  3. Set client timeouts above 60 seconds and retry 410 and 429 with backoff. Failures aren't billed
  4. Prefer the parsed endpoints (Google, Amazon) over scraping the raw page when one exists

Questions

Which is better for AI agents, ScrapingAnt or Scrapingdog?

ScrapingAnt scores 42.5 (E) on agent readiness against Scrapingdog's 40.3 (E), and leads in 2 of 7 scored categories. Scrapingdog leads on reliability, schema & documentation and maintenance & community.

Do ScrapingAnt and Scrapingdog need an API key?

Both need an API key.

Can an agent call ScrapingAnt and Scrapingdog without installing anything?

Yes. ScrapingAnt has a hosted endpoint at https://api.scrapingant.com/v2/general and Scrapingdog at https://api.scrapingdog.com/scrape.

Other comparisons with ScrapingAnt or Scrapingdog

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.