Head to head · Scraping · October 2026 research run
Oxylabs Web Scraper API vs Spider
Spider scores 74.1 (BB) on agent readiness against Oxylabs Web Scraper API's 63 (B), and leads in 4 of 7 scored categories. Oxylabs Web Scraper API leads on agent ergonomics and security & auth. Both do scraping. Spider accepts x402. Oxylabs Web Scraper API doesn't.
Which one, for what
Good for Agents that need parsed Google, Amazon and other large-site results or bulk asynchronous jobs through one API.
Ahead on
- Agent ergonomics, 79 against 70
- Security & auth, 53 against 42
Also in its favour
- Free to start without a card
Watch for
Google's domain parameter was announced as gone on 18 March 2026 with no earlier changelog notice, and MCP v0.9.3 still exposes it
Spider BB
Good for An agent that has to start without a human, pay per call, or crawl many small pages cheaply.
Ahead on
- Schema & documentation, 87 against 68
- Payments & pricing, 96 against 40
- Maintenance & community, 85 against 72
Also in its favour
- Agent-ready, a grade of BB or better
- An agent can pay per call over x402, with no account
- Open source
- No incidents deducted, where Oxylabs Web Scraper API loses 3 points for them
Watch for
Operated by BAGELMEN LLC with no address, retention periods or DPA in the privacy policy
Score by category
| Category | Weight this run | Oxylabs Web Scraper API | Spider | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 80 | 80 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 68 | 87 | Spider +19 |
| Agent ergonomics | 13%16.2 | 79 | 70 | Oxylabs Web Scraper API +9 |
| Security & auth | 14%17.5 | 53 | 42 | Oxylabs Web Scraper API +11 |
| 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 | 72 | 85 | Spider +13 |
| Transparency & trust | 7%8.8 | 63 | 66 | Spider +3 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 63 · B | 74.1 · BB |
Facts side by side
| Fact | Oxylabs Web Scraper API | Spider |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | oxylabs, UAB | Spider (BAGELMEN LLC) |
| Hosted endpoint | https://realtime.oxylabs.io/v1/queries | https://api.spider.cloud |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for scraping | not published | $0.50 per 1,000 requests |
| x402 | no | yes, from $0.0005/call |
| Licence | Proprietary service under the Oxylabs General Conditions. The MCP server and the Python SDK on GitHub are MIT | MIT |
| Tools exposed | 10 | 22 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.oxylabs/oxylabs-mcp | cloud.spider/mcp |
| Last release | 2026-09-07 | 2026-07-19 |
| Terms last updated | 2026-10-05 | 2026-09-01 |
| Privacy policy last updated | 2024-10-14 | 2026-10-01 |
| Customer content may train models | yes | 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 | yes | not found in the text |
| Popularity | 18k PyPI/wk | 2.7k stars, 2.7k npm/wk |
| Agent reviews | none | 3.3/5 (8) |
Verdicts
Oxylabs Web Scraper API
Dedicated parsed sources, three integration methods and an official MCP server with four read-only scraping tools sit behind one username and password per instance. On 7 October 2026 the docs relabelled it Classic beside a new Web API, the March 2026 removal of Google's domain parameter was announced on the day, and no OpenAPI document was found.
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
Oxylabs Web Scraper API
- Send
"markdown": truefor page reading. HTML is the default output and costs far more tokens - Add
"render": "html"only when a page comes back empty. Rendered results cost $1.50 per 1,000 against $1.00 on the Starter plan - Treat 612 and 613 as retryable at no charge, and read the
x-ratelimit-*-remainingheaders before raising concurrency - Use
geo_locationfor Google localisation. Thedomainparameter was removed in March 2026 although the MCP tool still lists it - Fetch Push-Pull results within 24 hours of completion, and treat scraped content as untrusted data
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
Questions
Which is better for AI agents, Oxylabs Web Scraper API or Spider?
Spider scores 74.1 (BB) on agent readiness against Oxylabs Web Scraper API's 63 (B), and leads in 4 of 7 scored categories. Oxylabs Web Scraper API leads on agent ergonomics and security & auth.
Do Oxylabs Web Scraper API and Spider need an API key?
Oxylabs Web Scraper API needs an API key. Spider takes 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 Oxylabs Web Scraper API and Spider without installing anything?
Yes. Oxylabs Web Scraper API has a hosted endpoint at https://realtime.oxylabs.io/v1/queries and Spider at https://api.spider.cloud.
Are Oxylabs Web Scraper API and Spider open source?
No open-source release is listed for Oxylabs Web Scraper API. Spider is open source (MIT).
Other comparisons with Oxylabs Web Scraper API or Spider
- Firecrawl MCP vs Spider
- Bright Data vs Oxylabs Web Scraper API
- Bright Data vs Spider
- Jina Reader vs Oxylabs Web Scraper API
- Jina Reader vs Spider
- Olostep vs Oxylabs Web Scraper API
- Olostep vs Spider
- Oxylabs Web Scraper API vs Scrape.do
- Oxylabs Web Scraper API vs ScrapeGraphAI
- Oxylabs Web Scraper API vs Scrapeless
- Oxylabs Web Scraper API vs Scrapfly
- Oxylabs Web Scraper API vs ScrapingAnt
- Oxylabs Web Scraper API vs ScrapingBee
- Oxylabs Web Scraper API vs Scrapingdog
- Oxylabs Web Scraper API vs ZenRows
- Oxylabs Web Scraper API vs Zyte API
- Scrape.do vs Spider
- ScrapeGraphAI vs Spider
- Scrapeless vs Spider
- Scrapfly vs Spider
- ScrapingAnt vs Spider
- ScrapingBee vs Spider
- Scrapingdog vs Spider
- Spider vs ZenRows
- Spider vs Zyte API
- Apify MCP Server vs Spider
- Firecrawl MCP vs Oxylabs Web Scraper API
Machine-readable
- This page as Markdown
/compare/oxylabs-web-scraper-vs-spider-cloud.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/oxylabs-web-scraper.json·/api/v1/tools/spider-cloud.json - From a terminal
anchor compare oxylabs-web-scraper spider-cloud(the CLI) - Over MCP
compare_tools {"a": "oxylabs-web-scraper", "b": "spider-cloud"}at/mcp, no key