Can I find episodes by topic or person with the Listen Notes API?

Yes. GET /search supports full-text search across podcasts and episodes with q for the query, type to scope to podcast or episode, and filters for language, country, and length. GET /search_episode_titles narrows search to episode titles only when that's a better match for the use case.

What are the rate limits for the Listen Notes API?

Rate limits are tiered by plan. Free tiers are tightly throttled (suitable for development) while paid plans provide thousands of monthly requests with higher per-second limits. Agents should cache podcast metadata by id rather than re-fetching for repeated queries.

How do I search podcasts through Jentic?

Run pip install jentic, then search for 'search podcasts on a topic'. Jentic returns GET /search. Load the schema, supply q=<topic>, type=podcast, and any filters, and execute. Iterate by calling GET /podcasts/{id} for full metadata on the top hits.

Does Listen Notes expose audience demographics?

Yes, on supporting plans. GET /podcasts/{id}/audience returns audience demographic signals for the requested podcast id, useful for ad-inventory analysis and editorial sizing. Pair it with GET /podcasts/{id}/recommendations to surface comparable shows.

Can I limit what my agent is allowed to do with the Listen Notes API?

Yes. Because you run your own self-hosted Jentic One instance, your rules decide which Listen Notes operations and credentials the agent may use. Since the podcast or episode id sits in the URL path on calls like GET /podcasts/{id}, GET /episodes/{id}, GET /podcasts/{id}/recommendations, and GET /podcasts/{id}/audience, you can pin the agent to reads for a specific show, such as its recommendations or audience insights. Every operation in this API is a read, so the agent retrieves directory and insights data and performs no writes.