> For the complete documentation index, see [llms.txt](https://docs.cherry-ai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cherry-ai.com/docs/en-us/pre-basic/settings/providers.md).
# Model Services Settings
This page only introduces the interface functions; for configuration tutorials, please refer to the [Service Provider Configuration](/docs/en-us/pre-basic/providers.md) tutorial.
{% hint style="info" %}
* When using a built-in provider, you only need to enter the corresponding secret key.
* Different providers may use different names for the secret key; secret key, Key, API Key, token, etc. all refer to the same thing.
{% endhint %}
### API Secret Key
In Cherry Studio, a single provider supports round-robin use of multiple keys, cycling through the list from top to bottom.
* Add multiple keys separated by English commas, as in the following example:
sk-xxxx1,sk-xxxx2,sk-xxxx3,sk-xxxx4
{% hint style="warning" %}
Must use **English** comma.
{% endhint %}
### API address
When using a built-in provider, you generally do not need to fill in the API address; if you need to modify it, please strictly use the address provided in the corresponding official documentation.
> If the address provided by the provider is /v1/chat/completions in this format, just fill in the root address part () is sufficient.
>
> Cherry Studio will automatically append the remaining path (/v1/chat/completions) Failing to enter it as required may result in it not working properly.
{% hint style="info" %}
Note: the large language model routing of most providers is unified, so in general you do not need to perform the following operation. If the provider's request route is not the usual /v1/chat/completions one, you can manually enter in the API address field **the full API address**, and end with `#`it.
That is:
* When the API address uses `#` as the ending, no concatenation will be performed; only the entered address will be used. 
{% endhint %}
### Add model
In general, click the `Manage` button at the bottom left of the provider configuration page to automatically fetch all models supported by the provider, then click the `+` icon in the fetched list to add them to the model list.
{% hint style="info" %}
When clicking the Manage button, not all models in the popup list will be added; you need to click the `+` , only after adding it to the model list on the provider configuration page can it appear in the model selection list.
{% endhint %}
### Connectivity check
Click the Check button after the API Secret Key input box to test whether the configuration was successful.
{% hint style="info" %}
When checking a model, it uses by default the last chat model in the model list; if the check fails, please verify whether the model list contains incorrect or unsupported models.
{% endhint %}
{% hint style="danger" %}
After configuration succeeds, be sure to turn on the switch in the top right; otherwise the provider will remain disabled and the corresponding models cannot be found in the model list.
{% endhint %}
***
### 💡 Get help and submit feedback
If you encounter any questions, bugs, or have suggestions for feature improvements during configuration or use, please refer to [Feedback and Suggestions](/docs/en-us/question-contact/suggestions.md) the official channels provided there.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.cherry-ai.com/docs/en-us/pre-basic/settings/providers.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.