Skip to main content

Stable cloud browsers for agents that click, read, and extract

AI Agent Browser API

Give coding agents and computer-use models a reliable Chromium session on BrowserSolver. Screenshots, DOM exports, and stealth routing without local browser babysitting in the agent sandbox.

  • Stable cloud Chromium for agent loops
  • Screenshot and DOM exports for model context
  • Stealth-aware sessions when sites fingerprint bots
  • Same API key as human dashboards and cron scrapers

Agent

ready

DOM

export

PNG

context

Cloud

Chrome

Browsers agents can depend on

  1. Step 1

    Provision

    Open a clean cloud session per agent turn or job.

  2. Step 2

    Ground

    Pull screenshots and DOM for the model tool loop.

  3. Step 3

    Extract

    Hand URLs to Rendering or WebUnlocker when scrapes take over.

Browsers agents can depend on

Local Chromium in agent sandboxes flakes. BrowserSolver gives each run a clean session with routing included. Built for production jobs that need predictable access before brittle parsing.

  • Pair with Claude Computer Use workflows for model-driven browsing
  • Use Screenshot for visual grounding and Rendering for HTML context
  • Escalate to unlock only on allowlisted domains
  • Same API key and credit balance across BrowserSolver scrape modes

Context that matches production scrapes

Agents and scrapers share the same browser stack, so debug traces look like production traffic. Built for production jobs that need predictable access before brittle parsing.

  • llms.txt and agent-instructions for tool discovery
  • Markdown library twins for endpoint reference in IDEs
  • One API key across human dashboards and agent runners
  • Same API key and credit balance across BrowserSolver scrape modes

Browsers for agents, not demos

Production sessions for computer-use and scraping agents.

Sessions

Fresh browser per agent turn.

Stable Chrome

No local WebDriver mess.

Stealth

Fewer false bot blocks.

Screenshots

Pixels for multimodal models.

DOM

HTML for tool-calling agents.

One key

Same creds as scrape jobs.

Stable

No flaky local Chromium in sandboxes

Multimodal

Pixels and HTML for tool calls

Stealth

Fewer false bot blocks mid-loop

Shared key

Same creds as production scrapes

Frequently asked questions

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

Is this a separate runtime from Website Rendering?

Same managed Chromium stack as Rendering and Screenshot, tuned for agent loops that need screenshots, DOM, and stable sessions between tool calls.

Which model providers are supported?

Any agent that can call HTTP APIs or a remote browser. For Claude computer-use specifically, see the Claude Computer Use product.

How do agents discover endpoints?

Start with /llms.txt and /agents.json, then pull Markdown API docs from the library for the modes you need.

Can agents unlock Cloudflare?

Yes, through WebUnlocker on allowlisted domains after AntiBot, same as human-operated jobs.

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