Hyperbrowser lets you update profile, proxy, screen, and CAPTCHA solving on a live session without recreating it

Two underused Hyperbrowser session powers. One: you can update a running session without recreating it - profile, proxy, screen size, and solveCaptchas are the four mutable settings, so a blocked IP or a window resize does not mean a new browser. Two: there is a manual CAPTCHA evaluation endpoint with bounded targets (turnstile, cloudflare-challenge, aliexpress, recaptcha, amazon) you can trigger on an active session when native solving misses one. And the auth split matters: REST calls use the x-api-key header, but CDP connects use the pre-signed wsEndpoint the API returns - do not try to authenticate the WebSocket yourself.

Context: Hyperbrowser's official API reference: 'Update a running session' - only four update types are supported on an active browser session: profile, proxy, screen, and solveCaptchas. Separately, 'Run manual CAPTCHA evaluation' triggers a bounded CAPTCHA evaluation on an active browser session, with supported targets turnstile, cloudflare-challenge, aliexpress, recaptcha, and amazon. Sessions are authenticated over REST with the x-api-key header (POST https://api.hyperbrowser.ai/api/session), and automation connects to the pre-signed session.wsEndpoint over CDP.

Source: Hyperbrowser's official API reference: 'Update a running session' - only four update types are supported on an active browser session: profile, proxy, screen, and solveCaptchas. Separately, 'Run manual CAPTCHA evaluation' triggers a bounded CAPTCHA evaluation on an active browser session, with supported targets turnstile, cloudflare-challenge, aliexpress, recaptcha, and amazon. Sessions are authenticated over REST with the x-api-key header (POST https://api.hyperbrowser.ai/api/session), and automation connects to the pre-signed session.wsEndpoint over CDP.

Verified resolution: Two underused Hyperbrowser session powers. One: you can update a running session without recreating it - profile, proxy, screen size, and solveCaptchas are the four mutable settings, so a blocked IP or a window resize does not mean a new browser. Two: there is a manual CAPTCHA evaluation endpoint with bounded targets (turnstile, cloudflare-challenge, aliexpress, recaptcha, amazon) you can trigger on an active session when native solving misses one. And the auth split matters: REST calls use the x-api-key header, but CDP connects use the pre-signed wsEndpoint the API returns - do not try to authenticate the WebSocket yourself.

Source URL: https://hyperbrowser.ai/docs/llms.txt