> For the complete documentation index, see [llms.txt](https://docs.gremsy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gremsy.com/gimbals/pixy-we/getting-started/features.md).

# Features

### **SUPPORT MULTIPLE DRONE PLATFORMS**

Pixy WE can be integrated with DJI M300 (via gPort) or drones using Pixhawk/ Cube Pilot FC.

Supported features:

<figure><img src="https://3309772875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnikHUDUd2JXqkOsnOi7l%2Fuploads%2F5kxHVGJKonhB1CNqWdRb%2F1.PNG?alt=media&amp;token=500a65b6-f075-4e4e-a852-bde270d74ca8" alt=""><figcaption></figcaption></figure>

### **OPTIMIZED IN SIZE & WEIGHT FOR LONG FLIGHT TIME**

It is specifically optimized for the Wiris Enterprise Camera. No balancing is required; setup and deployment occur within seconds.

### **BUILT-IN ADVANCED FUNCTIONS FOR INDUSTRIAL MISSIONS**

Pixy WE and the Wiris Enterprise camera work together perfectly with built-in functions for aerial imaging capabilities, ideally for thermal inspections, security applications, firefighting, geological, archeological, and forestry studies, as well as ecological and environmental research.

### **PRICE & AVAILABILITY**

Pixy WE will be available for delivery from January 5, 2023, in limited quantity. Please order directly on our website, or get in touch with us [HERE](https://gremsy.com/contact) if you require further assistance.


---

# 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.gremsy.com/gimbals/pixy-we/getting-started/features.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.
