AIGCS

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

FieldValue
Type Keyopenai
AuthBearer Token (API Key)
Default Modelgpt-4o-mini
Endpointhttps://api.openai.com/v1
{
  "type": "openai",
  "apiKey": "sk-...",
  "model": "gpt-4o-mini",
  "enabled": true
}

Google Gemini

FieldValue
Type Keygemini
AuthAPI Key (URL query param ?key=)
Default Modelgemini-2.0-flash
Endpointhttps://generativelanguage.googleapis.com/v1

Anthropic Claude

FieldValue
Type Keyclaude
Authx-api-key header
Default Modelclaude-sonnet-4-20250514
Endpointhttps://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.

ProviderType KeyDefault ModelEndpoint
DeepSeekdeepseekdeepseek-chathttps://api.deepseek.com
Qwen (千问)qwenqwen-turbohttps://dashscope.aliyuncs.com/compatible-mode/v1
GLM (智谱)glmglm-4-plushttps://open.bigmodel.cn/api/paas/v4
Hunyuan (混元)hunyuanhunyuan-turbohttps://api.hunyuan.cloud.tencent.com/v1
Doubao (豆包)doubaodoubao-1.5-prohttps://ark.cn-beijing.volces.com/api/v3
MiniMaxminimaxminimax-text-01https://api.minimax.ai/v1
Kimi (月之暗面)kimikimi-latesthttps://api.moonshot.cn/v1
Quark (夸克)quarkqwen-turbohttps://dashscope.aliyuncs.com/compatible-mode/v1
Grok (xAI)qrokgrok-2-latesthttps://api.x.ai/v1

Local Providers

Ollama

FieldValue
Type Keyollama
AuthNone
Default Modelllama3
Endpointhttp://localhost:11434/v1

Custom Provider

Any unknown type key creates an OpenAI-compatible provider dynamically:

{
  "type": "custom-provider-name",
  "apiKey": "sk-...",
  "endpoint": "https://your-custom-endpoint/v1",
  "model": "your-model",
  "enabled": true
}

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:

  1. API connectivity
  2. Authentication
  3. Model response quality

API Key Security

API keys follow this security flow:

User input → AES-256-GCM encrypt → Store in database

Generation time → Decrypt in memory → Send to API → Discard

The encryption key is derived from ENCRYPTION_KEY (or falls back to JWT_SECRET).

On this page