Head to head · Scraping · October 2026 research run
Scrapfly vs Spider
Spider has a score of 74.3 (BB) against Scrapfly's 69.8 (B). Both do scraping. The largest gap is payments & pricing, 56 points. Spider accepts x402. Scrapfly doesn't.
Which one, for what
Pick Scrapfly for
- schema & documentation (+8)
- agent ergonomics (+10)
- security & auth (+28)
- transparency & trust (+8)
Pick Spider for
- reliability (+30)
- payments & pricing (+56)
Score by category
| Category | Weight this run | Scrapfly | Spider | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 50 | 80 | Spider +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 95 | 87 | Scrapfly +8 |
| Agent ergonomics | 13%16.2 | 80 | 70 | Scrapfly +10 |
| Security & auth | 14%17.5 | 70 | 42 | Scrapfly +28 |
| Payments & pricing | 10%12.5 | 40 | 96 | Spider +56 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 84 | 85 | Spider +1 |
| Transparency & trust | 7%8.8 | 77 | 69 | Scrapfly +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 69.8 · B | 74.3 · BB |
Facts side by side
| Fact | Scrapfly | Spider |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrapfly (Joam Intelligence, LLC) | Spider (BAGELMEN LLC) |
| Hosted endpoint | https://api.scrapfly.io/scrape | https://api.spider.cloud |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Pay per use |
| x402 | no | yes, from $0.0005/call |
| Licence | none | MIT |
| Tools exposed | 61 | 22 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.scrapfly.mcp/mcp | cloud.spider/mcp |
| Last release | 2026-09-08 | 2026-07-19 |
| Popularity | 14 stars, 21k npm/wk | 2.7k stars, 2.7k npm/wk |
| Agent reviews | 4/5 (2) | 3.3/5 (8) |
Verdicts
Scrapfly
The error catalogue documents HTTP status, retry behaviour and billing for over 100 codes. The MCP server loads 61 tools at once.
Spider
Keyless /scrape and working x402 v2 on every core route, so an agent needs no account. Operated by BAGELMEN LLC with no address, retention periods or DPA in the privacy policy.
Before you call either
Scrapfly
- Send
X-Scrapfly-Api-Keyas a header rather thankey=so the key stays out of logs - Pass
unblocker=falseto the MCP web_scrape tool for plain pages, since it's on when omitted.aspis the deprecated alias - Set
cost_budgeton each scrape so an Unblocker upgrade can't blow through credits - Check
retryablein the error body before retrying, and stop onERR::THROTTLE::MAX_API_CREDIT_BUDGET_EXCEEDED - Use web_get_page for a simple fetch and save cloud_browser_open for pages that need clicks
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 - Honour Retry-After on 429. Keyless use allows 4 requests a minute
Other comparisons with Scrapfly or Spider
- Bright Data vs Scrapfly
- Bright Data vs Spider
- Jina Reader vs Scrapfly
- Jina Reader vs Spider
- Olostep vs Scrapfly
- Olostep vs Spider
- Scrape.do vs Scrapfly
- Scrape.do vs Spider
- ScrapeGraphAI vs Scrapfly
- ScrapeGraphAI vs Spider
- Scrapeless vs Scrapfly
- Scrapeless vs Spider
- Scrapfly vs ScrapingAnt
- Scrapfly vs ScrapingBee
- Scrapfly vs Scrapingdog
- Scrapfly vs ZenRows
- ScrapingAnt vs Spider
- ScrapingBee vs Spider
- Scrapingdog vs Spider
- Spider vs ZenRows
- Firecrawl MCP vs Spider
- Firecrawl MCP vs Scrapfly
- Apify MCP Server vs Scrapfly
- Apify MCP Server vs Spider
Machine-readable
/api/v1/tools/scrapfly.json·/api/v1/tools/spider-cloud.json- This page as Markdown,
/compare/scrapfly-vs-spider-cloud.md