Managed Chromium for JS scrapes, screenshots, and agent workflows
Headless Browser API
Run headless Chrome in BrowserSolver cloud instead of Docker fleets. Wait for selectors, capture HTML or pixels, keep sessions on the same balance as unlock modes, and skip WebDriver ops for most production scrapes.
- Rendered HTML after client-side JavaScript
- PNG, WebP, or PDF captures on the same stack
- Stealth-aware sessions for protected targets
- REST-first design with optional driver products
Chrome
managed
JS
render
PNG
PDF out
REST
API
Headless without the farm
- Step 1
Call the API
Send a URL with wait and viewport options.
- Step 2
Get DOM or pixels
Rendering for HTML, Screenshot for images/PDF.
- Step 3
Scale workers
Your queue fans out; we host the browsers.
Headless Chrome as an API
Spin sessions on demand for scrapers, QA captures, and agent tools. BrowserSolver owns cold starts, routing, and cleanup.
- Selector waits and load delays for SPA scrapes
- Device profiles for mobile screenshot jobs
- Escalate to WebUnlocker on allowlisted hardened domains
- Same API key and credit balance across BrowserSolver scrape modes
One stack for HTML and pixels
Keep render extracts and visual checks in sync instead of maintaining two browser pipelines. Built for production jobs that need predictable access before brittle parsing.
- Website Rendering for DOM, Website Screenshot for raster/PDF
- Cheatsheets for Playwright workflows when you script locally against cloud lanes
- Credit accounting shared with crawler and unlock
- Same API key and credit balance across BrowserSolver scrape modes
Headless without the farm
Browser jobs that used to need Kubernetes Chrome pools.
Stealth-ready
Sessions tuned for protected scrapes.
Interaction
Waits and delays for dynamic pages.
Scroll
Lazy-load before capture.
Flows
Multi-step navigation patterns.
Profiles
Coherent browser surfaces.
CDP hygiene
Avoid obvious automation flags.
Sessions
Reuse cookies across calls when needed.
Capture
HTML, PNG, WebP, or PDF.
Managed
No Chrome images in your deploy
Stealth-ready
Sessions tuned for protected scrapes
HTML + pixels
Render and Screenshot on one stack
Scale
Burst jobs without grid capacity planning
Frequently asked questions
Credits, scrape types, and billing before your first production job.
Which endpoint should I call?
Use Website Rendering for HTML after JS, Website Screenshot for images/PDF, and WebUnlocker when an allowlisted domain still blocks.
Is WebDriver required?
Not for REST scrape modes. If your stack already speaks Selenium, Puppeteer, or Playwright, connect those clients to our cloud Chromium instead.
How does Headless Browser fit with Crawler and Unlock?
Use Crawler for cheap static HTML, Headless/Rendering when the page needs JavaScript, and WebUnlocker on allowlisted domains when challenges persist. One key across every mode.
Can agents use the same browsers?
Yes. See AI Agent Browser and Claude Computer Use for agent-oriented entry points on the same stack.
Pick your next move
Wire up an integration, review plans, or read the API reference before your first job.
Integrations
Trigger BrowserSolver from n8n, Zapier, Make, or any stack that speaks HTTP.
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