Listen Notes
DATA · DATA & ANALYTICS
Podcast and episode search, curated lists, and show metadata on their own key.
Connecting Listen Notes in practice
The Listen Notes free tier is 150 requests a month, not per minute, and search is separately capped at 2 requests a second and 20 a minute on both Free and Pro, so the podcast search an agent most wants to run is the one with the tightest ceiling. Paid usage is billed per thousand requests above the included 5,000, which means a retry loop costs money instead of failing.
Scopes that draw scrutiny
X-ListenAPI-KeyThe single API key header. There are no scopes; the key identifies the plan, which is what determines both the quota and the rate limit.
Rate limits
- FREE: 150 requests per month.
- PRO: from $200/month including 5,000 requests, then $1.60 per 1,000 up to 1M, $1.30 per 1,000 to 5M, and $1.10 per 1,000 above that.
- GET /search: 2 requests per second and 20 requests per minute on both FREE and PRO.
- Other endpoints get a medium rate limit on PRO and a high one on ENTERPRISE, with no published figures.
Worth knowing
- There is a keyless mock host, https://listen-api-test.listennotes.com/api/v2, which needs no API key — so tests pass against canned data that is not the account’s, and a misconfigured base URL fails silently rather than 401ing.
- Overage is metered per 1,000 requests rather than blocked, so on PRO an agent that retries aggressively runs up the bill instead of hitting a wall.
- The monthly free quota does not smooth out: there is no burst allowance and no per-minute headroom to borrow against 150 calls a month.
- The production host is listen-api.listennotes.com, not the www site the docs are served from.
Checked against Listen Notes API docs (2026-09-29), Listen Notes API pricing (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Listen Notes behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.