AI Providers
Complete guide to configuring AI providers
Overview
AIGCS supports 14 built-in AI providers plus any OpenAI-compatible custom provider. Provider API keys are encrypted at rest using AES-256-GCM.
Built-in Providers
Native SDK Providers
OpenAI
| Field | Value |
|---|---|
| Type Key | openai |
| Auth | Bearer Token (API Key) |
| Default Model | gpt-4o-mini |
| Endpoint | https://api.openai.com/v1 |
Google Gemini
| Field | Value |
|---|---|
| Type Key | gemini |
| Auth | API Key (URL query param ?key=) |
| Default Model | gemini-2.0-flash |
| Endpoint | https://generativelanguage.googleapis.com/v1 |
Anthropic Claude
| Field | Value |
|---|---|
| Type Key | claude |
| Auth | x-api-key header |
| Default Model | claude-sonnet-4-20250514 |
| Endpoint | https://api.anthropic.com/v1 |
OpenAI-Compatible Providers
These providers use the OpenAI-compatible API format — configure with the same settings, just change the endpoint and model name.
| Provider | Type Key | Default Model | Endpoint |
|---|---|---|---|
| DeepSeek | deepseek | deepseek-chat | https://api.deepseek.com |
| Qwen (千问) | qwen | qwen-turbo | https://dashscope.aliyuncs.com/compatible-mode/v1 |
| GLM (智谱) | glm | glm-4-plus | https://open.bigmodel.cn/api/paas/v4 |
| Hunyuan (混元) | hunyuan | hunyuan-turbo | https://api.hunyuan.cloud.tencent.com/v1 |
| Doubao (豆包) | doubao | doubao-1.5-pro | https://ark.cn-beijing.volces.com/api/v3 |
| MiniMax | minimax | minimax-text-01 | https://api.minimax.ai/v1 |
| Kimi (月之暗面) | kimi | kimi-latest | https://api.moonshot.cn/v1 |
| Quark (夸克) | quark | qwen-turbo | https://dashscope.aliyuncs.com/compatible-mode/v1 |
| Grok (xAI) | qrok | grok-2-latest | https://api.x.ai/v1 |
Local Providers
Ollama
| Field | Value |
|---|---|
| Type Key | ollama |
| Auth | None |
| Default Model | llama3 |
| Endpoint | http://localhost:11434/v1 |
Custom Provider
Any unknown type key creates an OpenAI-compatible provider dynamically:
Provider Avatars
Each provider has a built-in SVG avatar. You can also upload custom SVG avatars in the admin panel.
Testing a Provider
After configuring a provider, click Test to generate a sample comment. This verifies:
- API connectivity
- Authentication
- Model response quality
API Key Security
API keys follow this security flow:
The encryption key is derived from ENCRYPTION_KEY (or falls back to JWT_SECRET).