> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/zh/wu-dai-ma-ti-yan/avatar-studio-experiences/customizing-your-avatar/publishing-an-experience.md).
# 发布 Avatar Studio 体验
了解如何发布并共享你定制的头像体验，以便在网页、自助终端、应用等场景中使用。
## **准备好与世界分享你的体验了吗？**
当你的角色和头像设置完成后，你可以直接从 Convai Character Creator 仪表板发布你的体验。
{% hint style="success" %}
**开始之前：**\
确保你的头像已 **保存** 并且角色已 **创建** 然后再前往 **发布** 选项卡。
{% endhint %}
***
## **发布步骤**
### 1. 前往 **发布** 你角色仪表板中的选项卡。
### **2. 完成你的体验**
填写必要的详细信息，以定义并展示你的模拟：
* **体验名称**\
例如： *消防站虚拟参观*
* **体验描述**\
例如： *通过你的虚拟导览员 Lina，更深入地了解消防站的内部运作！*
* **缩略图（可选）**\
上传一张图片来直观展示你的体验。
### 3. 选择可见性设置
选择体验的分享方式以及分享对象：
* **公开**
* 所有人可见
* 可通过 [**x.convai.com**](https://x.convai.com)
* **私密**
* 仅你和受邀用户可见
* **未公开列出**
* 未公开列出，但可通过直接链接访问
* **嵌入到你的网站** *（仅限企业版）*
* 直接将你的体验发布到你自己的网站
{% hint style="danger" %}
**Convai 像素流嵌入** 目前仅可通过 **企业版方案**。\
要了解如何将头像嵌入到你自己的平台，请查看 [嵌入文档](/api-docs/zh/cha-jian-yu-ji-cheng/convai-pixel-streaming-embed.md).
{% endhint %}
***
## **发布后**
一旦发布，你的体验就可以部署到：
* 网站
* 应用程序
* 自助终端系统
* 任何受支持的数字平台
***
{% content-ref url="/pages/e3b2574f41391a110a00219f0017e755c074458e" %}
[Convai Pixel Streaming 嵌入](/api-docs/zh/cha-jian-yu-ji-cheng/convai-pixel-streaming-embed.md)
{% endcontent-ref %}
---
# 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.convai.com/api-docs/zh/wu-dai-ma-ti-yan/avatar-studio-experiences/customizing-your-avatar/publishing-an-experience.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.
