A read-only HTTP API for Exploring Next episodes: metadata, audio, scripts, and
transcripts. There is also an iframe player you can embed on any site. No account or
API key is required.
Get one episode. Accepts a UUID or an episode number — /v1/episodes/787 works. The links object contains the URLs for the audio, script, transcript, episode page, and embed.
curl "https://ingest.sandrise.io/v1/episodes/787"
GET/v1/episodes/{idOrNumber}/audio
Get the audio. Returns the episode MP3. Supports HTTP Range requests, so players can seek. Add ?download=1 to get a Content-Disposition: attachment response with a descriptive filename.
Query parameters for /v1/episodes/{idOrNumber}/audio
Get the script. Returns the dialogue as speaker-labeled segments with stage directions removed, plus chapters with per-chapter summaries and takeaways.
Trimmed here for length. Run it to see every segment.
{
"id": "44e9a9d1-b0dd-4ab4-b425-3e436cb7540d",
"episodeNumber": 787,
"title": "MCP server portals",
"hosts": {
"a": "Asteria",
"b": "Draco"
},
"chapters": [
{
"title": "One front door for messy MCP servers",
"summary": "Cloudflare's core move is centralizing multiple MCP servers behind a single Access-controlled portal, with per-portal tools, prompt templates, aliases, and policies.",
"takeaways": [
"This fits the hosts' recurring boundary-infrastructure pattern around MCP.",
"The practical audience is teams with multiple MCP servers and real identity controls, not hobby setups."
]
},
"… more chapters"
],
"segments": [
{
"speaker": "Asteria",
"text": "Cloudflare basically turned scattered M C P servers into one Access-controlled front door, Draco, and I hate how much this fits our boundary obsession."
},
{
"speaker": "Draco",
"text": "Oof. You are dangerously happy already. But yes, this is absolutely episode seven eighty-seven of us saying the boring edge is where the product is."
},
"… 27 more segments"
]
}
GET/v1/episodes/{idOrNumber}/transcript
Get the transcript. Returns the transcript as text/plain, one line per spoken turn.
the episode has no usable script (uncommon; older episodes)
rate_limited
too many requests; retry after Retry-After seconds (429)
Embed the player
A self-contained iframe player for embedding on other sites. It plays the audio, seeks,
changes speed, and offers a download. It sets no cookies, uses no storage, and loads no
third-party scripts. Each player includes a "Listen on Exploring Next" link back to the
episode page.
the most recent episode; updates as new episodes publish
/embed/{number}
a specific episode, by number or UUID (e.g. /embed/787)
?theme=dark
dark palette; the default is the light theme above
?accent=RRGGBB
accent color as 6-digit hex, without the #
size
height is fixed at 180; width is fluid down to 250px
keyboard
Space/K play–pause, ←/→ seek ±5s
The player posts playback events to the parent page via postMessage, as
{ source: "exploring-next-embed", event, id, episodeNumber }, where
event is one of ready, play, pause, or
ended.
oEmbed
Platforms that support oEmbed (for
example WordPress and Ghost) embed the player automatically when an episode URL is
pasted. Episode pages declare the endpoint in their <head>. You can
also call it directly:
https://mcp.sandrise.io — list, search, and fetch episodes (including transcripts and structured scripts) over the Model Context Protocol. Streamable HTTP at /mcp.
This API is free and open — no keys, no signup. In return, a few terms apply to keep it
that way:
Attribute it. When you show or quote an episode, credit Exploring Next and link back to the episode page (sandrise.io/exploring-next/…). The embed player and oEmbed responses already include the link.
Don't re-host the archive. Building on top of the API is welcome; scraping the full catalog to republish it as your own feed, app, or dataset is not.
Respect the rate limits. 120 requests/min for metadata, 30/min for audio, per IP. They're generous for real use; sustained bulk extraction will be throttled.
It can change. Content is generated and occasionally corrected or removed. Cache reasonably, but treat the API — not your copy — as the source of truth.
Questions, higher limits, or a partnership? Get in touch. The same
terms are advertised on every API response as a Link: …; rel="license" header.
Versioning
v1 is additive-only: new fields may be added over time, but existing
fields are not removed or renamed, and existing URLs do not change. If a v2
is ever introduced, v1 will continue to work.
🧠
PM Perspective
Crafting your PM challenge
Analyzing context and generating a thoughtful question...