> 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/air-quality/ja/readme.md).
# 空気質センサー
施設内で起きていることを詳細なリアルタイムビューで確認する
**概要**\
Verkada 空気質センサーは、施設全体の空気質と環境条件を単一のインターフェースからモニターできるクラウド管理型デバイスです。CO₂、温度、湿度、微小粒子状物質 (PM)、VOC などの指標を測定し、健全で Safe な環境の維持に役立つリアルタイムの洞察を提供します。
このコレクションでは、センサーのインストールと設定、測定値のモニター、アラートの設定、信頼性の高い運用の維持に関する詳細なガイダンスを提供します。センサーを効率的にセットアップし、環境モニタリングを正確かつ確実に保つのに役立ちます。
始めるには、これらのリンクをご確認ください。
---
# 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://help.verkada.com/air-quality/ja/readme.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.