Observable counts
Likes, reposts, followers, and viewers stay tied to the sample or profile the route fetched.
← All features
Feature · Engagement
Engagement signals taken from returned records.
Followers, reactions, views, and interaction rates derived from what the call actually returns — not from opaque third-party rank scores.
What this unlocks
Capability outcomes, not availability claims.
Engagement routes expose observable interaction fields. API Aha will not present unsupported fraud, bot-percentage, or revenue claims as measured fact.
Rate honesty
Engagement-rate style fields are computed from collected numerators and denominators when present.
No demography theater
Interest or country breakdowns appear only when a verified field supports them.
Evidence-gated surface
Launch routes that back this feature.
Paths below are taken from each product's committed route manifest. Catalog status still decides whether buyers may call them.
Facebook Master StackVerification pending
/api/facebook/engagement-quality/api/facebook/audience-quality
Instagram IntelligenceVerification pending
/api/instagram-snapshot/engagement-quality/api/instagram-snapshot/audience-quality
TikTok IntelligenceVerification pending
/api/tiktok/profile-engagement-rates/api/tiktok/post-stats
Twitch IntelligenceVerification pending
/api/twitch/profile-followers/api/twitch/stream-viewers
Pinterest IntelligenceVerification pending
/api/pinterest/profile-followers/api/pinterest/profile-engagement-rates
Bluesky Engagement & SignalsVerification pending
/api/bluesky/engagement/api/bluesky/post-likes
Endpoint presence is not a public-availability claim. Review the canonical catalog before integrating.