Scraping API PricesBright Data SERP API vs Oxylabs SERP API
The current commitment and volume boundaries between Bright Data and Oxylabs SERP APIs.
Bright Data SERP API
Oxylabs SERP Scraper API
The difference
Both paths, one ruler
Bright Data SERP API
Successes you want
100,000 standard searches
Your stated workload. Every vendor on this site is priced against this same number.
- × 1
Attempts you are billed for
100,000 standard searches
Bright Data SERP API does not bill failed fetches, so failures cost nothing here.
- × 1
What the meter counts
100,000 requests
One attempt is one billed unit for this workload.
- =
Metered cash this month
$142.50 /mo
Pay as you go. Cheapest of every eligible purchase option, not the first plan that fits.
Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
Oxylabs SERP Scraper API
Successes you want
100,000 standard searches
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 1
Attempts you are billed for
100,000 standard searches
Oxylabs SERP Scraper API bills failed fetches. This workload assumes none fail, so nothing is added here.
- ≥
Cash per month
No floor published; total unknown
Advanced price is not published, so its total is unknown
Bars share one linear scale across the 2 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
Both ladders share one linear scale, topping out at 100,000 counted units, so a longer bar means more billed work rather than a different drawing.
These figures are for one stated workload: 100,000 standard search calls with one default-depth result set per call. This site has not computed a crossover volume for this pair, and does not claim one. Move the volume on either product page to see where the answer moves.
Decision boundary: for Google SERP requests, Bright Data’s recurring 5,000-request free tier plus pay-as-you-go billing produces the lower computed outlay through 37,666 successful requests because Oxylabs starts with a $49 monthly commitment. At 37,667 requests, Oxylabs’ first commitment becomes lower than Bright Data pay as you go, and Oxylabs remains lower across the current published Google-result tiers and top-up rates. (Bright Data SERP pricing, Oxylabs SERP API pricing, rechecked July 29, 2026)
That boundary is specific to Google and to Bright Data pay as you go. Oxylabs publishes different rates for Google, Amazon, other targets, and JavaScript, while Bright Data publishes a successful-request meter with parsing, unlocking, retries, and bandwidth included. A target mix or a move to Bright Data’s committed Scale plan requires a fresh calculation. (Bright Data SERP billing, Oxylabs billing explanation, retrieved July 26, 2026)
Billing models side by side
Bright Data offers pay as you go plus a committed Scale plan. Billing is per successful SERP request, and a successful request is counted once even when it retrieves one hundred or more results. JSON, Markdown, or raw HTML parsing, proxy management, unlocking, CAPTCHA handling, retries, location targeting, and device user agents are included in that meter. Failed or errored requests and internal retries are not billed. (Bright Data SERP pricing, Bright Data SERP billing, retrieved July 26, 2026)
Oxylabs uses monthly successful-result commitments with target-specific rates and plan-specific top-up rates. Its Google allowance grows across the public tiers, while Amazon, other targets, and JavaScript have separate rates. Target HTTP 2xx and 4xx responses count as successful, while system-side 5xx and 6xx errors do not. Published job-per-second limits rise on larger plans, and rendered-job limits are lower. (Oxylabs SERP API pricing, Oxylabs billing explanation, Oxylabs rate limits, retrieved July 26, 2026)
The billable event is not perfectly matched. Bright Data says only successful responses are billed but does not use the Oxylabs 2xx-and-4xx wording in the selected billing guide. Oxylabs explicitly counts target 4xx responses. Model missing, forbidden, and invalid target pages separately rather than assigning the same billable count to both. (Bright Data SERP billing, Oxylabs billing explanation, retrieved July 26, 2026)
What each provides that the other does not
Bright Data is the only one of this pair with a public pay-as-you-go route that avoids a monthly commitment. Its reviewed pricing also advertises unlimited concurrency and includes parsing, unlocking, CAPTCHA handling, retries, and location targeting in the one-request meter. (Bright Data SERP pricing, Bright Data SERP billing, retrieved July 26, 2026)
Oxylabs is the only one of this pair whose reviewed table separates Google, Amazon, other-target, JavaScript, and media rates. It also publishes target-specific top-up rates and explicit job-per-second limits, including lower rendered-job limits. (Oxylabs SERP API pricing, Oxylabs billing explanation, Oxylabs rate limits, retrieved July 26, 2026)
Who should pick which
Pick Bright Data below 37,667 monthly Google SERP requests when avoiding a commitment is the main constraint, or when its included parser and unlocking bundle matches the required output. Pick Oxylabs at or above 37,667 current Google results, or when target-specific Amazon, generic-site, JavaScript, or media billing is preferable. Recompute for rendered jobs and non-Google targets because the Google boundary does not transfer. (Bright Data SERP pricing, Oxylabs SERP API pricing, rechecked July 29, 2026)
The current Oxylabs public pages do not expose monthly prices for every intermediate and corporate tier, and they do not state a rollover rule. Bright Data’s Scale rollover rule is also not stated. Oxylabs may throttle a domain to one request per second when its preceding five-minute success ratio is below forty percent, which is an operational constraint from vendor documentation, not a comparative success-rate claim. (Oxylabs billing explanation, Oxylabs rate limits, Bright Data SERP pricing, retrieved July 26, 2026)