Omni API
Omni API Docs

Models

Model groups, task types, and public readiness rules.

Models

The public catalog only lists model groups that are ready for real traffic. Model groups can share the same worker platform while keeping independent queue, scaling, pricing, and task schema rules.

Categories

Category Current status
Image Omni Image AIO is visible and ready.
Video Omni Video AIO is visible and ready.
Multi Omni Multi AIO is visible and ready for mixed media tasks.
Audio Standalone audio groups remain hidden until runtime and frontend are ready.
VLLM Standalone VLLM groups remain hidden until model selection and text protocol are ready.

Omni Image AIO

Image tasks cover single image editing, local inpaint through the website wrapper, and multi-image-compatible API shape for future models. The public API exposes supported task types only; website-only wrappers can stay hidden from API users.

Omni Video AIO

Video tasks cover text-to-video, image-to-video, first-last-frame video, and video-to-video. Video extend is treated as video-to-video naming compatibility.

Omni Multi AIO

Omni Multi AIO runs mixed media tasks on a shared runtime that maintains multiple model groups. Current task types are:

  • image_upscale for image upscaling.
  • audio_transcribe for speech-to-text transcription.
  • voice_clone_tts for voice clone text-to-speech.
  • vlm_chat for image-aware text responses.
  • talk2prompt for audio transcription followed by VLM prompt generation.
  • voice_translate for ASR, VLM translation, and voice-clone TTS in one task.

Text and JSON outputs are stored directly in the task result. Image and audio outputs use the normal signed R2 output contract. The runtime executes one task per warm worker slot and uses standard proxy environment variables when needed.

Readiness requirements

A model group should not be public until these are true:

  • Worker warmup completes before accepting tasks.
  • Segmented timing logs are available for download, inference, upload, and total runtime.
  • Queue and scaling limits are configured.
  • Pricing and credit deduction rules are defined.
  • At least one smoke task has passed in the current release candidate.