Authenticate all requests by including your API key in the 'x-api-key' HTTP header — obtain the key from your Transistor account settings; the API follows the JSON:API specification and returns JSON-encoded responses
Create a new episode by POSTing to '/v1/episodes' with a JSON body containing at minimum 'show_id' (your podcast's Transistor show ID), 'title', and 'audio_url' or by uploading audio separately using the audio upload endpoint
To upload audio, POST to '/v1/episodes/{id}/audio_upload' with a multipart/form-data body containing the audio file — the endpoint returns an upload URL or accepts the file directly depending on your plan
Set episode metadata in the create or update call: 'summary' (plain text description), 'description' (HTML-formatted show notes), 'number' (episode number), 'season' (season number), 'type' ('full', 'trailer', or 'bonus'), and 'explicit' (boolean)
Publish the episode by sending PATCH to '/v1/episodes/{id}/publish' — this endpoint accepts a 'published_at' field for immediate publishing (leave empty) or a future ISO 8601 datetime for scheduled publishing; set to a past datetime to backdating
Retrieve episode status and published feed URL via GET '/v1/episodes/{id}' — the response includes 'status' ('draft' or 'published'), the public audio URL, and the episode's page URL on your Transistor site
Known gotchas
The Transistor API uses JSON:API conventions — request bodies must nest attributes inside a 'data.attributes' object and responses return data in the same nested structure, which differs from flat REST conventions
Publishing is a separate API call from episode creation — creating an episode leaves it as a draft; you must explicitly call the publish endpoint to make it live
Transistor's API rate limits are not publicly documented — implement exponential backoff for bulk operations such as migrating a large back-catalog
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