Create a Livepeer Studio stream, retrieve its stream key/playback ID, and upload a VOD asset
domain: docs.livepeer.studio · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call POST https://livepeer.studio/api/stream with an API key in the Authorization header and a body containing at least a name field.
Read streamKey and playbackId from the response — streamKey is the secret used to broadcast (RTMP or WebRTC WHIP), playbackId is the public identifier safe to give viewers.
Broadcast via RTMP ingest, or via WebRTC WHIP for in-browser publishing, using the streamKey.
For VOD, call POST /api/asset/request-upload with the asset name to get back a direct-upload url (PUT) and a tusEndpoint for resumable/chunked upload, plus an asset object (id, playbackId, status).
Upload the file to either the direct url or the tus endpoint, then check the asset's status by id — processing is asynchronous, so the asset is not immediately playable right after upload.
Known gotchas
Never expose streamKey to viewers/clients — only playbackId is meant to be public; anyone with the streamKey can broadcast into your stream.
The tus (resumable) upload path is specifically recommended over the direct PUT url for unreliable/slow networks — the direct URL has no resume support if interrupted.
Asset processing after upload is async — poll/check asset status before serving its playbackId, rather than assuming it's ready immediately after the upload call returns.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?