> 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/connectivity/ja/readme.md).
# 接続性
携帯電波またはWi‑Fiがあれば、どこでもVerkada製品を導入できます
**概要**\
Verkada Connectivity は、従来の配線が難しい場所で、ゲートウェイを使用して Verkada デバイスにネットワークと電源を提供します。ゲートウェイは、セルラーまたは WiFi 接続をサポートし、接続されたデバイスに PoE を供給できるため、カメラやその他の Verkada ハードウェアを遠隔地や屋外エリアに設置できます。
このコレクションでは、ゲートウェイの選定、設置、接続設定、そして安定した運用を維持するためのガイダンスを提供します。これにより、柔軟な電源およびネットワークオプションを必要とする拠点へ、Verkada の導入を拡張できます。
開始するには、次のリンクをご覧ください:
---
# 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/connectivity/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.