Social media and search trend intelligence for AI agents

Spot the trends your users care about.Know what to distribute next.

Paste your product URL. TrendsFast turns live social conversations, search demand, developer adoption, news, and content signals into one evidence-backed topic, angle, format, and channel for every agent in your stack.

Reach the right users before the moment passes—without chasing irrelevant hype.

Private by default. Public sharing is a separate opt-in after delivery.

See it in action One free founder-reviewed scan · No card · Private by default · Open source
Founder-reviewedEvidence-linkedPrivate by defaultNo auto-postingOpen source
SOURCE COVERAGE
Product websiteComing soonXComing soonGoogle TrendsComing soonHacker NewsComing soonGitHubComing soonOpen web / newsComing soonYouTubeComing soonManual evidenceComing soon
Source truth →

Social listening gives you a feed.

Trend dashboards give you charts.

Raw APIs give you JSON.

TrendsFast gives your agents the next move.

01 / THE SIGNATURE OBJECT

See what your agent gets.

Switch between all four honest outcomes. Each decision keeps its context, why-now reasoning, evidence receipts, truth class, confidence, and limitations attached.

Your next distribution moveFor SignalKit
Founder-reviewed
PUBLISHXFounder text post

Why live signals still fail to tell founders what to do

I spent more time researching distribution than shipping the feature.
THE ANGLE

Show the gap between a feed of signals and one evidence-bound decision, using a product-specific scan teardown.

WHY NOW

Search interest and two independent founder and developer discussions converge on agent-ready research workflows.

  1. 01Open with the weekly research loop you replaced.
  2. 02Show the evidence receipts and what each one contributes.
  3. 03End with the decision and invite one founder URL.
Evidence receipts2 bound sources
Search demandDistribution agent workflowsExample measured 30-day direction
Developer communityFounder discussion on agent researchExample independent conversation
Limitations
  • Example data does not represent current source coverage or customer traction.

Product demo using example data.

02 / PROOF YOU CAN INSPECT

Open engine. Visible rules.

AGPL-3.0

Inspect the provider contracts, truth classes, deterministic ranking, evidence binding, WAIT quality floor, API schemas, and PostgreSQL lifecycle yourself.

View the source on GitHub

03 / BUILT FOR THE BUILDER

Who is TrendsFast for?

Technical founders and small teams who build faster than they distribute.

01

AI founders

Turn fast product cycles into timely, product-specific distribution decisions your agents can use.

02

SaaS founders

Find the conversations and demand shifts that matter to a narrow buyer instead of chasing broad hype.

03

Developer-tool founders

Connect developer adoption, search, community, and release signals to one useful next action.

04

Agents and automation builders

Give workflows structured trend intelligence without handing them a feed to interpret or a publishing key.

04 / HOW IT WORKS

From a URL to one defensible move.

01

Understand

Read the public product, infer its buyer and credible topics, and keep assumptions visible for founder review.

02

Detect

Check bounded social, search, developer, news, and content signals while preserving original URLs and source limits.

03

Decide

Rank the evidence, apply the quality floor, and return one PUBLISH, REPLY, REMIX, or WAIT.

YOUR URL IS THE ONBOARDING

What trend should your product act on next?

05 / SEE IT IN ACTION

From public URL to evidence-backed decision.

The walkthrough follows the real contract: infer context, inspect coverage, reveal the move, open evidence, complete founder review, then call the API.

Interactive walkthrough using example data.

Your next distribution moveFor SignalKit
Founder-reviewed
PUBLISHXFounder text post

Why live signals still fail to tell founders what to do

I spent more time researching distribution than shipping the feature.
THE ANGLE

Show the gap between a feed of signals and one evidence-bound decision, using a product-specific scan teardown.

WHY NOW

Search interest and two independent founder and developer discussions converge on agent-ready research workflows.

  1. 01Open with the weekly research loop you replaced.
  2. 02Show the evidence receipts and what each one contributes.
  3. 03End with the decision and invite one founder URL.
Evidence receipts2 bound sources
Search demandDistribution agent workflowsExample measured 30-day direction
Developer communityFounder discussion on agent researchExample independent conversation
Limitations
  • Example data does not represent current source coverage or customer traction.

06 / AGENT-READY

Power every agent with live trend intelligence.

Give the tools you already use one structured, evidence-backed distribution move.

ChatGPT

Example HTTP workflow

Claude

Example HTTP workflow

Codex

Example HTTP workflow

Cursor

Example HTTP workflow

OpenClaw

Example HTTP workflow

Hermes

Example HTTP workflow

n8n

Example HTTP workflow

Make

Example HTTP workflow

Zapier

Example HTTP workflow

Available: HTTP APIAvailable: Example workflowsComing soon: Native integrations

07 / IMPLEMENTED OUTCOMES

Enough signal to decide. Enough restraint to WAIT.

01

Relevant trend detection

Signals are filtered against the product, buyer, credibility, timing, and usable formats.

02

Measured versus inferred momentum

Time series and stored snapshots stay distinct from an emerging but unmeasured signal.

03

Cross-source confirmation

Independent origins can strengthen a decision; copies of one announcement cannot.

04

One Next Move

Every completed scan resolves to PUBLISH, REPLY, REMIX, or WAIT—never another research feed.

05

Evidence receipts

Original URLs, observation times, reasons, and limitations stay attached to the recommendation.

06

WAIT quality floor

Thin, stale, dependent, or poorly matched evidence stops the move instead of manufacturing urgency.

07

Founder review

The first cohort gets a human context and evidence check before a result is delivered.

