> 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/licensing/verkada-product-warranty.md).

# Product Warranty

Learn about the product warranty for all Verkada products

At Verkada, we stand by our products and are pleased to offer warranties included with the purchase of your Verkada products. Full warranty details (including hardware) are outlined in our [End User Agreement](https://www.verkada.com/support/end-user-agreement/). This agreement defines our relationship with you and our services.

Our warranties are up to 10 years, depending on the model of your Verkada device. Please check the datasheet for your device for its specific warranty information, found on our [Docs](https://www.verkada.com/docs/?contentType=datasheet) page.

Reach out to our [Support team](http://verkada.com/support) anytime you need to use the warranty.

{% hint style="warning" %}
For all products, the primary warranty limitation is that they are not damaged due to an accident, abuse or misuse, acts of God, or any unauthorized use of the hardware.
{% 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/licensing/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.