Model discovery
One catalog across every registered provider, with priced routes, capability badges, and immutable manifest revisions.
OpenRouter-compatible control plane
Discover provider endpoints, govern keys and budgets, and settle every generation to the exact decimal — behind one OpenAI-compatible API.
OpenAI-compatible
Chat, images, audio, streaming
Exact decimal
Double-entry ledger accounting
Iroh + HTTPS
Provider transports with health
Metadata-first
Retention and ZDR routing controls
The workspace
Catalog, credentials, accounting, provider health, privacy, and administration share one account-aware surface — no separate consoles, no approximated numbers.
One catalog across every registered provider, with priced routes, capability badges, and immutable manifest revisions.
Scoped inference and management credentials with exact spend limits, reset windows, and per-key traffic policy.
Every generation is gateway-measured, priced against immutable revisions, and settled in one balanced journal.
Health, capacity, route exclusions, and earnings for Iroh and HTTPS endpoints, refreshed as attempts complete.
Metadata-only retention by default, zero-retention endpoint eligibility, and region-aware routing preferences.
Provider review, incident suspension, and least-privilege investigations with a complete audit trail.
Drop-in compatible
The client surface speaks the OpenRouter profile of the OpenAI API — streaming, tools, images, audio, usage, and exact cost metadata included. Change the base URL, key, and model; keep the rest of your stack.
curl https://api.omni.nocean.xyz/api/v1/chat/completions \
-H "Authorization: Bearer $ROUTER_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "router/model",
"messages": [{ "role": "user", "content": "Route this." }],
"stream": true
}'Routing you can inspect
Route decisions, provider attempts, and settlement journals are immutable evidence. A generation page shows exactly which endpoint served it, what it cost, and why.
Route trace
Settled01
Every request narrows the catalog by capability, price, regions, and data policy before a route is considered.
02
Latency, throughput, failures, and queue depth roll up per endpoint, never penalizing a model globally.
03
The selected route binds immutable price and fee revisions, so the quote you routed with is the bill you get.
Create a key, fund exact usage, and watch every routed generation account for itself.