> 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/command/ja/raisensu/verkada-product-warranty.md).

# 製品保証

すべてのVerkada製品の製品保証について学ぶ

Verkadaでは、当社は製品に自信を持っており、Verkada製品のご購入に含まれる保証を提供できることを嬉しく思います。完全な保証内容（ハードウェアを含む）は、当社の [エンドユーザー契約](https://www.verkada.com/support/end-user-agreement/). この契約は、お客様と当社の関係および当社のサービスを定義するものです。

当社の保証期間は、お使いのVerkadaデバイスのモデルによっては最長10年です。デバイスの個別の保証情報については、当社の [ドキュメント](https://www.verkada.com/docs/?contentType=datasheet) ページ。

当社の [サポートチーム](http://verkada.com/support) 保証をご利用いただく必要があるときはいつでも。

{% hint style="warning" %}
すべての製品において、主な保証の制限は、事故、乱用または誤用、天災、あるいはハードウェアの無断使用によって損傷していないことです。
{% endhint %}


---

# 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/command/ja/raisensu/verkada-product-warranty.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.