Use case
Category intelligence as a system, not a quarterly deck
Brand moves, rising trends, and audience shifts across the whole category, tracked daily and queryable by anyone on the team.
The short answer
Waldo turns category intelligence into infrastructure. Activate the brands in a category and one surface tracks their activity, the audience conversation, and the rising trends, refreshed every 24 hours. Insights teams query it over API for scheduled reporting or over MCP for live questions, and every finding links to sources.
The job to be done
Somebody on the insights team owns the question of what is happening in the category, and today the answer is assembled by hand: analyst reports that lag by months, newsletters that cover what is loud, and one-off pulls whenever a stakeholder asks. Each question becomes a small project, so most questions go unasked.
The job is a standing model of the category that stays current on its own: which brands moved, which themes are rising, how the audience is shifting. The quarterly deck should be a view over that model, not a heroic act of collection that starts from zero every time.
How Waldo does it
Activate the category
Track the brands and audiences that define the space. From then on their activity, conversation, and ads refresh every 24 hours, and everything captured is stored permanently, so the model accumulates history instead of evaporating.
Watch the trends layer
MCP: category_trends surfaces rising themes from Waldo’s proprietary trends database, each linked to the posts driving it, so the category read leads with evidence.
Map the messaging landscape
GET /category/{id}/angle-library returns the versioned hook taxonomy across the set, which turns how the category talks into a diffable artifact rather than an impression.
Serve the stakeholders
The MCP connector installs org-wide, so account leads ask their own questions in Claude or Copilot while a weekly cron writes the digest. The insights team curates the model instead of fielding every query.
The endpoints
MCP: category_trendsRising themes for the category, evidence attached/category/{id}/angle-libraryThe messaging landscape as a versioned, diffable artifactMCP: brand_overviewPer-brand files that keep themselves currentDiscover endpointsLive platform queries for anything not yet trackedQuestions teams ask
How many brands can we put in a category?
As many as the category needs. There are no per-brand minimums and no per-seat fees; credits draw from an org pool, and the annual activation fee applies only to entities not already tracked.
Can non-technical teammates use it?
Yes. The MCP server is one block in mcp.json and installs org-wide as a connector, so anyone working in Claude, ChatGPT, or Copilot can query the category model conversationally.
How far back does the history go?
From activation onward, everything captured is stored permanently, including posts and ads that later get deleted. The category model gets more valuable every month it runs.
Keep reading
Put Waldo behind your agents
Brand, category, and audience intelligence over 200+ API and MCP endpoints. Sign up, mint a key, and run it against the brands you actually track.