> For the complete documentation index, see [llms.txt](https://docs.avataar.ai/knowledge-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avataar.ai/knowledge-center/before-getting-started/3d-user.md).

# 3D User

Avataar’s Creator platform helps users by reducing both the time and cost needed to create 3D spatial experiences. 

**Benefits:**

* The traditional process of creating 3D experiences is time-consuming and expensive. It requires expertise in various 3D functions like modeling, texturing, animation and rendering along with different softwares.  
* In the Creator platform, users can easily bring AI or human generated 3D objects, rooms, text, and images. It provides various smooth transitions and animations, as well as pre-fabricated blocks along with a high quality render engine ensuring amazing final outputs, all through a single platform

**Related Topics:** 

* [How to use a template? ](/knowledge-center/creator/projects.md)
* [How to import a free 3D model?](/knowledge-center/creator/projects/object.md)
* [Watch Step by Step tutorial](https://youtu.be/EpAHVBViOIY)

<br>

<br>


---

# 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.avataar.ai/knowledge-center/before-getting-started/3d-user.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.