Social data, by the job you need done.
Every page is a working recipe: the calls it takes, which platforms serve each one, what it costs, and code you can run. Start from the job, or from your team.
- Platforms
- 26
- Endpoints
- 194
- Recipes
- 9
- Free credits
- 100
By job
The workloads people run on the API, each with its exact call sequence.
- Social listeningTrack a brand, product or topic everywhere people discuss it.3 steps · 20 platforms
- Comment scrapingEvery comment on a public post, replies linked, one schema.3 steps · 10 platforms
- Creator analyticsHandle in, profile, posts and engagement out.3 steps · 22 platforms
- Influencer discoverySearch creators, check their audience, score them.4 steps · 21 platforms
- Video transcriptsThe words in a video, from the platform that hosts it.3 steps · 8 platforms
- Ad intelligenceSee what a competitor is paying to say.4 steps · 3 platforms
- Trend detectionWhat is climbing now, and the posts driving it.3 steps · 4 platforms
- Shop and product researchProducts, prices and reviews from social shops.4 steps · 3 platforms
- Arabic social analyticsDialect, sentiment and entities for Arabic posts and comments.3 steps · 9 platforms
By team
If you would rather start from who you are than from what you are building.
- The social data API built for developersOne REST API, one auth header, one JSON shape.→
- Social data for AI agentsA hosted MCP server and one schema your agents can rely on.→
- Social data for marketing teamsCompetitors, mentions, creators and ads in one feed.→
- One social data API for every clientEvery client’s platforms on one key.→
- Social data for indie hackersOne key instead of a dozen scrapers.→
- Social data for researchers and analystsConsistent public datasets across platforms.→
Questions
What can I build with a social data API?
Brand monitoring, creator and competitor analytics, influencer discovery, content research from transcripts, ad tracking, trend dashboards, and data for AI agents. Each recipe on this page shows the calls it takes.
Do I need a different key per platform?
No. One key covers every platform and every operation; the platform is part of the path.
Are these separate products?
No. They are recipes on the same API, billed from the same credit balance.
Can I combine several recipes?
Yes. They return the same unified types, so the output of one feeds straight into another.
One key, every platform, whichever job you picked
100 free credits on signup. No card, and credits never expire.