The router

One address, two APIs, and for every request one decision: which class, which axis, which model. The box does no inference itself; it routes.

The CoeOS box is the router of CoeOS, and the single way out of an instance. It speaks the OpenAI and Anthropic APIs. For each request it reads the class, picks a competence axis, looks up the model bound to that axis, and relays the call to the provider that hosts it: a cloud endpoint, or an OdyssAI-X engine on your premises. In a managed instance, we run and update the box for you.

The concepts

Term	What it is
Class	open or confidential, from the x-coeos-class header. Missing = confidential.
Competence axis	A benchmarked category of work: python, debug, legal_rgpd, creative, plan_spec, reasoning, agent_exec, voice and the rest of the 18 routing axes.
Setting	The routing table for open work: which model serves each axis, the default axis and the decider. Settings are published by TMB (catalogue eco, full, eu…); the box pulls the catalogue and the administrator enables one.
Local table	The routing table for confidential work, composed in the box from safe models only.
Provider	Who hosts a model: a cloud provider (OpenRouter, a European provider under DPA…) or your own engine. Each provider is declared with its safety: safe or not, local or ZDR/DPA.

How the axis is chosen

1. An explicit x-coeos-axis: <axis> header. The client knows what it is doing; the box obeys.
2. Otherwise the decider, a small decision model that classifies the request. For confidential work, the decider is itself a safe model.
3. Otherwise the default axis of the setting.

In a conversation where tools are used, the axis chosen on the first call is kept for the whole loop.

When a model fails

• Open: the box retries the step on another provider or another model — the fallback cascade.
• Confidential: no fallback. The turn fails rather than leaving the safe perimeter.

Who answered

Every response carries:

Header	Content
x-coeos-axis	the axis the request was classified on
x-coeos-model	the model that served it
x-coeos-provider	the provider that hosted it
x-coeos-decision	the full verdict: requested class, served class, provider, model, axis, use of the decider, profile

Where the routing comes from

The settings are data, not opinion. They come from the TMB Scoreboard: every candidate model scored axis by axis on the same tests, judged the same way. When a new model wins an axis, a new setting is published.

Read next

• What CoeOS is
• Confidentiality and Guardian
• OdyssAI-X and CoeOS — the engine that serves Hybrid and Local.