Evidence boundary: LiteLLM's documentation shows how its model interface connects to OpenRouter. It is an integration example, not evidence that another company runs this stack in production.
Documented integration pattern
- Configure the OpenRouter API credential as a secret.
- Use the provider-prefixed model identifier.
- Set routing headers deliberately when required.
- Capture usage and errors without logging prompts or credentials.
Relevant provider records
- OpenRouter · router channel
First-party evidence
- LiteLLM OpenRouter documentationFirst-party provider integration documentation.
What this page does not claim
It does not claim that the project's hosted service uses these providers in production, that the integration handles every feature, or that any private cost or revenue figure is known.
Questions developers ask
Does this page prove LiteLLM's private production stack?
No. It documents only the linked public repository or first-party documentation evidence and makes no private deployment claim.
Does APIDir know this project's provider spend or revenue?
No. APIDir does not infer private usage, cost, customer, or revenue information from a public integration.
How should I reuse this integration pattern?
Open the cited source, confirm its current license and configuration, then test the relevant provider record against your own workload.