Skip to main content
A Provider is an LLM endpoint the engine talks to. One provider can expose many Models. Providers are managed in Command Center → Settings → Providers, scoped to your tenant.
Viewing the catalog is open to any tenant user; only tenant-level users can add, edit, or delete providers. See Users & Organizations.
Providers catalog

Settings → Providers: each row is an endpoint the engine can call.

​
Fields

​
Provider types

Use a compatible type to register a self-hosted model server (vLLM, Ollama, LM Studio) or any vendor exposing an OpenAI- or Anthropic-style API.
Adding a new endpoint of an existing type is pure configuration. Adding a brand-new type (a vendor with its own API shape) requires a 2501 release — contact your Account Executive.

​
API key resolution

The API key is resolved at runtime in two steps:
  1. 2501 looks for a Credential matching the API Key Var Name — for an org-scoped provider, one scoped to that organization first, then a tenant-wide one; for a tenant-wide provider, only a tenant-wide credential.
  2. If none exists, it falls back to an environment variable of the same name on the engine.
This lets you rotate keys in the UI without touching the engine environment. When you save the provider, the dialog checks that the key resolves and warns if it cannot be found.
For a tenant-wide provider (no Organization set), the matching Credential must be tenant-scoped — a credential restricted to a specific organization will not be found. For an org-scoped provider, the credential may be scoped to that organization or tenant-wide.
Providers that do not need a key (e.g. a self-hosted model on a private network) can turn off Requires auth.

​
Azure settings

For the azure type, two extra fields appear: Azure API Management (APIM) gateways are supported as the endpoint: set the Base URL to your APIM gateway URL to route model traffic through it for centralized policy, rate limiting, and logging.

​
Deletion rule

A provider that still has models cannot be deleted. Remove or reassign its models first, or simply disable the provider instead.

​
Deploy-time seeding

On deploy, the installer seeds providers from API keys detected in the engine environment. After that, management moves to Command Center — no engine restart needed for additions or edits.