08

Agent-ready JSON

The web result and REST API use the same bounded, structured decision contract.

08 / TRENDSFAST FOR AGENTS

Create once. Poll normally. Receive the same Next Move.

Approved users receive a unique project-scoped key. Scan creation is bounded by rate and cost limits; normal result polling does not create a research run. Nothing auto-publishes.

01POST /v1/next-moveCREATE
curl -X POST https://trendsfast.com/v1/next-move \
  -H "Authorization: Bearer tf_live_<prefix>.<secret>" \
  -H "Idempotency-Key: 4a2d1201-9666-4ef0-90a9-e5aa47786c8e" \
  -H "Content-Type: application/json" \
  -d '{
    "product_url": "https://example.com",
    "goal": "qualified_signups",
    "market": "US",
    "language": "en",
    "preferred_channels": ["x", "linkedin"]
  }'
02202 AcceptedPOLL
HTTP/1.1 202 Accepted
Location: https://trendsfast.com/v1/next-moves/scan_01J...

{
  "id": "scan_01J...",
  "status": "QUEUED",
  "status_url": "https://trendsfast.com/v1/next-moves/scan_01J..."
}
03GET status_urlREADY
GET /v1/next-moves/scan_01J...

{
  "status": "READY",
  "next_move": {
    "action": "PUBLISH",
    "channel": "x",
    "topic": "Evidence-first distribution agents",
    "confidence": 0.82,
    "valid_until": "<absolute ISO-8601 timestamp>"
  },
  "why_now": {
    "signal_class": "CORROBORATED_SIGNAL",
    "independent_source_count": 3
  },
  "evidence": [{ "url": "https://original.example/..." }],
  "founder_reviewed": true,
  "auto_publish": false
}

09 / SOURCES ARE NOT DESTINATIONS

Evidence in. Recommended channel out.

Evidence and recommended channel do not have to be the same.

Evidence sources
  • Search demand
  • X
  • Hacker News
  • GitHub
  • Web and news
  • YouTube
  • Product site
  • Manual evidence
Output channels
  • X
  • LinkedIn
  • Reddit
  • YouTube
  • TikTok
  • Blog and newsletter
Explore channel guidance

10 / WHY I BUILT IT

Building got fast. Choosing what to say did not.

Building became fast. Distribution research stayed slow. I kept reopening the same social, search, developer, news, and video tabs—then still had to decide what was relevant to say. More raw data did not solve that last mile. TrendsFast is built around one decision: understand the product, detect a credible moment, and return one evidence-backed Next Move. The first cohort is founder-reviewed because context and trust matter more than volume. The engine is open source, results are private by default, and nothing auto-posts.

Read the thinking

11 / PRICING

Start with the decision. Pay only for managed repetition.

The free scan proves the product object. Open source gives you control. Managed monitoring stays bounded by real research and provider cost.

Free Scan

$0 once

See the complete URL-to-Next-Move loop before signup or payment.

  • One founder-reviewed scan
  • One public product URL
  • One PUBLISH, REPLY, REMIX, or WAIT
  • Evidence and limitations
  • No card
  • Private by default
Run a free scan
Open Source

$0 + provider costs

Run the real engine yourself and own the operational work.

  • The same decision engine
  • Example mode
  • PostgreSQL
  • Bring your own provider keys
  • Self-hosted operations
View on GitHub

12 / STRAIGHT ANSWERS

Before you paste a URL.

What is a Next Move?

One evidence-backed distribution action: PUBLISH, REPLY, REMIX, or WAIT, with a topic, channel, angle, hook, format, outline, why-now explanation, evidence, confidence, limitations, and validity window.

Does one Next Move equal one content piece?

Not always. A move is one distribution action. It can power a post, reply, thread, article, short video, tutorial, or brief, but it is not promised as a finished asset.

Is this a social media trend API?

Yes. TrendsFast combines social and search trend detection with product context, then returns a decision rather than reselling a raw feed.

Does it guarantee viral content?

No. Relevant evidence can improve timing and fit, but TrendsFast never guarantees virality, views, users, customers, or revenue.

Which sources are connected?

The source ledger distinguishes Connected, Limited, Coming soon, Unavailable, and Permission required. A source is never marked connected without a dated deployed read-back.

Why can the result be WAIT?

WAIT protects your credibility when evidence is weak, stale, dependent, irrelevant, saturated, or outside the formats you can credibly make.

Do I connect social accounts?

No. The free scan begins with one public product URL and does not ask for social-account access.

Does it publish?

No. TrendsFast recommends one move and binds the evidence. You review, edit, and decide whether and where to publish.

Can every agent call it?

Any tool that can make an authenticated HTTP request can use the REST contract once its project has approved API access. That is not the same as a native integration.

What does unlimited agents mean?

Multiple agent clients may use the same project-scoped key. It never means unlimited research runs, projects, provider fan-out, or model usage.

What are the plan limits?

Founder is €39/month and covers one monitored product, one scheduled run per day, ten accepted on-demand refreshes per billing month, at most one delivered move per day, and 30-day history.

How does cloud differ from open source?

Open source includes the same decision engine with PostgreSQL and bring-your-own provider keys. Managed cloud adds provider accounts and operations when those services are enabled.

How is submitted data handled?

Free scans are private by default, use unguessable links, and accept a public product URL. Public sharing is a separate explicit opt-in after delivery.

ONE URL. ONE DECISION.

Stop researching every platform.Spot the trend your users care about now.

One free founder-reviewed scan · Private by default · No card