Skip to content

Web Scraping API Joins Oxylabs Group: What the Announcement Says

The co-founders of the web scraping API have announced that the company is now part of Oxylabs' group. This page summarizes what that announcement says, in its own terms, for people already running scrapers on the platform: what it states about plans, credit costs, support and performance, and which of those items are described as done versus still to come. All business statements below are attributed to the announcement; confirm current terms on the official pricing and status pages before budgeting against them.

What the announcement says stays the same

According to the announcement, current subscription plans are unchanged. The web scraping API is described as continuing to operate as a separate product and entity, with the co-founders staying with the company. The stated mission — a transparent, easy-to-use, high-performance scraping API — is not being retired as part of the move.

What the announcement says changes

Three items were announced alongside the acquisition:

  1. Google API credit cost drops. The announcement states that Google Search API and HTML API calls now cost 15 credits instead of 25. This is described as a per-call credit change, not a change to subscription pricing.
  2. Support team expanded. The announcement says the support team has more than doubled, with the aim of covering more time zones and shortening response times.
  3. Performance work begins in June. The first wave of scraping performance improvements is described as rolling out throughout June. The announcement presents these as forthcoming, not already live.

Checklist for existing subscribers

Use this list to decide whether anything on your side needs attention, based on what the announcement states:

  • Plan price: the announcement says no action is needed — subscription plans stay the same.
  • Google API budget: if you forecast credits per Google Search or HTML API call, the announced multiplier moves from 25 to 15.
  • Support expectations: the announcement says the expanded team is intended to cover more hours; it gives no measured response-time commitment.
  • Performance-sensitive jobs: the announcement schedules improvements for June, so plan to re-test after rollout rather than assuming they are already in place.
  • Product continuity: the announcement states the web scraping API keeps operating as a separate product and entity.

Worked example: Google API credit math

Suppose a job makes 1,000 Google Search API calls in a month. At the previously announced rate of 25 credits per call, that job consumed 25,000 credits. At the newly announced rate of 15 credits per call, the same 1,000 calls consume 15,000 credits. The difference is 10,000 credits per 1,000 calls — a 40% reduction in credit consumption for that workload. The announcement frames this as a credit-cost change only; subscription pricing is stated to be unchanged.

Two things that are easy to confuse

Plan price vs. credit cost. The announcement says subscription plans stay the same and that Google API calls cost fewer credits. Those are separate facts: the plan line does not move, but credit burn for Google calls does. Checking only the plan price would miss the credit change.

Announced as done vs. announced as scheduled. The support expansion is described as already completed ("more than double our support team"). The performance improvements are described as beginning to roll out in June. Treat the first as a stated current condition and the second as a scheduled change to verify after rollout.

The future of the web scraping API, as described

The announcement frames the move as continuity rather than absorption: the web scraping API is said to remain its own product and entity, with both co-founders staying on and the team expanding. The co-founders describe Oxylabs' group as the right home for the product and express confidence that the change will work out well for customers, staff and the company. For the corporate version of the news, the post points readers to the official press release.

What the announcement says changes and what it says stays the same
AreaBeforeAfterHow the announcement frames it
Subscription plan priceUnchangedUnchangedStated as staying the same
Google Search API credit cost25 credits per call15 credits per callStated as already in effect
HTML API credit cost25 credits per call15 credits per callStated as already in effect
Support team sizeBaselineMore than doubledDescribed as already done
Scraping performanceBaselineFirst wave rolling out in JuneDescribed as scheduled, not yet live
Product structureSeparate productSeparate product and entityStated as staying the same

Figures reflect the acquisition announcement as captured. Verify current credit rates and rollout status on the official pricing and status pages before relying on them for budgeting.

Frequently asked questions

Does the announcement say my web scraping API subscription price will go up?

No. The announcement states that current subscription plans stay the same. Separately, it says Google API calls now cost 15 credits instead of 25, which lowers credit consumption for those calls without changing the plan price.

Which APIs did the announcement say got the credit reduction?

Google Search API and HTML API calls. Both are stated to move from 25 credits per call to 15 credits per call.

Is support faster now, or is that planned?

The announcement describes the support team as already more than doubled, intended to cover more time zones and shorten response times. The scraper performance improvements are a separate item, described as beginning to roll out in June.

Will the web scraping API be merged into another Oxylabs product?

The announcement says the web scraping API will keep operating as a separate product and entity, and that the co-founders remain with the company.