Skip to main content
Model Fusion answers a request with several models at once, has a judge compare their answers, and returns one response. Callers use it like any other model: one model ID, one response.

Use cases

  • Review across providers: put models from different providers on the panel and read the judge’s list of contradictions before shipping an answer or a code change.
  • High-stakes answers: the Safety preset makes the judge weigh physical, financial, legal, and medical risk, and flag it before synthesis.
  • Swap models without touching callers: the fusion owns the model ID, so changing the panel or the judge leaves client code unchanged.

Create a Model Fusion

Open AI Gateway → Model Fusion, then select Model Fusion in the page header. The list filters by Preset and Status, and the switch in the Status column turns a fusion on or off without deleting it. The detail page carries Overview telemetry, Traces, and Settings.
Creating or changing a fusion through the SDK or API needs a Management Key with Model fusions access. The Model Fusion SDK reference covers the list, create, retrieve, update, enable, disable, and delete calls. Calls to the fusion through the gateway use a regular API Key.

Use it

Pass the fusion to the gateway as <workspacename>@orq/<name>, the same reference form as the Smart Router.

Synthesis modes

Presets

The preset changes what the judge weighs.

Limits

  • The panel takes 1 to 8 distinct chat models. Provider models only: another fusion cannot sit on the panel.
  • Max tool calls runs from 0 to 20 per phase. The Budget preset keeps web tools off whatever the switch says.
  • An error answers the request when every panel call fails, or when the judge or orchestrator call fails.
A fusion request carries the conversation and nothing else: the panel, the judge, and the orchestrator come from the fusion configuration. A request that sets a generation, routing, or tool control is rejected with invalid_model_fusion (400) instead of applying it to one inner call. Remove the listed fields; the panel, judge, orchestrator, and web tools are set on the fusion.

Cost

One fusion request makes several model calls: one per panel model, one judge call, plus at most one repair attempt when its analysis fails validation, and in Analysis mode one orchestrator call. Each call pays its own prompt.
  • A panel call carries the request plus a fixed panel prompt.
  • The judge call carries the request plus every panel answer, so its input grows with panel size and answer length, not only with the request.
  • The orchestrator call carries the request, the judge’s structured analysis, and the raw panel answers when Include raw panel answers is on.
Usage and cost on the fusion response add up every inner call. Billing follows the inner calls; the aggregate is not charged again. Traces shows the run as three phases, panel, judge, and synthesis, each with a span per model call carrying that call’s tokens and cost.