Skip to main content
Rules gives you one place to decide how Opper handles every model call in your organization. Set a retention policy, cap spend, limit which models are available, and inspect inputs and outputs—all without changing application code.
The Rules page showing data retention and spend limits
Open Rules from Observe & Control in the Opper platform. The page is also available at platform.opper.ai/<your-org>/rules on plans that include Rules.
Rules can also be managed from code: the Management API lists, creates, updates and deletes the same rules, with a management key carrying the controls:write scope.

​
What you can configure

Opper retention

Turn Opper tracing on or off and choose how long to keep traces.

Spend limits

Set a monthly organization budget and optional project caps.

Model access

Restrict the providers, regions, countries, and models your apps can use.

Checks

Score quality or flag, redact, and block content.

Routing

Choose which provider a model pool tries first.
Rules apply to LLM calls made through the Opper v3 API, including calls from the compatibility gateway and the playground. Spend limits also cover image, speech, and video generation. Model access and checks do not currently apply to those modalities.
The deprecated v2 API is not covered by Rules.

​
Organization rules and project overrides

Start with an organization rule to set the default for every project. Add a project override when a workload needs a stricter policy. Project overrides cannot loosen an organization rule. For example, a project cannot use a provider blocked at the organization level or retain data for longer than the organization allows. Routing is the exception: a project’s order replaces the organization’s rather than narrowing it. Overrides for retention, spend, model access, and routing appear directly below their organization rule. For checks, choose the scope while editing the check.

​
Save a set of changes

You can edit several sections before applying them. Nothing changes until you select Save changes.
The unsaved-changes bar listing the edited sections
The save bar lists every section with unsaved changes. Select Discard to reload the saved configuration, or Save changes to apply the entire draft. If something needs attention, the bar links to the affected field and disables saving until the problem is fixed.
A check that cannot be saved until at least one project is selected

​
When no rules are configured

Data retention and spend limits before any rules are configured
With no applicable enabled rules:
  • Opper records usage metadata, but does not store trace content such as inputs, outputs, or spans.
  • Usage is uncapped.
  • Every model in the catalog is available.
  • No checks run.
See Opper retention for the difference between trace content and the usage metadata Opper keeps for billing. Each section has a stable URL fragment: When trace storage is enabled, checks and model-access decisions appear as events on the relevant trace span. Rules still enforce when effective retention is zero or unset, but no trace content is stored.