One-click import of relay station accounts to the local CLIProxyAPI management interface, automatically generating OpenAI-compatible provider configurations to avoid manual configuration file maintenance.

CLIProxyAPI Integration and One-Click Import

Feature Overview

Management Interface Integration
- Read and write back configurations via CLIProxyAPI's Management API (/openai-compatibility).
- Supports appending/updating API Keys on existing providers, or automatically creating new providers.
One-Click Key Import
- Click "Import to CLIProxyAPI" in the key list to write the current site's Base URL and key to CLIProxyAPI.
Avoid Duplicate Configurations
- Automatically reuses site names and Base URL. If the same provider is detected, only the key list will be updated, and no duplicate entries will be created.

Prerequisites

A compatible CLIProxyAPI is deployed or running, with the management interface enabled:
- Example address: http://localhost:8317/v0/management
- Supports GET/PUT/PATCH /openai-compatibility and other interfaces.
Possess the Management Key for the management interface (used for authentication).
In All API Hub, the following has been completed:
- At least one relay station account has been added and an available key obtained.

Setup Entry

Open the plugin → Go to the Settings page.
Switch to the "CLIProxyAPI" group (Basic Settings → CLIProxyAPI tab).
Fill in the following fields:
- Management Interface Base URL: e.g., http://localhost:8317/v0/management
- Management Key: The key used to access the management interface.
After saving, the configuration will be stored in local preferences for subsequent import operations.

One-Click Import from Key List

Open the plugin → Go to the Key Management page.
Find the site key card you want to import to CLIProxyAPI.
Click the CLIProxyAPI icon button to the right of the key (usually next to the CherryStudio / CC Switch / New API buttons).
The plugin will:
- Read CLIProxyAPI configuration (Base URL and Management Key).
- Use the site's Base URL to generate an OpenAI-compatible address (automatically appends /v1).
- Use the site name or Base URL as the provider name.
- (Optional) Configure Model Mapping (original model → alias) in the import pop-up; the pop-up will attempt to fetch the model list from the upstream /v1/models for easy selection of original models.
- Call CLIProxyAPI:
  - If a provider with the same name or base-url already exists:
    - Deduplicate and append the current key to api-key-entries.
  - If it does not exist:
    - Create a new provider entry, containing only the current key and basic information.
After the operation is complete, you will see an import result notification in the upper right corner (success/failure and error reason).

Effects After Importing to CLIProxyAPI

In CLIProxyAPI's configuration, a similar structure will be added or updated:
- name: Derived from the site name (or Base URL).
- base-url: Uniformly points to the corresponding relay station's /v1 OpenAI-compatible interface.
- api-key-entries: Contains one or more api-key records, which can be further manually edited in CLIProxyAPI.
This means:
- Keys for multiple upstream relay stations can be uniformly managed at the CLIProxyAPI layer.
- All API Hub is responsible for synchronizing basic configuration information, and subsequent details can be customized within CLIProxyAPI.

Common Issues

Prompt: CLIProxyAPI not configured
- Check if the Base URL and Management Key are filled in Settings → CLIProxyAPI.
- Ensure that /openai-compatibility is not redundantly included; it should be the management interface prefix, e.g., .../v0/management.
Returns 401/403 or other HTTP errors
- Confirm that the Management Key is correct and that the current account has permission to access the management interface.
- Check CLIProxyAPI backend logs to confirm if routes and methods (GET/PUT/PATCH) are enabled.
Will repeated imports generate many records?
- No. The plugin will look for existing providers based on base-url or name:
  - If it exists, only api-key-entries will be updated, and duplicate keys will be removed.
  - If it does not exist, a new provider will be created.

Usage Recommendations

It is recommended to verify the import effect on a small number of test accounts before using it in a production environment.
It can be used in conjunction with All API Hub's Quick Export feature to synchronize the same batch of upstream sites to various downstream systems such as New API / CLIProxyAPI.