> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/advanced-features/ai-character-builder.md).

# AI Character Builder

The AI Character builder allows you to create AI powered characters that users can talk to. This feature is available to Enterprise, Education and PRO customers.

These characters can be used as NPCs (non-player characters), tour guides, assistants and more. AI Characters can also be integrated into your experiences.

A full guide on how to create AI Characters can be found here:

{% file src="/files/RdQJIWnVmxztntw0ZiyT" %}

A guide on how to integrate AI Characters deeply into your Experiences can be found here:

{% file src="/files/Cl3FtxmhJoNyn7m0uclJ" %}


---

# 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.engagevr.io/engage/advanced-features/ai-character-builder.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.