Declare the Podcasting 2.0 namespace in your RSS feed: add 'xmlns:podcast="https://podcastindex.org/namespace/1.0"' to the 'rss' root element — clients should support alternate prefixes but 'podcast' is the canonical suggestion
Add the 'podcast:funding' tag at channel or item level to link to a donation or membership page: '<podcast:funding url="https://example.com/donate">Support the Show</podcast:funding>' — the tag text is the call-to-action label displayed in supporting apps
Link to a JSON chapters file for each episode using the 'podcast:chapters' tag inside the 'item': '<podcast:chapters url="https://example.com/ep1/chapters.json" type="application/json+chapters" />' — this references an external file and does not embed chapter data in the feed
Link to transcript files using one or more 'podcast:transcript' tags inside each 'item': the 'url' attribute points to the transcript file, the 'type' attribute specifies the MIME type ('text/vtt', 'application/json', 'application/x-subrip', or 'text/plain'), and the optional 'language' attribute carries a BCP-47 language code
Multiple 'podcast:transcript' tags per episode are allowed and encouraged — provide VTT for in-player display and SRT or plain text for accessibility tools
Test your feed in Podcast Index (podcastindex.org) and Podverse or Castamatic — these are among the most comprehensive Podcasting 2.0 client implementations and will display chapters, transcripts, and funding buttons if tags are valid
Known gotchas
The 'podcast:chapters' tag points to an external JSON file, not inline data — the JSON file must be publicly accessible and return 'Content-Type: application/json'
Not all podcast apps support Podcasting 2.0 tags — traditional apps like Apple Podcasts have partial or no support, so these tags supplement rather than replace standard iTunes namespace tags
The 'podcast:transcript' type attribute is required and must match the actual file format — using 'text/vtt' for an SRT file will cause apps to fail parsing the transcript
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp