> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/sound-systems/ja/sound-systems.md).
# Sound Systems
Verkada Sound Systems は、あらゆる拠点でエンタープライズグレードの音楽、即時アナウンス、AI を活用した抑止を提供し、すべてを直感的なダッシュボードから一元管理できます。
**概要**\
Verkada Sound Systems は、商用ライセンスの音楽、即時アナウンス、AI を活用した抑止機能などを備えた、クラウド管理のエンタープライズ向けオーディオソリューションです。このプラットフォームは Alarms および Desk Station と連携し、単一の画面で建物全体をさらに統合します。
始めるには、こちらのリンクをご覧ください：
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.verkada.com/sound-systems/ja/sound-systems.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 `build a script that syncs our docs to a CMS` 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.