> For the complete documentation index, see [llms.txt](https://docs.cherryai.com.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cherryai.com.cn/docs/en-us/pre-basic/settings/websearch/volcengine.md).
# Online access via Volcano Engine
A hand-holding tutorial on using Cherry Studio with Volcano Engine to access DeepSeek R1 online features.
### 1. Log in/Register a "Volcengine" account
Visit the official website:
Volcengine official website
### 2. Create a "network-enabled" "My App"
2.1. Log in to Volcengine and go to the "Volcano Ark" page. Portal:
2.2. **Click in order:****"My Apps" - "Create App" - "No-code" - "One-on-one chat"**
### 3. Fill in the information and publish the app
**App name**: Just give it any name as required. (With**\*required**, the rest can be left blank)
**Key point: the network plugin must be enabled (it needs to be activated first)**
#### 3.1. Activate the network plugin feature (note the cost and free usage count)
Click Buy Now and follow the steps until the interface below appears, which means activation was successful.
Pay attention to the status; activation is now successful
Then return to the "Fill in app information" page and continue.
#### 3.2. Network search "Advanced configuration" instructions
Choose according to the actual situation; my personal recommendation:
* If you want precise control over input and output, you can use "**Custom invocation**" network access;
* If you want to avoid trouble, you can leave it unchanged and use "**Automatic invocation**" - default value;
* If cost is not an issue and you have very high requirements for information timeliness, you can "**Force enable**".
#### 3.3. Publish the app
Click the "Publish" button in the top right corner, and the app will be created successfully.
### 4. Get API Key
Click in order:**"API Invocation Guide" - "Select API Key and Copy" - "View and Select"**
Copy the API key first, then paste it into Cherry Studio. (See the interface below for details.)
Note: If you don't have an API key, in the top right corner of the pop-up window - "**Create API Key**", then just copy the API key.
### 5. Use the API key in Cherry Studio to enable network access to DeepSeek-R1
#### 5.1. Open Cherry Studio - "Settings" - "Enter any name" - "Type: openAI"
#### 5.2. Configure the URL and key
Note: If you can't find the address, or it's not a Beijing node, you can find the specific address here. Don't forget the "/":
#### 5.3. Add the model name
Note: copy the small text below as the model name, otherwise an error will occur.
### 6. Preview of the result
***
### 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) for the official channels provided.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.cherryai.com.cn/docs/en-us/pre-basic/settings/websearch/volcengine.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)