podcastapi.com valid

PodcastAPI.com

The Listen Notes Podcast API provides podcast and episode search, directory metadata, discovery, playlist curation as a headless CMS, and audience insights for server-side applications and agents.

For agents: Listen Notes Podcast API for podcast and episode search, directory metadata, playlists and audience insights, with an agent reference and API catalog.

podcast apipodcast searchepisode metadataaudience insightslisten notes

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-22T13:59:07.661Z. Cached copy · Source on podcastapi.com

# PodcastAPI.com

> The Listen Notes Podcast API provides podcast and episode search, directory metadata, discovery, playlist curation as a headless CMS, and audience insights for server-side applications and agents.

API version: 2.0
Production base URL: https://listen-api.listennotes.com/api/v2
Mock base URL: https://listen-api-test.listennotes.com/api/v2

## Start Here

- [Get API keys](https://www.listennotes.com/api/pricing/)
- [API documentation](https://www.listennotes.com/api/docs/)
- [Complete agent reference](https://www.podcastapi.com/llms-full.txt)
- [API catalog](https://www.podcastapi.com/.well-known/api-catalog)
- [API discovery index](https://www.podcastapi.com/apis.json)
- [OpenAPI YAML](https://listen-api.listennotes.com/api/v2/openapi.yaml)
- [Agent Skill](https://github.com/PodcastAPI/skills)

## No-Code Listen Notes Tools

The Podcast API is designed for building interactive podcast apps, agents, and workflows that need programmatic podcast data, but it is not always the right fit for every use case. Listen Notes also provides no-code tools that people can use immediately:

- Free podcast search engine: search podcasts and episodes on the web, similar to using Google, with filters to narrow results efficiently.
- Batch CSV exports: specify podcast or episode conditions and receive a CSV file on demand, typically within 1 minute. No subscription is required; pricing is usage-based.
- [Listen Notes complete product reference](https://www.listennotes.com/llms-full.txt)
- Prompt: `Read from https://www.listennotes.com/llms-full.txt so I can ask questions about no-code Listen Notes tools and other product offerings.`

## Authentication and Safety

- Keep `LISTEN_API_KEY` in a trusted backend or serverless secret store.
- Send it in the `X-ListenAPI-Key` header to production.
- Never expose a production key in browser code, mobile binaries, URLs, logs, or source control.
- Use the mock base URL without a key only for transport and response-shape tests; its data is fixed and fake. Playlist writes do not persist there.
- Handle successful `200` and `201` responses, plus `400`, `401`, `403`, `404`, `429`, network failures, and `5xx` responses explicitly. A `401` can also indicate a plan or private-playlist access restriction.
- Only playlists owned by your admin API account can be modified. Authenticate and authorize your app's editors before forwarding writes.
- Follow response-provided pagination cursors and set an application-level page or item bound.

## Rate Limits and 429 Retries

- Listen API rate limits vary by endpoint, plan, and account history. FREE has the lowest limits, PRO has higher limits, and ENTERPRISE has the highest limits; compute-intensive endpoints may be more restrictive. Do not hard-code one global requests-per-second assumption. See the [rate-limit FAQ](https://www.listennotes.com/api/faq/#faq17).
- Control concurrency, pace requests, batch work when an endpoint supports it, and avoid tight polling loops.
- T
…

Related sites

Other listed sites in Media. See the whole category →

Machine-readable: GET /v1/resolve?q=podcastapi.com · GET /v1/domain/podcastapi.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for podcastapi.com:
1. POST https://agentwebmap.com/v1/sites/podcastapi.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://podcastapi.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/podcastapi.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/podcastapi.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.