Overview
Build with Omni API model groups, tasks, credits, and webhooks.
Omni API documentation
Omni API exposes production image, video, audio, and multimodal model groups through one task API. Use the model catalog to choose a model group, upload input files through signed URLs, submit a task, and poll or open task details from Console.
Core flow
- Create an API key in Console.
- Fetch the public model catalog from
GET /api/omni/models. - Upload input files with signed upload URLs when the model requires files.
- Create a task with
POST /api/omni/tasks/create. - Poll
GET /api/omni/tasks/{portal_task_id}or use status batch endpoints. - When the task succeeds, call
GET /api/omni/tasks/{portal_task_id}/output-urlsto download file outputs, or read text and JSON outputs inline from the task.
Ready model groups
| Model group | Category | Status |
|---|---|---|
| Omni Image AIO | Image | Ready |
| Omni Video AIO | Video | Ready |
| Omni Multi AIO | Multi | Ready |
| MM Audio AIO | Audio | Ready |
Omni Multi AIO exposes image upscaling, audio transcription, voice-clone TTS, VLM chat, Talk to Prompt, and voice translation. MM Audio AIO exposes prompt-, image-, and video-conditioned sound generation. Always use the live catalog as the public capability source.
Console
Console contains task history, task details, credits, billing, payments, usage, and API keys. Anonymous visitors can browse model and pricing pages, but task submission and API usage require a signed-in account.
