Skip to content
EN
Get API key

Google Search API comparison

Oxylabs Alternative

Pay for the searches you need. Subscribe when it makes sense.

Build a Google Search feature or a recurring research task without starting a monthly subscription. Compare Google-specific pricing and migrate the request your app actually uses.

Read as Markdown

Comparing YouTube Data? See the YouTube comparison →

01 · At a glance

Feature-by-feature comparison

A better fit for intermittent search workloads, small applications and agents getting through their first task.

Feature-by-feature comparison: FlashData and Oxylabs
FeatureFlashDataOxylabs
Start small and avoid a recurring commitment
Paid search without a subscriptionYesPay-as-you-go creditsActive subscription requiredFor a paid shared balance
Starting paid commitment$10 credit purchase$1.00 / 1,000 · $0 monthly fee$15.00 / monthStarter · $1.00 / 1,000 non-JS Google
Starting plan with a lower Google rate$49.00 / monthMicro · $0.80 / 1,000$100.00 / monthBasic · $0.90 / 1,000 non-JS Google
Get an app or agent to its first result
Agent trial before owner signupYesUp to 50 Google searches · 72 hoursAccount API key firstPublished agent setup asks for a Web API key
Separate product instance to configureNoneUse a key with google_search permissionWeb API instanceCreate the instance and generate its key
Parsed JSON by defaultYesStructured Google Search resultsSelect output: [json]Dedicated Google scraper defaults to HTML
Search controls and result formats
Country and language targetinggl and hlCountry and interface language; location for local targetingdomain, locale and locationNational index, UI language and request origin are separate
Date filters for current researchYesparams.tbs · Google time filtersYestbs · forwarded to Google
Collect consecutive result pagesOne page per querypage + num; Batch multiple queriesstart_page + pagesEach fetched page is charged
Structured source records for citationsOrganic result arrayTitles, source URLs and snippetsParsed JSONSelect JSON output; read the job result
Device-specific search resultsNo published device selectorDesktop or mobiledevice parameter
Output for apps and agentsJSON, text or Markdown contentJSON, Markdown, HTML or screenshotScreenshot requires run_js
Custom extraction schema or promptPublished source schemaTransform the response in your applicationYesCustom JSON extraction can replace the built-in parser
Background work and recurring agents
Realtime and persisted async searchesYesSave a job ID and retrieve the resultYesSync or async delivery modes
Queries per batch submission100 on pay as you goUp to 500 by plan · per-query settingsUp to 5,000 inputsQuery array with shared settings
Completion callbacksYescallback_url on each async or Batch queryYescallback_url on an async job
MCP and agent skillsYesHosted MCP and installable skillsYesWeb API agent integrations
Owner claim and credential handoffYesClaim once; reuse the saved CLI profileConfigure a Web API instance key

The comparison uses Oxylabs’ current Web API subscription catalog and its Google-specific rates. The generic /Scrape starting price is not the Google Search price. Both services have structured output and background jobs.

Pay as you go for uneven workloads

FlashData lets you buy credits without a monthly commitment. That suits occasional research, a new app feature or a scheduled task that only runs a few times a week.

Calculate your search volume →

Get a search-specific price

Compare Google requests directly. Keep Oxylabs /Search, Google /Scrape and JavaScript-rendered Google pricing separate so the estimate matches your workload.

Choose the Google mode →

Let the first task precede signup

An eligible FlashData agent can obtain limited temporary access, return a useful result and then ask the owner to claim it for continued use.

See the agent flow →

02 · Plans & usage

Price the Google endpoint you are using.

For full Google SERPs, compare the dedicated Google scraper’s non-JS or JS rate. Select your plans below; included requests use the whole monthly balance for that Google mode.

FlashData returns structured results; it has no rendering-mode switch.

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.

Oxylabs · Starter

$1.00per 1,000 Google non-JS requests

Monthly fee
$15.00
Included requests / month
15,000
Extra credits needed
$0.00
Monthly funding needed
$15.00
Effective cost / 1,000 at this volume
$1.50

Subscription credits are shared across products. Add funds before the balance runs out; top-ups normally expire at the cycle’s end.

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.

Oxylabs Starter is $15/month, Basic $100/month and Flexible $500/month in the current Web API catalog. Non-JS Google rates are $1.00, $0.90 and $0.70 per 1,000; JS rates are $1.35, $1.30 and $1.15. These are not the generic /Scrape starting rates or the separate /Search endpoint. Enterprise pricing and legacy Web Scraper API contracts are outside this estimate. FlashData does not expose a run_js or screenshot option.

All FlashData Google Search plans
FlashData Google Search plans
PlanPer 1,000 requestsMonthly feeIncluded creditsGoogle Search requests
Pay As You Go$1.00$0 · no monthly feeNoneTop up as needed
Micro$0.80$49.001,000 ($50.00 of usage)≈ 62,500
Starter$0.65$199.004,000 ($200.00 of usage)≈ 307,692
Pro$0.60$499.0010,000 ($500.00 of usage)≈ 833,333
Scale$0.50$999.0020,000 ($1,000.00 of usage)≈ 2,000,000
Business$0.40$1,999.0040,000 ($2,000.00 of usage)≈ 5,000,000
Full FlashData pricing →
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.

