All API HubAll API Hub
Homepage
Getting Started
Frequently Asked Questions
Changelog
  • 简体中文
  • English
  • 日本語
Homepage
Getting Started
Frequently Asked Questions
Changelog
  • 简体中文
  • English
  • 日本語
  • 🚀 Getting Started

    • Getting Started
    • Overview (Main Dashboard of the Settings Page)
    • Permission Management (Optional Permissions)
    • Installation Channels and Updates
    • Safari Extension Installation Guide
    • Other Browser Installation Guide
  • 🔑 Accounts & Credentials

    • Add Accounts
    • Account Management
    • Service Guides
    • Managing FennoAI API Assets with All API Hub
    • Managing XuanShu API Assets with All API Hub
    • Manage Suixiang AI Relay with All API Hub
    • API Credential Library
    • Key Management
    • Bookmark Management
    • Sorting Priority Settings
  • 📊 Analytics & Dashboard

    • Balance History
    • Usage Analysis
    • Share Snapshot
    • Model List and Price Comparison
    • Automatic Refresh and Real-time Data
  • 🤖 Automation Helpers

    • Automatic Check-in and Check-in Monitoring
    • Site Announcements
    • Task Notifications
    • Redemption Assist
    • Web AI API Sniffing and Verification
    • Cloudflare Shield Bypass Assistant
  • 🔌 Ecosystem & Integrations

    • Supported Site List
    • LDOH Site Lookup
    • Supported Export Tools List
    • Quick Export Site Configuration
  • 🛠️ Admin Management

    • Managed Site Model Sync
    • Self-Hosted Site Management
    • CLIProxyAPI Management
    • Model Redirect
    • New API Security Verification
  • 🛡️ Data & Support

    • Data Import and Export
    • Cloud Backup and Automatic Sync
    • All API Hub Privacy Policy
    • Troubleshooting Guide for Auto-Identification
    • Developer & Advanced Tools
    • Frequently Asked Questions
  • Changelog

Self-Hosted Site Management

Bring the accounts you already use in the extension into your self-hosted site without copying URLs and keys again. Once connected, you can use your own API to access them, then manage settings, update models, and move channels to another site from the extension.

Supported System Types

All API Hub is deeply adapted to the following open-source/self-hosted AI distribution systems:

System TypeCore Management ObjectFeatures
CLIProxyAPIProvidersManage upstream providers, credentials, and model mappings.
New API / Veloera / DoneHubChannelClassic channel management, supporting 55+ upstream types, with group, priority, and weight systems.
Sub2APIAccountUnified access and shared management for Claude, OpenAI, Gemini, Antigravity, and other subscriptions.
AxonHubChannelHigh-performance AI gateway, supporting 15+ channel types, with a simple interface and efficient configuration.
Claude Code HubProviderFocused on multi-vendor access and elastic scheduling, with clear provider management logic and adaptation to multiple response protocols.
OctopusChannelLightweight aggregation service for individuals, supporting 6 mainstream channel types.

Features at a Glance

  • 🔑 Use Your Own API for Multiple Accounts: Connect your self-hosted site, then choose the keys you want in "Key Management" and import them as channels, individually or in bulk. URLs and keys are filled in for you, saving repeated copying and typing.
  • 📋 Make Channel Changes in the Extension: When you need to add a channel or change settings, open the extension's channel list. Select channels you no longer need to delete them together, and switch sites here when you manage more than one.
  • 🔄 Let the Extension Keep Up with Model Updates: You can sync model lists for one channel or several at once. Turn on scheduled sync to have the extension update them at the interval you choose, then check the sync results.
  • 📦 Take Your Channels with You When Switching Sites: Choose the channels and destination, then use Channel Migration (Beta) to copy them over. The preview shows which settings can be kept and which need attention, so you can review them before starting and save yourself repeated setup.

What you can do depends on the site you select. Check the available actions and guidance on its page.

Configuration Guide

Before using the management features, you need to complete the connection configuration for the corresponding backend in the extension.

1. Access the Configuration Page

Open the extension settings page, go to "Basic Settings" in the left menu, and find "Self-Hosted Site Management".

2. Fill in Connection Information

OptionDescription
Base URLYour self-hosted system's backend address (usually the web access address).
Authentication CredentialsCLIProxyAPI: Management key.
New API Series: Requires Admin Token and User ID.
Sub2API: Admin API Key (if key access requires additional web verification, the extension cannot view or export keys or migrate channels out).
AxonHub: Admin email and password.
Claude Code Hub: Admin email and password.
Octopus: Username and password.

