OpenRouter

proxium calls OpenRouter with your own OpenRouter key. Your applications send their requests to proxium with a proxium virtual key. They never hold the OpenRouter key.

Setting	Value
Preset id	openrouter
Base URL	https://openrouter.ai/api/v1
How proxium sends the key	an Authorization: Bearer header
Request format	the OpenAI Chat Completions format
Request type	chat

Add OpenRouter to a project

1. Get a key from OpenRouter at openrouter.ai/keys.
2. In the console, open Providers and select Add a vendor.
3. In What are you adding, select OpenRouter. proxium fills in the base URL and the models.
4. Paste the key into API key, and select Add OpenRouter.

proxium stores the key encrypted. The console does not show the key again.

Models

A new OpenRouter vendor starts with a list of its models. You can change the list on the Providers screen.

Call a model

A vendor that you add has the provider id t.<project>.openrouter, where <project> is the project slug. Send GET /v1/models to get the exact ids that your key can use, and put one in place of <model>.

curl https://proxium.tech/v1/chat/completions \
  -H "Authorization: Bearer $PROXIUM_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "t.<project>.openrouter/<model>", "messages": [{"role": "user", "content": "Hello"}]}'

You can also send a tier name, such as trial, in model. proxium then picks the model from the routing policy of the project. Refer to Routing.

Ready-made routing

proxium suggests a routing for a project with OpenRouter. When you choose it on Routing, a request with "model": "auto" works at once: a classifier picks the tier, and the tier picks the model. The Routing screen shows the models of each tier. A tier that you set yourself keeps your models. Refer to Automatic routing.