API documentation — Omnia Model Hub
Point an OpenAI-compatible client at the Omnia base URL and use your platform API key.
Authentication
Send Authorization: Bearer <api_key>. Keys are shown once at creation and stored only as a SHA-256 hash. Keys can be revoked from the console or by an administrator.
Endpoints
POST /v1/chat/completions, POST /v1/responses, POST /v1/completions, POST /v1/embeddings, POST /v1/images/generations, POST /v1/video/generations, POST /v1/audio/transcriptions, POST /v1/batches and GET /v1/models.
Provider routing object
The provider object supports order, only, ignore, allow_fallbacks, sort, data_collection, zdr, require_parameters, quantizations, max_price, preferred_min_throughput, preferred_max_latency, enforce_distillable_text and ignore_performance. Unknown fields are rejected rather than ignored.
Example request
POST /v1/chat/completions with model, messages and an optional provider object. The response contains standard choices and usage fields plus an omnia object with the chosen resource, fee rate, subtotal, platform fee, auxiliary charge, total and route reason.
Recomputable bills
Every response includes a bill identifier. GET /api/user/bills/<id> returns the bill header, all line items and the settlement split between invite credit and service credit.