3. Verify Connection

Click "Verify Configuration". After successful verification, the management entrance for the corresponding system will be automatically unlocked.

Channel Management Operating Guide

1. List Operations

Select "Self-Hosted Site Management" at the top of the settings page (or click the "Manage Channels" button in basic settings):

  • Search and Filter: Supports real-time search by name, type, and status.
  • Quickly Switch Systems: If you have configured multiple self-hosted systems, you can quickly jump between them using the switcher at the top.
  • Custom Columns: For systems that do not support "Priority" or "Weight" (such as Octopus), the corresponding columns will be automatically hidden.

2. Create or Edit Channels

  1. Click Add Channel or open an existing channel for editing.
  2. Fill in connection, model, and group information for the current system. Expand advanced settings when needed:
    • New API: Model detection and automatic sync, model mappings, proxies, and related options.
    • DoneHub: Model mappings, custom headers, Responses compatibility, and related options.
    • For other systems, follow the form prompts. Available options depend on the channel.
  3. Enter or adjust keys in the key section. Supported New API, Octopus, AxonHub, and CLIProxyAPI channels allow individual management of multiple keys while retaining unchanged keys. New API also offers random or round-robin selection.
  4. Review and save. If reading an existing key requires verification, complete it as prompted.

3. Security Verification (2FA / OTP)

When performing sensitive operations (e.g., viewing a channel's real key), if the system has secondary verification enabled, the extension will pop up a verification window.

  • For details, see: New API Security Verification

4. Channel Migration (Beta)

Copy channels from the current self-hosted site to another configured site without recreating each one manually. Configure connections for both sites before starting.

  1. Enable "Channel Migration" on the source site's channel list, then select channels or use the current filtered results.
  2. Choose the target site. Review the preview for changes to types, URLs, models, groups, and statuses, along with settings that cannot be preserved.
  3. Click "Start migration" and confirm. The extension reads each source channel's key and creates a channel on the target site.
  4. Check each result. If a result is "Uncertain", refresh the list and inspect the target site before deciding whether to retry, to avoid duplicates.

Migration only creates new channels. It does not modify the source, detect duplicates, overwrite existing channels, or roll back changes automatically.

Multi-key channels: The preview compares source and target key counts. New API, Octopus, AxonHub, and supported CLIProxyAPI API-key providers can export their complete key lists. If the target can retain the keys and their enabled states together, migration creates one multi-key channel. Otherwise, it creates a channel per key, appends [Key 1], [Key 2], etc. to the names, and reports each result separately. Splitting may change traffic distribution.

Key enabled states are preserved, but rotation policies, disable reasons, runtime history, and provider-specific per-key proxy or weight settings may not be retained. Check the preview warnings. A source that cannot export all keys is blocked. If key counts or enabled states change during execution, refresh the preview before handling unfinished items. Successful creations are never retried automatically.

Supported channel types and settings vary by system; follow the statuses and guidance in the migration preview. Groups, model mappings, priorities, and other settings may change or be omitted. After migration, check the channel settings and enabled status on the target site.

If prompted to complete verification before reading a source key, do so and retry. If the required verification method is not supported, retrieve the key from the source dashboard and add the channel manually on the target site.

FAQ

QuestionSolution
Configuration verification failedPlease confirm if the Base URL is entered correctly (including https://) and if the administrator permissions are valid. Some systems require disabling two-step verification or using a specific API token.
List loads slowlyWhen the number of channels is large (>100), loading may take a few seconds due to backend API performance limitations; please be patient.
Unable to sync modelsPlease confirm if the backend network of the self-hosted site can normally access the upstream addresses (such as OpenAI / Claude official sites).
Some fields show UnknownThis is usually because the version of the self-hosted site is too new or too old, returning a type ID that the extension hasn't yet adapted to.

Related Docs

  • Managed Site Model Sync: Automatically batch sync channel models.
  • Quick Export and Integration: Learn how to push channels to downstream applications.
  • Supported Sites List: View more compatible systems.
Last Updated: 9/13/26, 5:19 PM
Contributors: anime, github-actions[bot], qixing-jk
Prev
Managed Site Model Sync
Next
CLIProxyAPI Management