While a live input is active, use the Cloudflare Stream API to create a clip by calling the clip creation endpoint, specifying the live input ID along with startTimeSeconds and endTimeSeconds relative to the stream start.
Cloudflare Stream processes the clip asynchronously; poll the resulting video object's status field or use a webhook to detect when the clip transitions to ready.
Once ready, the clip is a standard Cloudflare Stream video asset with its own video ID and playback URL — use it for on-demand playback independently of the live stream.
For full VOD recording of the entire live session, ensure recording is enabled on the live input; Cloudflare Stream automatically creates a video asset from the recording when the stream ends.
Use the Cloudflare Stream API to list video assets associated with a live input UID to retrieve all clips and full recordings.
Apply Cloudflare signed URLs or token authentication to the VOD assets if the content should be access-controlled.
Known gotchas
Live clipping is only possible within the DVR window retained by Cloudflare Stream; clips requested outside the retention period will fail.
Clip creation is asynchronous; do not expect the clip to be immediately available for playback — build polling or webhook-based readiness checks into your workflow.
The exact API endpoint paths and parameter names for clipping may evolve; always verify against the current Cloudflare Stream API documentation rather than relying on cached examples.
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