> For the complete documentation index, see [llms.txt](https://docs.viverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.viverse.com/standalone-app-publishing.md).

# STANDALONE APP PUBLISHING

- [Intro to Standalone App Publishing](https://docs.viverse.com/standalone-app-publishing/intro-to-standalone-app-publishing.md): This page overviews the requirements, tools, and process for building applications on VIVERSE.
- [Unity WebGL](https://docs.viverse.com/standalone-app-publishing/unitywebgl-examples.md): Code examples and compatibility guides for Unity WebGL builds on VIVERSE. This page covers packaging and upload. Gameplay APIs are in the VIVERSE Unity SDK.
- [ThreeJS](https://docs.viverse.com/standalone-app-publishing/three.js-with-vite-or-getting-started-tutorial.md): This document provides a guide for creating a sample app in Three.js, building the app with Vite and deploying the app to VIVERSE.
- [Godot HTML5](https://docs.viverse.com/standalone-app-publishing/godot-html5-example.md): This document provides a guide for exporting a Godot project for HTML 5 and publishing to VIVERSE.
- [Open Brush](https://docs.viverse.com/standalone-app-publishing/open-brush.md): This page details how to publish to VIVERSE from the VR illustration tool Open Brush.
- [Wonderland Engine](https://docs.viverse.com/standalone-app-publishing/wonderland-engine.md): Integration example of VIVERSE Avatar SDK with Wonderland Cloud networking for multiplayer VR experiences.


---

# 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.viverse.com/standalone-app-publishing.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.