Video API Encoding and Editing Ops

The Video API family exposes deterministic video operations: subtitle burn-in, adaptive bitrate packaging, tracked reframing, sprite previews and audio metrics.

  • each::labs
  • 39 variants
  • From $0.00044 per processing second

More from each::labs.

A family groups the versions of one model line. Open one to compare its variants side by side.

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.

Questions about Video API

The short answers. For anything specific to your setup, talk to our team.

Talk to an engineerPlan for your expected volume.
  • No. They are deterministic video operations, so the same input and settings produce the same output every time.

Ready to close the gap?

Find the model. Build the workflow. Make it production-ready.