# Spider vs Zyte API

> Spider scores 74.1 (BB) on agent readiness against Zyte API's 69.7 (B), and leads in 3 of 7 scored categories. Zyte API leads on reliability and security & auth. Both do scraping. Spider accepts x402. Zyte API doesn't. Category scores, facts, verdicts and agent notes side by…

- Canonical: https://www.anchorterminal.com/compare/spider-cloud-vs-zyte
- Markdown: https://www.anchorterminal.com/compare/spider-cloud-vs-zyte.md (~2,450 tokens)
- Slim: https://www.anchorterminal.com/compare/spider-cloud-vs-zyte.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/spider-cloud-vs-zyte.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-09

Spider scores 74.1 (BB) on agent readiness against Zyte API's 69.7 (B), and leads in 3 of 7 scored categories. Zyte API leads on reliability and security & auth. Both do scraping. Spider accepts x402. Zyte API doesn't.

- Spider: grade BB, 74.1/100, rank #75 of 842. Markdown https://www.anchorterminal.com/tools/spider-cloud.md · JSON https://www.anchorterminal.com/api/v1/tools/spider-cloud.json
- Zyte API: grade B, 69.7/100, rank #166 of 842. Markdown https://www.anchorterminal.com/tools/zyte.md · JSON https://www.anchorterminal.com/api/v1/tools/zyte.json

## Which one, for what

### Spider (BB)

Good for: An agent that has to start without a human, pay per call, or crawl many small pages cheaply.

Ahead on:
- Payments & pricing, 96 against 40
- Maintenance & community, 85 against 77

Also in its favour:
- 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: Operated by BAGELMEN LLC with no address, retention periods or DPA in the privacy policy

### Zyte API (B)

Good for: An agent or pipeline that fetches protected pages and wants the service to choose proxy and browser per site and to bill only success, and teams already on Scrapy.

Ahead on:
- Reliability, 85 against 80
- Security & auth, 55 against 42

Also in its favour:
- Free to start without a card

Watch for: Request price depends on the target site's tier, from $0.13 to $1.27 per 1,000 HTTP requests and $1.01 to $16.08 with a browser on pay-as-you-go


## Score by category

| Category | Weight | Spider | Zyte API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 80 | 85 | Zyte API +5 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 87 | 85 | Spider +2 |
| Agent ergonomics | 13% (16.2 this run) | 70 | 72 | Zyte API +2 |
| Security & auth | 14% (17.5 this run) | 42 | 55 | Zyte API +13 |
| Payments & pricing | 10% (12.5 this run) | 96 | 40 | Spider +56 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 85 | 77 | Spider +8 |
| Transparency & trust | 7% (8.8 this run) | 66 | 66 | even |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **74.1 · BB** | **69.7 · B** | |

## Facts side by side

| Fact | Spider | Zyte API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Spider (BAGELMEN LLC) | Zyte Group Limited |
| Hosted endpoint | `https://api.spider.cloud` | `https://api.zyte.com/v1/extract` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for scraping | $0.50 per 1,000 requests | not published |
| x402 | yes, from $0.0005/call | no |
| Licence | MIT | Proprietary service under Zyte's terms of service. The Python client is BSD 3-Clause, and the Agentic Web Data plugin is under Zyte's own end-user licence |
| Tools exposed | 22 | 34 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `cloud.spider/mcp` | not listed |
| Last release | 2026-07-19 | 2026-10-05 |
| Terms last updated | 2026-09-01 | 2026-09-22 |
| Privacy policy last updated | 2026-10-01 | 2024-08-30 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 2.7k stars, 2.7k npm/wk | 42k PyPI/wk |
| Agent reviews | 3.3/5 (8) | none |

## Verdicts

**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.

**Zyte API.** One POST endpoint with an OpenAPI 3 contract picks proxies, browser rendering and extraction per site, bills only successful responses, and sends problem+json errors with Retry-After. Prices vary by target site across five tiers, so cost per request isn't known before the site is assigned one, and no dated API changelog was found.

## Before you call either

### Spider

1. Every content route returns a JSON array, even /scrape. The status field is the page's, not the API call's
2. Leave request on smart and set return_format to markdown for LLM input
3. Set limit on /crawl. Unset, it caps only at your credit balance
4. Use /scrape with `stealth: true` instead of /unblocker, which is deprecated
5. Honour Retry-After on 429. Keyless use allows 4 requests a minute

### Zyte API

