Google does not offer a public Trends API. If you want search-interest data in code or in an assistant, you use an unofficial client, a paid SERP API, or a hosted service. TrendFlow is the last of those: REST, Python, JavaScript, and MCP.
| pytrends | SerpApi / DataForSEO | TrendFlow | |
|---|---|---|---|
| You run it | Yes — your process, your proxies | No | No, unless you self-host the libraries |
| Hosted HTTP API | No | Yes, paid per call | Yes — /api/v1 |
| MCP for ChatGPT / Claude | No | No | Yes — trendflow.mory.dev/mcp |
| Python / JS library | Python only | Official clients | trendflow-py and trendflow, MIT |
Point the client at https://trendflow.mory.dev/mcp. See MCP server or Google Trends in Perplexity. Trending searches and topic lookup need no account.
Python (pip install trendflow-py) or JavaScript (npm install trendflow), or the REST API from any language.
No. Google does not publish a public Trends API. Independent tools query Trends and re-expose the same kind of data: relative interest over time, by region, related queries, trending searches, and topic lookup.
pytrends is an unofficial scraper you install and keep working when Google changes. TrendFlow is a hosted alternative: a REST API, Python (trendflow-py), JavaScript (trendflow), and an MCP server at https://trendflow.mory.dev/mcp for ChatGPT, Claude, Perplexity, and Cursor. The libraries are MIT licensed if you still want to self-host.
Those products sell Google Trends as one endpoint among many, billed per request. TrendFlow is only Trends, with a free tier for trending searches and topic lookup, and an MCP server so an assistant can call it without you writing the HTTP client.