FinTwit & Reddit Sentiment Tracking for Tickers: An Agent-Driven Approach

What's Actually Shipped

TradeLoop's sentiment capability is not a single skill with a unified backend pipeline. It's a use-case grouping that points at source skills the agent calls when you ask about a ticker's narrative:

• x-search — Grok Live Search over X (Twitter), the home of FinTwit, with citations
• reddit — official Reddit API, search across investing subs (r/wallstreetbets, r/stocks, r/options)
• news — headline and press-release search for the symbol

What you see in the dashboard is one card for sentiment with chips for the sources. Behind it there's no daemon process polling, no cron, no merged feed. There's the agent, a few skills, and a workflow.

This is a deliberate design choice worth explaining — because it's not what most sentiment tools do.

The Traditional Model: Dashboards + Standing Pipelines

The incumbents all work the same way:

1. You configure tickers / cashtags to track

2. A backend polls each source every N minutes, normalizes records, dedupes

3. Records land in a database

4. A web dashboard renders sentiment scores and charts

The merge / dedupe / scoring logic is the product, which is why these tools run a steep monthly bill for a serious workspace.

The Agent-Driven Model

TradeLoop inverts it. The "what to track" lives in the agent's working context — the name you're researching right now, what's in your journal, the thesis you're chasing. When you ask "what's the FinTwit and Reddit sentiment on NVDA this week?", the agent fans out:

agent:
  parallel:
    x-search.search("$NVDA OR NVDA", recency="week")
    reddit.search("NVDA", subs=["wallstreetbets","stocks"], since_days=7)
    news.search("NVIDIA", since_days=7)
  collect → dedupe by URL → weigh bullish/bearish tone → summarize → cite

No standing infrastructure. The agent does the merging at query time — typically 3-5 tool calls plus a synthesis pass — and tells you whether the crowd is leaning long or short, and why.

FinTwit Is the Centerpiece — via Grok

X is the highest-signal feed for trader chatter, and the official X API is unusable below the Enterprise tier. We use Grok's Agent Tools API (formerly Live Search), which xAI built specifically to let LLMs query X with semantic ranking and citations.

The x-search skill exposes search(query, recency, mode); Grok runs the actual X search server-side and returns post URLs, text, author, and timestamps. From the gateway's perspective it's just /v1/grok/chat/completions with a structured-output schema; tier quotas are accounted in Grok tokens.

Why No Unified Pipeline (Yet)

Standing pipelines pay off when the volume of things to track exceeds what an agent can re-derive each query. For a trader watching a handful of names and checking sentiment once a day, the agent re-running the searches is fine — and avoids the staleness and billing complexity of a 24/7 polling backend.

If we see traders doing high-cadence monitoring (every hour, dozens of cashtags), we'll add:

• A scheduled "watch" tool that registers a cashtag + cadence (folding into the [monitoring loop](/blog/set-and-forget-market-monitoring-loop-for-your-agent))
• A backend worker that runs queries on schedule and files results into your [journal knowledge base](/blog/trading-journal-as-durable-agent-memory) under raw/sentiment/
• Daily roll-ups via scheduled workers

Shipping that before there's demand would be over-engineered. Today's version is honest: source skills plus a use-case grouping that tells the agent how they fit.

What This Means in Practice

You ask Claude: "is the crowd bullish or bearish on TSLA into earnings?"

The agent calls x-search for cashtag chatter, reddit for the relevant subs, news for headlines. It reads the top hits, dedupes the obvious cross-posts, weighs the tone, and gives you a read with citations — plus a caveat when the sample is thin or one loud account is skewing it.

If you want to keep it, you ask "file that as a sentiment note." The agent writes it into your journal knowledge base. Next time you ask, that note is one more search hit — the read compounds.

That's sentiment tracking as an agent capability, not a dashboard product. Less dashboard, more answers.

When This Isn't Right

• Real-time alerts — the agent-driven model can't notify you the instant a cashtag spikes. For that you want the monitoring loop, or wait for the scheduled watch tool.
• Sentiment time-series — we don't track historical sentiment over months. The agent answers "right now" well, "trend over two quarters" badly.
• High-volume coverage — 50 cashtags on hourly checks isn't this tool yet.

For the "what is everyone saying about this name right now" question a trader actually has, agent-driven works.