Syncore Social Listening: An Agent-Driven, Composable Approach

What's actually shipped

Syncore Social Listening is not a single skill with a unified backend pipeline. It's a use-case grouping in the dashboard that points at four already-shipped source skills the agent calls when you ask:

• x-search — Grok Live Search over X (Twitter) with citations
• reddit — official Reddit API, search across subs
• github — official GitHub API for issues / discussions / repos
• linkedin — UI placeholder for now (LinkedIn's permissioned APIs aren't open enough to ship a real skill yet; tracked separately)

What the user sees in the [dashboard](/dashboard) is one card titled "Syncore Social Listening" with chips for the four sources. Behind that card there's no daemon process, no cron, no merged feed. There's the agent, four skills, and a workflow.

This is a deliberate design choice we want to explain — because it's not what most "social listening" tools do.

The traditional model: dashboards + standing pipelines

Brandwatch, Sprout Social, Mention all work the same way:

1. User configures a list of keywords / accounts / brands to track

2. Backend service polls each source every N minutes, normalizes records, dedupes

3. Records land in a database

4. Web dashboard renders charts, alerts, sentiment scores

The merge / dedupe / score logic is the product. That's why these tools cost $300+/mo for a serious workspace.

The agent-driven model

Syncore inverts it. The "what to track" lives in the agent's working context — whatever you and the agent discussed recently, whatever's in your wiki, whatever decision you're chasing. When you ask "what are people saying about X this week?", the agent fans out:

agent:
  parallel:
    x-search.search_x("X this week", recency="week")
    reddit.search("X", sort="hot", since_days=7)
    github.search_issues("X", since_days=7)
  collect → dedupe by URL when present → summarize → cite

No standing infrastructure. No backend dedupe. The agent does the merging at query time — typically 3-5 tool calls + a synthesis pass.

X is the centerpiece — via Grok

X is the highest-signal feed for tech / builder / agent conversations, 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_x(query, recency, mode) — Grok handles the actual X search server-side and returns post URLs + text + author + 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 (50K / 1M / 10M for free / premium / ultra per month).

Why no unified pipeline (yet)

Standing pipelines pay off when the volume of "things to track" exceeds what an agent can reasonably re-derive each query. For an early-product use case where the user has 1-3 topics they care about and asks once a day or once a week, the agent re-running the searches is fine — and avoids the staleness / billing complexity of a 24/7 polling backend.

If we see real users doing high-cadence monitoring (every hour, dozens of topics), we'll add:

• A scheduled "watch" tool that lets the agent register a query + cadence
• A backend worker that runs queries on schedule and writes results into the user's [wiki](/blog/syncore-wiki-llm-maintained-knowledge-base) under raw/messages/
• Daily-summary roll-ups via Cloudflare Workers Cron

But shipping that infrastructure before there's user demand for it would be expensive and over-engineered. Today's version is honest: four source skills + a use-case grouping that tells the agent how they fit together.

What this means in practice

You ask Claude: "what's the conversation around MCP-based agent platforms this week?"

The agent — having read the use-case description — calls x-search for X, reddit for /r/LocalLLaMA + /r/Anthropic, github for repos/issues mentioning MCP. It reads the top hits, dedupes the obvious ones (same article shared on X + Reddit), and summarizes. Adds frontmatter sources for each cited post.

If you want to keep the result, you ask: "file that as an analysis." Agent calls wiki.write_page("wiki/analyses/mcp-conversation-week-of-2026-04-26.md", ...). Next time you ask, the wiki page is one more search hit — the conversation compounds.

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

When this isn't right

• Real-time alerts — agent-driven model can't notify you the moment something happens. If you need that, you want a dedicated tool. (Or wait until we build the watch tool.)
• Sentiment time-series — we don't track historical sentiment over time. The agent answers "right now" questions well, "trend over 6 months" questions badly.
• High-volume brand monitoring — if you have 50 keywords and want hourly checks, this isn't the tool yet.

For the bulk of "I want to know what's being said" questions an early-stage builder or researcher actually has, agent-driven works.