Bright Data API review

Which Bright Data API a GTM team actually calls

Bright Data's own advice is to use a pre-built scraper when one exists for the site, the Unlocker for arbitrary URLs, and the SERP API for search. The three draw on the same free pool and share the same plan shape.

The unit is the thing to check per product. The SERP and Unlocker APIs charge per successful request, and the Web Scraper API charges per record delivered, so one Scraper API call that returns 50 LinkedIn profiles is 50 units, not one. In asynchronous mode only sending the request counts; collecting the response is free.

Bright Data API pricing, plan by plan

Bright Data SERP API pricing, and the Unlocker and Web Scraper prices beside it, follow one shape: a free monthly allowance, pay as you go per 1,000, a $499 Scale plan and a quote above that. The tiers below are the SERP API's, read from its pricing page.

Scale is cheaper than pay as you go only when the allowance gets used: 380,000 requests at $1.50 would be $570, so the plan saves money above about 333,000 requests a month and costs more below it. Under that line, pay as you go with a spend limit is the cheaper Bright Data API cost.

Unlimited concurrency, with one cap since January 2026

Bright Data API rate limits are mostly absent, and that is a deliberate selling point: all three API products advertise unlimited concurrency. The exception is search. Since January 2026 Bright Data applies a fair use rate limit to its SERP services, and an unfunded account is held to 1,000 requests a minute.

So the Bright Data API rate limits that matter are the SERP cap on a new account and the spend limit you set yourself. Everything else will take as much traffic as you send, which is the strength and the risk in one sentence.

How to create a Bright Data API key

A Bright Data API key is created for you when the account is, and more can be added with different permissions under Account settings. Every call sends it as a Bearer token, and the SERP, Unlocker and Browser APIs also need a zone, which is how Bright Data separates one API's settings and usage from another's.

The zone is the part that catches people out. A valid key with no SERP zone cannot run a search, so create the zone first, and keep one zone per pipeline so the usage of each can be read on its own.

A first Bright Data API call

This is the request Bright Data's own SERP quickstart shows, and the Web Unlocker takes the same body with an Unlocker zone instead. The proxy form below it is the native-access equivalent for a client that already speaks HTTP proxies.

POST https://api.brightdata.com/request
# {"zone": "<serp zone>", "url": "<a Google search URL>", "format": "raw"}

# or as a proxy, with the zone's username and password:
# brd.superproxy.io:44445, and brd_json=1 on the Google URL for JSON

Where the Bright Data API documentation lives

Bright Data publishes two indexes for machines: brightdata.com/llms.txt for products and pricing, and docs.brightdata.com/llms.txt for setup and the API reference. Every docs page has a Markdown twin when you append .md, and so do the pricing pages.

Read the pricing as Markdown. The interactive pricing pages fill their numbers in with JavaScript, and a plain fetch of them returns the plan names with every price blank; the .md twins carry the figures.

The MCP page lists Bright Data's MCP access alongside the others in this directory.

Bright Data's own walkthrough of the API

Bright Data publishes this on its own channel, so it is Bright Data's account of Bright Data, not ours. It is here because a rate card cannot show you the thing moving, and a minute or two of the product is faster than any paragraph on this page at telling you whether the shape of it fits yours.

A one-minute product film for the Web Scraper API, with no description and no walkthrough. It shows what the product is for; it does not show a call, a price or a limit, and every figure on this page came from Bright Data's pricing files and docs instead.

Published 17 February 2025 on Bright Data, the channel Bright Data's own pages link to, and read on 23 October 2026. Nothing in it is a source for a price or a limit on this page: every figure in the tables above comes from a Bright Data page.

Strengths and limits

Bright Data is the broadest web data provider in this directory, and its API pricing is simpler than its product list suggests.

The pattern is a large platform with a small, consistent API price underneath. Read the .md pricing files rather than the marketing figures, set a spend limit, and the three APIs behave like one product with three endpoints.

Who should actually buy this

Buy Bright Data when the job is search results or structured records from a site somebody has already built a scraper for, at volume. The SERP API and the Web Scraper API are the two a GTM pipeline calls, and at $1.50 per 1,000 on success with unlimited concurrency they are easy to forecast.

Start on the free 5,000 credits, then pay as you go with a spend limit. Scale at $499 only pays for itself above about 333,000 requests a month, so most teams should not start there.

Look elsewhere if you want one API that turns any page into clean text for a model with nothing to configure, or a price per contact rather than per page. Bright Data hands you the web; deciding which rows matter is still your job.

Before you build against it

Five things to settle first, each one read off Bright Data's own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration.

If Bright Data is not the answer

Four providers in the Sourcing APIs listing that solve the same problem differently. Each one is a trade, and the trade is named.

The full set, organized by the reason people leave, is on the Bright Data alternatives page.

Bright Data against the obvious rival

Same rate cards, read side by side, with the arithmetic done on a worked volume rather than left to you: Apify vs Bright Data. Every pairing in the directory is on the compare hub.