> 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/experience-editor/tutorials/introductory-presentation/adding-other-ifx.md).
# Adding other IFX
ENGAGE includes a library of over 1200 IFX that you can use to enhance your presentations. However, if you want to use a custom 3D model, such as a company product or just something that isn’t in the library, you can import your own.
As an Enterprise client, you can request that ENGAGE staff upload a 3D model on your behalf, or you can use the ENGAGE SDK. For more information about the ENGAGE SDK, refer to the [developer documentation](https://docs.engagevr.io/developer/).
{% hint style="info" %}
If you have access to the Cloud File Manager, you can upload 3D models to share files in a Session or for testing purposes. However, because the Cloud File Manager is currently in a beta test phase, we don’t recommend that you load files from Cloud File Manager in experience files that will be shown to other users.
{% endhint %}
Example of an uploaded 3D model
The following sections describe how to add an IFX and include a basic animation.
---
# 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/experience-editor/tutorials/introductory-presentation/adding-other-ifx.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.
