> 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/ko/readme.md).

# 공기질 센서

시설에서 일어나고 있는 일을 상세한 실시간으로 확인하세요

**개요**\
Verkada Air Quality Sensors는 클라우드로 관리되는 장치로, 단일 인터페이스에서 시설 전반의 공기질과 환경 조건을 모니터링할 수 있게 해줍니다. 이 장치는 CO₂, 온도, 습도, 미세먼지(PM), VOC, 기타 지표를 측정하여 건강하고 안전한 환경을 유지하는 데 도움이 되는 실시간 인사이트를 제공합니다.

이 컬렉션은 센서 설치 및 구성, 측정값 모니터링, 알림 설정, 안정적인 운영 유지에 대한 자세한 가이드를 제공합니다. 이를 통해 센서를 효율적으로 설정하고 환경 모니터링을 정확하고 신뢰할 수 있게 유지할 수 있습니다.

시작하려면 다음 링크를 확인하세요:

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><a href="/air-quality/ko/getting-started/get-started-with-verkada-air-quality-sensors.md">Verkada 공기질 센서 시작하기</a></td></tr><tr><td></td><td><a href="/air-quality/ko/getting-started/quick-reference-guide-for-verkada-air-quality-sensors.md">Verkada 공기질 센서 빠른 참조 가이드</a></td></tr><tr><td></td><td><a href="/air-quality/ko/getting-started/air-quality-sensor-network-settings.md">공기질 센서 네트워크 설정</a></td></tr></tbody></table>


---

# 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/ko/readme.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.