Build / Replit · podcasts / audio (all shows - business, sports, tech, finance, academia)

Podcast Wire

A hosted, self-updating podcast-intelligence site - the readable takeaways AND the structured claims behind them, every one linked to the episode - with an optional weekly digest emailed to you. A live, always-on public site where anyone can browse this week's podcasts, read the takeaways, expand the structured claims, filter by show/topic/person/company, and jump to the real episode - refreshed on a cron and, if you want, delivered to your inbox every week - all cited, none invented.

Replit + Synorb build film

How do you build a podcast intelligence app with Replit?

Use the Podcast Wire one-shot prompt to have Replit build a hosted episode feed, database, Brief and Signal views, entity and topic filters, search, scheduled refresh, and weekly digest. Synorb streams supply fresh podcast content with real links to each original episode.

Watch the complete Replit build playlist →

A hosted Replit web app that shows the past week of podcast episodes as browsable cards - each with a human-readable Brief (narrative summary + key insight) and an expandable list of Signals (the atomic claims Synorb extracted) - plus combinable filters (podcast, topic, entity, significance), a link to every original episode, and a Scheduled Deployment that refreshes the feed (and can email a weekly digest) automatically.

Synorb extracts structured, cited claims from HOURS of spoken audio (210 podcast episodes in the last 7 days; ~48 claims/episode) - something no news API or scraper can do. Replit's Scheduled Deployments make it run itself: the feed stays fresh and a weekly digest lands in your inbox without anyone pressing a button. It shows off both Synorb primitives at once - the human Brief for readers and the machine Signals for the technical - side by side, each cited, on infrastructure that never sleeps.

Click, answer a few plain-English questions, get a working product.

No setup to learn. Replit asks a handful of normal-person questions — each with a smart default, so “you pick” always works — then builds it with live Synorb data flowing in.

1

Which podcasts should the feed cover?

Smart default: All podcasts (the broadest view - business, sports, tech, finance, academia), with quick-filter buttons; you can narrow to specific shows or topics after.

2

How should each episode show up - readable takeaways first, the structured claims first, or both side by side?

Smart default: Readable Brief up top with an 'expand claims' toggle that reveals the structured Signals underneath.

3

Pick a look: Editorial (magazine, serif, warm), Terminal (dark, dense, data-room), or Minimal (clean, lots of whitespace).

Smart default: Editorial - it reads like a premium publication and screenshots beautifully.

4

Should I also email you a weekly digest, and how often should the site refresh?

Smart default: Refresh daily at 7am (rolling 7-day window) and email a weekly digest every Monday - I can turn the email off.

Pick a look. It ships with taste by default.

Editorial

Warm magazine aesthetic: serif headlines, generous spacing, the Brief's key_insight pulled out as a standfirst, show name + episode date as a byline, a subtle 'expand claims' toggle. Reads like a premium podcast-intelligence publication - and the weekly email matches it.

Terminal

Dark, dense data-room feel: monospace accents, compact episode rows, color-coded show + topic chips, significance dots, claims shown as a tight structured list. For an analytical/insider vibe.

Minimal

Clean and quiet: lots of whitespace, one accent color, each card foregrounds the key takeaway with a subtle 'Signals' expander and a 'Listen' chip. Distraction-free browsing.

Synorb is the cited core. Replit’s own tools make it pop.

INFRA-BACKED, hosted Replit deployment. BUILD-TIME: optionally connect the Synorb MCP as an Agent tool so the build inspects real audio manifests (media_format=audio) and builds the Brief+Signals UI against the true shape. RUNTIME: the app's server calls Synorb's REST API for the last 7 days of audio manifests (media_format=audio) plus any active filters (tag_names for topic/entity, source channel for the show), reading the Synorb API key + secret from Replit Secrets - never in client code - and caches into Postgres so the site is fast. A Replit Scheduled Deployment refreshes on the chosen cadence and (optionally) emails a weekly digest. Credentials: Synorb is a real API and is THE data source - do not substitute another provider; I'll provide the key or you can ask me; Synorb Connect returns api_key, api_secret, and mcp_token.

Cited data core
Synorb
StreamsAll podcast source channels (media_format=audio) - business, sports (e.g. Locked On team pods), tech, finance, academia (e.g. Stanford GSB), ~210 audio manifests / 7 days, topic + person + org + place tags on each episode, home_domains span economics-business-work, arts-culture-entertainment, engineering-technology, and more
PrimitivesBrief (human-readable narrative + key_insight), Signals (atomic structured claims per episode), Tags (topic / person / organization / place) for filtering, source channel = the podcast/show, for the show filter, media_format=audio (the broad, correct way to get ALL podcasts), provenance citations (real episode source_url, never invented), significance level, coverage.status honesty
Experience layer
Replit native tools
ComposesReplit Scheduled Deployments (cron) - refresh the feed daily/weekly AND send an optional weekly email digest, unattended, Replit Secrets - store the Synorb api-key + secret server-side, never in client code, Replit Postgres / built-in DB - cache the week's episodes so the site is instant, A browse/filter UI (combinable filters for podcast, topic, entity, significance - options populated from the week's real data), A small 'most-active podcasts this week' chart from the real data, Email delivery (Resend/SMTP) for the optional weekly digest of top episodes, Replit Object Storage - optional generated hero art so it reads like a publication
Web searchgaps only — clearly marked, never the primary feed

Credential safetySynorb credentials stay server-side or local — never in client/frontend code. You only enter them when the agent asks, with credentials from synorb.com/connect.

One click from the original source.

Provenance is the product. Every episode card - and every row in the weekly email - carries a 'Listen to the episode' / source-domain link built from the real source_url Synorb returns, plus the show name (source channel) and episode date. Each expanded Signal claim and the Brief cite the same episode; a card with no source_url is suppressed rather than shown link-less. URLs are only ever the source_url Synorb returns - never invented.

Questions builders ask.

Will this show real live data on the first run?

Yes. The build prompt connects Synorb at build time to learn the real data shape, then wires live Synorb data into the running product. A live, always-on public site where anyone can browse this week's podcasts, read the takeaways, expand the structured claims, filter by show/topic/person/company, and jump to the real episode - refreshed on a cron and, if you want, delivered to your inbox every week - all cited, none invented.

Where do my Synorb credentials go?

Only where they are safe. INFRA-BACKED, hosted Replit deployment. BUILD-TIME: optionally connect the Synorb MCP as an Agent tool so the build inspects real audio manifests (media_format=audio) and builds the Brief+Signals UI against the true shape. RUNTIME: the app's server calls Synorb's REST API for the last 7 days of audio manifests (media_format=audio) plus any active filters (tag_names for topic/entity, source channel for the show), reading the Synorb API key + secret from Replit Secrets - never in client code - and caches into Postgres so the site is fast. A Replit Scheduled Deployment refreshes on the chosen cadence and (optionally) emails a weekly digest. Credentials: Synorb is a real API and is THE data source - do not substitute another provider; I'll provide the key or you can ask me; Synorb Connect returns api_key, api_secret, and mcp_token.

How are sources shown?

Provenance is the product. Every episode card - and every row in the weekly email - carries a 'Listen to the episode' / source-domain link built from the real source_url Synorb returns, plus the show name (source channel) and episode date. Each expanded Signal claim and the Brief cite the same episode; a card with no source_url is suppressed rather than shown link-less. URLs are only ever the source_url Synorb returns - never invented.

Is this just a Synorb feed, or a real app?

A real app. Synorb is the cited data core; it also composes the platform's own tools: Replit Scheduled Deployments (cron) - refresh the feed daily/weekly AND send an optional weekly email digest, unattended, Replit Secrets - store the Synorb api-key + secret server-side, never in client code, Replit Postgres / built-in DB - cache the week's episodes so the site is instant, A browse/filter UI (combinable filters for podcast, topic, entity, significance - options populated from the week's real data), A small 'most-active podcasts this week' chart from the real data, Email delivery (Resend/SMTP) for the optional weekly digest of top episodes, Replit Object Storage - optional generated hero art so it reads like a publication.

What will it ask me before building?

A few plain-English questions, each with a smart default so you can just say 'you pick': Which podcasts should the feed cover?; How should each episode show up - readable takeaways first, the structured claims first, or both side by side?; Pick a look: Editorial (magazine, serif, warm), Terminal (dark, dense, data-room), or Minimal (clean, lots of whitespace).; Should I also email you a weekly digest, and how often should the site refresh?.

Using a different agent?

The same Synorb MCP connects to every major coding agent. Pick yours.

Free credentials. No card.

Generate credentials, connect Replit, and ship something with live, cited intelligence.