Skip to main content
Every agent run costs a model call, and Providers is where you see which models this account can call, what each is costing, and whether it is working. The Komodor Agentic Operation Platform (KAOP) ships with managed models so agents run without any setup. You can also register your own provider account or route a self-hosted agent directly through an LLM gateway you manage.

​
Three tiers, one table

The page is one flat table of models, not a tab per tier. Each row is a model with its provider, who manages it, its upstream model id, its spend, its usage, and its status — so the tier is just a column you can sort and filter by. A registered account with no models yet still gets a row, so it is visible rather than something you have to remember exists. Above the table sits the account’s gateway budget. That strip is the only place the managed tier’s account-level numbers appear.

​
Bringing your own provider

Supported providers are OpenAI, Anthropic, Azure, Bedrock, Vertex AI, Gemini, Mistral, Groq, DeepSeek, OpenRouter, Together AI, xAI, Cohere, Ollama, Baseten, Nebius Token Factory, and a hosted vLLM endpoint.
1

Credential

Name the account and supply its API key. The key is stored so model discovery can authenticate with it later.
2

Models

Register one or more upstream model ids against that credential. Nothing is written until this step submits — the credential is created, then each model against it, as one action.
3

Verify

Each new deployment is health-checked, and you can talk to it directly to confirm it answers.
Verify is a step of its own rather than a result banner, because after the write “did this work” is a genuinely different question from “what should I create” — and a reader who has finished creating still has to answer it. To add models to an account you already registered, use Add models on that credential rather than walking the wizard again.
Registering your own provider does not replace the managed tier — both stay callable, and an agent picks a model from either.

​
Using your own LLM gateway

The Managed by me — your own LLM gateway tier is for self-hosted agents. The worker calls your gateway directly with your key: neither that inference key nor the inference request passes through Komodor’s model gateway. The upstream provider key stays inside your gateway as well. KAOP supports LiteLLM, Hosted vLLM, Ollama, and Azure AI Foundry gateways. The first three use an OpenAI-compatible interface. Azure AI Foundry uses its own discovery route and is distinct from registering a public Azure AI Foundry account under Add a new key.
Keeping Komodor out of the inference path does not turn off run reporting. Prompts, model spans, outputs, and other evidence emitted by the worker still follow the account’s normal data-handling rules.

​
Choose how KAOP reads gateway metadata

Both modes keep inference between your worker and your gateway. The difference is whether KAOP can read metadata from the gateway. The scoped key must be read-only and non-admin. It is stored encrypted, used only for metadata operations, never delivered to a worker, and never used for inference. Do not enter your gateway’s admin key or an upstream provider key.

​
Register a customer-managed gateway

1

Choose Managed by me

Open Providers, choose Add provider, then select Managed by me — your own LLM gateway. This tier can be used only by agents you host yourself.
2

Describe the gateway

Choose its kind and strict or scoped mode, then enter a source name and gateway base URL. For a private endpoint, select the Outpost that can reach it; leave the Outpost unset for a publicly reachable gateway.
3

Supply model access

In strict mode, enter the model ids and choose Add gateway. In scoped mode, enter a read-scoped key and choose Continue, select the discovered models your agents may use, then choose Save gateway.
An Outpost carries only metadata operations between KAOP and a private gateway: model discovery, verification, and spend reads. The self-hosted worker still reaches the gateway directly for every inference request. Make sure the gateway host is allowed by the selected Outpost before registering it.

​
Use the gateway from an agent

When you build or edit a self-hosted agent, select a model under Managed by me. Supply the Gateway API key in the wizard, or select I’ll provide the API key myself in the helm command and add it when you install the agent. In either case, the key is rendered into your cluster Secret; it is not stored as a KAOP provider credential.

​
Next steps

Credentials & secrets

How a provider key is stored and delivered to a run.

Outposts

Reach a private gateway without opening an inbound path.

Agent spend & attribution

What the fleet costs, attributed per run, agent, and model.

Model Evaluation

Decide whether a model is good enough for a given job.