Set up a podcast site that generates episode resources

A podcaster used Replit Agent to launch a site that turns new episodes into transcripts, tags, related links, and a guarded episode chat.

Done with Replit Agent· Intermediate

What they did
Across a weekend of back-and-forth, the podcaster explained the site they wanted and Replit Agent put it together and shipped it. The system pulls in episodes from the show’s RSS feed, sends audio to AWS Transcribe for transcription, and uses GPT-4o to label and analyze each episode. A smaller GPT-4o-mini model runs the chat feature, and its rules keep questions tied to the episode content; admins can also start transcript generation in batches.
How it went
The site is now live and produces transcripts, tags, related episodes, and chat after an episode is released. Switching from Whisper to AWS Transcribe lowered costs by 73% and increased the file ceiling to 2GB.
Tips
Keeping the chat narrowly focused is important if you want to avoid turning it into a general chatbot that can rack up costs. It also helps to test the RSS import and transcript flow with a few sample episodes before you publish widely.

Try it yourself with Replit Agent

I’m building a site for [podcast name]. When a new episode appears in the RSS feed, I want it to create a page with [transcript, tags, related episodes, and a chat limited to that episode]. Use [AWS Transcribe] for speech-to-text, [GPT-4o] to analyze the episode, and [GPT-4o-mini] for the episode chat. Include an admin action for bulk transcript jobs. First, use sample episodes to prove the workflow works, and pause for my approval before you deploy anything publicly or make irreversible changes.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

1 more report of this

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.