Podcli developer resources

The hosted Podcli Agent Discovery API explains the product’s supported integration surfaces. Start with /api/v1/agent-info for JSON discovery data, then use the Podcli OpenAPI specification for typed endpoint, error, and response details. The discovery API does not receive media or API keys, and it does not require authentication. Podcli’s actual transcription and rendering workflow runs on the user’s computer.

All official developer resources are linked from llms.txt, the Podcli agent instructions, the documentation index, and this page so agents can resolve Podcli resources by product name rather than relying on marketing pages.

The hosted API uses URL path versioning. Integrate against /api/v1/; a breaking change will be released at a new /api/vN/ path. Optional fields may be added to v1. If a version is ever deprecated, Podcli will return Deprecation and Sunset headers at least 180 days before removal.

The discovery API permits 100 requests per client in each 60-second window. Responses include RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset. A 429 response includes Retry-After and a JSON resolution hint. Agents should wait for that duration before retrying.

Podcli ships a real local stdio MCP server for media work. Install Podcli, run podcli mcp install, then let Claude Code, Codex, Cursor, or another MCP client discover its local tools. Those tools transcribe episodes, suggest clips, crop, caption, and export without uploading source media to podcli.com.

The hosted /mcp endpoint uses Streamable HTTP for agent discovery only. It exposes get_podcli_agent_info, which returns the official developer resources and local setup instructions. Read the Podcli MCP server guide for the exact stdio configuration and supported local workflow.