Use case
Brand mention data via API
For teams that already know they want mentions programmatically: the buying question is coverage, freshness, and traceability, not what social listening is.
Updated
The short answer
A brand mention API returns the posts, articles, and conversations that reference a brand as structured data your own software can consume. The serious options split into agent-native APIs built for programmatic use, enterprise suite APIs sold with a dashboard seat, and affordable trackers with lighter coverage; the ranked list below states each one’s honest fit.
Tools to get brand mention data via API, ranked
- Waldo: agent-native: mentions, ads, and audience data over 200+ API and MCP endpoints, daily refresh, every mention traceable to its source; credit-metered rather than seat-licensed.
- Brandwatch (Consumer Research API): the deepest historical social archive in the category; enterprise contract and dashboard seat come with it.
- Meltwater API: strong global news and media coverage with PR workflow integration; API access is sold as part of the enterprise suite.
- Brand24 API: the affordable route to programmatic mentions for small and mid-sized teams, with lighter source coverage.
- Mention API: straightforward mention tracking with API access on business plans; suited to monitoring more than analysis.
Fit depends on the buyer: suite APIs reward existing enterprise customers; agent-native and affordable options reward teams building something.
The job to be done
The teams searching this phrase are building something: an internal dashboard, an agent workflow, a data product with a mentions layer inside it. What they need from a vendor is different from what a dashboard buyer needs: complete API surface rather than an export button, refresh cadence measured in hours, per-mention source links so numbers can be audited, and pricing that does not require an enterprise seat license to make one endpoint call.
The evaluation traps are consistent. Suite APIs often expose only a slice of what their dashboards show, mention counts without the underlying posts cannot be audited, and per-seat pricing models price out the exact automation use cases an API exists for. Ask every vendor the same four questions: what channels are covered, how fresh is the data, can I open every number back to its sources, and what does the meter charge for.
How Waldo does it
Track the brand set
Add your brands and competitors; Waldo tracks the conversation around all of them daily, news and social split by source type.
Pull mentions programmatically
Mentions endpoints return the posts and articles themselves with metadata, not just counts: filter by source type, window, and brand.
Join the summary layer
Per-brand mention summaries give platform splits and totals for trendlines, computed consistently so the series stays comparable.
Hand it to an agent
The same intelligence ships over the MCP server, so a Claude or MCP-compatible agent queries mentions mid-task without custom glue.
The endpoints
/v1/brands/{id}/mentionsThe mentions themselves: posts and articles with source links, filterable by source type and window./v1/brands/{id}/mentions/summaryTotals and platform splits per brand, the trendline layer.MCP: brand mention toolsThe same data as agent-callable tools for MCP clients.Questions teams ask
Can I get historical brand mentions through an API?
Depends on the vendor’s archive model. Suite vendors sell deep archives at enterprise prices; trackers mostly start collecting when you do. Waldo stores what it tracks permanently from the day tracking starts, so history accumulates without holes.
How do mention APIs price?
Three shapes: enterprise seat licenses with API access attached, per-mention or per-query metering, and credit systems that meter usage without seats. For automation-heavy use, metered pricing usually wins; for a team already paying for a suite dashboard, the attached API can be effectively free.
What does an MCP server add over a REST API?
A REST API needs your code; an MCP server lets an AI agent call the same data as tools, with the schema negotiated automatically. Teams building agent workflows skip the glue code entirely; teams building traditional dashboards still want REST. The serious vendors now ship both.
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.