Social listening, without the dashboard
Comments, replies, hashtag results and search, as raw typed JSON you put into your own pipeline. No dashboard to learn and no seat licences.
What serves this
Read from the platform registry, so nothing here is a job the API cannot currently do. Each endpoint links to its own reference.
What social listening actually needs
Most listening tools sell you a dashboard, and the dashboard is the problem. It decides what counts as a mention, what sentiment means, and which posts are worth showing you — and none of those decisions are yours, or visible, or the same as last quarter's.
What a team building its own listening actually needs is the raw material: the comments under a post, the replies under those, the posts carrying a hashtag, and the results of a search. Typed, whole, and cheap enough to pull often. What you do with them — your sentiment model, your relevance rules, your alerting — is the part worth owning.
The practical constraint is cost per pull. Listening means running the same queries repeatedly, so a per-request rate that looked fine for a one-off becomes the whole budget on a daily schedule. Billing per result delivered is what makes a frequent poll affordable, and it means a quiet day costs almost nothing.