> 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-payloads-and-accessories/start-with-survey-payload.md).
# Start with Survey payload
The Surveying Payload turns the Elios 3 into a fl ying mobile scanner that can fi t through openings as small as 50x50 cm, and create high-resolution scans beyond line of sight, to provide rapid insights that are not accessible with traditional tools or other UAV technologies. The high-resolution Ouster OS0-128 Rev 7 LiDAR sensor in combination with the world’s leading FARO Connect SLAM algorithm creates incredibly accurate 3D maps and digital twins of the most inaccessible spaces with centimeter precision.
| What's in the box | Elios 3 Surveying Payload |
| -------------------------------------- | :-----------------------: |
| Ouster OS0-128 Rev 7 LiDAR | 1 |
| LiDAR Mount | 1 |
| Dedicated connection cable for Elios 3 | 1 |
| Reflective targets | 6 |
{% hint style="info" %}
When you purchase the Survey payload, you gain access to online training for the Faro Connect software for two people. If you have not received your access code, please contact with your name, email address, company name, and country.
{% 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://knowledge.flyability.com/getting-started/start-with-payloads-and-accessories/start-with-survey-payload.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.
