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

# Garantía del producto

Obtén información sobre la garantía del producto para todos los productos de Verkada

En Verkada, respaldamos nuestros productos y nos complace ofrecer garantías incluidas con la compra de sus productos Verkada. Los detalles completos de la garantía (incluido el hardware) se describen en nuestro [Acuerdo de usuario final](https://www.verkada.com/support/end-user-agreement/). Este acuerdo define nuestra relación con usted y nuestros servicios.

Nuestras garantías son de hasta 10 años, según el modelo de su dispositivo Verkada. Consulte la hoja de datos de su dispositivo para obtener su información específica de garantía, disponible en nuestro [Documentación](https://www.verkada.com/docs/?contentType=datasheet) página.

Póngase en contacto con nuestro [equipo de soporte](http://verkada.com/support) cuando necesite utilizar la garantía.

{% hint style="warning" %}
Para todos los productos, la principal limitación de la garantía es que no estén dañados debido a un accidente, abuso o uso indebido, casos fortuitos o cualquier uso no autorizado del 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/es/licencias/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.