One identity per call
Handle, page, channel, or actor resolution stays scoped to the fields the route contract documents.
← All features
Feature · Profiles
Profile and identity lookups with explicit bounds.
Read public profile and identity fields one target at a time — or in a documented batch — without inventing audience demographics the upstream fields do not support.
What this unlocks
Capability outcomes, not availability claims.
Each product family exposes profile-style routes in its governed contract. API Aha meters and caches those reads; missing fields stay missing instead of being backfilled by a model.
Comparable shapes
Agency and diligence workflows can map the same profile questions across platforms without scraping HTML.
Evidence-linked
Only paths present in the launch route manifest appear below. Catalog status still decides buyer access.
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/profile/api/facebook/people/profile
Instagram IntelligenceVerification pending
/api/instagram-snapshot/profile
TikTok IntelligenceVerification pending
/api/tiktok/profile
Twitch IntelligenceVerification pending
/api/twitch/profile/api/twitch/channel
Pinterest IntelligenceVerification pending
/api/pinterest/profile/api/pinterest/profile-identity
Bluesky Engagement & SignalsVerification pending
/api/bluesky/profile/api/bluesky/resolve-handle
Endpoint presence is not a public-availability claim. Review the canonical catalog before integrating.