Zyte vs UnblockingAPI for large-scale web data collection
Zyte API prices a browser-rendered response by site tier. UnblockingAPI charges 1 credit for every successful request, whatever the site.
This guide puts both on the same footing, works through three volumes, and says where Zyte may fit better.
The short version
- Zyte API: per successful browser-rendered response, priced by site tier (1 to 5). On our pricing page we show tier 3 of 5: $4.02 per 1,000 pay as you go, $1.92 per 1,000 on a $500/month commitment. Tier 5 sites cost 4x more.
- UnblockingAPI: 1 credit per successful request. Rendering, premium proxies, country routing and retries are included. €1.00 per 1,000 on the €10 pack, €0.83 on the €500 pack.
- The real difference: with Zyte the price of a request depends on the site you fetch. With UnblockingAPI it does not.
Prices are list prices as published in September 2026 on UnblockingAPI's pricing page, in each provider's own currency, with no conversion applied. Check both before you decide.
The rate card
Price per 1,000 JavaScript-rendered requests through premium proxies.
| Entry option | Per 1,000 | Best self-serve option | Per 1,000 | |
|---|---|---|---|---|
| UnblockingAPI | €10 pack (one-time) | €1.00 | €500 pack (one-time) | €0.83 |
| Zyte API (tier 3 of 5) | Pay as you go | $4.02 | $500/month commitment | $1.92 |
Two things to notice.
- Zyte's rate is tied to the target. The figure above is for a moderate site. A tier 5 site costs 4x more. We cannot tell you which tier your sites fall in. Zyte can.
- One is a commitment, one is a pack. A Zyte commitment is monthly. UnblockingAPI packs are one-time purchases and the credits never expire.
Worked example 1: 10,000 rendered requests a month
A small monitoring job, about 330 pages a day.
- Zyte, pay as you go, tier 3: 10 x $4.02 = $40.20.
- UnblockingAPI: one €10 pack is 10,000 credits. €10, once.
At this size the absolute gap is small. If you are testing, the 500 free credits on signup, with no card, cover the first 500 requests.
Worked example 2: 100,000 rendered requests a month
About 3,300 requests a day.
- Zyte, pay as you go, tier 3: 100 x $4.02 = $402.
- Zyte, $500 commitment: the $1.92 rate implies about 260,000 requests for $500. At 100,000 requests you would use roughly 40% of what the commitment covers, if it is a minimum spend. Confirm the terms with Zyte.
- UnblockingAPI: one €100 pack is 110,000 credits, including a 10% bonus. That covers the month with 10,000 credits to spare, and they carry over.
Worked example 3: 500,000 rendered requests a month
About 16,000 requests a day, realistic for a team scraping a few hundred sites daily.
- Zyte, pay as you go, tier 3: 500 x $4.02 = $2,010.
- Zyte, $500 commitment: 500,000 x $1.92 = $960, if the committed rate holds beyond the commitment. We do not know that it does, so ask.
- UnblockingAPI: one €500 pack is 600,000 credits (20% bonus), or €0.83 per 1,000. 500,000 requests use most of it. The rest carries over.
If any of your targets are tier 4 or 5, the Zyte figures above go up. The UnblockingAPI figure does not move.
For the formula behind these numbers, see the credit estimate guide. For sizing a daily job, see scraping hundreds of websites every day.
Why per-site pricing is hard to plan around
Tiered pricing is fair in principle. A simple site costs less to fetch. The trouble is forecasting.
- A new target can change your bill. Add a site from a higher tier and the same page count costs more.
- You need to know the tier before you buy. For a list of hundreds of sites, that is a lookup job before you have fetched a page.
- Cost depends on mix, not volume. Two months with the same request count can invoice differently.
With a flat credit, the only two numbers to plan against are how many requests you make and how many run at once.
What else you get
- Rotating residential proxies and country routing in the same credit.
- 25 concurrent requests on every account. Going over returns 429, not a bigger bill. Need more? Ask.
- Blocked and failed requests are retried and never charged. One exception: a
wait_forselector that never appears still returns the page, and that costs 1 credit. - A hosted MCP server for AI tools.
- Support from the engineers who build the product.
Where Zyte may be the better choice
We have compared price only, not feature by feature. Test the rest yourself.
- Your targets are mostly easy sites. If Zyte's lower tiers are cheap for your mix, the gap may be smaller than the tier 3 figures suggest. We only show tier 3.
- You depend on something we do not offer. UnblockingAPI fetches public pages and returns HTML or template JSON. It does not support login flows or private content.
- You need more than 25 concurrent requests today. Talk to us about Enterprise, and compare what Zyte offers for your plan.
- You prefer a monthly commitment. Some teams like a fixed line in the budget. UnblockingAPI is packs, not subscriptions.
Neither product guarantees success on every target. Hard sites still fail sometimes. On UnblockingAPI a failure is free.
How to compare them in an hour
- Create a free account. It starts with 500 credits and no card.
- Pick 10 of your real targets, including the ones that fail today.
- Fetch each once with rendering. Note the status, the size of the HTML and whether your data is in it.
- Run the same URLs through Zyte and note the tier each one lands in.
- Compare cost per 1,000 on your own mix, not on one tier.
If you decide to move, the team offers developer setup services for migrating an existing scraper.
Next step
Start with the 500 free credits and fetch your ten hardest URLs. Then see the pricing page for the full rate card, and the ScrapingBee and ScraperAPI comparisons if you are weighing more than one provider.
Stop babysitting scrapers.
Test the fetching layer before building your parser. Start with 500 free credits and no credit card. See pricing for credits from €5, with no subscription.
One successful request is one credit. No multipliers for rendering, proxies or retries.
Related guidesBrowse all guides
How to scrape public property listing pages
Fetch JavaScript-rendered property listing pages with country-level routing and parse the returned HTML.
How to scrape e-commerce product pages and pricing data
Fetch public product pages through UnblockingAPI, parse pricing and product details from the returned HTML.
How to scrape JavaScript-rendered pages
Use real browser rendering to fetch pages that load content dynamically through client-side JavaScript.
How to scrape hundreds of websites every day without breaking your pipeline
Separate fetching from parsing, queue small jobs, validate content and work out monthly credits before you buy.
A ZenRows alternative: credit multipliers compared
Compare ZenRows and UnblockingAPI on published rates, with worked examples at three volumes and where ZenRows may be the better fit.
A Bright Data alternative with flat per-request pricing
Compare Bright Data Web Unlocker and UnblockingAPI on published rates, with worked examples and where Bright Data is the better fit.
Bulk domain rating checker: Ahrefs DR for hundreds of domains
Check Ahrefs Domain Rating, backlinks and linking websites for a list of domains with one API call each - curl, Python, CSV export and daily DR tracking.
How to give your AI app live web data
Build a fetch tool for your agent, clean pages for the model and keep RAG sources fresh with rendered, unblocked page fetches.
Connect your AI agent framework to the live web over MCP
Give agents built with the Vercel AI SDK, LangChain or the Claude API a real browser through UnblockingAPI's hosted MCP server.
Scraping API cost at scale: estimate monthly credits for 500,000 requests
Count requests, find the credit multiplier, price the credits and leave headroom, with a worked example for 500,000 requests a month.