Skip to main content
You don’t have to switch models to start using Omnia. Store your existing provider key, point your traffic at the gateway, and keep calling the exact closed model you run today, while every request gains logging, grades, calibrated judges, and canary-gate eligibility.

​
Setup

  1. API Keys → Provider keys (also under Settings → Workspace): pick the provider, paste your API key. It’s encrypted at rest and write-only: after saving, only the key’s prefix is ever shown again, to anyone.
  2. Point your SDK at the gateway and prefix the model with the provider:
The request body is unchanged from what you send today; streaming, tools, everything. Your provider key never appears in any request; the gateway attaches it server-side.

​
Supported providers

Any model id the vendor offers works; new launches work day one. (Bedrock and Vertex use cloud credentials rather than a single API key and aren’t supported this way.)

​
Billing

Your provider bills your key directly — Omnia charges nothing for these tokens. Telemetry and logs still record full usage. Judging and evals you run over this traffic bill as normal Omnia usage, like any judging.

​
When your key stops working

A rotated or revoked provider key returns 401 with code provider_key_rejected and a message telling you where to update it, never a generic upstream error. Fix it on the API Keys page (or Settings → Workspace); a saved or deleted key takes effect at the gateway within seconds.

​
From BYOK to a cheaper model

Once your closed-model traffic flows through the gateway, validated evals can measure it against your own quality bar, and when an open-weights model from the catalog clears that bar at a fraction of the price, a quality-gated canary proves it on a live split and moves you over, with auto-rollback if it’s ever wrong. Same traffic, same judges, and a measured, interval-backed comparison at every step.