Bright Data documents Google Trends as a SERP API surface. The caller sends the public Explore URL through brd.superproxy.io (port and zone as in the current docs) with brd_json=1. brd_trends selects widgets (timeseries, geo_map, or both). geo, hl, date, cat, and gprop stay on the URL as Google wrote them. Trends API never opens a proxy zone. POST https://api.trendsapi.ai/api. body is a JSON string and must be parsed a second time. Docs: the API reference. Caps: pricing.
A proxy to trends.google.com
curl --proxy brd.superproxy.io:44445 --proxy-user brd-customer-ZONE:PASSWORD -k \
"https://trends.google.com/trends/explore?q=pizza&geo=us&brd_trends=timeseries,geo_map&brd_json=1"
That command is infrastructure. Zone credentials, -k, and a superproxy host are the integration. A Trends API integration is a JSON body and a Bearer header.
brd_json and brd_trends widgets
Bright Data's Google query parameter page lists date values that match Explore (now 1-H, today 12-m, custom ranges) and gprop values images, news, froogle, youtube. Those strings do not travel to percent_growth. A timeseries widget is not get_growth.
SERP infrastructure versus a trend product
Bright Data's SERP API also covers Search, Maps, Reviews, Hotels, Flights. Trends is one more URL family on that stack. Teams already paying for that stack add brd_trends with little new vendor work. Teams that only need a 0-100 series buy a different object: mode plus source.
Successful-request billing on their side
Official SERP notes say failed requests are not charged and retries collapse into the successful response. Confirm the current per-thousand rate on Bright Data's site. Trends API billing is this product's 200s. Read pricing. Do not assume the two unit prices are comparable without a side-by-side invoice.