Trends API: Google, TikTok, Amazon & 30+ Sources as JSON

Q: What counts as one request?

One POST to the endpoint, regardless of mode or source. A get_growth call for one keyword costs the same as a get_top_trends feed pull: one request.

Q: Do failed requests count against my quota?

No. Only successful 200 responses count. Client errors, server errors and rate-limit responses are always free.

Q: What happens when I run out?

Calls return 429 until your quota resets or you upgrade. Upgrades apply instantly, so you're never blocked for more than a minute.

Coverage

Every source they check separately.
One call here.

Fifteen keyword sources and twenty-one live trending feeds behind a single endpoint. Pass a source or a feed type, the JSON shape never changes.

Keyword sources 15

google search

Google search volume

google images

Google image search volume

google news

Google News search volume

google shopping

Google Shopping search volume

youtube

YouTube search volume

tiktok

TikTok hashtag volume

reddit

Subreddit subscribers

amazon

Amazon product search volume

wikipedia

Wikipedia page views

news volume

News article mention volume

news sentiment

News sentiment score (positive / negative)

app downloads

Android app downloads (AppBrain)

app rankings

Android app store ranking charts (AppBrain)

npm

npm package weekly downloads

steam

Steam concurrent players (monthly)

Live feeds, no keyword needed 21

Google Trends

Google News Top News

Messy platform metrics in.
One 0-100 score out.

Search volume, hashtag counts, concurrent players, package downloads. Different units, different scales, different APIs. We normalize all of it, so a TikTok hashtag and an npm package become directly comparable.

Googlesearch interest index

TikTokhashtag views

Amazonsearch volume est.

Steamconcurrent players

npmweekly downloads

NORMALIZE

74/100

trend score · "creatine gummies" · all sources

Same scale, every source

Each source is rescaled against its own history, then mapped to 0-100. Compare platforms without unit gymnastics.

Fresh, not fortnightly

Live feeds update continuously and keyword series are pulled on demand. The timestamp is in every response.

One response shape

Three modes, one endpoint, one schema. Parse it once and every source, feed and keyword just works.

Quickstart

Your first trend in 60 seconds.

One POST, three modes, your stack of choice. Full reference lives in the quickstart.

import json, requests

res = requests.post(
    "https://api.trendsapi.ai/api",
    headers={ "Authorization": "Bearer YOUR_KEY" },
    json={
        "mode": ,
        "source": ,
        "keyword": "ai agents",
        "percent_growth": [],
        "type": ,
        "limit": 25,
    },
)
data = json.loads(res.json()["body"])  # body is a JSON string
print(data[-1])  # → {'date': '2026-08-01', 'value': 33}
for r in data["results"]:
    print(r["period"], r["growth"], r["direction"])  # → 12M 120.0 increase
print(data["data"][0])  # → [1, "what's hot right now"]

# 1. Grab a free key above, then:
curl -X POST https://api.trendsapi.ai/api \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "mode": ,
       "source": ,
       "keyword": "ai agents",
       "percent_growth": [],
       "type": ,
       "limit": 25 }'

# → { "statusCode": 200, "body": "[{\"date\":\"2026-08-01\",\"value\":33}, ...]" }
# → body: {"search_term":"ai agents","results":[{"period":"12M","growth":120.0,"direction":"increase"}]}
# → body: {"type":"Google Trends","data":[[1,"what's hot right now"], ...]}
# note: "body" is a JSON string, parse it once more to use the data

const res = await fetch("https://api.trendsapi.ai/api", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_KEY",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    mode: ,
    source: ,
    keyword: "ai agents",
    percent_growth: [],
    type: ,
    limit: 25,
  }),
});
const envelope = await res.json();
const data = JSON.parse(envelope.body);  // body is a JSON string
console.log(data[data.length - 1]);  // → { date: "2026-08-01", value: 33 }
console.log(data.results[0]);  // → { period: "12M", growth: 120.0, direction: "increase" }
console.log(data.data[0]);  // → [1, "what's hot right now"]

Agent-native

Built for the things
that read docs for you.

A growing share of first contact with an API is an AI agent reading it on a developer's behalf. Trends API is ready for them, and for you.

/llms.txt at the root

The whole API, modes, sources and examples, in one machine-readable file.

MCP server included

Claude, ChatGPT and Cursor can query trends natively through our MCP server. Same data, same key, natural language.

One-shot prompt

Paste this into your assistant and it writes your first integration for you.

Copy-paste agent prompt

I want to track trends with the Trends API. Read https://trendsapi.ai/llms.txt, then help me make my first request: compare the 12-month growth of "ai agents" on Google, TikTok and YouTube, and chart the result.

Open in Claude ↗ Open in ChatGPT ↗

Pricing

Start free. Scale when it works.

One price, everything included. Every plan gets all 15 keyword sources and all 21 live feeds. No per-source pricing, no seats, no sales call.

Free

$0/mo

Lookups100 / mo
Data24-hour delayed
History90 days

Starter

$29/mo

Lookups5,000 / mo
DataReal-time
History1 year

Start with Starter

Common questions.

One POST to the endpoint, regardless of mode or source. A get_growth call for one keyword costs the same as a get_top_trends feed pull: one request.

No. Only successful 200 responses count. Client errors, server errors and rate-limit responses are always free.

No, quotas reset on the first of each month. If you consistently run out, that's the signal to move up a tier, not to hoard requests.

Calls return 429 until your quota resets or you upgrade. Upgrades apply instantly, so you're never blocked for more than a minute.

Yes, self-serve from your account, no emails required. You keep access until the end of the paid period, then drop to the free tier automatically.

Yes. Trends API ships with an MCP server, so Claude, ChatGPT and Cursor can query the same data with natural language. Your API key works there too.

Live feeds refresh continuously throughout the day. Keyword time series are pulled on demand from the source at request time. Every response includes its own timestamp so you never have to guess.

GET/trends
Every platform.

Every source they check separately.
One call here.

Messy platform metrics in.
One 0-100 score out.

Same scale, every source

Fresh, not fortnightly

One response shape

Your first trend in 60 seconds.

Built for the things
that read docs for you.

Start free. Scale when it works.

Common questions.

Ready when you are.

Get your free API key

Every source they check separately.One call here.

Messy platform metrics in.One 0-100 score out.

Same scale, every source

Fresh, not fortnightly

One response shape

Your first trend in 60 seconds.

Built for the thingsthat read docs for you.

Start free. Scale when it works.

Common questions.

Ready when you are.

Every source they check separately.
One call here.

Messy platform metrics in.
One 0-100 score out.

Built for the things
that read docs for you.