Oxylabs offers a one-time $5 welcome balance shared across products. FlashData’s agent trial is a separate, limited way to try a task before the owner creates an account. Neither is an unlimited source of free requests.

Agent trial and claiming →

03 · Migrate one task

Map the API generation your app uses.

Current Oxylabs Web API uses a Bearer key and dedicated scraper paths. Older Web Scraper API clients use a different host and Basic authentication. Identify yours before changing the adapter.

Oxylabs to FlashData: request and response mapping
ChangeOxylabsFlashDataWhat to do
Current Google endpointPOST /v1/scrape/google/search on webapi.oxylabs.ioPOST /v1/queries/realtime on data.flashdata.devKeep the query and rebuild the JSON payload.
Current authenticationAuthorization: Bearer · Web API instance keyX-API-Key · google_search permissionUse a new FlashData credential; an Oxylabs key cannot authenticate here.
Legacy clientrealtime.oxylabs.io/v1/queries · Basic auth · source=google_searchSame FlashData endpoint and key as aboveDo not send legacy Basic credentials to either provider’s new endpoint.
Google marketdomain, locale, locationparams.gl, params.hl, supported params.locationUS English example: gl=us and hl=en. A Google TLD, request origin and UI language are separate settings, not interchangeable strings.
Result pagesstart_page + pagesparams.page + params.numFetch one page per query; use Batch for multiple queries. Count pages as requests, not organic result rows.
Outputoutput: [json] · structured content in results[].jsonJSON by default · results[0].organic[]Rewrite the reader for the fields your app uses; do not keep the old results[].json path.
Job completionCurrent Web API response / async job statusstatus: done plus resultsCheck completion before treating an empty organic list as a successful search.

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.

flashdata-search.py
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 →
Illustrative application output
[
  {
    "position": 1,
    "title": "OpenAI | Research & Deployment",
    "url": "https://openai.com/",
    "snippet": "..."
  }
]
Check these before moving production traffic
Migration decisions
Your requirementAction
/Search or /Scrape?Keep a lightweight web-search tool separate from a full Google SERP scraper. This page compares the latter; do not reuse /Search pricing for it.
Parser-specific fieldsInspect a saved response. Preserve only the organic fields and SERP sections your application requires; do not assume the same result nesting.
Rendering and special Google tasksKeep a separate path for screenshots, custom JSON extraction, Google Lens, Trends or AI Mode requirements that are outside the FlashData source contract.
Scheduled workStore provider, job ID and output location. Recover a submitted job before deciding to submit again after a timeout.

04 · Beyond the first call

Make a small search workload economical to keep running.

Separate the search budget from the schedule. Use stored credentials, explicit run IDs and saved results so a restart does not become another search submission.

Choose a plan after measuring usage

Start with pay as you go. Use actual query counts to compare a monthly plan’s included balance and fee, rather than selecting a plan for its headline unit rate alone.

View all search plans →

Translate jobs, not job IDs

Drain existing Oxylabs jobs on Oxylabs. Submit new FlashData work with your own work-item ID, save its returned job ID and export completed results to durable storage.

Build the async workflow →

Keep access across scheduled runs

Claim the agent connection once and persist its profile. Stop on revoked access or insufficient balance; schedule the next run only after the owner resolves access.

Reuse and revoke credentials →

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.

  1. Reuse access or start one eligible trial.

    Choose the CLI, MCP or skill that fits the host. Keep secrets outside chat.

  2. Return one useful result.

    Save the response and report actual usage. Keep the same profile and state directory.

  3. 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.

  4. 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.

Migration prompt · Oxylabs Google Search
Read https://flashdata.dev/compare/oxylabs/reference.md and https://flashdata.dev/auth.md.
Inspect my Oxylabs 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.

Verify access, validate, then search
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 oxylabs-migration-first --json --non-interactive

06 · Common questions

Before you switch

Why not compare with Oxylabs’ generic /Scrape price?

Google has its own rates. Its non-JS and JS modes are priced separately, and /Search is a different endpoint. The selector uses Google-specific rates so the unit comparison reflects a Google SERP workload.

Can I buy FlashData credits without subscribing?

Yes. Pay-as-you-go credit purchases start at $10 and do not require a monthly plan. Optional subscriptions include credits and lower usage rates. Oxylabs’ current paid shared balance requires an active subscription.

What if I still use the older Oxylabs API?

Identify the host and authentication in your existing code. The legacy realtime.oxylabs.io client differs from the current Web API. Migrate both to FlashData’s X-API-Key request and response schema; check your own legacy contract separately from current public pricing.

Can FlashData replace generic page scraping?

This migration is for supported Google Search tasks. Keep a separate page-reading or browser tool for full webpage extraction, screenshots and JavaScript interaction. Search results supply source links and snippets.

Start with one query

Put FlashData behind your next Google search.

Run the example, keep the fields your app needs, then connect the workflow.