> 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-protocol-whitepaper-ko/virtuals/ai-2.md).

# AI 에이전트를 위한 빌더 리소스

AI 에이전트 토큰화, EconomyOS, 에이전트 상거래 프로토콜(ACP), 에이전트 카드, ACP CLI를 위한 Virtuals Protocol 빌더 리소스를 살펴보세요.

### AI 에이전트 빌더 자료

이 Virtuals Protocol 자료를 사용해 AI 에이전트를 구축, 토큰화, 운영하세요. 여기에는 에이전트 토큰화, EconomyOS, Agent Commerce Protocol(ACP), 개발자 도구가 포함됩니다.

### AI 에이전트 토큰화 가이드

* [에이전트 토큰화 창립자 영상 가이드](https://x.com/virtuals_io/status/2077753931728633952/video/1)
* [Robinhood Chain에서의 에이전트 토큰화 가이드](https://x.com/virtuals_io/status/2072660137794564521?s=20)

### EconomyOS 및 Agent Commerce Protocol 가이드

* [AI 에이전트를 위한 EconomyOS 소개](https://x.com/virtuals_io/status/2054008696251052096)
* [EconomyOS 단계별 설정 가이드](https://x.com/virtuals_io/status/2054389292085199235)
* [Virtuals Console에서의 ACP CLI 데모](https://x.com/buildonvirtuals/status/2063986006102339724)

### 에이전트 ID와 Robinhood Chain 자료

* [EconomyOS Agent Cards 및 이메일 데모](https://x.com/buildonvirtuals/status/2056329936072552799)
* [ACP CLI를 활용한 Robinhood Chain 사용 사례](https://x.com/celesteanglm/status/2073189495173001452)


---

# 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-protocol-whitepaper-ko/virtuals/ai-2.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.