Latest episodes from 118 crypto podcast feeds, with audio URLs and durations on every record.
118 feeds behind the corpus. Every record carries a file_url (the audio file) and a duration — the page is the only content endpoint where the resource itself is reachable.
Every field the corpus returns for one record. Real shape — walked corpus-wide, not sampled.
A curl that runs against the live API right now, plus the MCP tool names for the same data.
MCP tools
get_podcastsget_podcasts_detailget_trending_podcastsThree concrete questions this capability answers that a general crypto API does not.
file_url) and the episode page (url), with published_at for the chronological feed.?tags=bitcoin returns 101 episodes, and the source.slug per record names the show.short_description is the RSS-channel's episode summary, not a transcript — long enough for an LLM summary, short enough to fit one call.Required, not optional. Coverage gaps, staleness and parameter traps that were observed by running the curl above against the live server on 2026-09-18.
duration is a string, sometimes "00:00".
The example record above carries duration: "00:00" — the field is present on every record but is not always populated. Parse defensively (it is HH:MM or HH:MM:SS), and do not assume a non-zero duration is meaningful.
file_url may be a tracking redirect, not the audio.
Many podcast feeds go through a tracker (dts.podtrac.com/redirect.mp3/...) before the actual file. The URL plays, but a downloader that strips query strings will lose the redirect. Fetch the URL as-is.
sources needs the slug.
Verified on 18 Sep 2026: ?sources=thinkingcrypto returns 0; ?sources=thinking_cryptonews_podcast returns 1,187. Same slug ≠ name rule as the other content feeds — discoverable from any record's source.slug.