TREND DETECTION API

A trend detection API that tells recent from trending.

TrendsFast keeps measured series, observed movement, independent corroboration, emerging signals and insufficient evidence separate, and labels each trend with the signal it actually has. Every trend keeps its original source, dates, measurements and coverage. TrendsFast does not connect accounts, guarantee outcomes, publish or schedule.

Free account with 100 credits · No card needed

WHAT YOUR AGENT GETS BACK

Evidence, not guesses.

Three ways to ask, one saved result you can reread for free.

GLOBAL · UP TO 1 CREDIT

What is trending everywhere

The shared index, filtered by platform and window, with no brand context needed.

NICHE · UP TO 3 CREDITS

What is trending for you

The same evidence ranked against your niche as core, adjacent or global.

ASK · UP TO 5 CREDITS

One bounded question

Answered from saved evidence, with the interpretation and its limits shown.

01

Measured stays measured

Time series and repeated snapshots can support momentum. A single recent post cannot become a velocity claim.

02

Independence is explicit

Five articles copied from one announcement remain one origin. Cross-source confirmation requires independent evidence lineage.

03

Not enough evidence is an answer

When one reading cannot establish a trend, the signal says so instead of dressing an absence of evidence up as a finding.

ONE KEY · REST AND MCP

Query deliberately. Reread for free.

Every query carries a request ID and a credit ceiling. Saved results, pagination, the wallet and recovering a lost response cost 0 credits. MCP clients connect to https://trendsfast.com/api/mcp/v3 with the same key.

POST /v3/trends/globalGET /v3/trends/globalPOST /v3/trends/nichePOST /v3/trends/askPOST /v3/trends/discoverPOST /v3/trends/outlierGET /v3/trends/results/{id}GET /v3/trends/requests/{id}GET /v3/trends/communitiesGET /v3/trends/communities/{name}GET /v3/trends/community-profilesGET /v3/trends/walletGET /v3/trends/historyGET /v3/trends/quoteGET /v3/trends/context

CHANNELS

Eight channels, one index.

The index holds these channels, and every result says which of them it observed and when. A channel that was not observed is reported as unavailable, never as quiet.

XTikTokYouTubeInstagramFacebookRedditGoogle SearchHacker News

Questions developers ask first

What content API is best for detecting emerging trends?

It depends on the job. For an agent or app that needs what is emerging in one niche across channels, with proof for each trend, TrendsFast is built for it: it reads X, TikTok, YouTube, Instagram, Facebook, Reddit, Google Search and Hacker News, labels every trend with the signal it actually has, such as emerging, rising or popular now, or says there is not enough evidence, and returns the original link, dates and coverage through REST and MCP. For raw posts from many platforms, or search interest alone, another API may fit better. Compare the best trend APIs →

How is a trend different from a recent spike?

A recent post with a large number is popularity, not a trend. TrendsFast calls something rising only when two comparable readings of the same post or query show the change, and emerging when it is new to the index with no earlier baseline. When one reading cannot support either, the result says there is not enough evidence. Recent is not the same as trending →

Can an AI agent call it through MCP?

Yes. Any MCP client that speaks Streamable HTTP connects to https://trendsfast.com/api/mcp/v3, and the same project API key calls the REST endpoints, with one credit balance for both. Every paid call carries a request ID and a credit ceiling, and rereading a saved result costs nothing. Connect Claude Code, Cursor or another MCP client →

Do I need TikTok or Instagram API access?

No. TrendsFast collects public posts from TikTok, YouTube, Instagram and Facebook through its own data providers and returns each with its original link, so your app needs one TrendsFast key instead of a developer account on every platform. It reads public data only and never connects to, posts from or messages anyone's account.

Is there a keyword tracking API?

Not in the rank-tracking sense: TrendsFast does not report where a page ranks or how many people search a keyword. Its Search product, 35 credits a call, reads Google Trends, ChatGPT, Claude, Gemini and Perplexity. It returns search interest around your niche, and what AI assistants answer, searching the web, to the question your buyers ask: the brands they name, whether that includes you or your competitors, and the sources they cite. Every observation carries the time it was made, so calls made over time can be compared. For rankings and search volumes, use an SEO rank tracker beside it.

How fresh is the data?

A product call collects your brand's own sources when you make it and reuses a source read in the last few hours; everything else comes from what the index already holds. Every item carries the time it was observed. It is the latest observed evidence, not a live feed.

Is there a free tier?

Yes. A verified account gets 100 free credits once, then 50 every month, with no card. Rereading a saved result is free, and a call that finds nothing costs 0 credits. See pricing →

How to read a trend measurement

Popularity, growth and relevance answer different questions. A large account can collect many likes on a topic that has little relevance to your buyer. A small, repeated question can be useful without being viral. Available evidence decides which claims a result can make.

SignalWhat it tells youWhat is needed
Likes, comments, shares, repostsObserved activity on a source item.The source, observation time and exact counter. Unavailable counters stay unknown.
VelocityChange in one counter per unit of time.Two comparable observations of the same item and metric. A post’s age is not a measurement interval.
AccelerationWhether that rate is increasing.At least three comparable observations. Two counts alone do not establish acceleration.
Engagement rateInteractions relative to an explicitly named denominator.Compatible numerator and views or impressions from the same window. Follower rate and view rate are different measures.
Search interestMovement in a relative search index, or observed queries from an owned property.The measurement type, market and window. A 0–100 index is not search volume or website traffic.
AI answer visibilityWhat a controlled answer check returned.The prompt, model and observation context. It does not measure what all users ask an AI assistant.
Product relevanceWhy a topic may help a particular audience.Confirmed product context and an explicit, reviewable angle. This is a recommendation, not a measured performance outcome.

A worked example

Suppose the same post has 120 comments at 09:00 and 180 at 12:00. The observed change is 60 comments over three hours: 20 comments per hour and 50% growth from the first count. That says nothing by itself about views, acceleration, sales or performance on another platform. If the first count is zero, percentage growth is undefined; the absolute change is still useful. These numbers are illustrative.

Calculate your own observation →

Why a signal is not a virality score

Each trend carries one signal: popular now, rising, emerging, new development, recurring problem, search interest or creative pattern, or “not enough evidence” when one reading cannot establish any of them. Measured growth is reported only from comparable observations. None of them is a percentage chance of going viral.

A niche query adds why each trend relates to your niche, as core, adjacent or global. Compare that reason with the measured observations before deciding to publish.

Use a broader news topic only when you can name the affected buyer task and offer a useful contribution. For an API monitoring product, an outage might support a specific timeout diagnostic. It does not justify attaching the product to unrelated popular news. If the link is weak, keep the topic as context and choose another post.

Read the V3 connection contract →