How will you prevent your service from being used to flood the world with worthless algorithmically generated slop?
As the prices decrease, due to model improvement, best/worst practice guides, and promotion of successful use cases may act as an additional mechanism to prevent such cases.
Realistically though, given that we’re lowering the bar of podcast creation to effectively the level of blog creation there might be an increase in slop content. I think that’s a necessary problem when you lower the barrier, but there will always be proper curation in the aggregator level. I think HM is the perfect example. Internet has made blogging so easy and there is so much slop. But it goes unnoticed given the curation.
If the creator can't be bothered to read the script, it would be a waste of time for anybody else to listen to it.
It's not that the creator can't be bothered, but that the tool unlocks features that are just not feasible for a creator. Think of Hacker News Recap for example - a 20' episode has been generated every single day for the past 122 days. That's extremely hard for a person to do. So the consistency that this enables is one feature.
Automatic translation and video generation are other features that using this method of podcast creation lead to. So it's not necessarily that the "creator can't be bothered to"... there's inherently more value in some use cases to create a podcast this way over the traditional method.