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.
no auth CORS enabled 120 req/min versioned (v1)
Example response (captured at build time). Press Run it to fetch it live from your browser.
{
"episodes": [
{
"id": "91c1a621-bf24-4c31-979c-aab481d73dcb",
"episodeNumber": 966,
"title": "Procedural Graphs: Self-Evolving Execution Structures for LLM Agents",
"summary": "Masonry and Eyre discuss the 'Procedural Graphs' paper, which proposes a self-evolving graph structure to manage procedural knowledge for LLM agents, moving away from flat history logs toward a structured 'what-to-do' map that the agent can refine through trial and error.",
"publishedAt": "2026-09-10T14:44:28.31+00:00",
"durationSeconds": 286,
"hosts": {
"a": "Masonry",
"b": "Eyre"
},
"topics": {
"domains": [],
"concepts": [],
"entities": []
},
"links": {
"self": "https://ingest.sandrise.io/v1/episodes/966",
"audio": "https://ingest.sandrise.io/v1/episodes/966/audio",
"script": "https://ingest.sandrise.io/v1/episodes/966/script",
"transcript": "https://ingest.sandrise.io/v1/episodes/966/transcript",
"page": "https://sandrise.io/exploring-next/966",
"embed": "https://sandrise.io/exploring-next/embed/966",
"oembed": "https://sandrise.io/exploring-next/oembed?url=https%3A%2F%2Fsandrise.io%2Fexploring-next%2F966"
}
}
],
"pagination": {
"nextCursor": "eyJkIjoiMjAyNi0wNy0…",
"limit": 1
}
}https://ingest.sandrise.io/v1. The discovery document lists every endpoint.GET/HEAD only).Access-Control-Allow-Origin: *, so it can be called directly from browser code.429 response includes Retry-After.ETag. Send If-None-Match and unchanged resources return 304 Not Modified.
Episode metadata, scripts, and transcripts require a free API key. Audio streaming,
the discovery document, the OpenAPI spec, the embed widget,
and oEmbed do not. Send the key as Authorization: Bearer <key>
(or an X-API-Key header). The "Run it" buttons on this page go through a
rate-limited demo proxy, so you can try everything without one.
To get a key, email Nick with a line about what you're building. Keys are free; the usage terms still apply.
/v1/episodes List episodes. Published episodes, newest first. Keyset-paginated — follow pagination.nextCursor until it returns null. Requires an API key.
limit | 1–50 · default 20 |
|---|---|
cursor | opaque, from pagination.nextCursor |
domain | topic facet slug, e.g. agents |
since | ISO 8601 date — only newer episodes |
/v1/episodes/{idOrNumber} Get one episode. Accepts a UUID or an episode number — /v1/episodes/966 works. The links object contains the URLs for the audio, script, transcript, episode page, and embed. Requires an API key.
/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. No API key needed.
download | set to 1 to force a download |
|---|
/v1/episodes/{idOrNumber}/script Get the script. Returns the dialogue as speaker-labeled segments with stage directions removed, plus chapters with per-chapter summaries and takeaways. Requires an API key.
Trimmed here for length. Run it to see every segment.
{
"id": "91c1a621-bf24-4c31-979c-aab481d73dcb",
"episodeNumber": 966,
"title": "Procedural Graphs: Self-Evolving Execution Structures for LLM Agents",
"hosts": {
"a": "Masonry",
"b": "Eyre"
},
"chapters": [
{
"title": "The Procedural Gap",
"summary": "The hosts discuss the failure of 'flat logs' in long-horizon agents and the concept of a Procedural Graph as a map for action.",
"takeaways": [
"Long trajectories cause agents to drift or loop because procedural knowledge is implicit in the history.",
"Procedural Graphs use (procedure, relation, procedure) triplets to explicitly map 'what-to-do'."
]
},
"… more chapters"
],
"segments": [
{
"speaker": "Masonry",
"text": "Wait, so the whole premise is basically that we've been treating agent memory like a giant, messy scroll of text, and it's just... not working for long tasks?"
},
{
"speaker": "Eyre",
"text": "Exactly. Most agents just look at a flat log of everything they've done and try to guess the next move. As the history grows, they just... drift. They start repeating the same useless tool call or completely forget the original goal because it's buried under ten pages of logs."
},
"… 23 more segments"
]
}/v1/episodes/{idOrNumber}/transcript Get the transcript. Returns the transcript as text/plain, one line per spoken turn. Requires an API key.
The list endpoint uses cursor pagination, so results stay consistent as new episodes publish. To page through the full archive:
/v1/episodes?limit=50.pagination.nextCursor from the response, then request /v1/episodes?limit=50&cursor=<that>.nextCursor is null.Cursors are opaque — pass them back unchanged rather than parsing them.
All errors use the same JSON envelope. Match on error.code:
{
"error": {
"code": "not_found",
"message": "Episode not found.",
"status": 404
}
}not_found | no such episode, or its audio is not yet published (404) |
|---|---|
invalid_episode_ref, invalid_cursor, invalid_limit | malformed input; the response says which (400) |
script_unavailable, script_unparseable | the episode has no usable script (uncommon; older episodes) |
rate_limited | too many requests; retry after Retry-After seconds (429) |
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.
/embed/latest | the most recent episode; updates as new episodes publish |
|---|---|
/embed/{number} | a specific episode, by number or UUID (e.g. /embed/966) |
?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.
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:
Other representations of the same data:
https://ingest.sandrise.io/v1/openapi.json — the full spec, for import into a client generator or API tool.https://sandrise.io/llms.txt — a plain-text index of the machine-readable surfaces on this site.https://mcp.sandrise.io — list, search, and fetch episodes (including transcripts and structured scripts) over the Model Context Protocol. Streamable HTTP at /mcp.https://sandrise.io/exploring-next/rss.xml — podcast feed (iTunes/Spotify-compatible) with audio enclosures.This API is free and open — no keys, no signup. In return, a few terms apply to keep it that way:
sandrise.io/exploring-next/…). The embed player and oEmbed responses already include the link.
Questions, higher limits, or a partnership? Get in touch. The same
terms are advertised on every API response as a Link: …; rel="license" header.
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.