Premium Browser Engine
Route a request through a premium stealth browser engine with engine-level fingerprinting for the toughest authorized browser workflows.
Route a request through a premium stealth browser engine with a coherent, engine-level device identity, for sites with the strictest browser verification during authorized workflows.
Command
Set "hq": true to run the request on the premium stealth browser engine. An alternative engine is available with "cc": true — it applies its stealth and device fingerprint at the binary level. Use one of the two; both accept the same parameters as a normal browser request.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
hq |
boolean | No | Run the request on the premium stealth browser engine. |
cc |
boolean | No | Run the request on the alternative premium engine (engine-level fingerprinting). Use either hq or cc, not both. |
proxyCountry |
string | No | Residential exit country (e.g. "UnitedStates"). The engine auto-aligns timezone and WebRTC to the proxy exit IP. |
profileId |
string | No | Reuse the same device identity, cookies, and proxy across requests. |
fingerprint |
string | No | Deterministic identity seed — the same seed yields the same device fingerprint. |
fingerprintNoise |
boolean | No | Canvas/WebGL/audio fingerprint noise. On by default; set false to disable (honored by hq; cc handles noise internally). |
operatingSystem |
string | No | Spoofed OS for the device identity: "windows" or "macos". |
browser |
array | No | Browser brand for the identity, e.g. ["Chrome"]. |
Example
Alternative engine — the same request with cc instead of hq:
What It Offers
Both modes render through a full browser with a deeper, coherent device identity than a standard browser request, plus the complete feature set:
- Engine-level stealth fingerprint — the browser's identity (user agent, platform, screen, canvas/WebGL/audio) is coherent down to the binary, not patched on afterward.
- Proxy-aligned environment — with a residential proxy or
proxyCountry, the timezone and WebRTC egress are matched to the proxy exit IP automatically. - Full browser actions — clicking, typing, scrolling, waiting, dropdowns, conditionals, captcha solving, and the rest run inside these engines.
- Session capture — video and screenshots are returned as hosted URLs.
- Cookie and localStorage injection — warm a session by passing
cookiesandlocalStorage. - Consistent identity — pin a
fingerprintseed or aprofileIdso the same device identity (and cookies) is reused across requests. - XHR interception and referer — capture the page's own API responses and control the navigation referrer.
Notes
Recommended setup for the strictest sites. The biggest lever is a clean residential proxy that matches the content's region — it drives the timezone and WebRTC alignment. Reuse a profileId across requests so the identity stays consistent (a device identity that changes on every request is itself a signal), and let the engine supply the user agent rather than overriding it.
Choosing between the two. hq and cc are independent premium engines; if one struggles on a particular target, try the other. They accept the same parameters, so switching is a one-field change.
Use these modes for authorized workflows on sites with strict browser verification. Respect third-party terms, robots.txt where applicable, rate limits, and applicable law.