Stealth browser for AI agents — fingerprint-clean Chromium on demand
TL;DRAI agents that need to interact with anti-bot-protected sites (Cloudflare, DataDome, Akamai) cannot use vanilla Chromium — its default fingerprint is detected on day one. Stealth browsers ship with randomised canvas, WebGL, font, and audio fingerprints, plus realistic timing and TLS JA3. Agent402 Stock sells stealth sessions at $0.40 per session, returned as a CDP URL the agent connects to with Playwright or Puppeteer, settled in USDC on Base via x402.
What 'stealth' actually means
Headless Chromium emits dozens of telltale signals — navigator.webdriver, default font set, missing Chrome runtime, generic WebGL renderer string. Anti-bot vendors fingerprint all of them and flag the visitor before any human-like behaviour kicks in.
A stealth browser patches the runtime to lie about each of these signals. It also randomises canvas, WebGL, AudioContext, timezone, and screen size on each session so the same browser does not look identical across visits. The session feels like a real Chrome on a real desktop.
Why agents pay for it instead of running their own
Building stealth Chromium in-house is expensive. The patches drift with each Chrome release, anti-bot vendors update their detectors weekly, and a single missed signal voids the whole effort. Browserbase, Anchor, and Hyperbrowser exist as managed services for this reason.
Agent402 Stock proxies the request to one of those managed services and returns a CDP URL. The agent does not need to know which provider is upstream — only that the fingerprint passes the target's detector.
How to connect
After paying $0.40 the response includes a wsEndpoint string. Connect to it with any CDP-compatible automation library:
from playwright.sync_api import sync_playwright
with sync_playwright() as pw:
browser = pw.chromium.connect_over_cdp(ws_endpoint)
page = browser.new_page()
page.goto("https://target.example/")
# automation continues normallySessions are capped at one hour. The session is destroyed at the end of the cap, which is by design — long-lived stealth sessions accumulate cookies and become fingerprintable.
Pair with a residential proxy for full coverage
Stealth browser without a residential exit IP still fails on most modern WAFs — a clean fingerprint coming from AWS is still suspicious. Use the X-Proxy header to route the session through a residential proxy session you already paid for, or buy the Identity Bundle which couples them at $1.20.
Frequently asked
Do you support Firefox or only Chromium?
Chromium only. Firefox stealth profiles do not pass current anti-bot checks reliably, so we do not advertise them. If your target requires Firefox specifically, file feedback at /api/v1/feedback and we will evaluate adding it.
What anti-bot systems does the stealth browser pass?
Cloudflare, DataDome, PerimeterX, Akamai Bot Manager, hCaptcha (interactive), Turnstile. We do not guarantee 100% — anti-bot systems are adversarial and evolve. A failed session is refunded.
Can I run multiple pages in one session?
Yes. The CDP URL gives you a full browser context. Each tab is a separate page object but shares cookies and storage with the rest of the session.