Google Trends
Trending searches and search-interest exploration from Google Trends, served as plain REST.
Endpoints
| Endpoint | Path params | Query params | What it returns | Price | Data up to |
|---|---|---|---|---|---|
GET /googletrends/trending |
— | geo |
Top-10 trending searches for a region, with related news. | $0.003 | 5 min |
GET /googletrends/trending-detailed |
— | geo, hours, category, active_only, sort |
Full trending list (~450 items/day) for a region. | $0.003 | 15 min |
GET /googletrends/explore |
— | q, geo, time, category |
Interest-over-time, interest-by-region, and related topics/queries for a search term. | $0.01 | 1 hr |
Prices are per call, paid in USDC with x402. "Data up to" is the cache window: a repeated call inside it returns the same data.
Calling it
# x402: no account or API key. The server answers 402 with payment instructions; an x402 client pays and repeats the request.
curl -i "https://<base-url>/googletrends/trending?geo=US"
Responses are JSON. Field names follow the upstream source, so a response can be larger than the table above suggests.
Notes
hours,sort, andcategory(ontrending-detailed) are closed enums;categoryonexploreis free text (Explore's category taxonomy is much larger and hierarchical).exploretakes noticeably longer than other endpoints (several seconds) — it assembles four separate widgets in sequence, matching how the Trends UI itself loads a query.
