Skip to content
OmnAPI Docs

Introduction

OmnAPI is a unified gateway over multiple AI services — music, lyrics, image and music-video generation. You issue a single API key and call a single base URL; the gateway handles provider routing, retries, account pooling, rate limiting, credit accounting and async job orchestration.

When to use OmnAPI

Section titled “When to use OmnAPI”
  • You want one auth surface across multiple AI providers.
  • You need async jobs with consistent polling semantics across providers.
  • You want per-tenant rate limits and predictable credit accounting.
  • You want the same interactive playground you read in these docs to drive real requests with your key.

When not to use OmnAPI

Section titled “When not to use OmnAPI”
  • You only need a single provider and want the absolute lowest latency — call them directly.
  • You need streaming protocols not yet bridged (track /changelog/ for streaming support).

Architecture in one diagram

Section titled “Architecture in one diagram”
You ──[x-api-key]──► api.omnapi.com ──► Provider accounts (pooled)
                          │
                          └─► Async job queue (poll /jobs/:id until terminal state)

Where to go next

Section titled “Where to go next”