Bright Data Web Unlocker
Add your own Bright Data Web Unlocker key for blocked-site fallback testing.
Bring your own Bright Data key
DeepSyte supports a bring-your-own Bright Data Web Unlocker setup from the dashboard.
Go to Dashboard -> Settings -> Bright Data Web Unlocker and add:
| Field | Value |
|---|---|
| API key | Your Bright Data API key |
| Web Unlocker zone | The zone name from your Bright Data account |
| Use mode | Off, Fallback only, or Always use Web Unlocker |
Use Test connection to verify the key and zone before enabling runtime fallback. The test runs server-side against Bright Data Web Unlocker and stores only the latest pass/fail status. Runtime fallback is ignored until the latest connection test passes.
Runtime fallback
This setting is BYO only. DeepSyte does not provide a shared Bright Data key.
When Fallback only is enabled, DeepSyte first tries the normal cloud browser. If navigation fails with a likely blocking error or the loaded page looks like a bot-block page, it retries the initial document through Bright Data Web Unlocker.
When Always use Web Unlocker is enabled, supported captures use Web Unlocker for the initial document immediately.
Current runtime coverage:
| Surface | Coverage |
|---|---|
| REST screenshot/PDF jobs | Fallback or always mode applies to /v1/screenshot, /v1/pdf, and dashboard captures that use the screenshot queue |
| MCP screenshot tools | take_screenshot, screenshot_mobile, screenshot_tablet, screenshot_responsive, screenshot_fullpage, screenshot_dark, screenshot_element, and screenshot_pdf use the queued screenshot fallback |
| CLI screenshot commands | Remote CLI screenshot commands use the same MCP tools, so the user's saved fallback mode applies |
| MCP browser sessions | browser_navigate can use Web Unlocker for the initial page load and reports when it did so |
Web Unlocker fallback is best for public page capture and evidence collection. Follow-up clicks, form fills, and post-login pages still rely on the live browser session after the initial page load.
Bright Data request shape
The connection test uses Bright Data's Web Unlocker API:
curl -X POST "https://api.brightdata.com/request" \
-H "Authorization: Bearer <BRIGHT_DATA_API_KEY>" \
-H "Content-Type: application/json" \
-d '{"zone":"<WEB_UNLOCKER_ZONE>","url":"https://example.com/","format":"raw"}'Raw keys are never returned from the dashboard after saving. Replace the key from Settings if it needs to change.