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

# Instruments

- [Instrument Library](https://docs.acestudio.ai/instruments/instrument-library.md): Browse AI instruments, unison presets, and third-party instrument plug-ins from the Instrument Library in ACE Studio.
- [Third-Party Instruments](https://docs.acestudio.ai/instruments/third-party-instruments.md): Load third-party VST3 and AU instrument plug-ins on Instrument Tracks in ACE Studio.
- [Create Instrument Sounds](https://docs.acestudio.ai/instruments/create-instrument-sounds.md): Learn how to use AI Instruments in ACE Studio.
- [Editing Notes](https://docs.acestudio.ai/instruments/create-instrument-sounds/editing-notes.md): Edit MIDI notes for AI Instruments in ACE Studio.
- [Articulations](https://docs.acestudio.ai/instruments/create-instrument-sounds/articulations.md): Discover ACE Studio AI Instrument articulations.
- [Expression Controls](https://docs.acestudio.ai/instruments/create-instrument-sounds/expression-controls.md): Discover ACE Studio AI Instrument expression controls.
- [Unison Mode for instruments](https://docs.acestudio.ai/instruments/create-instrument-sounds/unison-mode-for-instruments.md): Combine multiple AI instruments into a single unison track in ACE Studio.


---

# 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.acestudio.ai/instruments.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.