Channel management

Basic settings

Click “Add channel” to open the form, then fill in the basic information needed to connect to the upstream provider:

Select models

• Select the models this channel can forward, or click “Fetch from upstream” to call POST /api/channel/fetch_models
• Fetch models for a specific channel: GET /api/channel/fetch_models/{id}
• Selected models are written to the models field; together with the ability table in “Model management”, they determine routing

Advanced settings

Submit and save

• Create: POST /api/channel/
• Update: PUT /api/channel/
• Duplicate an existing channel: POST /api/channel/{id}/copy
• After saving, you return to the list; Root users can view the full key via POST /api/channel/{id}/key

Test a single channel

Click “Test” in the row, or call POST /api/channel/{id}/test. The system sends a probe using the channel's configured test_model and, on success, updates response_time and test_time.

Test in bulk

“Test all channels” in the toolbar maps to GET /api/channel/test and checks every enabled channel in turn. You can also call GET /api/channel/update_balance to refresh balances in bulk.

Select channels

Tick the checkboxes on the left side of the list. Use the tag tabs at the top to show channels that share a tag, or use the search box to filter by ID, name, key, Base URL, or model keyword (GET /api/channels?keyword=).

Run bulk actions

Configure multiple keys

Turn on “Multi-key” in the channel edit form and enter one upstream key per line, or maintain keys in bulk via POST /api/channel/multi_key/manage. This is useful for rotating across several accounts at the same provider to raise quota limits.

Choose a rotation mode

Save the configuration

Once saved, the gateway distributes requests across the keys using the selected mode. When a single key keeps failing, auto_ban can automatically disable that key or the entire channel.

Simple override mode

Enter a JSON object in param_override, where each key is a dot-separated path (such as temperature or max_tokens) and each value is what gets written into the request body. This works well for rewriting a few parameters with fixed values.

Advanced operations mode

Use the operations array to define complex parameter operations, including conditions, array operations, string concatenation, and normalization. It can be combined with header_override to handle unusual upstream formats.

Basic structure

{
  "operations": [
    {
      "path": "temperature",
      "mode": "set",
      "value": 0.8,
      "conditions": [...],
      "logic": "AND"
    }
  ]
}

Operation modes (mode)

1. set - Set a value: Sets the value at the given path; with `keep_origin: true`, existing values are left unchanged
2. delete - Delete a field: Removes the field at the given path from the request body
3. move - Move a field: Moves the value at the `from` path to the `to` path
4. append - Append content: Appends to the end of a string or array, or merges object properties

   {
     "path": "messages.0.content",
     "mode": "append",
     "value": "\n\nPlease answer in English."
   }

5. prepend - Prepend content: Inserts at the start of a string or array, or merges object properties
6. copy - Copy a field: Copies the value from `from` to `to` without removing the source field
7. trim_prefix - Remove a prefix: Removes the given prefix from a string; unchanged if it doesn't match
8. trim_suffix - Remove a suffix: Removes the given suffix from a string; unchanged if it doesn't match
9. ensure_prefix - Ensure a prefix: Makes sure the string starts with the given prefix
10. ensure_suffix - Ensure a suffix: Makes sure the string ends with the given suffix
11. trim_space - Trim whitespace: Runs TrimSpace on the string
12. to_lower - Convert to lowercase: Converts a string field to lowercase
13. to_upper - Convert to uppercase: Converts a string field to uppercase
14. replace - Replace text: Substring replacement; `from` is required and `to` is optional
15. regex_replace - Regex replace: Regex match and replace using Go regexp syntax

    {
      "path": "model",
      "mode": "regex_replace",
      "from": "^gpt-",
      "to": "openai/gpt-"
    }

Conditions

Use the conditions array to set when an operation runs; the operation is applied only when its conditions are met.

{
  "conditions": [
    {
      "path": "model",
      "mode": "contains",
      "value": "gpt-4",
      "invert": false,
      "pass_missing_key": false
    }
  ],
  "logic": "AND"
}

Path syntax

Use JSON paths to access nested fields:

Built-in variables (they don't need to exist in the request body and can be used directly in conditions):

Practical examples

{
  "operations": [
    {
      "path": "temperature",
      "mode": "set",
      "value": 0.3,
      "conditions": [{ "path": "messages.0.content", "mode": "contains", "value": "code" }]
    },
    {
      "path": "temperature",
      "mode": "set",
      "value": 0.9,
      "conditions": [{ "path": "messages.0.content", "mode": "contains", "value": "creative" }]
    }
  ]
}

{
  "operations": [
    {
      "path": "messages",
      "mode": "prepend",
      "value": [{ "role": "system", "content": "You are a professional AI assistant. Always remain polite and professional." }]
    }
  ]
}

{
  "operations": [
    {
      "path": "max_tokens",
      "mode": "set",
      "value": 4000,
      "conditions": [{ "path": "model", "mode": "prefix", "value": "gpt-4" }]
    },
    {
      "path": "max_tokens",
      "mode": "set",
      "value": 2000,
      "conditions": [{ "path": "model", "mode": "prefix", "value": "gpt-3.5" }]
    }
  ]
}

{
  "operations": [
    {
      "path": "stream",
      "mode": "set",
      "value": false,
      "conditions": [
        { "path": "model", "mode": "contains", "value": "claude" },
        { "path": "messages.0.content", "mode": "contains", "value": "long-form" }
      ],
      "logic": "AND"
    }
  ]
}

{
  "operations": [
    {
      "path": "temperature",
      "mode": "set",
      "value": 0.1,
      "conditions": [
        { "path": "max_tokens", "mode": "gt", "value": 1000 }
      ]
    }
  ]
}

{
  "operations": [
    {
      "path": "stream",
      "mode": "set",
      "value": true,
      "conditions": [
        {
          "path": "model",
          "mode": "contains",
          "value": "gpt-3.5",
          "invert": true
        }
      ]
    }
  ]
}

{
  "operations": [
    {
      "path": "temperature",
      "mode": "set",
      "value": 0.7,
      "conditions": [
        {
          "path": "custom_field",
          "mode": "full",
          "value": "special",
          "pass_missing_key": true
        }
      ]
    }
  ]
}

{
  "operations": [
    {
      "path": "messages.-1.content",
      "mode": "append",
      "value": "\n\nPlease explain your reasoning in detail."
    }
  ]
}

Notes

• Operations run in the order of the operations array; earlier operations affect later ones
• Parameter overrides are intended only for legitimate upstream API compatibility, corporate network compatibility, and request normalization
• Numeric comparison conditions only apply to number values; string operations compare as strings