> For the complete documentation index, see [llms.txt](https://knowledge.flyability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.flyability.com/getting-started/start-with-elios-3/download-install-and-connect-to-inspector.md).

# Download, install and connect to Inspector

Steps to download and install Inspector:

* [Download Inspector installer](/software/inspector/inspector-5.md)
* In your Download folder, install the file called InspectorSetup
* The first time you open Inspector, you will be asked to log in or register.
  * The license is attached to the drone and not to the user; this means that you can use the same login as for the activation of the drone. If another user want to install Inspector too, he can create a login for himself by clicking on “register.“
* Inspector training videos are available in the training simulator.


---

# 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://knowledge.flyability.com/getting-started/start-with-elios-3/download-install-and-connect-to-inspector.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.