Models Overview
ChemAgent supports mainstream model providers and separates the main chat model from vision, image generation, speech recognition, speech synthesis, embeddings, and search. Each capability can use its own provider and model.
Capability matrix
| Provider | Representative models | Text | Vision | Image | STT | TTS | Embedding |
|---|---|---|---|---|---|---|---|
| DeepSeek | deepseek-v4-flash / pro | ✓ | |||||
| MiniMax | MiniMax-M3 | ✓ | ✓ | ✓ | ✓ | ||
| Claude | claude-sonnet-5 / fable-5 | ✓ | ✓ | ||||
| Gemini | gemini-3.5-flash | ✓ | ✓ | ✓ | |||
| OpenAI | gpt-5.6 series | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| GLM | glm-5.2 / glm-5v-turbo | ✓ | ✓ | ✓ | ✓ | ||
| Qwen | qwen3.7-plus | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Doubao | doubao-seed-2.1 series | ✓ | ✓ | ✓ | ✓ | ||
| Kimi | kimi-k2.7-code | ✓ | ✓ | ||||
| ERNIE | ernie-5.1 | ✓ | ✓ | ||||
| MiMo | mimo-v2.5-pro / v2.5 | ✓ | ✓ | ✓ | |||
| LinkAI | 100+ routed models | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Custom | Compatible endpoints | ✓ |
The live ChemAgent console exposes separate routes for Chat, Vision, ASR, TTS, Embedding, Image, and Search. A provider selected for chat does not have to power the other capabilities.
Configure from the Web console
- 1Open Models
The console loads the supported providers and capability cards from the running deployment.
- 2Configure a provider
Add the authorized API credential, endpoint where required, and the exact model identifier.
- 3Route each capability
Select providers independently for chat, vision, image generation, speech, embeddings, and search.
- 4Save and validate
Test a bounded request and confirm streaming, tool calls, error handling, cancellation, and token telemetry.
Production selection criteria
Match model behaviour to engineering complexity and review expectations.
Choose a context window suitable for the project material and active workflow.
Validate tool calling, structured output, vision, speech, image, and embedding behaviour separately.
Evaluate data location, retention, access control, latency, availability, and cost.
Usage visibility
Token accounting is available when the selected integration returns and records prompt and completion usage fields. The UI reports session, daily, and cumulative usage where data is available.