# Premium Browser Engine

Source: https://docs.scrappey.com/docs/premium-browser-engine

> 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](/docs/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.  |
| `fingerprint`      | string  | No       | Deterministic identity seed — the same seed yields the same device fingerprint, so reuse one to keep an identity stable across requests. |
| `fingerprintNoise` | boolean | No       | Canvas/WebGL/audio fingerprint noise. On by default; set `false` to disable (honored by `hq`; `cc` handles noise internally). |
| `browser`          | array   | No       | Browser brand for the identity, e.g. `["Chrome"]` or `["Edge"]`.                                                    |

## Example

```bash
curl -X POST "https://publisher.scrappey.com/api/v1?key=YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "cmd": "request.get",
    "url": "https://example.com",
    "hq": true,
    "proxyCountry": "UnitedStates",
    "fingerprint": "stable-seed-123"
  }'
```

Alternative engine — the same request with `cc` instead of `hq`:

```bash
curl -X POST "https://publisher.scrappey.com/api/v1?key=YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "cmd": "request.get",
    "url": "https://example.com",
    "cc": true,
    "proxyCountry": "UnitedStates"
  }'
```

## 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](/docs/premium-proxy) or `proxyCountry`, the timezone and WebRTC egress are matched to the proxy exit IP automatically.
- **Full [browser actions](/docs/browser-actions)** — clicking, typing, scrolling, waiting, dropdowns, conditionals, captcha solving, and the rest run inside these engines.
- **Session capture** — [video](/docs/record-video) and [screenshots](/docs/screenshot) are returned as hosted URLs.
- **Cookie and localStorage injection** — warm a session by passing `cookies` and `localStorage`.
- **Consistent identity** — pin a `fingerprint` seed so the same device identity is reused across requests, and pass `cookies` to carry a warmed session.
- **Windows device identity** — both engines present a coherent Windows identity (macOS is not available).
- **[XHR interception](/docs/intercept-xhr) and [referer](/docs/add-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. Pin a `fingerprint` seed across requests so the identity stays consistent (the same seed yields the same device identity; an identity that changes on every request is itself a signal), pass `cookies` to reuse a warmed session, 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.