Providers

Bring any model from any provider.

Docs on GitHub

zot ships a broad provider catalog so /login, /model, --provider, and --list-models all speak the same IDs.

Use /login for subscription auth and simple API-key providers. Providers that need cloud-specific settings show setup guidance instead of opening a localhost browser form, which is safer for SSH, containers, and kubectl exec sessions.

Subscription login

Anthropic Claude Pro/Max (anthropic), OpenAI Codex / ChatGPT Plus/Pro (openai-codex), Kimi Code (kimi), and GitHub Copilot (github-copilot). OAuth tokens are stored in $ZOT_HOME/auth.json and refreshed when supported.

API-key providers

Simple API-key providers can be configured through /login or environment variables. Examples include Anthropic, OpenAI, OpenAI Responses, DeepSeek, Google Gemini, Kimi/Moonshot, Moonshot CN, Groq, Cerebras, xAI, Together AI, Hugging Face Router, OpenRouter, Mistral, Z.AI, Xiaomi/MiMo, MiniMax, Fireworks, Vercel AI Gateway, and OpenCode.

ProviderEnvironment
AnthropicANTHROPIC_API_KEY
OpenAI / OpenAI ResponsesOPENAI_API_KEY
Google GeminiGEMINI_API_KEY or GOOGLE_API_KEY
OpenRouterOPENROUTER_API_KEY
MistralMISTRAL_API_KEY
GroqGROQ_API_KEY
xAIXAI_API_KEY
FireworksFIREWORKS_API_KEY
Vercel AI GatewayAI_GATEWAY_API_KEY
OpenCodeOPENCODE_API_KEY

Cloud setup providers

These providers need more than a single pasted key, so /login shows setup instructions and points to the provider reference instead of starting a local web login flow.

ProviderRequired setup
Amazon BedrockAWS_BEARER_TOKEN_BEDROCK or AWS profile/IAM credentials, plus AWS_REGION.
Google Vertex AIGOOGLE_CLOUD_API_KEY or Google Cloud credentials, plus project/location settings when needed.
Cloudflare Workers AICLOUDFLARE_API_KEY and CLOUDFLARE_ACCOUNT_ID.
Cloudflare AI GatewayCLOUDFLARE_API_KEY, CLOUDFLARE_ACCOUNT_ID, and CLOUDFLARE_GATEWAY_ID.
Azure OpenAI ResponsesAZURE_OPENAI_API_KEY and AZURE_OPENAI_BASE_URL.

Amazon Bedrock

Bedrock API keys are bearer tokens. Set AWS_BEARER_TOKEN_BEDROCK and AWS_REGION, or use the standard AWS credential chain with AWS_PROFILE, IAM access keys, ECS task roles, or IRSA.

shell
export AWS_BEARER_TOKEN_BEDROCK=bedrock-api-key-...
export AWS_REGION=us-east-1
zot --provider amazon-bedrock --model anthropic.claude-sonnet-4-5-20250929-v1:0

Some Bedrock models require regional inference-profile IDs for on-demand throughput, such as us. or eu. prefixed model IDs. zot rewrites known families automatically where possible, while explicit profile IDs and ARNs are left unchanged.

Custom and local providers

  • Local/compatible: Ollama and OpenAI-compatible local endpoints via --base-url.
  • Named custom providers: define a new provider key with its own baseUrl and api format in $ZOT_HOME/models.json. It logs in through /login and reads a derived env var such as MY_COMPANY_API_KEY.
  • Private model IDs, deployment aliases, and provider overrides live in $ZOT_HOME/models.json.

See the models page for the full custom-provider schema, credential handling, and the --insecure TLS option.

The model picker only shows models from providers currently available through env vars, $ZOT_HOME/auth.json, Kimi CLI fallback, or local Ollama.