Skip to main content

Fingerprint-aware cloud Chromium for protected scrapes

Stealth Browser API

Run stealth browser sessions on BrowserSolver when stock headless gets blocked. Keep TLS, canvas, and navigator signals coherent, then escalate to WebUnlocker on allowlisted domains when vendor challenges still win.

  • Coherent fingerprints across canvas, WebGL, and TLS
  • Same stack as Rendering and WebUnlocker modes
  • No local Chrome fleet or driver maintenance
  • AntiBot guidance when you do not know the vendor yet

Stealth

sessions

TLS

coherent

Unlock

ready

0

local Chrome

Stealth path for hardened targets

  1. Step 1

    Session

    Open a stealth-aware browser session on BrowserSolver.

  2. Step 2

    Render or interact

    Pull DOM HTML after JavaScript settles.

  3. Step 3

    Unlock if needed

    Hand allowlisted hosts to WebUnlocker after AntiBot.

Stealth without a private browser farm

BrowserSolver runs patched Chromium sessions with routing included. Use Rendering for JS pages and WebUnlocker when allowlisted domains need hybrid unlock.

  • Canvas, WebGL, and navigator signals kept coherent per session
  • Escalate from AntiBot probes when you do not know the vendor yet
  • Screenshots and DOM export on the same credential
  • Same API key and credit balance across BrowserSolver scrape modes

Built for scrapers that hit bot walls

Retail, travel, and marketplace jobs often need more than a raw GET. Stealth sessions give you a browser path without owning the ops.

  • Pair with Website AntiBot to name the vendor before unlock
  • Reuse one API key across crawl, render, and unlock
  • Failed unlock retries follow product billing rules
  • Same API key and credit balance across BrowserSolver scrape modes

When stock headless gets blocked

Stealth sessions for pages that fingerprint automation surfaces.

Fingerprints

Coherent browser signals per session.

Canvas

Noise profiles that match real devices.

WebGL

GPU fingerprints aligned with the UA.

TLS

JA3/JA4 expectations stay consistent.

Sessions

Cookies and state across hops.

Unlock path

Hand off to WebUnlocker when needed.

Fingerprints

Coherent browser surfaces per session

TLS

JA3/JA4 expectations stay aligned

Cloud

No laptop Chrome or grid duty

Unlock path

Clean handoff to WebUnlocker

Frequently asked questions

Credits, scrape types, and billing before your first production job.

How is Stealth Browser different from Website Rendering?

Rendering focuses on returning JS-ready HTML for parsers. Stealth Browser is the hardened Chromium session when sites fingerprint automation before you even extract.

Can I drive it with Puppeteer?

Yes. Connect Puppeteer or Playwright to cloud Chromium, or call REST scrape modes when you only need HTML or screenshots.

Does stealth replace WebUnlocker?

No. Stealth helps sessions look real. Allowlisted vendor unlock is still WebUnlocker when challenges persist.

Does stealth help with CAPTCHA?

It reduces obvious automation signals. Persistent vendor challenges still need AntiBot detection and WebUnlocker on allowlisted domains.

Pick your next move

Wire up an integration, review plans, or read the API reference before your first job.

Integrations

Works with n8n, Zapier, and Make

Trigger BrowserSolver from n8n, Zapier, Make, or any stack that speaks HTTP.

  • n8n logo
  • Zapier logo
  • Make logo

Subscriptions

Credit-based plans

Usage billed on successful calls; client and platform errors usually do not bill. Every new account starts with 500 signup credits.

Documentation

Shared balance across six modes

Crawler, rendering, screenshot, unlock, detection, and technographics share one credit balance.

Scrape your first blocked URL

Fetch, render, screenshot, or unlock from one dashboard. Proxies, browsers, and anti-bot lanes stay on our side.

  • 500 signup credits
  • No card to start
  • All scraping modes