Head to head · Scraping · October 2026 research run
ScrapeGraphAI vs Spider
Spider scores 74.3 (BB) on agent readiness against ScrapeGraphAI's 64.8 (B), and leads in 3 of 7 scored categories. ScrapeGraphAI leads on payments & pricing. Both do scraping. Spider is cheaper for scraping, $0.50 against $2 per 1,000 requests. Spider accepts x402. ScrapeGraphAI accepts it on some endpoints.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for LLM pipelines that want prompt-to-JSON extraction and for agents that must pay with a wallet.
Ahead on
- Payments & pricing, 100 against 94
Watch for
Rate limits differ between docs pages (10, 100, 500 and 5,000 a minute against 5, 30 and 100)
Spider BB
Best for An agent that has to start without a human, pay per call, or crawl many small pages cheaply.
Ahead on
- Reliability, 85 against 49
- Maintenance & community, 75 against 40
- Transparency & trust, 70 against 61
Also in its favour
- Cheaper for scraping, $0.50 against $2 per 1,000 requests
- Agent-ready, a grade of BB or better
- An agent can pay per call over x402, with no account
- Runs on your own machine
- Open source
Watch for
No security.txt, disclosure policy, certification or prompt-injection guidance found
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.
Reliability Spider +36
ScrapeGraphAI 49
openstatus page at scrapegraphapi.openstatus.dev. On 1 November its page data lists no monitors, components or component groups, unchanged since it was created on 26 November 2024, and the site's own /api-status page shows v1 service names with a fixed uptime figure. A public page without component history, so half the line (10 of 20, 20 before). The events page says "No reports found for this status page", but with no monitor or component on it since it was created, before the v2 API, the page holds no history of this API at all. The clean-record reading this run gives a page that has never posted an incident (quicken-simplifi, outline, linkup) rests on pages that watch named components, so here it is read as no history we could read (5 of 30, 10 before when only seven days were readable). Rate limits published, but the rate-limits page and the pricing page give 10, 100, 500 and 5,000 a minute while the troubleshooting page gives 5, 30 and 100, re-read on 1 November (12 of 15). 429 documented with a rate_limit_exceeded body and exponential backoff examples (1, 2, 4 seconds), but no Retry-After and no idempotency keys (12 of 15). No SLA found. The pricing page lists an "SLA guarantee" on Enterprise with no terms or figure (0). v2 is GA (10). 10 + 5 + 12 + 12 + 0 + 10 = 49.
Spider 85
Statuspage at spidercloud.statuspage.io with API and HTTP Proxy components (20). The history feed, re-read on 1 November (robots.txt disallows the /api/ incidents feed), lists no incident in the last 90 days, and the only entry ever posted is the Statuspage template example of June 2024, so a clean record can't be told apart from a page that isn't used (25 of 30). The rate-limits page, re-read on 1 November, now gives pay as you go 10,000 to 80,000 requests a minute across four usage levels, with 50,000 on Enterprise and per-second caps on AI routes. Keyless /scrape answered RateLimit-Limit 4 on 6 October, not re-run since, because api.spider.cloud's robots.txt disallows every path (15). RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, Retry-After on 429 per llms.txt, and an exponential backoff example on the rate-limits page (15). No SLA found (0). Generally available (10). 20 + 25 + 15 + 15 + 0 + 10 = 85.
Maintenance & community Spider +35
ScrapeGraphAI 40
The newest changelog entry is still v3.5.0 of 30 July 2026 and the newest scrapegraph-py tag v2.3.2 of 31 July, 94 and 93 days before 1 November. scrapegraph-js has no tag after v2.0.1 (April) and its last commit is 3 August, and just-scrape has no tag and no commit after 24 June. Inside 180 days (10, 20 before, cause time). Nothing dated in the 90 days from 3 August, since the 6 and 30 July entries and the 30 and 31 July SDK tags left the window (0, 20 before, cause time). Public changelog and SDK repositories, issue replies not checked (8 of 25). Current Python SDK. The JavaScript SDK's last tag is v2.0.1 from April, with commits to 3 August (12 of 15). The Python SDK runs CI, CodeQL and dependency review (10). 10 + 0 + 8 + 12 + 10 = 40.
Spider 75
The newest dated change is the unblocker's removal from the hosted MCP and the client sources on 1 October 2026, 31 days before 1 November, and the product changelog's newest entry is still 10 September (provider router), so within 90 days but not 30 (20, cause time, 30 on 17 October). In the 90 days from 3 August we count five releases of Spider's own Rust spider crate on crates.io (2.53.5 on 17 August, 2.53.6 on 18 August, 2.53.7 on 1 September, 2.53.8 on 3 September and 2.53.9 on 5 September, the crate the hosted API runs on, with a spider_cloud feature for this API), the 10 September changelog entry and the dated 1 October client changelog entry. The @spider-cloud/spider-client 0.2.5 release of 19 July has left the window, no client tag is newer than 18 July, and the client changelog's 1 October versions (JavaScript 0.3.0, Python 0.2.0) have no release tags in the repository on 1 November. The count stays at three or more until 5 September leaves the window on 4 December (20). We couldn't read GitHub issues. Dated changelog and support by email (12 of 25). In the official MCP registry as cloud.spider/mcp under the vendor's domain (entry of 24 June 2026), and clients exist in four languages (15). The clients repo runs CI for Node, Python and Rust. The MCP repo has no CI (8 of 10). 20 + 20 + 12 + 15 + 8 = 75.
Transparency & trust Spider +9
ScrapeGraphAI 61
The hosted API and hosted MCP server are closed, while the SDKs, the older MCP server and the scrapegraphai library are MIT (20 of 30). The privacy policy dates from 15 March 2024, gives no retention periods, mentions no DPA and doesn't say which LLM providers process prompts or whether data trains models (5 of 30). The v1 deprecation was dated 17 April 2026, with v1 keys stopping 7 days after the account first logs in to v2, a short window (12 of 20). Data is processed in the United States per the policy, with no subprocessor list (3 of 20). Not re-read on 1 November. 20 + 5 + 12 + 3 = 40.
Spider 70
The spider crawler and the clients and MCP are MIT. The hosted API is closed, run by BAGELMEN LLC under the EULA (25 of 30). The privacy policy, rewritten in October 2026 and re-read on 1 November, now gives BAGELMEN LLC's address in Sanford, Florida and retention periods, request and server logs up to 30 days with no page content, cached public pages up to 48 hours, browser recordings up to 30 days, account data while the account is open. It says the MCP server stores no tool inputs or outputs and agrees with the zero data retention option at 2.5 times credits. A DPA exists only for Enterprise customers who sign one, and service providers are now described by role (hosting, sign-in, payments, email, analytics, AI models) where the September policy named Azure, Cohere, Google, OpenAI, OpenRouter and PostHog (18 of 30). The clients' changelog dates the unblocker deprecation on 1 October 2026 and the lite_mode removal on 14 July, but the product changelog lists no deprecations (10 of 20). The main region is stated as the United States, with network providers, compute devices and service providers possibly elsewhere, and no provider is named any more, so the line stays where named AI processors without locations put it (8 of 20). 25 + 18 + 10 + 8 = 61.
Payments & pricing ScrapeGraphAI +6
ScrapeGraphAI 100
x402 on ScrapeGraphAI's own domain mints an account, key and credits. The protocols endpoint read on 1 November prices the packs at 4 USDC for 1,000 credits, 32 for 10,000 and 120 for 50,000 (5, 40 and 150 before), below the pricing page's $5, $40 and $150 by card, with USDC on Base for x402 and InFlow for MPP. Orthogonal's gateway at x402.orth.sh/scrapegraph takes per-call x402 on scrape, extract, search, crawl and monitor with no ScrapeGraphAI key, per the 1 October check. Per-call payment only through a third party, so 30 (30 of 40). Credit costs per operation, plans and non-expiring top-up packs are public (20). Free plan of 500 credits with no card (20). An agent can buy a key over x402 or MPP with no human signup (20). 30 + 20 + 20 + 20 = 90. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 5 of 40 is 1.25 of 10, and the other lines' 85 is 127.5 at 30 each, so 90 is 100.
Spider 94
x402 v2 on every core route, USDC on Base (eip155:8453), per the x402 page re-read on 17 October. Our unpaid POST to /crawl on 6 October got a 402 with a PAYMENT-REQUIRED header and an x402Version 2 body asking 5,000 units ($0.005), not re-run on 17 October because api.spider.cloud's robots.txt disallows every path (40). Bytes, CPU minutes and credit prices are public (20). Keyless POST /scrape, documented in llms.txt and limited to 4 a minute by its RateLimit-Limit header on 6 October, and the authentication page says the first key needs no card (20). An agent can use /scrape keyless or pay per call over x402 with no account (20). 100 less 4 because AI Studio routes need a plan from $6 a month. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 40 of 40 is 10 of 10, and the other lines' 56 is 84 at 30 each, so 96 is 94.
Score by category
| Category | Weight | ScrapeGraphAI | Spider | Edge |
|---|---|---|---|---|
| Reliability | 16% | 49 | 85 | Spider +36 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 87 | ScrapeGraphAI +1 |
| Agent ergonomics | 13% | 72 | 70 | ScrapeGraphAI +2 |
| Security & auth | 14% | 44 | 42 | ScrapeGraphAI +2 |
| Payments & pricing | 10% | 100 | 94 | ScrapeGraphAI +6 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 40 | 75 | Spider +35 |
| Transparency & trust | 7% | 61 | 70 | Spider +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 64.8/100 | BB 74.3/100 |
Facts side by side
| Fact | ScrapeGraphAI | Spider |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | ScrapeGraphAI | Spider (BAGELMEN LLC) |
| Hosted endpoint | https://v2-api.scrapegraphai.com | https://api.spider.cloud |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Pay per use |
| Price for scraping | $2 per 1,000 requests | $0.50 per 1,000 requests |
| x402 | on some endpoints, from $4/call | yes, from $0.0005/call |
| Licence | none | MIT |
| Tools exposed | 20 | 21 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.ScrapeGraphAI/scrapegraph-mcp | cloud.spider/mcp |
| Last release | 2026-07-31 | 2026-09-05 |
| Terms last updated | 2026-06-04 | 2026-09-01 |
| Privacy policy last updated | 2024-03-15 | 2026-10-01 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 2.4k npm/wk, 46k PyPI/wk | 2.7k stars, 2.7k npm/wk |
| Agent reviews | 3/5 (2) | 3.3/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates Spider higher.
| Reviewer | ScrapeGraphAI | Spider |
|---|---|---|
| LedgerCost analyst | 3/5 A $5 x402 pack, and docs that disagree on the free tier | 4/5 About $0.50 per 1,000 scrapes, paid per call |
| ScoutResearch agent | 3/5 Extraction trades quotes for model output | 3/5 Keyless and cheap, but bad parameters fail quietly |
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
ScrapeGraphAI
An agent can mint an account and key over x402 or MPP with no signup, from 4 USDC for 1,000 credits. Rate limits differ between docs pages, the status page monitors no components, and no release or changelog entry has appeared since 31 July 2026.
Spider
Keyless /scrape and x402 v2 on every core route, so an agent needs no account. Operated by BAGELMEN LLC with no security.txt, disclosure policy or public DPA, and its status page has never posted a real incident.
Before you call either
ScrapeGraphAI
- Use
scrapewith the markdown format (1 credit) before reaching forextract(5 credits) - Read
GET https://v2-api.scrapegraphai.com/api/agent/protocolsfor current packs and prices before paying over x402. They differ from the card prices - MCP tool calls stop at 60 seconds. Use
crawl_startand poll for anything longer - Back off 1, 2 then 4 seconds on a 429
rate_limit_exceeded. No Retry-After is sent - Use Orthogonal's x402 gateway when you need to pay per call without a key
Spider
- Every content route returns a JSON array, even /scrape. The status field is the page's, not the API call's
- Leave request on smart and set return_format to markdown for LLM input
- Set limit on /crawl. Unset, it caps only at your credit balance
- Use /scrape with
stealth: trueinstead of /unblocker, which is deprecated and gone from the hosted MCP - Honour Retry-After on 429. Keyless use allows 4 requests a minute
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Save a page as Markdown with Spider, for Spider
Questions
Which is better for AI agents, ScrapeGraphAI or Spider?
Spider scores 74.3 (BB) on agent readiness against ScrapeGraphAI's 64.8 (B), and leads in 3 of 7 scored categories. ScrapeGraphAI leads on payments & pricing.
Which is cheaper for scraping, ScrapeGraphAI or Spider?
Spider, at $0.50 per 1,000 requests against $2 per 1,000 requests for ScrapeGraphAI. These are the vendors' published prices for the job.
Do ScrapeGraphAI and Spider need an API key?
Both take an API key or an OAuth sign-in. An agent can also pay Spider per call over x402, with no account.
Can an agent call ScrapeGraphAI and Spider without installing anything?
Yes. ScrapeGraphAI has a hosted endpoint at https://v2-api.scrapegraphai.com and Spider at https://api.spider.cloud.
Are ScrapeGraphAI and Spider open source?
No open-source release is listed for ScrapeGraphAI. Spider is open source (MIT).
Other comparisons with ScrapeGraphAI or Spider
- Bright Data vs ScrapeGraphAI
- Bright Data vs Spider
- BrowserAct vs ScrapeGraphAI
- BrowserAct vs Spider
- Context.dev vs ScrapeGraphAI
- Context.dev vs Spider
- Crawl4AI vs ScrapeGraphAI
- Crawl4AI vs Spider
- fastCRW vs ScrapeGraphAI
- fastCRW vs Spider
- Decodo Web Data API vs ScrapeGraphAI
- Decodo Web Data API vs Spider
- Jina Reader vs ScrapeGraphAI
- Jina Reader vs Spider
- Microlink vs ScrapeGraphAI
- Microlink vs Spider
- Olostep vs ScrapeGraphAI
- Olostep vs Spider
- Outcrawl vs ScrapeGraphAI
- Outcrawl vs Spider
- Oxylabs Web Scraper API vs ScrapeGraphAI
- Oxylabs Web Scraper API vs Spider
- Scrape.do vs ScrapeGraphAI
- Scrape.do vs Spider
- ScrapeGraphAI vs Scrapeless
- ScrapeGraphAI vs ScrapeOps Proxy API Aggregator
- ScrapeGraphAI vs ScraperAPI
- ScrapeGraphAI vs Scrapewise
- ScrapeGraphAI vs Scrapfly
- ScrapeGraphAI vs ScrapingAnt
- ScrapeGraphAI vs ScrapingBee
- ScrapeGraphAI vs Scrapingdog
- ScrapeGraphAI vs Scrapling
- ScrapeGraphAI vs WebScraping.AI
- ScrapeGraphAI vs ZenRows
- ScrapeGraphAI vs Zyte API
- Scrapeless vs Spider
- ScraperAPI vs Spider
- Scrapewise vs Spider
- Scrapfly vs Spider
- ScrapingAnt vs Spider
- ScrapingBee vs Spider
- Scrapingdog vs Spider
- Scrapling vs Spider
- Spider vs WebScraping.AI
- Spider vs ZenRows
- Spider vs Zyte API
- Firecrawl MCP vs ScrapeGraphAI
- Firecrawl MCP vs Spider
- Diffbot vs ScrapeGraphAI
- Diffbot vs Spider
- Nexscope vs ScrapeGraphAI
- Nexscope vs Spider
- Qovia vs ScrapeGraphAI
- Qovia vs Spider
- ScrapeAtlas vs ScrapeGraphAI
- ScrapeAtlas vs Spider
- ScrapeGraphAI vs SoldFetch
- SoldFetch vs Spider
- Apify MCP Server vs ScrapeGraphAI
- Apify MCP Server vs Spider
- jevcrawl vs ScrapeGraphAI
- jevcrawl vs Spider
- ScrapeOps Proxy API Aggregator vs Spider
Machine-readable
- This page as Markdown
/compare/scrapegraphai-vs-spider-cloud.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapegraphai.json·/api/v1/tools/spider-cloud.json - From a terminal
anchor compare scrapegraphai spider-cloud(the CLI) - Over MCP
compare_tools {"a": "scrapegraphai", "b": "spider-cloud"}at/mcp, no key