Provider credentials

Store your organization’s own model provider credentials in Altrum, or let callers send their own.

This is in development. Details may change before it is available.

Altrum calls model providers with your organization’s own accounts. You pay your providers as you do today. Altrum stores the credentials so your applications never need them: an application holds only an Altrum virtual key.

Supported providers

Provider	What you store
OpenAI	An API key
Anthropic	An API key
Google Gemini	An API key
Google Vertex AI	Your project, your region and a service account key
Bedrock	Your region, and either an API key or an access key with its secret. Optionally, the inference profiles your model names map to
Azure	Your endpoint and the deployments your model names map to, and either an API key or the details of an app registration. Covers Azure OpenAI and Azure AI Foundry

Add a credential

Owners and admins open AI Gateway, then Provider credentials, and choose Add credential. Name it, choose the provider and fill in what that provider needs. Under Models, list the models it may serve, or leave it empty for every model. Altrum checks the credential with the provider; one the provider refuses is marked Needs attention, with the provider’s reason.

• A credential is encrypted when it is stored, and never shown again. The list shows only its last characters.
• Altrum never writes a credential into a log.
• To replace a credential, store the new one and remove the old one. A stored credential can be renamed, switched off and limited to some models, but its secret cannot be edited.
• You can store several credentials for one provider, for example for different accounts or regions. Requests to that provider use all of them.
• The models a credential lists are the models anyone in your organization can reach through it. Each key can narrow them further. See Models and routing.

What Altrum refuses to store

Altrum calls a provider from the Altrum network, so it refuses a credential that would reach anything else:

• An address that is not public: an Azure endpoint must be an https address that anyone on the internet could reach. An address inside a private network, or one that points back at Altrum, is refused.
• A reference to somewhere else instead of the value itself, such as the name of an environment variable.
• A credential that relies on the machine Altrum runs on to sign in. A Bedrock credential needs its own API key or access key, a Vertex credential its own service account key, and an Azure credential its own API key or app registration. Altrum never signs in as itself on your behalf.
• For Vertex, anything other than a service account key.

Each refusal names the field and what to send instead.

Callers’ own credentials

Some teams want an application to send its own provider credential with each request. This is off by default. An owner or admin can switch it on for the organization in the AI Gateway settings. A request that sends its own credential must also carry an Altrum virtual key, so Altrum knows which organization it belongs to, and is refused if the organization has not switched this on. A credential sent this way is used for that request only, never stored and never logged. Guardrails, rate limits and logging still apply. Its cost is counted against budgets, but your provider bills the caller’s account.