Working with Video API
These are engineering operations rather than generative models. The family covers subtitle burn-in for silent-autoplay feeds, ABR and HLS ladder packaging for adaptive streaming, tracked reframing that follows the subject into vertical and square crops, hover-preview sprite sheets with a WebVTT index, and structured audio metrics as JSON.
When to choose Video API
Use the Video API when the output must be exact and repeatable — encoding, packaging, captions, crops. Generative video lives in the model families from Kling, Veo, PixVerse and the rest.
Choosing between the variants
Pick by the job: burn-in for permanent captions, ABR or HLS Ladder for streaming delivery, Tracked Reframe for aspect-ratio changes that must follow the action, Hover Preview Sprites for player scrubbing, and Audio Analyzer for loudness and peak checks.
About Video API
- Are these operations generative?
- No. They are deterministic video operations, so the same input and settings produce the same output every time.
- What does Tracked Reframe do that a plain crop does not?
- It follows the subject as it moves, keeping the action centred when a landscape video is re-cropped to vertical or square.
- What is an ABR ladder?
- A set of renditions at different resolutions and bitrates, packaged so a player can switch between them as the viewer's bandwidth changes.