Skip to main content
Omnia measures whether your AI is actually good. You capture your production LLM traffic, grade a slice of it, and Omnia calibrates LLM judges against your grades, so every number downstream (pass rates, model comparisons, canary verdicts) is corrected for the judge’s measured error and reported with a confidence interval. On that foundation, model changes become safe to ship: comparisons run on your own prompts, quality-gated canaries promote a new model only when live traffic proves it, and a model trained on your traffic is yours to run anywhere. The measurement runs on infrastructure you already know. Omnia’s gateway is an OpenAI-compatible inference API: if your code already talks to OpenAI, point it at Omnia’s base URL and change the key; request shapes, streaming, and tool calls stay the same. Routing through it adds one API across many open models, caching, fallbacks, and dedicated GPU capacity — but routing is only one of four integration paths, and two of them capture traffic without moving your inference at all. See How Omnia works.

​
Base URL

One host serves everything:
Inference (chat, embeddings, rerank, responses, models) and management (labels, criteria, evals, aliases, logs, traces, dedicated endpoints, fine-tuning) live under the same base URL. Requests to the older management base https://platform.omnia-voice.com/api/v1 keep working; it’s an alias, not a migration. Everything authenticates with the same workspace API key (Authorization: Bearer sk_sovereign_...). Create one in the dashboard under API keys.

​
Your first request

The response is the standard OpenAI chat-completion shape, and the usage object reflects the exact tokens deducted from your wallet. See the Quickstart for the SDK equivalents.

​
Start here

How Omnia works

The workflow end to end: capture, measure, improve, own.

Quickstart

From an API key to your first response in a few minutes.

Authentication

How keys work, the sk_sovereign_ format, and scoping.

API reference

Every endpoint and field, interactive, generated from the API.

The gateway

How a request is authenticated, routed, metered, and settled.

​
Measure and improve

Grade your traffic

Record pass/fail verdicts on real traffic: the ground truth every judge is measured against.

Judges & calibration

Calibrate every judge against your grades: TPR, TNR, Cohen’s κ, and a trust badge derived from confidence intervals.

Comparisons

Test whether a cheaper model holds up on your own prompts, with pass rates corrected for the judge’s measured error.

Self-improvement

Use a calibrated judge as a training reward, and prove the result on held-out grades.

​
Run at scale

Inference

Chat, streaming, tool calling, structured output, embeddings, and vision, all OpenAI-compatible.

Dedicated endpoints

Reserve private GPU capacity for a model, billed per GPU-hour while running instead of per token.

Fine-tuning

Train a model on your own data, then serve it on a dedicated endpoint and call it like any other model.

Billing

Prepaid wallet, per-token and per-GPU-hour metering, holds, and auto-reload.

​
How a request flows

Your app talks to Omnia exactly like it talks to OpenAI. Behind the endpoint, Omnia authenticates the key to a workspace, routes the request to the model across multiple clouds, meters the exact usage, and settles it against your wallet in real time.