Google Trends

A Google Trends MCP + API your AI agent can actually rely on. Interest over time and rising queries.

The unofficial Trends scrapers break constantly and the official API is still alpha-gated. /v1/trends gives you a stable endpoint for interest-over-time, related and rising queries, and a rising/falling/stable label, clean JSON, billed per call from the same balance as your AI-search and keyword endpoints.

  • $1 free on signup
  • Credits never expire
  • No subscription
  • MCP native
Get $1 free, try itInstall MCP
WHAT YOU CAN ASK

Ask in plain language. Get structured JSON.

Each is one call against the endpoint, ask in plain English through the MCP, or hit the API directly. Same key, same credit balance.

You ask“Is interest in my topic rising or fading?”
You get{ "trend": "rising", "change_yoy": 4.7, "interest": 87 }
You ask“What rising queries should I write about?”
You get{ "rising_queries": ["geo vs seo", "geo agency"] }
You ask“Where is demand for this hottest?”
You get{ "by_region": { "US": 100, "GB": 71 } }
Why a trends endpoint

Interest-over-time data your agent can pull, not a chart you read.

Google Trends is built to be looked at, not consumed by code. The official API is still alpha-gated with thin quotas, and the unofficial scrapers (pytrends and friends) break the week Google reshuffles the page. /v1/trends wraps a stable Trends data source behind one POST: pass a term, a timeframe, and an optional region, get back interest-over-time, related and rising queries, and a rising/stable/falling label as flat JSON.

The value here is not a lower price, it is access. Your agent or your cron job can ask "is demand for this topic rising?" in real time, over MCP or plain HTTP, and act on the answer, no SEO-suite seat, no dashboard, no scraper to babysit.

  • Rising queries surface breakout topics before they peak.
  • A rising/stable/falling label with YoY change, no chart-reading required.
  • Region breakdown where the source has it, to see where demand is hottest.
PRICED FOR REAL WORK

Real scenarios. Real numbers.

Real workflows, real call counts, real totals, see what this looks like before you commit. Credits never expire.

  • trend watcher

    Scan a topic watchlist daily

    Pull the 12-month trend and rising queries for 30 terms you track, every morning, to catch breakouts before they peak. 30 calls/day · $1.50/day.

  • newsroom editor

    Pitch stories off what’s breaking

    Check 200 candidate terms across a news cycle to surface the handful that are spiking and worth a story today. 200 calls · $10.00 total.

  • demand-monitoring agent

    Watch category demand on a schedule

    An MCP agent re-pulls 50 category terms hourly over a launch week and pings you the moment one starts rising. 8,400 calls · $420.00 for the week.

vs. a Trends scraper or SEO suite

A stable endpoint, or a scraper you patch every time Google moves.

Reading Trends yourself means a flaky pytrends fork that rate-limits and IP-blocks, or a six-figure SEO-suite contract you can't call from code. /v1/trends absorbs the maintenance and hands your agent the data directly.

Cite42Scraper / SEO suite
IntegrationOne POST or one MCP tool call, flat JSON backMaintain a pytrends fork, or log into a dashboard by hand
ReliabilityStable wrapped source, no alpha-gate, no page-breakBreaks when Google reshuffles the page; rate-limited and IP-blocked
Agent accessMCP-native, an agent pulls trend data mid-taskBuilt for humans to read; no clean API for code
ResponseInterest-over-time, rising queries, trend label, region splitRaw widgets you parse, or charts you eyeball
Billing$0.05 per call from one prepaid balance, no seatFree-but-fragile, or a monthly SEO-suite subscription
Cost, 30-term daily scan$1.50/day, same key as keywords and AI searchEngineering time on a scraper, or a fixed monthly fee
PRICING

Pay per call. $25 minimum deposit. Credits never expire.

This page's endpoints below. See /pricing for the full per-endpoint table.

EndpointPriceWhat you get
POST/v1/trends$0.05Interest over time, related + rising queries, trend label for a term

See all endpoints and the model coverage table →

KEEP EXPLORING

Related endpoints

Same API key, same credit balance, different question.

SEO KeywordsSEO KeywordsSearch volume, CPC, competition, and ideas.Explore seo keywordsAI search visibilityAI brand rankingsMention rate, position, and share of voice.Explore ai brand rankingsAI searchAI searchOne prompt in, every model's answer out.Explore ai search
QUESTIONS

Questions about google trends.

No, the official Google Trends API is still alpha-gated with low quotas. Cite42 wraps a stable third-party Trends data source so you get a dependable endpoint today. When the official API reaches general availability, we plan to route to it transparently behind the same /v1/trends contract.
You can, but the unofficial libraries break whenever Google changes the page, and self-scraping gets rate-limited and IP-blocked fast. /v1/trends absorbs that maintenance so your product doesn't inherit it. You pay a small per-call fee instead of owning a fragile scraper.
Interest-over-time series, a rising/stable/falling label with year-over-year change, related queries, and rising queries. Regional interest breakdown is included where the source provides it.
Trends tells you what demand is moving; /v1/rankings tells you whether AI models mention you for those terms; /v1/citations tells you which of your URLs they cite. Together they turn "what's trending" into "what should I publish and where am I missing." All on one key and balance.
Yes, it's live today alongside /v1/keywords, the first classic-data endpoints. The AI-search endpoints (/v1/rankings, /v1/compare, /v1/search, /v1/citations, /v1/sentiment) are live too, all on one key and balance.
READY WHEN YOU ARE

Add reliable Trends data to your stack.

$1 free on signup. One API for AI search, keywords, and trends.

Get $1 free, try itInstall MCP
Google Trends MCP + API - Interest Over Time & Rising Queries for AI Agents | Cite42 | Cite42