Hybrid unlock lane for allowlisted, vendor-hardened domains
Website WebUnlocker
Route blocked URLs through BrowserSolver unlock engine, a blend of realistic rendering and request-mode crawling tuned for Cloudflare, DataDome, Akamai, PerimeterX, and similar stacks on approved domains.
- Supported domains only: confirm coverage, or contact support if the host is not enabled yet
- Redirect and raw-source controls matching Crawler semantics
- Failed attempts after retries are not billed
Hybrid
render + fetch
Allowlist
required
Vendor
playbooks
When cheap HTTP and render are not enough
Retailer and marketplace scrapes often hit vendor stacks after a clean Crawler or Rendering call fails. WebUnlocker is a separate mode on the same balance, one URL per call, allowlisted domains only, hybrid engine when WAF layers block extraction.
- Confirm the domain is supported before production traffic, or contact support if it is not enabled yet
- Maintained playbooks for Cloudflare, DataDome, Akamai, PerimeterX, Kasada, and peers
- Failed retries after exhaustion are not billed
Unlocked HTML back into your parser
After challenges clear, page bodies land in the same shape as Website Crawler, no second integration path for protected extracts.
- Pass-rate visibility per allowlisted domain in the dashboard
- Run Website AntiBot first when you are unsure which layer is blocking
- Escalate from 1× Crawler or 2× Rendering only on URLs that still fail after probe
When Crawler and Rendering hit a wall
One URL per call on approved domains, after AntiBot tells you unlock is the right mode.
Allowlist
Production unlocks on approved domains.
Hybrid engine
JS rendering plus fetch-mode fallback.
Redirect control
Inspect or follow chains after unlock.
Clean HTML out
Unlocked page bodies ready for your parsers.
Session rotate
Fresh identity when blocks repeat.
Hybrid unlock
Built for vendor-hardened allowlisted domains.
Frequently asked questions
Credits, scrape types, and billing before your first production job.
Which domains support WebUnlocker?
Unlock runs on supported domains only (examples in docs include marketplaces and automotive sites). Confirm coverage first. If the host is not enabled yet, contact support before pointing production scrapers at it.
How is WebUnlocker different from Rendering?
Rendering executes JavaScript on pages you can already reach. WebUnlocker adds vendor bypass for hardened allowlisted domains, hybrid engine, and stricter domain controls.
Pick your next move
Wire up an integration, review plans, or read the API reference before your first job.
Integrations
Trigger BrowserSolver from n8n, Zapier, Make, or any stack that speaks HTTP.
Scrape your first blocked URL
Fetch, render, screenshot, or unlock from one dashboard. Proxies, browsers, and anti-bot lanes stay on our side.
- 500 signup credits
- No card to start
- All scraping modes