# Google Trends API for your agent

Google Trends API for an agent: it sends a keyword, a country and a time range to a catalog endpoint and reads interest over time, interest by region and related queries back. Several providers sell the call, so the agent tries the cheapest first. You pay per call, and a failed call costs nothing.

## Live prices

Prices read on 2026-10-14 from the live looot catalog. They change when a provider changes its price.

Cheapest today: SearchAPI.io at $0.0040 per call.

| Provider (endpoint) | Price | Per 1,000 |
|---|---|---|
| SearchAPI.io (searchapi-io-google-trends) | $0.0040 per call | $4.00 |
| SerpApi (serpapi-google-trends) | $0.0250 per call | $25.00 |
| DataForSEO (dataforseo-keywords-data-google-trends-explore-live-ai) | $0.0900 per call | $90.00 |

## What this does

Search interest rises and falls with seasons, news and launches. Before you write a page or stock a product, you want to know whether people search for it more or less than last year. Your agent sends a phrase and reads the curve back as data, week by week, without opening the Trends website.

The numbers are not search counts. Google samples searches, divides each point by all searches in that place and period, and scales the result from 0 to 100. Compare terms inside one request, and use the keyword research API when you need a monthly volume.

The providers read Trends in different ways. SearchAPI.io and SerpApi take a query and a data type, and SerpApi lists interest by region, related topics and related queries as views. DataForSEO reads the Explore view for up to five keywords at once, across web search, News, Images, Shopping and YouTube.

You give: a keyword, a country and a time range. Example: electric bikes.

## What differs between providers

- SearchApi (searchapi-io-google-trends): takes a query and a data type such as TIMESERIES, with optional region, time, category and search property filters.
- SerpApi (serpapi-google-trends): returns interest over time, interest by region, related topics or related queries, for one or more comma-separated queries.
- DataForSEO (dataforseo-keywords-data-google-trends-explore-live-ai): reads the Explore view for up to five keywords across web search, News, Images, Shopping and YouTube, with dates back to 2004 for web search.

## Before you start

- Set the country and the time range. A curve for the whole world hides what happens in one market, and with no dates DataForSEO reads the last 12 months.
- Compare terms in one call. Each answer is scaled from 0 to 100 on its own, so two phrases fetched in two calls cannot be read side by side.
- Expect a flat line for rare phrases. Google filters out searches made by very few people, so a niche term can come back at 0.
- What is rising today is a separate call. SearchAPI.io has a trending now endpoint that lists the topics climbing in a country, without a phrase to start from.

## Prompt

Use looot to show Google Trends interest over time for electric bikes in the United States over the last 12 months, with the related queries, and tell me which months peaked. 1. Set up https://looot.ai/skill.md. 2. Search the catalog for each step and check its price before you call. 3. Run the cheapest endpoint that fits. 4. Show the results as a table and the total cost.

## Steps and providers

- Read the trend: searchapi-io, serpapi, dataforseo. 1 call per keyword.

## What comes back

- Interest over time
- Interest by region
- Related queries
- Related topics

## The request and what comes back

Each run is one POST to /v1/runs with an endpoint id and an input. These are illustrative calls with generic values. The run's result holds the provider's own fields.

- SearchApi: {"endpointId":"searchapi-io-google-trends","input":{"q":"electric bikes","data_type":"TIMESERIES","geo":"US"},"wait":30}
- SerpApi: {"endpointId":"serpapi-google-trends","input":{"q":"electric bikes,e-bike","data_type":"TIMESERIES","geo":"US","date":"today 12-m"},"wait":30}

## What it cannot do

It does not return search counts, only interest from 0 to 100 within each answer. It cannot show who searched, and it leaves out phrases that too few people search. Watching a term over time needs scheduled runs, not available yet.

## Does the Google Trends API give search volume?

No. It gives interest from 0 to 100, relative to the peak in the place and period you asked for. For the monthly search volume of a keyword, use the keyword research API page.

## How do I get Google Trends data in Python?

Send one POST to the looot runs endpoint with the endpoint id and the input, using the requests library. Each endpoint page on docs.looot.ai has a Python example. Your agent reads the curve from the run's result as JSON.

## Can I compare several keywords?

Yes. SerpApi takes comma-separated queries and DataForSEO takes up to five keywords in one request. Keep the terms in one request so they share one 0 to 100 scale.

## Can I see interest by country or region?

Yes. Send a region code such as US or DE to limit the curve to one place. SerpApi also returns interest by region as its own view.

## Is this a Google Trends scraper?

It does the same job without running one. The providers fetch the Trends data and return JSON, and you pay per call. There is no browser or proxy for you to run.

## Can I get the related queries for a keyword?

Yes. Ask SerpApi for the related queries or related topics view, or DataForSEO for one keyword at a time. Your agent can then check the volume of each related query on the keyword research API page.

## How much does one keyword cost?

You pay per call, and the price depends on the provider your agent picks. This page reads the cheapest live price from the catalog and shows no number when the catalog is unreachable.

## Do I pay when a google Trends call fails?

No. A call that fails at the provider costs nothing, and your agent can retry it or send it to another provider.

## Do I need an account with each google Trends provider?

No. One looot key reaches every provider in the catalog. You top up once, and each call is billed at the price shown before it runs.

## How do I call google Trends from code?

Send a POST to /v1/runs with the endpoint id, the input and a new idempotency key, and your looot token in the Authorization header. With wait set to 30, the answer comes back in the response when the run ends within 30 seconds. Otherwise poll GET /v1/runs/<runId>.

## Can I run google Trends on a schedule?

That needs scheduled runs, not available yet. Run it by hand whenever you want fresh results.

## Do I pay while my agent is idle?

No. looot bills per call, and nothing runs while your agent is idle.

## Related pages

- /use-cases/keyword-volume-api
- /use-cases/google-serp-api
- /use-cases/rank-tracking-api

## Last reviewed

2026-10-04. The cost per 1,000 keyword runs is read live from the catalog on the web page.

## Agent skill for this page

https://looot.ai/use-cases/google-trends-api/skill.md sets an agent up for exactly the jobs on this page, with the live price of each, and offers the page's starter task once the user has picked a job and seen the price. The line to give an agent is under "Give this to your agent" below.

## For agents

### Give this to your agent

```text
set up looot for Google Trends API - https://looot.ai/use-cases/google-trends-api/skill.md
```
