Google Search API comparison
Bright Data Alternative
Google results for your app. Less setup around the search.
Move your Google Search workload from a SERP zone to a direct query API. Compare paid rates, keep the source fields your application uses, and give your agent access before its owner signs up.
01 · At a glance
Feature-by-feature comparison
Focus on the paid search bill, the configuration you maintain, and the first task your agent needs to finish.
| Feature | FlashData | Bright Data |
|---|---|---|
| Spend less on paid Google searches | ||
| Pay-as-you-go price / 1,000 | $1.00No monthly fee | $1.50No monthly fee |
| Starting monthly plan with a lower rate | $49.00 / monthMicro · $0.80 / 1,000 | $499.00 / monthScale · 380,000 included · $1.30 / 1,000 additional |
| Fewer setup dependencies | ||
| Google Search API configuration | API key + source + queryNo SERP zone to create | API key + zone + Google URLREST API; proxy setup is optional |
| Parsed JSON on the first request | YesDefault output for google_search | Add brd_json=1Parsed output selected in the target URL |
| Agent trial before owner email verification | YesUp to 50 Google searches · 72 hours | Email verification firstAgent registration issues a key after the emailed code |
| Search targeting and source evidence | ||
| Web, images, news, shopping, videos and places | YesSix Google sources | YesGoogle search types and Maps |
| Country, language and local targeting | gl, hl and locationTyped request parameters | gl, hl and uuleParameters in the Google URL |
| Date filters for current research | Yesparams.tbs · Google time filters | Yestbs · Google time filters |
| Retrieve the next result page | Page numberOne page per query; Batch for multiple pages | start offsetPagination replaces the deprecated Google num control |
| Titles, source URLs and snippets | title, link and snippetInside results[0].organic | title, link and descriptionInside organic |
| Rank used by the result parser | Organic positionposition | Global page rankglobal_rank; not the same metric |
| Device-specific search results | No published device selector | Desktop or mobilebrd_mobile and platform options |
| Scheduled workloads and agent tools | ||
| Realtime and persisted async searches | YesSave a job ID and retrieve the result | YesAsync zone and saved response ID |
| Multiple searches in one submission | 100 on pay as you goUp to 500 by plan · per-query settings | YesAsync multi array with per-search queries |
| Completion notifications | Yescallback_url on each async or Batch query | YesDefault or per-request webhook |
| Markdown for agent context | YesAPI response option | YesMarkdown output option |
| CLI without Node.js or Python | YesStandalone Linux, macOS and Windows executables | Node.js 20+Official CLI installs through npm |
| MCP and agent skills | YesHosted MCP and installable skills | YesMCP and agent integrations |
Bright Data offers both REST and proxy access. The setup comparison uses its REST API; a proxy is not required. Its signup free tier is separate from FlashData’s temporary agent trial.
Reduce the paid search bill
Start with FlashData pay as you go, then choose a monthly plan when your search volume justifies it. Compare the fee and included usage as well as the unit rate.
Compare your workload →Keep search configuration in the request
Send a source, query and parameters. You do not need to create a SERP zone or build a Google URL before making the first FlashData request.
Map the request →Run from a small worker or agent host
Install the FlashData executable on Linux, macOS or Windows. Its CLI does not need a Node.js or Python runtime and can reuse the same saved profile on later runs.
Set up the CLI →02 · Plans & usage
Compare the cost of paid Google searches.
Choose a plan on each side. The calculator separates the usage rate, monthly commitment and included requests, so a low unit price does not hide a large plan fee.
Count query pages, not individual organic result rows. Paid scenarios exclude free credits.
FlashData · Pay As You Go
$1.00per 1,000 Google Search requests
- Monthly fee
- $0.00
- Included requests / month
- 0
- Credit purchases
- From $10.00
- Modeled monthly cost
- $10.00
- Effective cost / 1,000 at this volume
- $1.00
No monthly commitment. Prepaid purchases may exceed this month’s consumed usage.
Bright Data · Pay as you go
$1.50per 1,000 Google requests
- Monthly fee
- $0.00
- Included requests / month
- 0
- Modeled monthly cost
- $15.00
- Effective cost / 1,000 at this volume
- $1.50
Usage at the pay-as-you-go rate. Free credits are not deducted in this paid scenario.
How the estimate works
USD, one Google result page per request. Select plans independently. FlashData uses the current catalog: plan fee plus usage beyond included credits. Pay-as-you-go credit purchases start at $10 and may leave funds for later. Bright Data Scale uses its included request allowance plus the listed additional-request rate. Its Free tier is capped; no paid price is inferred above the cap. Oxylabs uses the monthly subscription balance first, then shows the extra credit funding needed for this workload; service pauses until that funding is added, rather than automatically billing an overage. Included requests assume the full shared balance or pool goes to Google. Paid scenarios exclude free offers, taxes, promotions, other products and negotiated contracts. Effective cost divides the modeled cost by the entered volume; it is undefined at zero requests.
Bright Data Scale shown here includes 380,000 requests for $499/month; additional requests cost $1.30 per 1,000. Other Scale volumes and custom contracts are outside this comparison. The Free tier is a shared 5,000-credit monthly pool across eligible products, shown as Google requests when used entirely for SERP. Paid scenarios do not subtract free credits.
All FlashData Google Search plans
| Plan | Per 1,000 requests | Monthly fee | Included credits | Google Search requests |
|---|---|---|---|---|
| Pay As You Go | $1.00 | $0 · no monthly fee | None | Top up as needed |
| Micro | $0.80 | $49.00 | 1,000 ($50.00 of usage) | ≈ 62,500 |
| Starter | $0.65 | $199.00 | 4,000 ($200.00 of usage) | ≈ 307,692 |
| Pro | $0.60 | $499.00 | 10,000 ($500.00 of usage) | ≈ 833,333 |
| Scale | $0.50 | $999.00 | 20,000 ($1,000.00 of usage) | ≈ 2,000,000 |
| Business | $0.40 | $1,999.00 | 40,000 ($2,000.00 of usage) | ≈ 5,000,000 |
Trying before you pay
Eligible new FlashData accounts can try up to 2,000 Google searches after signup and email verification, using the whole signup trial balance for search.
Bright Data provides 5,000 free credits each month across eligible products, with no card required. Its agent registration uses the user’s email and emailed code before issuing credentials. FlashData’s temporary trial can run the first eligible task before owner signup; claiming comes afterward.
Agent trial and claiming →03 · Migrate one task
Replace the zone and target URL with a query.
Start with the REST request your app already makes. Keep the search expression and consumed citation fields; change the request builder and response reader together.
| Change | Bright Data | FlashData | What to do |
|---|---|---|---|
| Endpoint | POST /request on api.brightdata.com | POST /v1/queries/realtime on data.flashdata.dev | Change the client adapter, not only the base URL. |
| Access and setup | Bearer API key + SERP zone | X-API-Key + source: google_search | Keep the key in a secret store; remove the zone setting from this adapter. |
| Search input | Google URL with q, gl and hl | query + params.gl + params.hl | Send plain query text in JSON; avoid double URL encoding. |
| Pagination | Google URL start offset | params.page starting at 1 | For ten-result pages, start=20 becomes page=3 with num=10. Each page is another request. |
| Structured results | brd_json=1 in the target URL | JSON by default | A transport format setting is not a FlashData search parameter. |
| Source records | organic[].title, link, description | results[0].organic[].title, link, snippet | Translate the snippet field. Preserve your app’s title / URL / snippet contract. |
| Rank data | global_rank | position | Do not equate global SERP rank with organic position; keep rank semantics explicit. |
1 Prepare your FlashData key
Sign up or sign in, complete account setup, then create a key with google_search permission in API Keys. Check available credits. Keep the key in your environment or secret store. An agent can start with eligible trial access.
2 Save and run your first search
Python 3, standard library only. Save the complete code below as flashdata-search.py in a new task folder. It uses FLASHDATA_API_KEY or prompts privately for the key, saves flashdata-result.json in the current folder and prints the source records.
import getpass, json, os
from urllib.request import Request, urlopen
from urllib.error import HTTPError, URLError
key = os.environ.get("FLASHDATA_API_KEY")
if not key:
key = getpass.getpass("FlashData key: ")
payload = {"source": "google_search", "query": "openai",
"params": {"gl": "us", "hl": "en", "num": 10}}
request = Request("https://data.flashdata.dev/v1/queries/realtime",
data=json.dumps(payload).encode(),
headers={"X-API-Key": key, "Content-Type": "application/json"})
try:
with urlopen(request, timeout=120) as response:
body = json.load(response)
except HTTPError as error:
raise SystemExit(f"HTTP {error.code}: check input and access.") from None
except (URLError, TimeoutError):
raise SystemExit("No response; check state before retrying.") from None
with open("flashdata-result.json", "w", encoding="utf-8") as output:
json.dump(body, output, ensure_ascii=False, indent=2)
if body.get("status") != "done":
raise SystemExit("Search is not complete; check its status.")
items = (body.get("results") or [{}])[0].get("organic", [])
print(json.dumps([
{"position": item.get("position"), "title": item.get("title"),
"url": item.get("link"), "snippet": item.get("snippet")}
for item in items
], indent=2, ensure_ascii=False))In that folder, run: python3 flashdata-search.py. Each execution submits one search.
3 Check the result your app receives
The example searches for openai with gl=us and hl=en. It checks status=done before reading results[0].organic, then prints position, title, URL and snippet.
Results and their order come from the live search. An empty organic list can be a successful result. Keep the saved JSON to inspect usage and any other result blocks your app needs.
Google Search API schema →[
{
"position": 1,
"title": "OpenAI | Research & Deployment",
"url": "https://openai.com/",
"snippet": "..."
}
]Check these before moving production traffic
| Your requirement | Action |
|---|---|
| Proxy integration | Move only this search call to direct HTTPS. Keep the existing proxy configuration for other workloads. |
| Google-specific controls | Inventory brd_*, uule, device and AI Overview requirements. Map only controls supported by the FlashData source schema. |
| Raw HTML or other engines | Keep those on a separate adapter. A FlashData Google JSON response is not a replacement for browser rendering, Bing or a general web unlocker. |
| Location and ranking | Run the same query, country and language. Check the fields your app consumes; do not assume matching global-rank numbers. |
04 · Beyond the first call
Separate search jobs from your scraping infrastructure.
A Google Search adapter can move independently of browser sessions, proxies and extraction jobs. Keep each provider’s in-flight work on the system that created it.
Keep the application tool stable
Preserve your tool name and query schema. Convert the FlashData response into the title, URL and snippet records your downstream code already accepts.
Build the search adapter →Move new jobs, then drain old jobs
Bright Data response IDs do not become FlashData job IDs. Store provider + remote ID with every work item, and retrieve old results using the original provider.
Use async and Batch →Reuse a completed scheduled run
Persist the CLI profile and run state. Retry the same run ID to recover a completed result; create a new run ID for the next scheduled search.
Run recurring tasks →05 · Coding and personal agents
Try the task. Claim access when you want to keep it.
Eligible agents can start with 1 credit (up to 50 Google searches) for 72 hours. Reuse an existing credential first. Trial creation is limited and eligibility is checked.
- Reuse access or start one eligible trial.
Choose the CLI, MCP or skill that fits the host. Keep secrets outside chat.
- Return one useful result.
Save the response and report actual usage. Keep the same profile and state directory.
- Ask the owner to claim.
The owner signs in or signs up, verifies email, enters the claim code and approves permissions and shared-balance access.
- Continue with the saved owner credential.
Unused temporary credits do not transfer. Recurring work uses the owner’s balance; revoked access must stop the next request.
Read https://flashdata.dev/compare/brightdata/reference.md and https://flashdata.dev/auth.md.
Inspect my Bright Data Google Search integration and the fields its callers consume.
Migrate only supported Google tasks. Report requirements that have no FlashData mapping.
Reuse saved access; otherwise check eligibility before creating one temporary trial.
Keep secrets in the host credential store, never in chat or source control.
Run one US English search for "openai" and return title, URL and snippet.
Save the raw response and report usage. Do not purchase credits.
For recurring work, ask the owner to claim access and approve permissions and shared-balance use.
Keep the same CLI profile and state directory. Stop on revoked access or insufficient credits.Run with an already authenticated FlashData CLI
Use these commands after installing the CLI and completing authentication. Reuse this run ID only when recovering the same task; choose a new one for fresh results.
flashdata auth status --json --non-interactive &&
flashdata search "openai" --gl us --hl en --num 10 \
--dry-run --json --non-interactive &&
flashdata search "openai" --gl us --hl en --num 10 \
--run-id brightdata-migration-first --json --non-interactiveAgent authentication →CLI setup →Connect through MCP →Install the skill →
06 · Common questions
Before you switch
Is FlashData a replacement for Bright Data’s entire platform?
This comparison covers Google Search. Move supported search tasks; retain a separate provider for proxy networks, browser automation or other engines your application still uses.
Is FlashData always cheaper?
Compare paid usage at the same volume and plan commitment. Bright Data’s shared monthly free tier may cover a small workload. FlashData’s paid Google Search rates and optional plans are shown in the calculator with their fees.
Do I need to build and parse a Google URL?
No. FlashData accepts a query and typed parameters and returns structured JSON. Country, language, pagination and supported filters belong in params.
Can I use MCP, a CLI or an agent skill?
Yes. Both providers offer agent tools. FlashData adds a standalone executable and an eligible trial that can precede owner signup. After claiming, use the saved owner credential and shared account balance for recurring work.
Start with one query
Put FlashData behind your next Google search.
Run the example, keep the fields your app needs, then connect the workflow.