Reduce bot detection on a Browserbase session using Verified mode, OS fingerprint selection and advanced stealth

Documented steps

1. Authenticate with X-BB-API-Key on POST https://api.browserbase.com/v1/sessions; all anti-detection controls live under browserSettings. References: https://docs.browserbase.com/reference/api/create-a-session and https://docs.browserbase.com/platform/identity/verified-customization
2. Set browserSettings.verified: true to enable Verified Browser Mode - a purpose-built Chromium with real browser fingerprints that Browserbase's bot-protection partners recognize, which reduces CAPTCHA challenges.
3. Confirm plan eligibility first: Verified is offered on the Scale plan. On lower plans build the proof of concept with standard browsers plus proxies.
4. Optionally set browserSettings.os to one of windows, mac, linux, mobile or tablet to control the OS signal, e.g. { verified: true, os: "mac" }.
5. Account for the fixed viewports under Verified mode: desktop (linux, windows, mac) is 1280x720, mobile is 384x696, tablet is 800x1200. Viewport customization is unavailable for Verified sessions regardless of OS.
6. For non-Verified sessions set browserSettings.viewport.width and .height directly to control window size.
7. Set browserSettings.advancedStealth: true for Advanced Browser Stealth Mode, a boolean in the session-creation schema.
8. Combine with proxies (proxies: true or a geolocation-targeted array) - Browserbase's own guidance for protected sites is to enable Verified and rotate IPs and geolocations with proxies together.
9. Verify empirically: run the session against the target, then pull GET /v1/sessions/{id}/logs and check whether browser-solving-started events appear, indicating the site still challenged you.