# ZenRows alternative? From $0.16 per 1,000 pages, no plan

Spider costs from $0.16 per 1,000 pages on Nov 17 static pages. Cost varies by site. ZenRows' pricing page that day lists Build at $19 a month for 45,000 credits.

Canonical: https://spider.cloud/blog/spider-alternative-to-zenrows/

Spider costs from $0.16 per 1,000 pages, the rate we measured on 25 static pages on November 17, 2026, with no plan to fill and credits that never expire.

[Cost varies by site](/guides/pricing-and-plans/#what-pages-cost-by-site).

ZenRows’ pricing page, read on November 17, puts its entry plan, Build B1, at $19 a month for 45,000 credits, and its pricing docs say plan credits expire at each renewal. At the November 17 rate, 45,000 static pages cost $7.20, under B1 on either billing cycle. Documentation and articles measured $0.27 to $0.33 per 1,000 in our November 6 run, so 45,000 of them cost $12.15 to $14.85, still under B1 on either cycle. On Unlimited’s standard proxies, 200,000 pages cost $40 a month and 300,000 cost $56.25, whatever the pages weigh, if each takes 25 seconds or less. On ZenRows those months take Launch L1 at $69, and L1 plus one top-up at $88.50, or $57.50 and $73.75 a month billed yearly by our calculation.

Rendering widens the gap. ZenRows bills a rendered request at 5 credits, so 100,000 rendered pages take Launch L2 at $99 a month, and 200,000 take Growth G1 at $199. On Unlimited’s standard proxies, a browser request counts as 2, so the $40 plan runs one at a time. That carries 100,000 rendered pages a month if each takes 25 seconds or less, and 200,000 if each takes 12 seconds or less. Page weight does not change the price. Rendered pages took a median 10.0 seconds in [our timed run](/blog/how-web-scraping-works/) of November 16, 2026. We have not measured protected pages on Unlimited, or a premium proxy on pay as you go.

Spider is a research lab for web data quality. Its API bills the bandwidth and compute time each page used, with no multiplier for JavaScript rendering. ZenRows sells monthly credit plans in which a standard request is 1 credit, rendering 5, premium proxies 10 and both together 25. It is built for teams that want auto mode to find a working setup for each request and bill only that one. The [comparison page](/compare/) covers the rest of the field.

## Spider next to ZenRows

| Feature                        | Spider                                                                                                                                                                                       | ZenRows                                                                                      |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| How it bills                   | From $0.16 per 1,000 pages on the meter, measured on static pages on November 17. Cost varies by site. The meter is $1 per GB plus $0.0001 per CPU minute, and Unlimited is from $40 a month | Monthly plan credits, 1 to 25 credits a request by feature                                   |
| 45,000 pages a month           | From $7.20 on the meter at the November 17 static rate, or $40 on Unlimited’s standard proxies if each page takes 115 s or less                                                              | $19 on Build B1. Billed yearly, $15.83 a month by our calculation                            |
| 200,000 pages a month          | From $32 on the meter at the November 17 static rate, or $40 on Unlimited’s standard proxies if each page takes 25 s or less                                                                 | $69 on Launch L1. Billed yearly, $57.50 a month by our calculation                           |
| 200,000 rendered pages a month | $40 on Unlimited’s standard proxies if each page takes 25 s or less                                                                                                                          | $199 on Growth G1, at 5 credits a page. Billed yearly, $165.83 a month by our calculation    |
| Unused balance                 | Credits never expire                                                                                                                                                                         | Plan credits expire at each renewal, and top-up credits roll over once                       |
| JavaScript rendering           | Part of compute on the meter, with no multiplier. Unlimited’s price stays the same when pages render                                                                                         | 5 credits a request, 25 with premium proxies                                                 |
| Request limit                  | Pay as you go starts at 10,000 requests per minute and rises through four levels to 80,000 as the account uses more.                                                                         | 5 concurrent requests on Free, 20 to 400 on Build through Scale, 500 to 1,000+ on Enterprise |
| Open source                    | The crawler engine, MIT, self-hostable                                                                                                                                                       | Clients and MCP server, MIT, with the API hosted                                             |
| SDKs                           | Python, JavaScript, Rust, Go                                                                                                                                                                 | Python, Node, Go                                                                             |
| MCP server                     | 27 tools                                                                                                                                                                                     | Yes                                                                                          |

ZenRows’ column comes from its pricing page, pricing docs and API reference, read on November 17, 2026. We calculated the yearly figures from its rule of ten months’ price for twelve months of credits. The Spider rows start at the static-page rate, and the next section shows the runs. The [compare page](/compare/) puts every API we have written up in one table, and the [ScrapingBee](/blog/spider-alternative-to-scrapingbee/) and [ScraperAPI](/blog/spider-alternative-to-scraperapi/) posts cover the two credit models closest to ZenRows’.

## The bill at 45,000, 200,000 and 300,000 pages

Spider’s column starts at the static-page rate in the [pricing guide](/guides/pricing-and-plans/#what-pages-cost-by-site), and a heavier site costs more. Each rate there is the cost per 1,000 of 25 pages of one kind, fetched through `/scrape` with markdown output. The static set ran on November 17 against a public practice site with the cache off. Documentation and articles come from the November 6 run in [the true-cost report](/blog/true-cost-of-web-scraping-at-scale/), in smart mode.

| Pages a month | Spider, from the static rate of November 17                                                | ZenRows, monthly             | ZenRows, billed yearly, per month, calculated |
| ------------- | ------------------------------------------------------------------------------------------ | ---------------------------- | --------------------------------------------- |
| 45,000        | From $7.20 on the meter, or $40 on Unlimited in http mode if each page takes 115 s or less | $19 on Build B1              | $15.83                                        |
| 200,000       | From $32 on the meter, or $40 on Unlimited in http mode if each page takes 25 s or less    | $69 on Launch L1             | $57.50                                        |
| 300,000       | From $48 on the meter, or $56.25 on Unlimited in http mode if each page takes 25 s or less | $88.50 on L1 plus one top-up | $73.75                                        |

Documentation and articles measured $0.27 to $0.33 per 1,000 in the November 6 run, which puts 45,000 of them at $12.15 to $14.85, still under ZenRows’ yearly B1 price. [Unlimited](/docs/api/unlimited/) sells requests at once, $40 a month for 2 in http mode and $56.25 for 3, and it does not bill by page weight. A request counts as 1 in http mode and 2 in browser mode. Smart mode, the default, counts as 1, and as 2 once a page needs a browser. Over a 30-day month in http mode, a plan of 2 finishes 200,000 pages and a plan of 3 finishes 300,000 if each page takes 25 seconds or less. Each seconds-per-page bound in this post assumes the plan is full for the whole 30 days. On documentation and articles, the meter stays under Unlimited’s $40 until somewhere between 120,000 and 150,000 pages a month. Unlimited runs on standard proxies, reaches 15 countries through `country_code`, and sits under the [fair use](/eula/#fair-use) terms. We have not measured it on protected pages. It does not support Google search, multi-account use or social media automation on sites such as LinkedIn and Facebook. Those jobs run on pay as you go.

We calculated the yearly column as ten months’ price spread over twelve, since a yearly plan charges that up front for twelve months of credits. The 300,000 row adds one L1 top-up pack of 50,000 credits, $19.50 a month or $195 a year, from the pricing docs. On the meter, static pages come in under both ZenRows columns and under Unlimited in every row, and documentation and articles do at 45,000. At 200,000 and 300,000 in http mode, Unlimited’s $40 and $56.25 come in under both columns whatever the pages weigh, if each page takes 25 seconds or less. We have not measured protected pages on its standard proxies, or a premium proxy on the meter.

### Rendered pages

ZenRows bills a rendered request at 5 credits, so a month of rendered pages needs five times the credits. Each ZenRows price below is the cheapest plan that covers the month at the prices in its pricing docs, and a smaller plan with top-up packs costs more in every row. Unlimited sells requests at once rather than pages. A browser request counts as 2, so a plan runs half its size in browser requests at once, rounded down, and the table below uses that count.

| Rendered pages a month | Spider, Unlimited                                       | ZenRows, monthly  | ZenRows, billed yearly, per month, calculated |
| ---------------------- | ------------------------------------------------------- | ----------------- | --------------------------------------------- |
| 45,000                 | $40 if each page takes 57 s or less                     | $69 on Launch L1  | $57.50                                        |
| 100,000                | $40 if each page takes 25 s or less                     | $99 on Launch L2  | $82.50                                        |
| 200,000                | $40 if each page takes 12 s or less                     | $199 on Growth G1 | $165.83                                       |
| 300,000                | $72.50 for a plan of 4, if each page takes 17 s or less | $279 on Growth G2 | $232.50                                       |

In [our timed run](/blog/how-web-scraping-works/) of November 16, 2026, rendered fetches of 29 documentation, news and store product pages took a median 10.0 seconds and cost a median $1.40 per 1,000 on the meter. At that median the meter reaches Unlimited’s $40 at about 29,000 rendered pages a month. Every volume in the table is past that point, so Unlimited is the cheaper Spider path there if each page stays within the time bound in its row. We have not measured protected pages on Unlimited, or rendered pages through a premium proxy.

## Where Spider comes out ahead

**No plan to fill.** Build B1 bills $19 whether the month used 45,000 credits or 4,500, and the unused credits expire at renewal. Spider bills the pages you fetched from a balance that keeps, topped up from $5.

**Rendering without a multiplier.** A rendered request costs 5 ZenRows credits, and 25 on premium proxies, so B1’s 45,000 credits cover 9,000 rendered pages, or 1,800 rendered on premium proxies. Spider’s default smart mode opens a browser only when a page needs one, and in the November 6 run it cost the same per 1,000 pages as plain HTTP on the documentation, article, store product and reference sets, within a tenth of a cent. Forcing `request: "browser"` on every page costs more on the meter, because the browser then fetches each page’s scripts and data calls. On Unlimited a browser request counts as 2, so the $40 plan runs one at a time and carries 200,000 rendered pages a month if each takes 12 seconds or less, where ZenRows needs Growth G1 at $199. We have not measured protected pages there.

**Residential traffic by the GB.** ZenRows bills residential bandwidth at 25,000 credits per GB. With every credit spent on bandwidth, that works out to $10.56 a GB on Build B1 and $1.67 on Scale S5, by our arithmetic on its plan table. Spider’s [proxy mode](/guides/proxy-mode/) takes any HTTP, HTTPS or SOCKS5 client at `proxy.spider.cloud` and meters from $1 per GB.

**The sites ZenRows sends to premium proxies.** ZenRows’ API reference names Amazon, Walmart and Zillow among the jobs for premium proxies, at 10 credits a request, or 25 with rendering. In our [1,000-URL benchmark](/blog/firecrawl-vs-crawl4ai-vs-spider-honest-benchmark/) of February 2026, Spider returned 99.9% of the list with no extra configuration, and 99.6% of the 250 pages on large consumer sites such as Amazon, Nike, Walmart, Zillow and Bloomberg. ZenRows was not in that run, and it measured success, not cost.

**Pay as you go at a lower rate.** ZenRows’ agentic payments docs, read November 17, 2026, list pay as you go credits for AI agents at $0.50 per 1,000 credits, or 1,000 standard requests, for Fetch and Extract. The minimum purchase is 10,000 credits. Spider’s meter measured $0.16 per 1,000 static pages on November 17, and $0.27 to $0.33 for documentation and articles on November 6.

**A limit that grows with the account.** Pay as you go starts at 10,000 requests per minute and rises through four levels to 80,000 as the account uses more. ZenRows caps requests in flight by plan tier, from 20 on Build to 400 on S5, so a higher cap means a larger plan. The two limits measure different things, but only Spider’s moves without a plan change.

**The engine is open.** Spider’s crawler, [spider-rs/spider](https://github.com/spider-rs/spider), is MIT licensed Rust that you can run on your own machines. ZenRows publishes its clients and MCP server under MIT and keeps the scraping service hosted.

## ZenRows pricing, November 2026

ZenRows sells four paid tiers over a free plan. Build, Launch and Growth come in three sizes each, and Scale in five. The monthly prices below come from its [pricing page](https://www.zenrows.com/pricing), which gives each tier’s range, and its pricing docs, which price each size, both read on November 17, 2026.

| Plan                | Per month          | Credits                     | Requests in flight |
| ------------------- | ------------------ | --------------------------- | ------------------ |
| Free                | $0                 | 5,000                       | 5                  |
| Build B1 / B2 / B3  | $19 / $29 / $39    | 45,000 / 80,000 / 120,000   | 20                 |
| Launch L1 / L2 / L3 | $69 / $99 / $129   | 250,000 / 500,000 / 700,000 | 50                 |
| Growth G1 / G2 / G3 | $199 / $279 / $399 | 1.2M / 2M / 3M              | 100                |
| Scale S1 / S2 / S3  | $549 / $749 / $999 | 5M / 8M / 12.5M             | 200                |
| Scale S4 / S5       | $1,999 / $2,999    | 28M / 45M                   | 300 / 400          |
| Enterprise          | Custom             | Over 45M                    | 500 to 1,000+      |

The free plan needs no card and refreshes each month with no rollover. Billed yearly, ZenRows charges ten months up front for twelve, the 17% saving its pricing page shows, and the plan toggle there starts on the yearly price. The page rounds those prices, so B1 shows as $16 and L1 as $58. A yearly plan gets the whole year’s credits as one balance. Plan credits expire at each renewal, monthly or yearly. An upgrade carries unused credits onto the new plan once, and a downgrade lets unused plan credits expire while top-up credits carry over once.

### Credits per request

| Request                       | Credits                         |
| ----------------------------- | ------------------------------- |
| Standard request              | 1                               |
| JavaScript rendering          | 5                               |
| Premium proxies               | 10                              |
| Rendering and premium proxies | 25                              |
| Residential bandwidth         | 25,000 per GB                   |
| ZenRows Browser               | 5 per minute plus 25,000 per GB |

ZenRows calls these weights fixed on every plan. Its auto mode, `mode=auto`, bills only the setup that succeeded, so one request costs 1 to 25 credits. Crawl has no fee of its own and bills each page it opens as an auto mode Fetch, and Batch bills like Fetch. A response over the plan’s size cap returns a 413 error. The cap is 5 MB on Free and Build, 10 MB on Launch and Growth, and 20 MB on Scale.

The pricing docs, read November 17, 2026, give each paid plan one top-up pack for a short month, from 11,000 credits for $6.50 on B1 to 6 million for $560 on S5. A period allows 10 packs, and unused pack credits roll into the next period once, then expire. On a yearly plan a pack costs ten times its monthly price and adds twelve times the credits.

### A rendered page on premium proxies, plan by plan

At 25 credits for a rendered page on premium proxies, ZenRows’ plans work out as below. This is arithmetic on its own tables at monthly prices, not a measurement, and yearly billing takes a sixth off each figure. On Spider, a page fetched through a premium proxy bills its bandwidth at 1.5x to 4x the base rate. We have not measured Spider on pages that need a premium proxy, so the table has no Spider column.

| Plan             | Credits    | Pages at 25 credits | Per 1,000 pages |
| ---------------- | ---------- | ------------------- | --------------- |
| Build B1, $19    | 45,000     | 1,800               | $10.56          |
| Launch L1, $69   | 250,000    | 10,000              | $6.90           |
| Growth G1, $199  | 1,200,000  | 48,000              | $4.15           |
| Scale S1, $549   | 5,000,000  | 200,000             | $2.75           |
| Scale S3, $999   | 12,500,000 | 500,000             | $2.00           |
| Scale S5, $2,999 | 45,000,000 | 1,800,000           | $1.67           |

## Where ZenRows fits

**A free plan that refreshes.** 5,000 credits every month with no card will run a small monitor.

**Credits an agent can buy.** AI agents with no ZenRows account can buy Fetch and Extract at agents.zenrows.com, paying over x402, MPP or a card, at the same credit weights.

**Billing on success.** ZenRows spends credits only on successful requests, and a 404 or 410 counts as one.

## Moving a ZenRows call to Spider

A ZenRows Fetch in auto mode that asks for markdown:

```python
import os
from zenrows import ZenRowsClient

client = ZenRowsClient(os.getenv("ZENROWS_API_KEY"))

response = client.fetch(
    "https://example.com/listings",
    params={"mode": "auto", "response_type": "markdown"},
)
# Auto mode bills 1 to 25 credits, for the setup that worked.
markdown = response.text
```

The same page on Spider:

```python
import os
from spider import Spider

client = Spider(api_key=os.getenv("SPIDER_API_KEY"))

pages = client.scrape_url(
    "https://example.com/listings",
    params={"return_format": "markdown"},
)
print(pages[0]["costs"]["total_cost"])  # dollars billed for this page
markdown = pages[0]["content"]
```

Smart mode is Spider’s default, so the call names no mode. For a whole site, `crawl_url` takes the start URL and a `limit`, and the [crawl endpoint](/docs/api/crawl/) can stream pages as JSONL while it runs.

## When to pick which

Pick Spider for static pages, documentation and articles at the volumes priced above, for rendered pages on Unlimited, for months that vary, and for big consumer sites with no extra configuration, where it returned 99.6% in our February 2026 benchmark. Rendered, 200,000 pages a month take ZenRows’ Growth G1 at $199, against $40 on Unlimited’s standard proxies within the time per page shown above. We have not measured protected pages on Unlimited, or a premium proxy on the meter. Start on the meter, and move to Unlimited when the plan your month needs costs less than the meter bill.

Pick ZenRows if its free plan’s 5,000 credits a month cover your volume, if an agent should buy its own credits with no account, or if you want a year of credits paid up front as one balance.

The [playground](/playground/) prices one page from your own list in a single request, which tells you more than any table here.

## Frequently asked questions

### Is Spider cheaper than ZenRows?

Yes, at the volumes and page kinds below, on both of ZenRows' billing cycles. Spider costs from $0.16 per 1,000 pages, the rate we measured on 25 static pages on November 17, 2026. Cost varies by site. At the November 17 rate, 45,000 static pages cost $7.20. Documentation and articles measured $0.27 to $0.33 per 1,000 in our November 6 run, so 45,000 of them cost $12.15 to $14.85. ZenRows' pricing page and docs, read November 17, 2026, list Build B1 at $19 a month. Billed yearly, it comes to $15.83 a month by our calculation. On Unlimited's standard proxies, 200,000 pages cost $40 a month and 300,000 cost $56.25, whatever the pages weigh, if each takes 25 seconds or less. On ZenRows those months take Launch L1 at $69, and L1 plus one top-up at $88.50, at the prices in the same docs. Billed yearly, they come to $57.50 and $73.75 a month by our calculation. ZenRows bills a rendered request at 5 credits, so 200,000 rendered pages take Growth G1 at $199 a month, against the same $40 on Unlimited. We have not measured protected pages on Unlimited, or a premium proxy on pay as you go.

### Do ZenRows credits roll over?

Plan credits do not. They expire at each renewal, monthly or yearly. Top-up credits roll into the next period once, and an upgrade carries unused credits onto the new plan once. Spider credits never expire.

### Does ZenRows charge for failed requests?

No. ZenRows spends credits only on successful requests and counts 404 and 410 responses as successes. Spider bills differently. An attempt bills for the bandwidth and compute it used, whatever status the page returns. A failed page is not free. A blocked page usually costs a fraction of a cent.

### Does ZenRows have a crawler?

Yes. ZenRows Crawl starts from one URL and follows links to the depth and page count you set, as many as 100,000 pages, then returns HTML or markdown with webhooks and an NDJSON download. ZenRows' pricing docs, read November 17, 2026, say Crawl has no fee of its own and each page bills as a Fetch at 1 to 25 credits. Spider's crawl endpoint bills each page for its bytes and compute, and it can stream pages as JSONL while the crawl runs.

### How many credits does a ZenRows request cost?

ZenRows' pricing page, read November 17, 2026, prices a standard request at 1 credit, JavaScript rendering at 5, premium proxies at 10, and both together at 25. On the monthly plan prices in its pricing docs, read the same day, a 25 credit page comes to $10.56 per 1,000 on Build B1 and $1.67 per 1,000 on Scale S5, by our arithmetic.

### Is there a free ZenRows alternative?

Spider's crawler engine, spider-rs/spider, is MIT licensed and self-hostable. The hosted API gives you 2,500 free credits, worth $0.25, if your signup passes our checks. After that it runs pay as you go with top ups from $5, and the credits never expire.

## Sources

1. [ZenRows pricing page, read November 17, 2026](https://www.zenrows.com/pricing)
2. [ZenRows pricing docs, plans, top-ups and billing rules, read November 17, 2026](https://docs.zenrows.com/first-steps/pricing.md)
3. [ZenRows agentic payments docs, pay as you go prices, read November 17, 2026](https://docs.zenrows.com/first-steps/agentic-payments.md)
4. [ZenRows Fetch API reference](https://docs.zenrows.com/universal-scraper-api/api-reference)
5. [ZenRows Crawl endpoints](https://docs.zenrows.com/crawl/endpoints.md)
6. [ZenRows Python SDK](https://github.com/ZenRows/zenrows-python-sdk)
7. [ZenRows MCP server](https://github.com/ZenRows/zenrows-mcp)
8. [Spider pricing guide, what pages cost by site: static pages from $0.16 per 1,000, measured 2026-11-17 on 25 pages with the cache off, and the 2026-11-06 daily run](https://spider.cloud/guides/pricing-and-plans/)
9. [Spider 1,000-URL benchmark, February 2026](https://spider.cloud/blog/firecrawl-vs-crawl4ai-vs-spider-honest-benchmark/)
10. [Spider Unlimited docs: plan prices, request modes, standard proxies, the 429 when the plan is full, what Unlimited does not support](https://spider.cloud/docs/api/unlimited/)
11. [Spider rate limits](https://spider.cloud/docs/core/rate-limits/)
12. [How web scraping works: the cost of a plain fetch and of a rendered fetch on the same pages, measured 2026-11-16](https://spider.cloud/blog/how-web-scraping-works/)
13. [Spider MCP server](https://spider.cloud/mcp/)
14. [Web scraping at scale: a daily run of 25 pages per kind of page, November 6 to 17, 2026, with twelve-day medians](https://spider.cloud/blog/true-cost-of-web-scraping-at-scale/)
15. [Spider crawler engine](https://github.com/spider-rs/spider)
