PlatPhorm Podcasts

Podcasts Documentation

A practical guide to finding, understanding, playing, and saving public media through one input, one player, and one canonical media graph.

What Podcasts does

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

One universal input

Enter natural language, keywords, titles, artists, stations, locations, languages, or one public source URL. The same MediaIntent contract searches canonical records first and performs bounded provider discovery only when useful.

One persistent player

Every Check / Play action updates the same global player. Direct media, radio, HLS, DASH, Archive files, relayed sources, and validated provider embeds share one truthful playback and fallback contract.

Cloudflare web and API ownership

The Cloudflare web Worker at podcasts.vanagon.com owns rendering, public routes, SEO, the universal input, and the player. The Cloudflare API Worker at podcasts-api.ja1.io owns D1 canonical truth, KV derived state, R2 bounded artifacts, Queues, Workflows, health, ranking, repair, enrichment, and relay in PH3AR.

Relevant discovery and provider coverage

A useful search can include podcasts, public feeds, radio, recordings, video, and collections. Native provider search, saved records, URL resolution, and collection enumeration have separate capabilities. Results keep source attribution and explicit language, location, date, and provider constraints. Availability varies; missing sources must not be replaced with invented results.

Fast results and continued exploration

The experience goal is useful results quickly, more relevant choices as you scroll, and the same recording continuing while you browse. Background work is bounded and resumable. Partial results, upstream failures, and actual exhaustion need distinct states; saving a collection should not wait for full enumeration.

Cross-platform playlists

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

Compatibility APIs

Resolve, ingest, feed, import, and search endpoints remain supported for existing integrations, agents, and automation. They converge on the same canonical media graph rather than creating separate consumer workflows or sources of truth.

Parser behavior

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

RSS, Atom, and JSON Feed support

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

JSON:API 1.1 compound documents and non-executing Atomic Operations normalization

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

Live radio and IPTV channel discovery with on-demand HLS relay

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

Platform links

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

Archive Mode and saved media

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

Operator configuration

PLATPHORM_PROTECTED controls operator mode. When set to 0, public workflows stay open. When set to 1, server write paths use backend PLATPHORM_API_KEY policy. Media artifacts use the configured server storage path and are never claimed unless confirmed.

Remote streaming fallback

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

Verified in-app playback

Play appears only for a verified direct, relayed, HLS, DASH, radio, Archive, or allowlisted provider-embed path. All methods use one persistent player; failures stay in the app with retry, the selected variant, and View original. Archive collections default to audio when available, expose video and text variants in context, and save the selected child variant to playlists with its source attribution.

Playlists and queues

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

Share pages

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

Playlist share playback

Playlist share pages and embeds render only the shared items, with one playback control per playable item and visible attribution for every item.

SEO share cards and social previews

Persisted share pages generate canonical URLs, Open Graph metadata, Twitter/X cards, a generated image, audio metadata when playable, and JSON-LD from the real share packet.

Share index persistence

Share creation persists a share packet plus a paginated share index. /api/v1/shares returns the index with storage evidence for agents and tests.

Attribution persistence

Each shared item persists public-safe attribution: show, episode, creator, source URLs, artwork URL, submitted-by label, source host, and trace ID.

Discovery and metrics

/api/v1/discovery describes public capabilities, routes, MCP, LLMS, graph, policy, and Web Status. /api/v1/metrics excludes the browser-local draft queue and counts playlists or clip manifests only when server persistence confirms them.

Clips and embeds

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

Tags and categories

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

Emoji scoring

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

XML and JSON validation

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

OpenContent sharing

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

API analytics

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

Docs and Sheets export

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

BrowserOps, Evals, AgentUI, Claws, and Trace integrations

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

MCP tools and OpenAPI

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

Agent policy, trust policy, security, and redaction

Supported where real parser, playback, storage, validation, or integration evidence exists; otherwise the UI and APIs report degraded, unavailable, or local-only state.

How discovery reaches your player

The web and API run in Cloudflare. Source media stays with its publisher, while the library keeps canonical metadata and background progress.

Listeners and agents use the Cloudflare web Worker; the API Worker manages D1 records, cache, artifacts and background jobs, while one player streams attributed source media.
Runtime ownership. Provider availability and playback are verified independently.

Discovery and continuation diagram · Collection lifecycle diagram · Developer contracts