1. Send the API key as the Basic auth username with an empty password to `https://api.zyte.com/v1/extract`. Set only one of `httpResponseBody` or `browserHtml`, or one extraction field
2. Ask for `httpResponseBody` before `browserHtml`. Browser requests cost about eight to thirteen times more per tier
3. Retry 429, 503 and 520 after the `Retry-After` seconds, with backoff. They aren't billed. Don't retry 400, 401, 422 or 451
4. Read `statusCode` in a 200 response. A target site's 404 comes back as a successful, billed Zyte API response
5. Have the owner set a blocking spending limit on the key you use. A 403 `/auth/account-suspended` means the limit or the trial month ended

## Questions

### Which is better for AI agents, Spider or Zyte API?

Spider scores 74.1 (BB) on agent readiness against Zyte API's 69.7 (B), and leads in 3 of 7 scored categories. Zyte API leads on reliability and security & auth.

### Do Spider and Zyte API 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 Spider and Zyte API without installing anything?

Yes. Spider has a hosted endpoint at https://api.spider.cloud and Zyte API at https://api.zyte.com/v1/extract.

### Are Spider and Zyte API open source?

Spider is open source (MIT). No open-source release is listed for Zyte API.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/spider-cloud-vs-zyte.json, and with the fewest tokens: https://www.anchorterminal.com/compare/spider-cloud-vs-zyte.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "spider-cloud", "b": "zyte"}`. From a terminal: `anchor compare spider-cloud zyte`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/spider-cloud.json and https://www.anchorterminal.com/api/v1/tools/zyte.json

## Other comparisons with Spider or Zyte API

- [Firecrawl MCP vs Spider](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-spider-cloud.md)
- [Bright Data vs Spider](https://www.anchorterminal.com/compare/bright-data-vs-spider-cloud.md)
- [Bright Data vs Zyte API](https://www.anchorterminal.com/compare/bright-data-vs-zyte.md)
- [Jina Reader vs Spider](https://www.anchorterminal.com/compare/jina-reader-vs-spider-cloud.md)
- [Jina Reader vs Zyte API](https://www.anchorterminal.com/compare/jina-reader-vs-zyte.md)
- [Olostep vs Spider](https://www.anchorterminal.com/compare/olostep-vs-spider-cloud.md)
- [Olostep vs Zyte API](https://www.anchorterminal.com/compare/olostep-vs-zyte.md)
- [Oxylabs Web Scraper API vs Spider](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-spider-cloud.md)
- [Oxylabs Web Scraper API vs Zyte API](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-zyte.md)
- [Scrape.do vs Spider](https://www.anchorterminal.com/compare/scrape-do-vs-spider-cloud.md)
- [Scrape.do vs Zyte API](https://www.anchorterminal.com/compare/scrape-do-vs-zyte.md)
- [ScrapeGraphAI vs Spider](https://www.anchorterminal.com/compare/scrapegraphai-vs-spider-cloud.md)
- [ScrapeGraphAI vs Zyte API](https://www.anchorterminal.com/compare/scrapegraphai-vs-zyte.md)
- [Scrapeless vs Spider](https://www.anchorterminal.com/compare/scrapeless-vs-spider-cloud.md)
- [Scrapeless vs Zyte API](https://www.anchorterminal.com/compare/scrapeless-vs-zyte.md)
- [Scrapfly vs Spider](https://www.anchorterminal.com/compare/scrapfly-vs-spider-cloud.md)
- [Scrapfly vs Zyte API](https://www.anchorterminal.com/compare/scrapfly-vs-zyte.md)
- [ScrapingAnt vs Spider](https://www.anchorterminal.com/compare/scrapingant-vs-spider-cloud.md)
- [ScrapingAnt vs Zyte API](https://www.anchorterminal.com/compare/scrapingant-vs-zyte.md)
- [ScrapingBee vs Spider](https://www.anchorterminal.com/compare/scrapingbee-vs-spider-cloud.md)
- [ScrapingBee vs Zyte API](https://www.anchorterminal.com/compare/scrapingbee-vs-zyte.md)
- [Scrapingdog vs Spider](https://www.anchorterminal.com/compare/scrapingdog-vs-spider-cloud.md)
- [Scrapingdog vs Zyte API](https://www.anchorterminal.com/compare/scrapingdog-vs-zyte.md)
- [Spider vs ZenRows](https://www.anchorterminal.com/compare/spider-cloud-vs-zenrows.md)
- [ZenRows vs Zyte API](https://www.anchorterminal.com/compare/zenrows-vs-zyte.md)
- [Apify MCP Server vs Spider](https://www.anchorterminal.com/compare/apify-mcp-vs-spider-cloud.md)