Add vendors and your own keys
Proxium calls a model with the key of a vendor that you add to your project. Your apps never hold that key. They send their calls to Proxium with a virtual key.
Your app
Proxium
Vendors
Add a vendor from the list
Proxium has a preset for each vendor in Providers. A preset fills in the base URL, the way to send the key, and a first list of models.
- Get an API key from the vendor. The form shows a get a key link for the vendor that you select.
- In the console, open Providers, and select Add a vendor.
- In What are you adding, select the vendor, for example Groq.
- Paste the key into API key.
- Select Add Groq.
The vendor shows in the Vendors table, with its Models. Each model now has an id that you can send, or put in a chain:
t.acme.groq/<model-a>
t.acme.groq/<model-b>
acme is your project. To list the ids from your code, send GET /v1/models with a virtual key.
Proxium stores the key encrypted. The console never shows it again. To change the key, remove the vendor and add it again.
Add a server that you run yourself
Use this for a server that speaks the OpenAI API, such as vLLM, Ollama or an Azure deployment.
- Open Providers, and select Add a vendor.
- In What are you adding, keep A server I run myself.
- Fill in the form:
| Field | Value | Example |
|---|---|---|
| Name | A short name of lower-case letters, digits and -. No - at the start or the end | my-vllm |
| Base URL | The address of the OpenAI API of the server, on the public internet | https://llm.example.com/v1 |
| Request type | Text, Embeddings, Images, Speech, Transcription or Video | Text |
| Models | The model names of the server, one on each line | my-model |
| API key | Optional. Give it if the server asks for one |
- Select Register.
Proxium refuses a private, loopback or link-local address, such as 10.0.0.5 or localhost. Proxium calls the server from its own network, so the server must be on the public internet.
Change the models of a vendor
- On the row of the vendor, select Models.
- In Models this vendor serves, change the list, one model on each line.
- Select Save.
The new list replaces the old list. The same panel holds the word for the reasoning level none. See Set the word for reasoning level none. To use a new model, add it to a chain on Routing, or send its id. See Route requests to models.
Set the word for reasoning level none
Some vendors refuse the value none for reasoning_effort and ask for another word, such as off. Set that word for the vendor, and proxium rewrites the level none in each call to it. Every other level goes to the vendor as you sent it.
Proxium picks the word in this order:
- The word set on the vendor.
- The word of the vendor preset, for a vendor that has a preset with a word.
- No word. The level
nonegoes to the vendor unchanged.
The word is one of off, none, minimal, low, medium, high, xhigh or max.
- A project sets the word of its own vendor with the field
reasoning_none_wordofPOST /api/teams/{slug}/vendors, or with the fieldreasoning_none_wordof the toolproxium_add_vendor.GET /api/teams/{slug}/vendorsshows the word. - An operator sets the word of a platform vendor with
PUT /provision/providers/reasoning-noneand the body{ "provider_id": "...", "word": "off" }, or with the toolproxium_set_reasoning_none. The body{ "provider_id": "...", "word": null }removes the word.GET /provision/providers/wireshows the word, the word in force and its source (endpoint,presetornone).
A change takes effect within the config refresh, 30 seconds by default.
Remove a vendor
Select Remove on the row, and confirm. Proxium removes the vendor, its models and its key. A chain that names one of its models skips that model.
Your own keys
The Your own keys section holds a key that replaces another key:
- In a project with the pooled keys of Proxium, give your own key for one of the platform providers. The calls to that provider then bill your vendor account.
- In each project, give a new key for one of your own vendors. It replaces the key that you added the vendor with.
A new project on proxium.tech has no pooled keys. For such a project, the form lists only its own vendors. If the project has no vendor yet, the section tells you to add one, and it shows no form. Add a vendor as above.
A key for a platform provider, sent from a project without pooled keys, gets 403 pool_not_granted.
Related pages
- Providers: each preset, its base URL and its first models.
- Route requests to models: put the models of your vendors in a chain.
- Create endpoints and keys: the keys that your apps send.