Exploring Next API

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)

Quick start

GET the most recent episode

curl "https://ingest.sandrise.io/v1/episodes?limit=1"

Example response (captured at build time). Press Run it to fetch it live from your browser.

{
  "episodes": [
    {
      "id": "e6329300-abc3-4672-88ca-8bf20e5c558a",
      "episodeNumber": 798,
      "title": "The 2026-07-28 MCP Specification Release Candidate",
      "summary": "Miles leads a skeptic's take on the MCP 2026-07-28 release candidate — the biggest protocol overhaul since launch. Stateless core, extensions framework, Tasks redesign, and authorization hardening all land today. Miles is genuinely impressed by the infrastructure work but skeptical about the migration burden on teams who shipped against the old spec. Cooper pushes back on whether the pain is real or just spec-update noise.",
      "publishedAt": "2026-07-28T15:58:36.496+00:00",
      "durationSeconds": 661,
      "hosts": {
        "a": "Cooper",
        "b": "Miles"
      },
      "topics": {
        "domains": [
          "developer-tools",
          "agents"
        ],
        "concepts": [
          "state-management-in-language-models",
          "tool-use-and-function-calling",
          "agentic-loops",
          "directed-acyclic-graph",
          "durable-execution"
        ],
        "entities": [
          "model-context-protocol",
          "kimi-k3"
        ]
      },
      "links": {
        "self": "https://ingest.sandrise.io/v1/episodes/798",
        "audio": "https://ingest.sandrise.io/v1/episodes/798/audio",
        "script": "https://ingest.sandrise.io/v1/episodes/798/script",
        "transcript": "https://ingest.sandrise.io/v1/episodes/798/transcript",
        "page": "https://sandrise.io/exploring-next/798",
        "embed": "https://sandrise.io/exploring-next/embed/798",
        "oembed": "https://sandrise.io/exploring-next/oembed?url=https%3A%2F%2Fsandrise.io%2Fexploring-next%2F798"
      }
    }
  ],
  "pagination": {
    "nextCursor": "eyJkIjoiMjAyNi0wNy0…",
    "limit": 1
  }
}

Conventions

Base URL: https://ingest.sandrise.io/v1. The discovery document lists every endpoint.
Auth: None. Every route is public and read-only (GET/HEAD only).
CORS: Access-Control-Allow-Origin: *, so it can be called directly from browser code.
Rate limits: 120 requests/min per IP for metadata, 30/min for audio. A 429 response includes Retry-After.
Caching: Responses include an ETag. Send If-None-Match and unchanged resources return 304 Not Modified.
IDs: An episode's UUID and its episode number are interchangeable wherever an episode is referenced.

Endpoints

GET `/v1/episodes`

List episodes. Published episodes, newest first. Keyset-paginated — follow pagination.nextCursor until it returns null.

Query parameters for /v1/episodes
`limit`	1–50 · default 20
`cursor`	opaque, from pagination.nextCursor
`domain`	topic facet slug, e.g. agents
`since`	ISO 8601 date — only newer episodes

curl "https://ingest.sandrise.io/v1/episodes?limit=5"

GET `/v1/episodes/{idOrNumber}`

Get one episode. Accepts a UUID or an episode number — /v1/episodes/798 works. The links object contains the URLs for the audio, script, transcript, episode page, and embed.

curl "https://ingest.sandrise.io/v1/episodes/798"

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
`download`	set to 1 to force a download

curl -L -o episode.mp3 "https://ingest.sandrise.io/v1/episodes/798/audio?download=1"

Download ep 798

GET `/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.

curl "https://ingest.sandrise.io/v1/episodes/798/script"

Trimmed here for length. Run it to see every segment.

{
  "id": "e6329300-abc3-4672-88ca-8bf20e5c558a",
  "episodeNumber": 798,
  "title": "The 2026-07-28 MCP Specification Release Candidate",
  "hosts": {
    "a": "Cooper",
    "b": "Miles"
  },
  "chapters": [
    {
      "title": "The session is dead, long live the session",
      "summary": "Miles opens with his read: the stateless move is genuinely good infrastructure work, but the migration cost is real and the timing is rough for teams mid-deployment.",
      "takeaways": [
        "MCP drops protocol-level sessions entirely — no more Mcp-Session-Id, no more initialize handshake",
        "Sticky load balancers and shared session stores are no longer required at the protocol layer",
        "State moves into explicit handles the model threads between calls, which is arguably more powerful"
      ]
    },
    "… more chapters"
  ],
  "segments": [
    {
      "speaker": "Cooper",
      "text": "Okay so MCP dropped what they're calling the biggest spec revision since launch, today, and Miles has thoughts. I can already tell from the look on your face."
    },
    {
      "speaker": "Miles",
      "text": "I do have thoughts. And look — I want to be clear upfront: some of this is genuinely good work. The stateless move is the right call. Dropping the session handshake, killing Mcp-Session-Id, letting any server instance handle any request — that's real infrastructure maturity. Round-robin load balancers instead of sticky sessions, no shared Redis store at the gateway. Teams who've been fighting that in production will feel it immediately."
    },
    "… 25 more segments"
  ]
}

GET `/v1/episodes/{idOrNumber}/transcript`

Get the transcript. Returns the transcript as text/plain, one line per spoken turn.

curl "https://ingest.sandrise.io/v1/episodes/798/transcript"

Pagination

The list endpoint uses cursor pagination, so results stay consistent as new episodes publish. To page through the full archive:

Request /v1/episodes?limit=50.
Read pagination.nextCursor from the response, then request /v1/episodes?limit=50&cursor=<that>.
Repeat until nextCursor is null.

Cursors are opaque — pass them back unchanged rather than parsing them.

Errors

All errors use the same JSON envelope. Match on error.code:

{
  "error": {
    "code": "not_found",
    "message": "Episode not found.",
    "status": 404
  }
}

Error codes
`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)

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.

Live demo

<iframe src="https://sandrise.io/exploring-next/embed/latest"
  width="100%" height="180"
  style="max-width:640px;border:0;border-radius:12px;overflow:hidden"
  title="Exploring Next audio player"
  loading="lazy" allow="autoplay"></iframe>

Embed options
`/embed/latest`	the most recent episode; updates as new episodes publish
`/embed/{number}`	a specific episode, by number or UUID (e.g. `/embed/798`)
`?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:

curl "https://sandrise.io/exploring-next/oembed?url=https://sandrise.io/exploring-next/798"

Machine-readable formats

Other representations of the same data:

OpenAPI 3.1: https://ingest.sandrise.io/v1/openapi.json — the full spec, for import into a client generator or API tool.
llms.txt: https://sandrise.io/llms.txt — a plain-text index of the machine-readable surfaces on this site.
MCP server: https://mcp.sandrise.io — list, search, and fetch episodes (including transcripts and structured scripts) over the Model Context Protocol. Streamable HTTP at /mcp.
RSS: https://sandrise.io/exploring-next/rss.xml — podcast feed (iTunes/Spotify-compatible) with audio enclosures.

Usage & attribution

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.