Data APIs · billed per successful request

Web Unblocker

Used like a proxy, behaves like an API. It picks the route and browser behaviour per request so that you do not maintain that logic.

What it is

You point your existing HTTP client at it, as with any proxy, and send requests normally.

Request-priced, so the cost of a hard target is explicit rather than hidden in retry traffic.

Good for

  • Targets where a plain residential proxy still fails often.
  • Teams that would otherwise maintain browser-fingerprint logic of their own.

Not for

  • Easy targets. Paying per request for a page a datacenter proxy fetches reliably is waste.

Specification

Metered byRequest
InterfaceProxy endpoint, plus API options
OutputThe response from the target
DocumentationOptions and limits are in the API reference

Prices, limits and country coverage for your account are shown in the dashboard before you pay. See how pricing works.

How to evaluate it

  1. Test on the single hardest target you have and measure success rate against your current setup.
  2. Compare cost per successful page with the cost of residential traffic plus the engineering time you currently spend.

Works well for

Test it on your own targets.

Create an account, run the measurement harness against your real workload, and read the numbers before you commit to anything.