> 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/playcanvas-toolkit/building-with-the-playcanvas-toolkit-legacy-v3/no-code-tools/media/audio.md).
# Audio
This document provides a guide that can be used to setup audio and extend the functionality of audio in a VIVERSE project.
***
### Media Audio
#### **Adding Audio and Extending Audio Functionality**
An audio clip has been added to the scene.
{% stepper %}
{% step %}
#### Setup audio
A. Create a new entity.
B. Click the **Edit Viverse Extension** button.
{% endstep %}
{% step %}
#### Add the audio module
A. In the VIVERSE extension, select the **Media** plugin for the **Select plugins** dropdown.
B. Select the **Audio** module and add it.
C. Add the audio to the **Asset** field.
D. Uncheck the **auto play** property to prevent the audio from starting when the avatar enters the environment.
{% endstep %}
{% endstepper %}
---
# 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/playcanvas-toolkit/building-with-the-playcanvas-toolkit-legacy-v3/no-code-tools/media/audio.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.
