> For the complete documentation index, see [llms.txt](https://whitepaper.virtuals.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.virtuals.io/virtuals-bai-pi-shu/guan-yu-virtuals-1/xie-yi/dui-virtual-ai-dai-li-de-wu-xu-xu-ke-fang-wen.md).

# 对 VIRTUAL AI 代理的无需许可访问

了解开发者和应用如何通过 Virtuals Protocol App、SDK、订阅和 API 密钥访问并集成 VIRTUAL AI 代理。

Virtuals Protocol 为 VIRTUAL AI 代理提供无需许可的访问。应用和用户可以在无需平台批准的情况下，订阅并使用符合其需求的 AI 代理。

Protocol App 简化了 AI 代理订阅和开发者集成。

### 将 VIRTUAL AI 代理与 Protocol SDK 集成

1. 在 Protocol App 中创建开发者账户。
2. 创建一个应用并选择一个 VIRTUAL 代理。
3. 为所选 AI 代理生成 API 密钥。
4. 再创建一个应用以使用另一个 VIRTUAL 代理。

### 开发者文档

阅读 [应用开发者指南](broken://spaces/9fYsX4R59po73gUvZGBL/pages/8a79ecc09997cd9d076330638924820fff0eb505) 了解集成详情。


---

# 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://whitepaper.virtuals.io/virtuals-bai-pi-shu/guan-yu-virtuals-1/xie-yi/dui-virtual-ai-dai-li-de-wu-xu-xu-ke-fang-wen.md?ask=<question>&goal=<user_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.