Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.opper.ai/llms.txt

Use this file to discover all available pages before exploring further.

Control Plane features are in early access and need to be turned on per account. Contact support@opper.ai if you’re interested.
Route picks the model used when a caller omits the model field. You define one or more Route rules, each scoped to your organization, specific projects, or specific functions. The picker only offers models that pass Comply at the rule’s scope — Route doesn’t have its own allowlist; constraints live in Comply.

​
Rules

Each Route rule has a single setting: the default model for its scope. Open platform.opper.ai and navigate to Controls → Route to add a rule. The model picker filters its options against the effective Comply allowlist for the rule’s scope. If the allowlist denies every model at that scope, the UI shows:
No models pass the comply allowlists at this scope. Adjust the comply rules to broaden what this scope can use.
Leave the default empty (the picker shows “Auto”) to let the gateway pick — callers can then steer with the prefer hint (fast / cheap / quality / balanced).

​
Scope

  • Organization — every project and every function.
  • Projects — one or more specific projects.
  • Functions — specific functions inside a project.
A function-level rule’s default wins over a project-level rule’s default for that function, which wins over an org-level default.

​
In traces

Route events appear on a span with a Compass icon labeled Route, status Applied when a rule was used to pick the model. Each event carries the rule’s name (when set) and a scope badge (Org-level / Project-level / Function-level), so you can see which rule fired. The model that actually ran appears in the span’s Model field as usual.

​
In playground

Route is where the playground gets the most interactive:
  • Model picker — top of the left-sidebar task config. Pick any model from the catalog for the run. This is the per-call equivalent of a Route rule’s default.
  • Compare models — toggle to a multi-lane view. Add lanes, give each a different model, and run the same input across all of them in parallel. Useful for sanity-checking a switch before changing a project rule.
  • Parameters — Temperature, Max tokens, Reasoning effort. Each is shown only when the selected model supports it.
  • Routing → Preference — shown when the model is left blank (“Auto”). Segmented toggle: fast / cheap / quality / balanced. Sets the prefer hint for the run.
The Project controls toggle in the task sidebar gates whether your Comply allowlist and Route rules apply. When it’s on, picking a disallowed model in the playground produces the same error a production call would.

​
Caller overrides

Passing an explicit model in a call still works — as long as it passes the Comply allowlist for that scope. This lets you tune per-call trade-offs (a cheaper model for high-volume background jobs, a higher-quality one for user-facing replies) without giving up scope-wide policies. If the requested model doesn’t pass the allowlist, the call is rejected with a clear error rather than silently falling back to the default.
Use Route rules to keep your application code free of model names. Pin defaults per scope; switch models by editing the rule, not your code.