Bright Data Browser API

Bright Data Browser API — CDP browsers on a 70M+ residential IP network with challenge handling built in. Formerly Scraping Browser, this is a CDP endpoint that happens to sit on one of the largest residential proxy networks in existence, with challenge solving and fingerprint rotation handled server-side. You connect Playwright or Puppeteer to a websocket URL and pay for the gigabytes that flow through it. The developer surface is thin compared with the agent hosts; the network is the product. Built by Bright Data. Founded 2014.

We track it in 1 comparison — Browser APIs — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 12 other tools, and what follows is where it visibly separates from them.

Where it wins.

• Residential proxy — included, tied for best across 3 of 13 tools.
• Funding stage — later-stage, 2nd of 13.

Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.

Where it gives ground.

• Pricing model — per-gb, 12th of 13. Browserbase records per-hour.
• Agent API — No. Hyperbrowser records Yes.
• Human handoff — No. Browserless records Yes.

None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.

Provenance. 20 of 26 tracked fields carry a value for Bright Data Browser API, and 6 of those cite a document you can open. Last verified 2026-07-01. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.

Its nearest neighbour in our data is Airtop. Bright Data Browser API is ahead on Funding stage (later-stage against seed) and CDP endpoint (Yes against Partial). Airtop takes Agent API (Yes against No) and Human handoff (Yes against No). That pattern repeats across the rest of the roster — see Bright Data Browser API alternatives for the other rivals, each compared the same way.

Company

Bright Data

Founded

2014

Fields we track

20 of 26

Last verified

2026-07-01

When the target genuinely fights back, this is the one that keeps working, because IP quality beats fingerprint patching and Bright Data owns the IPs. The developer experience is comparatively bare and the per-GB bill punishes image-heavy pages, so block resources aggressively and do not use it as a general agent host.

Residential proxy

included1st of 13

Inferredverified 2026-07-01

Pricing model

per-gb12th of 13

Inferredverified 2026-07-01

Stealth mode

●Yes1st of 13

Vendor-claimedverified 2026-07-01source

CDP endpoint

●Yes1st of 13

Vendor-claimedverified 2026-07-01source

CAPTCHA solving

●Yes1st of 13

Vendor-claimedverified 2026-07-01source

Playwright

●Yes1st of 13

Vendor-claimedverified 2026-07-01source

Live view

●Yes1st of 13

Inferred

Agent API

○No8th of 13

Inferred

Bright Data Browser API is the right call in these situations, each one drawn from a field we actually record:

• Hard commercial targets behind enterprise bot management.
• Country-specific access including Australian exits.
• Scraping teams that already buy proxy bandwidth.
• Residential proxy is your binding constraint. Bright Data Browser API records included, the best figure in the Browser APIs roster. We define that field as how residential egress is supplied.
• Funding stage is your binding constraint. Bright Data Browser API records later-stage, 2nd of 13 in the Browser APIs roster. We define that field as latest publicly known funding stage, as a survival proxy.

Reach for something else when any of the following is a requirement rather than a nice-to-have:

• Pricing model. Bright Data Browser API records per-gb, 12th of 13 in the Browser APIs roster. Browserbase records per-hour on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Agent API. Bright Data Browser API records No on the Browser APIs table. Hyperbrowser records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Human handoff. Bright Data Browser API records No on the Browser APIs table. Browserless records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.

We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.

What we don't know. 6 of the 26 fields we track for Bright Data Browser API are still blank: Anti-bot pass rate, Cold start, Max concurrency, Chrome extensions, Per browser-hour and GitHub stars. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.