Skip to main content

Use your own model provider

What this does

Fleets run on the platform’s model by default. Your tenant can run them on a model you pay for instead. Store a provider credential in the workspace vault, then select it as the tenant provider. --provider is checked against the model catalogue your server serves, so a credential that could never work is never stored. Run agentsfleet models to see that catalogue — the dashboard’s model picker reads the same one.

Before you begin

Select the workspace that should own the credential. Have the provider’s API key ready, and run agentsfleet models to pick a provider id and model this server serves:
The provider column supplies --provider and the model column supplies --model in the next step.

Steps

  1. Store the provider credential. The provider id, API key, and model are all required.
    Provider ids are matched without case: --provider Anthropic stores anthropic, the catalogue’s own spelling. A provider the catalogue does not price is refused, and the message names what it does price. --model is checked the same way, against that provider’s models only. Model ids are matched exactly — they belong to the provider, and several are case-sensitive (MiniMaxAI/MiniMax-M3), so a wrong-case model is refused rather than silently corrected.
  2. Select the stored credential as the tenant provider.
  3. Confirm the active provider.
Fleets you install or resume after this point run on your provider.

Point at your own endpoint

A gateway or self-hosted server that speaks the OpenAI API takes the openai-compatible form. --base-url must be https; a plain http URL is refused before any request. The API key is optional, because some private gateways take none.

Verify it works

Run agentsfleet tenant provider show and check it names your secret. Then steer any fleet; its responses now come from your provider, and its usage lands on your provider account.

Common problems

A --provider value your catalogue does not price is refused, and the message names what it does price. Run agentsfleet models for the full list. To use a provider the catalogue does not carry, point at it directly: --provider openai-compatible --base-url https://host/v1 --model <MODEL>. The ids claude-cli, codex-cli, gemini-cli, openai-codex, and claude-code are refused with their own message. They name local coding tools that carry no API key, so a stored credential could never reach them. The openai-compatible form does not help here — these tools have no endpoint. --api-key or --model without --provider is refused. The three flags describe one credential and travel together. A --model the provider does not serve is refused, and the message lists that provider’s models. Run agentsfleet models --provider <ID> for the list. --base-url with a named provider is refused. A named provider carries its own endpoint; the flag belongs to openai-compatible alone.

Remove or undo

Return to the platform default:
The stored credential stays in the vault. Delete it with agentsfleet secret delete my-openai when no fleet needs it.