AI inference.
On your terms.Quality first.
Cost controlled.

o10 is the control plane for inference spend. It routes every AI inference call to the cheapest model that clears your quality floor, across unified inference gateway, OpenRouter, Amazon Bedrock, and owned capacity. Shadow mode proves savings without changing production; enforce mode holds budget envelopes in the path. Evals define per-use-case quality floors; KYI governs the supply chain for board reporting; an immutable ledger records model, venue, and fully loaded cost on every call.

Shadow mode mirrors live traffic and shows what would have routed and saved, without changing production responses. Enforce mode places o10 in the request path and actively routes each call to the cheapest eval-passing model within your budget envelope. Teams always start in shadow to build a verified per-use-case baseline; finance signs off before enforce flips. Both modes write to the immutable ledger; only enforce changes spend.

Savings depend on the current route, task distribution, acceptance criteria, and candidate endpoint costs. The website calculator is illustrative. Compare your baseline with evaluated alternatives and include shadow evaluation, routing, retries, and tool charges before reporting a saving.

Know Your Inference (KYI) is a governance framework by o10 that scores inference systems across five weighted pillars: Performance (25%), Economics (25%), Integration (20%), Strategy (20%), and Risk (10%). Each pillar scores 0–100; the composite rolls into a confidence level and board-signable recommendation. KYI runs continuously in the o10 control plane, not as a one-off audit. So every routed call and eval updates the score. A composite floor of 65 triggers enforcement levers: cap, rightsizing, or sunset per policy.

A quality floor is the minimum eval score a model must achieve for a specific use case before o10 routes production traffic to it. Floors are per workload. Support, RAG, code, and batch clear at different bars, and measured by replaying representative traffic through eval suites, not assumed from vendor benchmarks. Once a cheaper candidate passes the floor, o10 can route to it in shadow (proof) or enforce (live). Floors without evals are hopes; evals without floors are expensive defaults.

o10 unifies routing across per-token API gateways (unified inference gateway), OpenRouter (multi-provider aggregator), Amazon Bedrock (per-token and committed capacity), and owned or open-weight infrastructure. A single control plane sits above all venues. You do not need separate dashboards per provider. o10 selects the cheapest eval-passing route per call and holds budget envelopes. Committed Bedrock drawdown and open-weight routing are first-class venues, not afterthoughts.

Savings are verified against your own shadow baseline per use case, not industry averages or vendor marketing claims. o10 mirrors a week or more of production traffic, segments by workload, and compares what you actually spent versus what you would have spent on the cheapest eval-passing route at the same quality floor. Finance signs off on the delta before enforce mode flips. Gainshare pricing ties o10 fees to this verified number, so savings must be real and auditable.

Start free at https://app.o10.io/signup. No card. Signup creates an org and issues a free o10 route key (o10_sk_…), shown once. Point your OpenAI-compatible client at https://app.o10.io/v1, set model to o10/auto (or another mode), and paste the free route key as the API key. Use a placeholder like $O10_ROUTE_KEY in docs. Copy your own key after signup; do not use a shared demo key. Shadow mode shows what you'd save before enforce.

Free is $0 with no card required. Free is bring-your-own provider keys (BYOK): you route on your own provider keys; o10 can run shadow receipts on live traffic. Paid plans add routed credits. Free does not include prepaid o10-hosted frontier credits.

Four modes. o10/auto. Default: cheapest model that clears the quality bar. o10/frontier. Value-first across frontier-class models (open-weight and proprietary); orgs can set a preferred frontier model. o10/squad. Multi-agent planner → workers → judge for hard multi-step work (typically 1–4 minutes). o10/pinned. Org-saved model override; if unavailable, falls back to auto with a visible notice. Base URL https://app.o10.io/v1. Concrete slugs and ! pin syntax also work per-request.

Frontier Tokens (model o10/frontier): value-first across frontier-class models, including open-weight (e.g. DeepSeek R1, GLM, Kimi) and proprietary (e.g. GPT-5.5, Claude Opus/Sonnet). Orgs can set a preferred frontier model. Status: beta / live for entitled accounts. Open https://app.o10.io/frontier after signup.

Squad (model o10/squad): multi-agent planner → workers → judge. For hard multi-step work. Latency is typically 1–4 minutes, not chat-speed. Status: beta / live. Open https://app.o10.io/squad.

Mention @o10 in Slack; answers are routed through o10 with receipts. Email path: ask@o10.io. Set up in the console under Settings → Integrations → Tag. Tag is available to connect or pilot. Marketplace listing may still lag; do not assume it is already on the Slack Marketplace.