Tool Integration

Configure AIFast in Chatbox and Cherry Studio

Add OpenAI Compatible custom providers for Chatbox and Cherry Studio, configure AIFast API Key, API address and model ID, and troubleshoot model list, address splicing and connection testing issues.

Updated on 2026-07-15Checked 2026-07-15Estimated reading time: 8 minutesAvailable for desktop clients that support custom OpenAI Compatible vendors
Configuration fields were checked against public documentation. Models, prices, and capabilities can change; verify current values in the console and live API responses.
Special topic: AI development tool custom API access center

Common configuration parameters

Field Recommended value
Supplier type OpenAI Compatible / Custom OpenAI
API Key Independent Key created by AIFast console
Base URL https://www.aifast.club/v1
Model ID from /v1/models Return result copy

Verify before configuring:

curl https://www.aifast.club/v1/models \
  -H "Authorization: Bearer $API_KEY"

Chatbox configuration ideas

  1. Open the model provider or model settings.
  2. Choose OpenAI API or OpenAI Compatible custom service.
  3. Fill in the API Key and Base URL.
  4. Add the real model ID manually, or refresh the model list.
  5. After saving, create a new session for minimal testing.

If Chatbox will automatically append /v1, the address should be adjusted based on connection testing or request logs to avoid /v1/v1

Cherry Studio configuration ideas

  1. Go to "Settings/Model Services".
  2. Add custom suppliers.
  3. Select the OpenAI Compatible method.
  4. Fill in the API Key and API address.
  5. Use the Manage or Add Model function to enter the real model ID.
  6. Perform a connection check and set the model as the assistant default model.

The client interface will be updated. If the menu name is different from this article, you should look for similar fields such as "Model Service", "Supplier", "API Address", "Custom Model", etc.

Connection test passed but unable to chat

Connection tests may only check domain names, certifications, or model lists. Keep checking:

  • Whether the model actually selected in the session is consistent with the added model.
  • Whether the model ID contains extra spaces or a Chinese name.
  • Request whether to enter /v1/chat/completions
  • Whether the current model supports images, tool calls, or long contexts.

401, 404 and model not found

  • 401: Check API Key and Bearer authentication.
  • 404: Check Base URL and client automatic splicing rules.
  • model not found: Requery /v1/models, copy the real id
  • Return HTML: The request did not enter the API route.

Multi-device use

Different devices use independent keys to facilitate statistics, quotas and revocation. Do not pass keys via public sync services, chat logs, or screenshots.

Source checked

Reference and Check Sources

Next step

Check the model and price first, then create an independent test Key

The model ID, open status and price will change; it will be added to production after passing small-scale verification.

Model PricingCreate Account View API documentation