> 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/pre-basic/providers.md).

# 模型服务

Cherry Studio 内置 60+ 家 Provider（模型服务商）的连接模板，覆盖国内外大部分主流模型与本地推理框架。本节为每家 Provider 提供独立配置指南。

### Provider 类型

Cherry Studio 把 Provider 按协议分为以下几类，行为略有差异：

| 类型               | 兼容协议                      | 典型代表                                            |
| ---------------- | ------------------------- | ----------------------------------------------- |
| **OpenAI 兼容**    | `/v1/chat/completions`    | OpenAI、DeepSeek、硅基流动、OpenRouter、绝大多数三方网关        |
| **Anthropic 兼容** | `/v1/messages`            | Anthropic、CherryIN、部分网关。**Cherry Agent 需要此类型**  |
| **Gemini**       | Google AI Studio / Vertex | Google Gemini、Vertex AI                         |
| **Bedrock**      | AWS Bedrock SDK           | AWS Bedrock                                     |
| **Azure OpenAI** | Azure OpenAI Service      | Azure OpenAI                                    |
| **本地推理**         | 本地 HTTP 服务                | Ollama、LM Studio、GPUStack、OpenVINO Model Server |
| **特殊网关**         | 厂商私有协议                    | NewAPI、OneAPI、AiHubMix、DMXAPI 等                 |

### 添加一个 Provider 的通用步骤

1. 打开 `设置 → 模型服务`
2. 在内置 Provider 列表中找到目标 Provider，点击进入详情页
3. 填写 **API 密钥**（必填），按需修改 **API 地址**（默认是 Provider 官方地址）
4. 点击 **获取模型列表**，按需添加你常用的对话/嵌入/视觉模型
5. （可选）点击 **检测**，用任一对话模型验证连接是否成功

### Provider 配置详解

#### 通用/网关类

* [CherryAI (免费)](/pre-basic/providers/cherryai.md)
* [CherryIN](/pre-basic/providers/cherryin-1.md) — 双端点（OpenAI + Anthropic），Cherry Agent 推荐
* [NewAPI](/pre-basic/providers/newapi.md) / [OneAPI](/pre-basic/providers/oneapi.md) — 自建/三方网关

#### 海外厂商

* [OpenAI](/pre-basic/providers/openai.md)
* [Google Gemini](/pre-basic/providers/google-gemini.md)
* [Vertex AI](/pre-basic/providers/vertex-ai.md)
* [GitHub Copilot](/pre-basic/providers/github-copilot.md)
* [MiniMax Coding Plan](/pre-basic/providers/minimax-coding-plan.md)

#### 国内厂商

* [阿里云百炼](/pre-basic/providers/a-li-yun-bai-lian.md)
* [硅基流动](/pre-basic/providers/siliconcloud.md)
* [火山引擎（豆包）](/pre-basic/providers/doubao.md)
* [华为云](/pre-basic/providers/huawei.md)
* [无问芯穹](/pre-basic/providers/wu-wen-xin-qiong.md)
* [PPIO 派欧云](/pre-basic/providers/ppio.md)
* [ModelScope（魔搭）](/pre-basic/providers/modelscope.md)

#### 本地推理

* [Ollama](/pre-basic/providers/ollama.md)

#### 自定义服务商

* [自定义服务商](/pre-basic/providers/zi-ding-yi-fu-wu-shang.md) — 任意 OpenAI / Anthropic / Gemini 兼容端点

{% hint style="info" %}
**没找到你用的 Provider 怎么办？**

Cherry Studio 内置 60+ Provider 模板，但**远多于本节文档已收录**的数量。如果你用的是 Anthropic（Claude）、Azure OpenAI、DeepSeek 官方、Grok、Groq、LM Studio、OpenRouter、Mistral、Perplexity、Together 等，**它们都在 Provider 列表里**，直接添加密钥即可。本节文档将分批补齐这些 Provider 的专题页。
{% endhint %}

### API 密钥与 API 地址

详见 [模型服务设置](/pre-basic/settings/providers.md)（含 多 Key 轮询、`#` 结尾固定路径等高级用法）。

***

### 💡 获取帮助与提交反馈

如果您在配置或使用过程中遇到任何疑问、Bug 或有功能改进建议，请参考 [反馈与建议](/question-contact/suggestions.md) 中提供的官方渠道。


---

# 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/pre-basic/providers.md?ask=<question>&goal=<endgoal>
```

`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.