each::labs | Video API | Multi-capability video editing.
- eachlabs
- AI Models
- $0.0015 per processing second
- ~5 sec ortalama
EACHLABS Video API - the easiest way for an AI agent or developer to edit video.
each::labs | Video API | Multi-capability video editing neyde iyi?
En uygun kullanımNerede işe yarar
each::labs Video API is useful when this specific operation fits between source preparation and delivery. These scenarios show how it can support different…
Sınırlar ve ipuçlarıİyi sonuç almak için
Keep an untouched source file and verify its duration, dimensions and streams before choosing edit settings. Make one small representative request, inspect the…
İlgili modelView modelMureka | Describe Song
Çıktıyı, hızı ve fiyatı karşılaştırmak için aynı girdiyle çalıştırın.
Model dokümantasyonu
Bu model hakkında
EACHLABS Video API - the easiest way for an AI agent or developer to edit video. 44 curated operations: editing (trim, segment, concat, crossfade, speed, reframe), encoding (transcode, scale, gif), audio (extract_audio, loudnorm, audio_replace, audio_master), captions (captions, subtitle_compose), analysis (probe, scene_detect, silence_detect), streaming (hls_ladder, package_abr) - plus a raw ffmpeg escape hatch (mode=run_ffmpeg with an argv array, argv[0]=ffmpeg). Inputs are media URLs (input_url / input_urls); outputs land on the EACHLABS CDN. Billed $0.0015 per compute-second; every job includes 200 MB of output delivery free, then $0.30/GB. mode=capability with capability+params is the recommended path.
Overview
each::labs Video API Overview
each::labs Video API processes media through named editing, encoding, audio, captioning, analysis and streaming capabilities, with a separate raw-argument mode.
The preferred interface selects capability mode with a capability name and a params object; raw argument mode is separate.
each::labs Video API is available through each::labs in the each-tools family.
mode: capability: run one of 45 curated operations chosen via capability + params (default, recommended). capability: The operation to run when mode=capability (each documents its own params schema).
Use the each::labs Video API API when you need this transformation or analysis as a repeatable step in an application or creative pipeline. The sections below distinguish the required material, adjustable controls and checks that matter before delivery.
Capabilities
Capabilities
- The preferred interface selects capability mode with a capability name and a params object; raw argument mode is separate.
- mode: capability: run one of 45 curated operations chosen via capability + params (default, recommended).
- capability: The operation to run when mode=capability (each documents its own params schema).
- input_url: Source video/audio to process.
- Produces a video result for the next stage of your workflow.
Use cases
Use Cases for each::labs Video API
each::labs Video API is useful when this specific operation fits between source preparation and delivery. These scenarios show how it can support different parts of a working pipeline.
Creators
Build a multi-step editing tool. Use a representative source or a concise brief, then inspect the result before preparing a larger set of assets.
Design and marketing teams
Transcode and resize media programmatically. Compare the result with the intended message, composition and destination. Keep reviewable versions of the source and output.
Developers
Add analysis or packaging to an application pipeline. Inspect the actual returned value before connecting it to another step, and keep the chosen request settings with the result.
Start with a clear definition of the desired result and use the exposed controls to reach it. Keep any additional generation, editing or application logic in separate steps so that the effect of this operation remains easy to review.
Tips & tricks
Tips and Tricks
Keep an untouched source file and verify its duration, dimensions and streams before choosing edit settings. Make one small representative request, inspect the returned asset, and use the same settings only when they fit the remaining material.
- capability: The operation to run when mode=capability (each documents its own params schema).
- input_url: Source video/audio to process.
Set the named operation controls directly. This entry has no general creative-prompt interface; supplying an invented prompt field will not replace a required source or numeric setting.
Compare one deliberate adjustment at a time. Inspect the part of the result affected by that change, then check the rest of the asset or response for unwanted side effects before reusing the settings.
Technical spec
Technical Specifications
- Result type: video.
- Required fields: mode-dependent inputs.
- output_format: string; options mp4, webm, mkv, mov, gif, mp3, wav, m4a, jpg, png, vtt, hls, dash; default "mp4".
- mode: string; options capability, run_ffmpeg; default "capability".
- capability: string; options transcode, trim, segment, thumbnails, scale, extract_audio, gif, watermark, concat, concat_copy, crossfade, rotate, crop, pad, reframe, reframe_track, speed, volume, loudnorm, reverse, fade, color, lut3d, stills, poster, captions, subtitle_compose, title_card, overlay, sticker_overlay, audio_replace, audio_duck, audio_master, audio_analysis, probe, scene_detect, silence_detect, silence_remove, keep_ranges, silence_split, slideshow, storyboard_sprites, hls_ladder, package_abr, package_abr_ladder; default "transcode".
- input_url: string.
Values must use the types and accepted options listed in the parameter reference. A displayed default does not remove a required-field requirement. Choose a supported output setting for this entry rather than borrowing a preset from a related model.
Things to be aware of
Things to Be Aware Of
Check the processed asset in the actual destination player or editor. Review the opening, closing, sound, crop and any transition points relevant to this operation instead of assuming a successful job proves the edit is correct.
Optional settings are not necessarily interchangeable with those on another entry in the same family. Use the accepted names, types and values shown for this operation.
Check the returned content against the original input and your application requirements. A successful request means the operation completed; your application still needs to verify that the response is suitable for the next step.
Key considerations
Key Considerations
Capabilities have their own option schemas, so the outer catalog is not a complete reference for every operation. Use the selected operation's documented parameters.
Public estimate: $0.0015 per processing second.
Prepare mode-dependent inputs before starting. Optional settings include mode, capability, input_url. Keep these settings aligned with the intended delivery, especially when a later step expects a particular type or format.
Run a representative request before scaling to a larger collection. Judge the result against the source and the brief, and account for all generated outputs or usage-sensitive options when estimating a batch.
Limitations
Limitations
- mode: allowed values: ["capability", "run_ffmpeg"].
- capability: allowed values: ["transcode", "trim", "segment", "thumbnails", "scale", "extract_audio", "gif", "watermark", "concat", "concat_copy", "crossfade", "rotate", "crop", "pad", "reframe", "reframe_track", "speed", "volume", "loudnorm", "reverse", "fade", "color", "lut3d", "stills", "poster", "captions", "subtitle_compose", "title_card", "overlay", "sticker_overlay", "audio_replace", "audio_duck", "audio_master", "audio_analysis", "probe", "scene_detect", "silence_detect", "silence_remove", "keep_ranges", "silence_split", "slideshow", "storyboard_sprites", "hls_ladder", "package_abr", "package_abr_ladder"].
Unsupported parameters do not establish additional capabilities. Source quality and the chosen settings constrain what a processing step can deliver. Keep the source and check the result before replacing a final asset.