> For the complete documentation index, see [llms.txt](https://docs.deltaquad.com/evo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deltaquad.com/evo/introduction.md).
# Introduction
This document describes how to set up, operate, and maintain your DeltaQuad Evo series VTOL UAV.
Document status: DRAFT
## Safety and legal notice
* The vehicle must be operated in accordance with local laws and regulations.
* The vehicle may not be operated or flown near or over people, roads, vehicles, buildings, or anything that could result in damage or danger to people or property.
* Radio or video transmitters might require special licensing and/or permits.
* DeltaQuad or its affiliates can not be held responsible for vehicles that have not been operated or maintained in accordance with the guidelines set forth in this manual, or for behavior resulting from changes made to the vehicle.
* This operations manual is provided "As-Is". No rights can be obtained from the contents of this manual.
* The original language of this document is English, if this document is read in a translation to any other language, the interpretation of the English version takes precedence.
* Software used in conjunction with the vehicle is provided under their respective license and warranty.
* The vehicle is provided in accordance with the DeltaQuad [Warranty](https://www.verticaltechnologies.com/info/warranty-and-support) and under the DeltaQuad [Terms & Conditions](https://www.verticaltechnologies.com/info/terms-conditions).
* The DeltaQuad Evo is not a toy and is not suitable for people under the age of 16.
---
# 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://docs.deltaquad.com/evo/introduction.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.
