Cherry Studio New API setup guide
Follow Cherry Studio’s official New API integration flow to add 穷哥么 with the OpenAI-compatible provider type and the API root URL.
Quick configuration
- Menu path
Settings → Model Providers → Add Provider- Provider type
OpenAI- This is the main path in the official online guide. If your newer build offers a dedicated New API option, you may use that instead.
- Name
qionggeme- API Key
The key created in the qionggeme token console- API URL
https://qionggeme.com- OpenAI-compatible requests use https://qionggeme.com/v1 in practice. A separately configured native Anthropic provider uses https://qionggeme.com.
This guide follows the main flow in Cherry Studio’s official online documentation: choose the OpenAI provider type when adding a provider. If your newer version also offers a dedicated New API option, you may select it; both use the same API key and URL rules below. First create an API key in the qionggeme token console.
Setup steps
Create and copy an API key
Open the qionggeme token console, create a token, and copy the key. Paste it into Cherry Studio’s API Key field later. Never put the secret in the provider name or API URL field.
Add a provider through the official menu path
In Cherry Studio, open Settings → Model Providers → Add Provider. Following the official online guide, choose OpenAI as the provider type. If your version offers a dedicated New API option, that is also acceptable. In either case, you will enter a name, API key, and API URL.
Enter the name, API key, and API URL
- Name:
qionggeme - API Key: paste the key you just created
- API URL:
https://qionggeme.com
This field must contain the root URL. Do not change it to
https://qionggeme.com/v1, and never add/docs.- Name:
Understand the configured URL and the actual protocol endpoints
Cherry Studio’s API URL field stays at
https://qionggeme.com. The client sends OpenAI-compatible requests throughhttps://qionggeme.com/v1. If you separately create a native Anthropic provider, its Base URL ishttps://qionggeme.com. These are fixed protocol-specific rules, not addresses to try at random.Enable the provider and test a request
Save the provider, turn on its Enable switch, and send a test request with an exact model ID that is currently available. Model availability may change, so check the model pricing page or the console model list. A normal response confirms that the setup works.
Configuration example
# Cherry Studio → New API Name: qionggeme API Key: your qionggeme API key API URL: https://qionggeme.com # Protocol-specific Base URLs OpenAI compatible: https://qionggeme.com/v1 Native Anthropic (when configured separately): https://qionggeme.com
Troubleshooting
The request returns 401 or says the API key is invalid
Copy the key again from the token console, remove any leading or trailing spaces, and confirm that the token is active, the account has sufficient balance, and the token can access the selected model.
The request returns 404 or the URL is not recognized
Use the OpenAI type from the official flow, or the dedicated New API option if your version provides it. In both cases, set API URL exactly to https://qionggeme.com without /v1 or /docs.
The client says the model does not exist or is unavailable
Check the current model ID on the model pricing page and make sure the spelling matches exactly. Do not keep using a retired or differently spelled ID.
The OpenAI and Anthropic URLs look inconsistent
That is expected. The OpenAI-compatible provider described here takes https://qionggeme.com in Cherry Studio’s API URL field and uses https://qionggeme.com/v1 as the actual OpenAI Base URL. A separately created native Anthropic provider uses https://qionggeme.com.
Ready to get started?
Create a qionggeme account, generate an API key, and access every currently available model.
Create an accountFrequently asked questions
Should Cherry Studio’s New API URL include /v1?
No. Following the official integration guide, enter https://qionggeme.com in that field. Cherry Studio sends OpenAI-compatible traffic through https://qionggeme.com/v1.
Can I use the content-site URL as the API URL?
No. The API URL must be https://qionggeme.com; never use the content-site address containing /docs.
What should I enter in the name field?
Use “qionggeme” so the provider is easy to recognize. Authentication and routing are controlled by the API key and API URL, not the display name.
Why do OpenAI and Anthropic use different actual Base URLs?
Their path conventions differ. OpenAI-compatible requests use https://qionggeme.com/v1, while native Anthropic requests use https://qionggeme.com. Configure each provider according to its protocol.
Where can I confirm the correct model name?
Use the current model IDs on the model pricing page or in the console. If a model no longer appears in the current data source, do not continue using the old ID.