domain: docs.mux.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a live stream via the Mux API as normal; the response includes a whip_url field when the stream supports WebRTC ingest.
Use any WHIP-compatible client (browser SDK, OBS with WHIP output, GStreamer whipsink) and set the WHIP endpoint URL to the whip_url value.
Pass authentication as required by the WHIP endpoint — Mux uses the stream key embedded in the URL or as a bearer token, per their current WHIP implementation; verify exact auth mechanism in the Mux WHIP docs.
The WHIP client performs an HTTP POST with an SDP offer; the server responds with an SDP answer completing the WebRTC handshake.
Monitor stream status via Mux webhooks (video.live_stream.active) to confirm the WebRTC session is producing media.
Viewers receive LL-HLS output; WHIP is an ingest-only protocol and does not affect the egress path.
Known gotchas
WHIP support on Mux is subject to change; always check the current Mux docs for whip_url availability on your account tier.
WebRTC NAT traversal may require TURN server configuration on the sending client; Mux handles the server side.
WHIP connections are stateless HTTP — if the WebRTC connection drops, the client must re-POST to re-establish.
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?