Comparison guide

A Bright Data alternative with flat per-request pricing

Bright Data's Web Unlocker bills per successful request. That is already simpler than credit multipliers. But if you scrape a lot of ordinary sites every day, two things still make the bill hard to predict: the cheapest rate sits behind a large monthly commitment, and premium domains cost more at a rate that is not published.

This guide compares the two on the numbers on UnblockingAPI's pricing page, and says where Bright Data is the better fit.

5 min read

What you are comparing

Both products fetch a public URL, get past bot protection and return the page. The difference is in how you pay.

  • Bright Data Web Unlocker: per successful request, rendering included. Standard domains only. Premium domains are billed higher at an unpublished rate.
  • UnblockingAPI: one credit per successful request. Rendering, premium proxies, country routing and retries are included. Credits come in one-time packs that never expire, with no subscription. Blocked and failed requests are not billed. One thing to know: a wait_for selector that never shows up still returns the page as it loaded, so that request counts as a success and costs 1 credit.

The rate card

Price per 1,000 JavaScript-rendered requests through premium proxies, on each platform's public pricing. UnblockingAPI is in euros and Bright Data in dollars. No conversion is applied, as on the pricing page.

Entry pricePer 1,000Best self-serve ratePer 1,000
UnblockingAPI€10 pack (10,000 credits)€1.00€500 pack (600,000 credits, one-time)€0.83
Bright Data Web UnlockerPay as you go (usage-based)$1.50Scale, $1,999/month$1.00

Bright Data's rates were published in September 2026. UnblockingAPI's are its current credit packs, from €5 to €500, where bigger packs add up to 20% bonus credits. Check both before you decide.

Two things stand out.

  1. The entry rates are close. €1.00 against $1.50 per 1,000. At low volume the gap is small.
  2. The best rates sit at very different commitments. UnblockingAPI reaches €0.83 with a one-time €500 pack, with no subscription and credits that never expire. Bright Data's $1.00 belongs to a $1,999-a-month plan.

A worked example: 700,000 rendered requests a month

Say you fetch 700,000 rendered pages a month. That is about 23,000 requests a day across your target list.

  • UnblockingAPI packs: one €500 pack (600,000 credits) plus one €100 pack (110,000 credits) is €600 for 710,000 credits, about €0.86 per 1,000 requests. One request is one credit, and the 10,000 spare credits carry over because pack credits never expire.
  • Bright Data pay as you go: 700 × $1.50 = $1,050, on standard domains only.

The $1.00 rate is tied to the $1,999 Scale plan, so it does not help at this volume unless you grow into that plan.

Now a smaller month, 100,000 rendered requests:

  • UnblockingAPI packs: one €100 pack is €100 for 110,000 credits, including a 10% bonus. That covers the month with 10,000 credits to spare, and they never expire.
  • Bright Data pay as you go: 100 × $1.50 = $150.

The gap is real but modest. At this volume, price is not the main reason to switch.

Where the model differs

  • Premium domains. Bright Data's page says premium domains cost more at a rate it does not publish. You find out the cost on your hardest targets after the first invoice. UnblockingAPI has no such tier: a hard site costs one credit, the same as an easy one.
  • Retries and blocks. A request that is blocked or fails is not billed. You can retry without watching the meter, though you should still cap retries, because they cost time. A page that loads but never shows your wait_for selector is a delivered page and costs 1 credit.
  • Country routing and proxies. Our proxy network (residential and mobile connections where a site needs them) and country-level routing are part of every request. They are not a separate line.
  • A budget you can compute. Credits equal requests. Sites × pages × days gives the monthly bill before you start. The guide to scraping hundreds of websites every day walks through that arithmetic.
  • Concurrency is the same for everyone. Every account can have 25 requests in flight, whichever pack you buy. Going over returns 429 rather than costing extra. Check this against your run window, and ask us if you need more.

What you also get

  • A hosted MCP server, for AI tools that need to read pages that block bots.
  • Support from the engineers who build the product, with no sales call needed to start.

Where Bright Data is the better choice

We would rather you pick the right tool.

  • You need more than an unblocker. Bright Data is a large provider. If you rely on its other products, UnblockingAPI is not a replacement for them. It does one job: fetching public pages.
  • You want volume at a lower per-request rate than we list. At very high volume, talk to both. UnblockingAPI offers custom Enterprise pricing for workloads beyond the 600,000-credit pack or more than 25 concurrent requests.
  • Your targets sit behind a login. UnblockingAPI is built for public web data only. It does not support login flows or private content.

Neither product guarantees success on every target. Test yours.

How to test it in an hour

  1. Create a free account. It starts with 500 credits and no card.
  2. Take 10 of your real targets, including the hard ones.
  3. Fetch each once with rendering and note the status, the size of the HTML and whether the data you need is in it.
  4. Do the same on Bright Data with the same URLs.
  5. Count the credits you used. On UnblockingAPI it is one per successful request.

If you already run a scraper on another provider, the team offers developer setup services for migration.

Next step

Start with the 500 free credits, no card, and fetch your ten hardest URLs. If you want a cost estimate for your own volume, the credit estimate guide has the formula, and the pricing page has the full rate card.

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.

Zyte vs UnblockingAPI for large-scale web data collection

Compare Zyte API tiered pricing with a flat one credit per request, with worked examples at three volumes and where Zyte may fit better.

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.

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.