The Data Model
Podcast → episode → insight
SonicAlpha has three core objects. A podcast is a show. An episode is one conversation from that show. An insight is one investment-relevant claim extracted from that conversation.
Every insight points back to its episode and podcast, so you can start with a claim and trace it to the conversation it came from.
Most integrations start with insights — they are the objects you search, filter, cite, and use in research — so this page starts there and works up to episodes and podcasts.
Insight
An insight is one investment-relevant claim, with the context needed to understand where it came from. Each insight object is self-contained: the claim, the speaker, the companies, and the pointer back to the source audio are all on it — displaying, citing, or playing an insight never requires a follow-up call.
Key fields
body — SonicAlpha’s extracted paraphrase of the claim.
quote — the verbatim source passage. Cite body, ground with
quote.
type — what kind of claim it is: thesis = a forward-looking
argument, observation = a qualitative read on the present,
data_point = a concrete number. The types search filter takes the
same values.
speaker_name / speaker_role — who made the claim and what they
do professionally. Roles:
operator— runs or operates a businessinvestor— deploys capitalresearcher— produces researchcommentator— journalist, host, or commentatorgovernmentunknown
A CEO of a VC firm is an investor, not an operator — the role is
what the speaker does professionally, not their job title.
mentions — the companies referenced in the insight. One insight
can mention multiple companies, and each company carries its own
sentiment.
published_at — when the underlying episode was published.
start_seconds / end_seconds — where the claim sits in
episode_audio_url. Pass them to a player to hear the claim at the
moment it was said.
episode_id / podcast_id — the episode and podcast the insight
came from.
Full insight fields are documented in the API reference.
Episode
An episode is one conversation from a podcast. It connects a set of insights back to the conversation they were extracted from.
Full episode fields are documented in the API reference.
Use episode_id when you want to retrieve the episode behind an
insight, search within a single conversation, or group insights from
the same episode.
insight_count is the number of searchable insights extracted from the
episode.
Podcast
A podcast is the show that episodes belong to. Use it to scope research to a particular show or speaker:
Find everything this podcast has said about NVIDIA.
A podcast appears in the API only if it has searchable insights — absence means not covered, not “not found.”
insight_count and episode_count show how much searchable content
SonicAlpha has from the show. latest_episode_at shows how recently it
last produced searchable content.
Naming convention
An object’s own fields use simple names: id · title · name ·
body. Fields that reference another object are prefixed:
episode_id · podcast_id · podcast_name. This convention is
consistent across the API.