Introduction

Open Architecture

Each job uses six parts, from the browser to file storage. Bring vendor accounts for the first five, or use Browser Fleet's accounts. Browser Fleet provides storage for both plans.

Parts

Each part has a role in a job. Bring a supported vendor for all of the first five parts, or for none of them to use Browser Fleet's vendors. Browser Fleet provides storage on both plans.

browsers

The browser each job drives through a CLI. Supported: BrowserAct. Coming soon: Kernel, Browser Use, Bright Data, and Scrapeless.

cloud_infrastructure

The cloud service that hosts each job's agent. Supported: Cursor, with one key for each Cursor account; launches spread over every key. Coming soon: Hetzner, Claude, and Codex.

llm

The LLM the agent that reads your steps and drives the browser runs on. Supported: any OpenAI-compatible API, with its base URL and the model you choose, and OpenCode Go with DeepSeek V4.1 Flash. Coming soon: Claude-compatible APIs.

stealth

The CAPTCHA solvers a job can use when a page blocks it. Supported: CapSolver, 2Captcha, and NopeCHA. Coming soon: Anti-Captcha and CapMonster.

network

The rotating residential proxies a job reaches sites through. Supported: Proxiware. Coming soon: Bright Data, Oxylabs, and Decodo.

storage

Browser Fleet stores job files on Cloudflare R2 for seven days after the job finishes.

BYOK and Cloud

Your plan depends on which vendor accounts you configure. Browser Fleet provides storage on both plans.

BYOK · $0.02

Configure your own vendor for every part except storage. You pay your vendors directly, and Browser Fleet charges $0.02 per job request.

Cloud · $0.10

Browser Fleet provides the vendor accounts and charges $0.10 per job request. Model token costs are billed separately.

Some parts

A configuration with some parts but not all runs no job: job creation answers 422 until you set every part, or remove them all.

How a Job Picks Vendors

A job reads your organization's vendor configuration when it starts. Changes apply to jobs that start after the update.

1. Read

When the job starts, Browser Fleet reads your organization's configuration.

2. Yours

For each part with your credentials, the job uses your vendor account.

3. Ours

With no part configured, the job uses Browser Fleet's vendors for every part and is billed as Cloud.

Request:
GET https://api.browserfleet.dev/rest/public/configuration

Response:
{
  "plan": "cloud",
  "configuration": {
    "browsers": { "vendor": "browseract", "key": "…4f2a" },
    "stealth": [{ "vendor": "capsolver", "key": "…9c1e" }]
  }
}