Model Providers
Connect and orchestrate Large Language Models within the OpenAgent infrastructure.
Model Providers
In OpenAgent, Model Providers represent the compute backbone of your agents. The platform abstracts the complexities of individual LLM APIs, providing a unified interface to manage intelligence, failover, and cost across your organization.
Supported Providers
OpenAgent is designed for maximum flexibility, supporting a wide range of cloud-based and local intelligence engines. All providers are normalized into a unified interface for system prompts and tool calling.
| Provider | Notable Models / Notes |
|---|---|
| OpenAI | GPT-5.5 / 5.2 / 5.1, GPT-4.1, GPT-4o, o4, o3, o1 series. |
| Claude | Claude Opus 4.7 / 4.5 / 4.1, Claude 3.x (Sonnet / Haiku). |
| Gemini | Gemini 3.1 Pro/Flash, Gemini 2.5 Pro/Flash. |
| DeepSeek | DeepSeek V4 (Pro/Flash), DeepSeek-R1. deepseek-v4-flash is handled as a thinking-capable model. |
| Mistral | Mistral Large, Mixtral, Codestral. |
| Grok | Grok-3, Grok-3-mini, Grok-2. |
| Alibaba Cloud | Qwen-Max, Qwen-Plus, Qwen-Turbo, Qwen3.6, and Qwen-VL/QVQ multimodal models. |
| Baidu Cloud | ERNIE 4.0, ERNIE 3.5. |
| Tencent Cloud | Hunyuan-Pro, Hunyuan-Standard. |
| Volcano Engine | Doubao-Pro, Doubao-Lite, and Doubao Seedance video models. Supports streamed thinking content when the provider has thinking enabled. |
| Moonshot | Moonshot-v1 (Kimi), including kimi-for-coding. |
| iFlytek | Spark-4.0 Ultra, Spark-3.5 Max. |
| Baichuan | Baichuan2-Turbo. |
| StepFun | Step-1, Step-2. |
| Yi (01.AI) | Yi-Large, Yi-34B. |
| ChatGLM | GLM-4, GLM-4V. |
| MiniMax | MiniMax-M3, M2.7, M2.5, M2.1, M2 (with -highspeed variants). |
| OpenRouter | Access to 200+ models via a single API key. |
| Silicon Flow | High-performance inference for open-weight models. |
| GitHub Models | Models via GitHub's serverless inference. |
| Hugging Face | Models via the HF Inference API. |
| Azure OpenAI | OpenAI models deployed on Azure infrastructure. |
| Amazon Bedrock | Claude, Llama, and Titan models via AWS. |
| Ollama | Local LLM execution (Llama, Mistral, Gemma, etc.). |
| Local | Any OpenAI-compatible API (vLLM, llama.cpp, LM Studio) with compatibleProvider field. |
| OpenCode | Delegate coding work to a local OpenCode agent server. |
| OpenAI Compatible | Any OpenAI-compatible API with a custom endpoint URL (no compatibleProvider needed). |
| Writer | Writer AI platform models. |
| Cohere | Command R+, Command R. |
Quick Setup
New deployments can configure their first model provider from the Quick Setup onboarding page instead of the full provider form. It presents the common providers as one-click cards; picking one pre-fills sensible defaults (a default model / Sub Type) so you only need to supply the credential.
Quick Setup covers most supported providers, including OpenAI, Claude, Gemini, DeepSeek, Grok, Mistral, MiniMax, OpenRouter, Alibaba Cloud, Moonshot, Silicon Flow, Volcano Engine, Baidu Cloud, Tencent Cloud, iFlytek, ChatGLM, Baichuan, StepFun, Yi, Cohere, Writer, Hugging Face, GitHub Models, Amazon Bedrock, Azure, Ollama, Local, OpenCode, and OpenAI Compatible.
Each card indicates what it needs — most only require an API Key, while local or self-hosted options (Ollama, Local, OpenAI Compatible, OpenCode) ask for a Provider URL instead, and enterprise types (Azure, Amazon Bedrock, Tencent Cloud) request their extra endpoint or region fields. For anything not listed, or to fine-tune advanced settings, use the full provider form described below.
Configuration
OpenAgent provides a unified form to connect these services. While most providers only require an API Key, some enterprise and local types have additional field mappings.
Provider-Specific Settings
Most providers (OpenAI, Claude, DeepSeek, OpenRouter) follow this pattern:
- Type: Select the provider name.
- Sub Type: The specific model ID (e.g.,
gpt-4o,deepseek-chat). - API Key: Your secret token.
- Fetch models: For supported providers, use the sync button beside Sub Type to load the current model list from the provider API.
Azure requires specific endpoint and deployment details:
- Type:
Azure - API Key: Your Azure OpenAI API key.
- Provider URL: Your resource endpoint (e.g.,
https://your-name.openai.azure.com). - Client ID: Enter your Deployment Name.
- API Version: (Optional) e.g.,
2024-02-15-preview.
OpenAgent uses the AWS SDK to connect to Bedrock:
- Type:
Amazon Bedrock - Sub Type: The Bedrock Model ID (e.g.,
anthropic.claude-3-opus-20240229-v1:0). - API Key: Your AWS Secret Access Key (ensure AWS credentials are also available in your environment).
For local inference engines:
Ollama:
- Type:
Ollama - Provider URL: The address of your Ollama server (e.g.,
http://localhost:11434). - Sub Type: The model name as it appears in
ollama list(e.g.,llama3.2). - OpenAgent sends chat requests through Ollama's OpenAI-compatible
/v1chat completions endpoint, so the base server URL is enough.
Local (with compatible provider):
- Type:
Local - Provider URL: Base URL of your local inference server.
- Sub Type: The model ID.
- Compatible Provider: Specify which API format it mimics (e.g.,
gpt-3.5-turbo) — used for correct message formatting.
OpenCode lets OpenAgent hand coding tasks to an OpenCode agent process:
- Type:
OpenCode - Provider URL: Your OpenCode server URL, usually
http://localhost:4096. - API Key: Optional.
OpenCode executes its own coding workflow and tool use internally. OpenAgent sends the conversation to OpenCode and streams the final response back; OpenAgent-side Store tools are not mapped into OpenCode tool calls.
For any server that implements the OpenAI Chat Completions API format at a custom URL:
- Type:
OpenAI Compatible - Provider URL: The base URL of your server (e.g.,
https://api.your-service.com). - Sub Type: The model ID to send in requests.
- API Key: Your API key if the server requires authentication.
Use this for hosted OpenAI-compatible services (Together AI, Fireworks AI, Groq, etc.) where you don't need the compatibleProvider adapter logic. OpenAI Compatible providers use the Chat Completions style request path and can track configured custom input/output pricing; if no custom price is configured, usage cost falls back to 0 instead of failing.
Key Platform Features
OpenAgent provides several infrastructure-level capabilities that go beyond simple API wrapping.
1. Automated Failover (Child Models)
To ensure high availability, OpenAgent allows you to configure Child Model Providers at the Store level.
- If the primary provider returns a rate limit or a 5xx error, OpenAgent automatically routes the request to the next available child provider in your list.
- Example: Use
DeepSeek V4for cost-efficiency, withGPT-4.1as a high-reliability fallback.
2. Context Logic Abstraction
OpenAgent handles the "dirty work" of different model families:
- Thinking Mode: Native support for reasoning models (o1, DeepSeek-R1, DeepSeek V4 Flash).
- Prompt Unification: Automatically formats system, user, and tool-call roles based on the provider's specific requirements.
Volcano Engine providers can stream reasoning content when Enable Thinking is turned on for the Provider. This reasoning is stored with the message detail and follows the Store's Hide Thinking display setting.
Alibaba Cloud Qwen-VL and QVQ models are treated as multimodal models, so image inputs and text tool outputs can be combined in vision-capable conversations.
Volcano Engine doubao-seedance models are treated as video generation models. OpenAgent creates a generation task, polls for completion, records token usage and cost, and returns the generated video URL when the task succeeds.
When a prompt or conversation history contains a supported document URL, OpenAgent can parse and cache the document text before calling the model. For OpenAI and Azure models this replacement is limited to local or private URLs; other providers can receive parsed content for supported document URLs.
3. Cost & Usage Tracking
By filling in the pricing fields in the Provider configuration, OpenAgent tracks expenditures at the organization level:
- Input/Output Price: Tracks cost per 1k tokens.
- Message Auditing: Every message stores the actual provider used and the calculated cost in the database for billing or reporting.
Unknown OpenAI-compatible model names no longer block message completion because of missing built-in pricing; OpenAgent records 0 cost unless custom input/output pricing is configured on the Provider.
4. OpenAI-Compatible API Access
Each Model Provider edit page shows an OpenAI-compatible API panel with copyable Base URL and Chat completions endpoint values. External clients can call these endpoints with Authorization: Bearer <provider key> to reach that provider directly, without creating Store chat history. See API Access for the full request semantics and the Store-key alternative.
Sampling Parameters
While OpenAgent exposes standard parameters (Temperature, Top-P, Min-P), the platform is designed to use Provider Defaults to ensure stable reasoning. Adjust these only if your specific agentic workflow requires high determinism or extreme creativity.
Recommendation: For agentic tool-use, always set Temperature to 0 to ensure strict adherence to JSON schemas.