ProvaraDocs
Configuration

Providers

Built-in adapters and how to add more.

Built-in

ProviderModelsAPI style
OpenAIgpt-4o, gpt-4.1, gpt-4.1-mini, gpt-4.1-nano, o3, o4-miniNative SDK
Anthropicclaude-opus-4-6, claude-sonnet-4-6, claude-haiku-4-5Native SDK
Googlegemini-2.5-pro, gemini-2.5-flash, gemini-2.0-flashNative SDK
Mistralmistral-large, mistral-medium, mistral-smallOpenAI-compatible
xAIgrok-3, grok-3-miniOpenAI-compatible
Z.aiglm-5.1, glm-5, glm-5-turbo, glm-4.7, glm-4.7-flashx, glm-4.7-flashOpenAI-compatible
Ollamaany model served locallyOpenAI-compatible

Registration

Providers auto-register at gateway startup based on:

  1. Env varsOPENAI_API_KEY, ANTHROPIC_API_KEY, etc.
  2. DB-stored keys — added via /dashboard/api-keys, encrypted with PROVARA_MASTER_KEY. DB keys take precedence over env vars.

Ollama is always registered (points at OLLAMA_BASE_URL, default http://localhost:11434/v1). Set OLLAMA_API_KEY only if your Ollama host requires bearer auth (e.g. a remote deployment).

Adding a provider

See the adding-a-provider runbook. Two paths:

  • OpenAI-compatible (Fireworks, Together, Groq, DeepSeek, etc.) — no code change; register via registerOpenAICompatible and add pricing
  • Native API — new adapter under packages/gateway/src/providers/