PodcastNewsFeeds aggregates RSS news from any source you choose, lets you script the stories you want to cover, and exposes the result to your podcast pipeline as JSON. Built for daily news shows, briefings, and automated audio production.
One workspace for collecting, curating, and exporting the news you want on your show.
Group any number of RSS feeds under a single show. Articles from every source land in one queue you can curate from.
Triage articles as scripted, archived, or used. Build tomorrow's run-down without losing track of what you've already covered.
Headlines written for the page rarely read aloud well. One click rewrites a clickbait headline into clean, spoken English ready for your script.
Pull your scripted articles into any automation pipeline. Mark them used in one call so tomorrow's queue starts fresh.
Articles from Reddit are tagged on sight so you can fold them into discussion blocks separately or hide them entirely with a single toggle.
Every feed and queue is scoped to your account. No public sharing, no leakage, no surprises — just your news for your show.
The whole pipeline takes minutes to set up and seconds per day to run.
Make a feed for each podcast. Add any RSS sources you want to pull from — news sites, blogs, Reddit, Substacks, anywhere with a feed URL.
Open the article list, mark the stories you want to cover as scripted, archive the noise. Rewrite titles for spoken delivery when you need to.
Hit /api/get_scripted from your recording rig or automation. When you're done, /api/move_to_used resets the queue for tomorrow.
Whether you're hosting solo or running a fully automated pipeline.
Curate ten headlines, hit the API, record. No spreadsheet, no copy-paste, no “wait what was that story I wanted to cover”.
Pull scripted articles into a TTS pipeline, generate audio, push the resulting MP3 to AudioRSS or your own host. The whole loop runs unattended.
Producer triages stories from a browser, hosts read off the queue. The article list is the run-down.
Run a tech podcast and a markets briefing? Each show is its own feed with its own RSS sources, queue, and API token.
You add RSS source URLs to each feed. A separate ingest job (run on your schedule) pulls those sources and populates the article table. The web UI is the curation surface; the API is the consumption surface.
It's the curated set of articles you intend to cover. The API endpoint /api/get_scripted returns exactly that set, and /api/move_to_used empties it so the next day's curation starts clean.
Yes. The alternate title field is editable on every scripted article. The AI rewrite button is just a one-click way to get a first draft; you can overwrite whatever it produces.
Yes. Feeds, articles, and the scripted queue are scoped to your account. There is no public sharing, no third-party analytics, and no leakage to other users.
AudioRSS hosts the podcast RSS feed you publish. PodcastNewsFeeds is the input side: it tells you what to record. They pair well — pull from PodcastNewsFeeds, record, publish through AudioRSS.
Not today. The service is free to use; the AI title rewrite consumes a small amount of API budget per call.
Create a free account, add an RSS source, and have a scripted queue running in under five minutes.