Setup
Opper’s model IDs use the sameprovider/model convention as OpenRouter, so LiteLLM’s OpenRouter-compatible provider works today:
A first-class
opper/ provider for LiteLLM is in review upstream. Once merged, the config becomes model: opper/anthropic/claude-haiku-4-5 with no api_base override, and cost tracking works on every dispatch path including streaming.Cost tracking
Every Opper response includesusage.cost (USD). LiteLLM’s OpenRouter path reads it into its spend tracking, so LiteLLM spend logs show Opper’s actual billed cost instead of estimates from a static price map.
Model discovery
GET https://api.opper.ai/v3/compat/models returns the models your key can use — filtered by your organization’s compliance rules, with per-token pricing and per-model compliance metadata (region, ZDR status, GDPR residency). Sync your model_list from it, or filter it first, for example to EU-resident, zero-data-retention models only.
Per-tenant usage attribution
Forward up to 8 tags per request with theX-Opper-Tags header, then group usage and cost by tag in Opper analytics:
Related
Tags and usage attribution
Group spend by tenant, environment, or app.
Model catalog
IDs, pricing, and compliance metadata.