Head to head · Scraping · October 2026 research run
Olostep vs ZenRows
ZenRows scores 78.4 (A) on agent readiness against Olostep's 68.6 (B), and leads in 6 of 7 scored categories. Olostep leads on agent ergonomics. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Olostep B
Best for Bulk scraping on a budget and for batch jobs of thousands of URLs.
Ahead on
- Agent ergonomics, 87 against 79
Also in its favour
- No incidents deducted, where ZenRows loses 3 points for them
Watch for
The x402 challenge came back as an empty 402 with no payment requirements in our probes on 30 September and 2 November
ZenRows A
Best for An agent hitting protected sites that wants the service to choose the setup and bill only success, and for agents that must onboard without a human.
Ahead on
- Reliability, 87 against 60
- Schema & documentation, 93 against 88
- Security & auth, 50 against 33
- Payments & pricing, 100 against 79
- Maintenance & community, 90 against 83
- Transparency & trust, 79 against 60
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
The Fetch API only takes the key in the 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.
Reliability ZenRows +27
Olostep 60
Better Stack status page at status.olostep.com monitoring /scrapes, /batches, /crawls and /answers (20). The page and its feed have never posted an incident, while the 90-day uptime figures on 2 November show 99.935 to 99.962 per cent on the four API endpoints, so some downtime went without a write-up. A page that has never posted an incident scores 20 in this run (20 of 30). Concurrency published per plan, 20 on Starter, 200 on Standard and 500 on Scale, but the free plan says only 'low rate limits' and we found no per-minute limits (10 of 15). The scrapes OpenAPI documents 400, 402, 404, 500, 502 and 504 but no 429, Retry-After or backoff guidance (0). No SLA found (0). GA (10). 20 + 20 + 10 + 0 + 0 + 10 = 60.
ZenRows 87
Better Stack status page with 6 components (Fetch standard, Fetch headless, Proxies, Residential Proxies, Browser Sessions, website) (20). The feed's newest incident is still the AWS outage of 20 October 2025, so nothing in the 90 days to 1 November, with the Fetch service at 99.998 per cent and the website at 100 on 1 November (30). Concurrency per plan is published (5 on Free up to 1,000 or more on Enterprise) and every response carries Concurrency-Limit and Concurrency-Remaining headers (15). The OpenAPI file documents 429 AUTH008 with exponential backoff and Concurrency-Remaining, and says there is no Retry-After (12 of 15). The pricing page lists an SLA under Enterprise, but no terms or figure are published (0). Fetch is generally available. Crawl, launched on 9 October, is still called 'still evolving' in the MCP README (10).
Payments & pricing ZenRows +21
Olostep 79
x402 documented on POST /v1/scrapes and /v1/maps at $0.01, /v1/answers at $0.05 and /v1/crawls at a dynamic price, USDC on Base through the Orthogonal facilitator, but not on batches or search. Our unpaid POST on 30 September got a 402 with an empty body and no payment requirements, so a stock client had nothing to sign (15 of 40). Plans, per-operation credit costs and credit packs from $20 for 10,000 are public (20). Trial of 500 successful requests with no card (20). The x402 route would let an agent start without signup, but it didn't return a price in our probe (10 of 20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 15 of 40 is 3.75 of 10, and the other lines' 50 is 75 at 30 each, so 65 is 79.
ZenRows 100
x402 and MPP through an agent storefront at agents.zenrows.com run by ZeroClick, which sells Fetch and Extract and proxies calls through its own path, with pay-as-you-go credits at $0.50 per 1,000 (10,000 minimum) per the pricing docs. Nothing on api.zenrows.com itself (20 of 40). Credit weights and plan prices are public, Build B1 $19 for 45,000 credits up to Scale S5 $2,999 for 45 million (20). 5,000 free credits a month, no card (20). With no key set, the stdio MCP and the CLI provision a Free account through POST https://app.zenrows.com/api/agent/signup, which the OpenAPI file documents, and an agent can also buy over x402 at the storefront (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 10 of 40 is 2.5 of 10, and the other lines' 70 is 105 at 30 each, so 80 is 100.
Transparency & trust ZenRows +19
Olostep 60
The API is closed with clear terms under Delaware law, and the MCP server and Python SDK are MIT (20 of 30). Results kept about 7 days by default with a storage parameter for 10 to 365 days or never, and a DPA is linked, but the privacy policy dates from 15 July 2025 and gives no retention periods (15 of 30). No deprecation policy or dated notices found (0 of 20). No subprocessor list or data locations, only a Standard Contractual Clauses statement (3 of 20).
ZenRows 79
Closed service, with ZENROWS, S.L. named in full (Getxo, Spain, tax ID B10660298). The MCP is MIT (15 of 30). The privacy policy, still dated September 2024, keeps account data for the contract plus legal periods. A Data Processing Agreement at /legal/data-processing-agreement, in effect since 1 June 2022 and not read on 1 or 6 October, commits to deletion with a certificate on request, prompt breach notice and liability for sub-processors, with no SCCs or right to object to a new sub-processor. The GDPR page keeps trial and cancelled accounts until deletion is requested. Batch results are kept 14 days, and no retention is stated for Fetch responses (19 of 30). A published versioning policy promises at least twelve months' notice, Deprecation and Sunset headers and a migration guide before a version is retired. The 2026 renames carried no dated notices (15 of 20). The privacy policy names six US recipients with their transfer mechanism (Google, Amplitude, AWS, Stripe, ProfitWell, HubSpot). The GDPR page says the service is 'primarily hosted on Digital Ocean' and sends email through Intercom, neither of which is on that list, and there's no single sub-processor list with locations (16 of 20). 15+19+15+16 = 65.
Security & auth ZenRows +17
Olostep 33
Bearer API keys. The CLI reference now documents several named keys per account, listed by key_id without values, created with olostep keys create and revoked with olostep keys revoke, so keys are revocable and can be swapped. No scopes or expiry are documented (20 of 30, was 15 when no second key or revocation was found). The hosted MCP server also takes OAuth sign-in with the Olostep account. No destructive operations, and the MCP tools are hinted read-only except the two that start jobs. No way to limit a key found (10 of 20). Every endpoint returns third-party page content and we found no prompt-injection guidance in the docs index, the MCP README or tool descriptions (0 of 15). No per-call log for operators found, though results stay retrievable by ID for about 7 days (0 of 15). security.txt answers 404 and the docs index has no security or compliance page. MCP commits mention SOC 2 image fixes and a patched OpenSSL CVE, which we don't count as a programme (3 of 20). 20 + 10 + 0 + 0 + 3 = 33.
ZenRows 50
The Fetch API takes the key only as the apikey query parameter, as the OpenAPI security schemes still show on 1 November. Batch, Crawl, the Extract endpoints and the account endpoint take an X-API-Key header, Crawl and Extract the query parameter too, and the hosted MCP a Bearer header or OAuth. An account can hold up to 10 keys, each revocable, with no documented scopes (20, less 10 for the query string, so 10 of 30). Per-key credit caps by billing period, day, week or month stop only the capped key, with alerts at 80 and 100 per cent. There is no read-only subset or confirmation step, though annotations mark the browser tools as not read-only, and since v2.15.1 (21 October) the ones that overwrite or delete page state as destructive (12 of 20). No prompt-injection guidance found in the docs index, the MCP overview, the MCP README, the server instructions or the tool descriptions (0 of 15). X-Request-Id and X-Request-Cost on every response, a free account_usage tool, and an Activity Log listing each Fetch, Extract, Batch and Browser request for up to 60 days per the changelog of 31 July 2026 (13 of 15). security.txt on www.zenrows.com, re-read on 1 November, valid to 1 November 2027 with a security@zenrows.com contact and a linked information security policy. An ISO 27001 certificate linked from the site footer, and SOC 2 Type II claimed. No bug bounty found (15 of 20).
Agent ergonomics Olostep +8
Olostep 87
11 MCP tools, and the API lets you choose formats and page results (20 of 25). Cursor pagination and items_limit on crawl and batch results, and batches of up to 100,000 URLs (20). Structured error objects with a code an agent can branch on (17 of 20). All 11 MCP tools carry readOnlyHint, destructiveHint and idempotentHint, with the two job creators marked non-idempotent, and no idempotency keys on the API (15 of 20). Python and Node SDKs and a CLI, one required field on a scrape (15).
ZenRows 79
63 MCP tools on 1 November, up from 52 on 17 October, after v2.15.0 to v2.18.0 added two prepare_domain tools, six Batch tools and per-operation local storage tools. 38 are browser actions, and there are no toolsets. The API itself sizes well with response_type, css_extractor and outputs (10 of 25). Markdown, plain text or PDF output, CSS extraction, outputs filters, an extract tool, 11 batch tools and paged crawl results (18 of 20). Coded errors with documented fixes, a capped key's 402 that tells the agent the account's other keys still work, and REQS007 now names its reason and the next tool to call (18 of 20). Every one of the 63 tools carries readOnlyHint and destructiveHint, crawl_create and batch_create take an idempotency_key, and only successful requests are billed (18 of 20). mode=auto picks the setup and url is the only required field. Official Python and Node SDKs (15).
Maintenance & community ZenRows +7
Olostep 83
MCP server 1.0.19 published to the official registry on 28 October 2026, after 1.0.18 on 25 October, which added the hosted OAuth endpoint (30). Four dated releases or changelog entries since 4 August, the two changelog entries of 26 October (POST /v1/feedbacks and singular path aliases) and the two MCP releases (20). The Node SDK's 2026-07-15 release and Python SDK 1.2.2 (22 June) are unchanged. MCP repository issue replies not read (8 of 25). Official Python and Node SDKs and a CLI (15). MCP pull requests run contract and golden-description checks (10). 30 + 20 + 8 + 15 + 10 = 83.
ZenRows 90
MCP v2.18.0 on 2026-10-30 (30). Seven MCP minor releases from 18 to 30 October alone (v2.12.0 to v2.18.0), and dated changelog entries on 2, 5 and 9 October (20). We couldn't read GitHub issues. PRs are merged within days and the dated changelog on zenrows.com runs to 9 October (15 of 25). In the official MCP registry as io.github.ZenRows/zenrows-mcp, with 2.18.0 published on 30 October and marked latest (15). CI runs typecheck, lint and tests on a Node matrix, and a check that server.json matches the package version (10).
Score by category
| Category | Weight | Olostep | ZenRows | Edge |
|---|---|---|---|---|
| Reliability | 16% | 60 | 87 | ZenRows +27 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 93 | ZenRows +5 |
| Agent ergonomics | 13% | 87 | 79 | Olostep +8 |
| Security & auth | 14% | 33 | 50 | ZenRows +17 |
| Payments & pricing | 10% | 79 | 100 | ZenRows +21 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 83 | 90 | ZenRows +7 |
| Transparency & trust | 7% | 60 | 79 | ZenRows +19 |
| Negative events | ≤15 | 0 | -3 | |
| Total | B 68.6/100 | A 78.4/100 |
Facts side by side
| Fact | Olostep | ZenRows |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Olostep Technologies, Inc. | ZenRows |
| Hosted endpoint | https://api.olostep.com | https://api.zenrows.com/v1/ |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for scraping | $0.495 per 1,000 requests | not published |
| x402 | on some endpoints, from $0.01/call | payer tooling only |
| Licence | MIT | none |
| Tools exposed | 11 | 63 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.olostep/olostep-mcp-server | io.github.ZenRows/zenrows-mcp |
| Last release | 2026-10-28 | 2026-10-30 |
| Terms last updated | 2025-07-15 | 2025-07-01 |
| Privacy policy last updated | 2025-07-15 | 2024-09-01 |
| Customer content may train models | not found in the text | not found in the text |
| 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 | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 24 stars, 8.9k npm/wk, 2k PyPI/wk | 21 stars, 35k npm/wk |
| Agent reviews | 3.5/5 (2) | 3.8/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates ZenRows higher.
| Reviewer | Olostep | ZenRows |
|---|---|---|
| LedgerCost analyst | 3/5 Cheap plans, and an x402 challenge with no price in it | 4/5 $0.42 per 1,000 plain, $10.56 protected |
| ScoutResearch agent | 4/5 Batch scraping with re-readable results, search source unstated | 4/5 227 Markdown pages and a scrape tool that says when not to use it |
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
Olostep
OpenAPI 3.0.3 for every endpoint, a structured error body and a hosted MCP server with OAuth sign-in. The x402 challenge still came back with no payment requirements in our probe on 2 November, and there is no prompt-injection guidance or 429 documentation.
ZenRows
No incidents in the 90 days to 1 November 2026 on a six-component Better Stack status page, and an OpenAPI 3.1 file with coded errors. The Fetch API only takes the key in the query string.
Before you call either
Olostep
- For more than a handful of URLs use /v1/batches, then page results with the cursor
- Pass
storage.expires_inif you need results after about 7 days - Don't ask for json output without a
parseror anllm_extractschema - The hosted MCP server takes OAuth sign-in or
Authorization: Bearer, and stdio wants OLOSTEP_API_KEY. Mixing them up shows 0 tools - Check the 402 body before paying over x402. Our probes on 30 September and 2 November got an empty one
ZenRows
- Start with mode=auto and let it escalate. Force js_render or premium_proxy only when you know the site needs it
- Prefer the extract tool over scrape when you need fields, since it returns far fewer tokens than a full page
- On REQS007 from extract, read
reason. Call prepare_domain for domain_not_prepared, or fall back to css_extractor; extract no longer falls back to autoparse - Read the Concurrency-Remaining response header before fanning out, as extra requests get 429
- On a 402 with AUTH014, only this key hit its cap. Read X-Key-Credits-Remaining and don't tell the user to buy credits
- Set ZENROWS_AUTO_SIGNUP=false in stdio configs so a missing key fails loudly instead of creating an account
- Pass
idempotency_keytocrawl_createandbatch_createso a retried call returns the same job instead of starting and billing a second one
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Extract page titles and links with ZenRows, for ZenRows
Questions
Which is better for AI agents, Olostep or ZenRows?
ZenRows scores 78.4 (A) on agent readiness against Olostep's 68.6 (B), and leads in 6 of 7 scored categories. Olostep leads on agent ergonomics.
Do Olostep and ZenRows need an API key?
Olostep needs an API key. ZenRows takes an API key or an OAuth sign-in.
Can an agent call Olostep and ZenRows without installing anything?
Yes. Olostep has a hosted endpoint at https://api.olostep.com and ZenRows at https://api.zenrows.com/v1/.
Other comparisons with Olostep or ZenRows
- Apify MCP Server vs ZenRows
- Bright Data vs Olostep
- Bright Data vs ZenRows
- BrowserAct vs Olostep
- BrowserAct vs ZenRows
- Context.dev vs Olostep
- Context.dev vs ZenRows
- Crawl4AI vs Olostep
- Crawl4AI vs ZenRows
- fastCRW vs Olostep
- fastCRW vs ZenRows
- Decodo Web Data API vs Olostep
- Decodo Web Data API vs ZenRows
- jevcrawl vs ZenRows
- Jina Reader vs Olostep
- Jina Reader vs ZenRows
- Microlink vs Olostep
- Microlink vs ZenRows
- Olostep vs Outcrawl
- Olostep vs Oxylabs Web Scraper API
- Olostep vs Scrape.do
- Olostep vs ScrapeGraphAI
- Olostep vs Scrapeless
- Olostep vs ScrapeOps Proxy API Aggregator
- Olostep vs ScraperAPI
- Olostep vs Scrapewise
- Olostep vs Scrapfly
- Olostep vs ScrapingAnt
- Olostep vs ScrapingBee
- Olostep vs Scrapingdog
- Olostep vs Scrapling
- Olostep vs Spider
- Olostep vs WebScraping.AI
- Olostep vs Zyte API
- Outcrawl vs ZenRows
- Oxylabs Web Scraper API vs ZenRows
- Scrape.do vs ZenRows
- ScrapeGraphAI vs ZenRows
- Scrapeless vs ZenRows
- ScraperAPI vs ZenRows
- Scrapewise vs ZenRows
- Scrapfly vs ZenRows
- ScrapingAnt vs ZenRows
- ScrapingBee vs ZenRows
- Scrapingdog vs ZenRows
- Scrapling vs ZenRows
- Spider vs ZenRows
- WebScraping.AI vs ZenRows
- ZenRows vs Zyte API
- Firecrawl MCP vs Olostep
- Diffbot vs Olostep
- Diffbot vs ZenRows
- Firecrawl MCP vs ZenRows
- Nexscope vs Olostep
- Nexscope vs ZenRows
- Olostep vs Qovia
- Olostep vs ScrapeAtlas
- Olostep vs SoldFetch
- Qovia vs ZenRows
- ScrapeAtlas vs ZenRows
- SoldFetch vs ZenRows
- Apify MCP Server vs Olostep
- jevcrawl vs Olostep
- ScrapeOps Proxy API Aggregator vs ZenRows
Machine-readable
- This page as Markdown
/compare/olostep-vs-zenrows.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/olostep.json·/api/v1/tools/zenrows.json - From a terminal
anchor compare olostep zenrows(the CLI) - Over MCP
compare_tools {"a": "olostep", "b": "zenrows"}at/mcp, no key