> For the complete documentation index, see [llms.txt](https://docs.qubitro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qubitro.com/add-ons.md). # Add-Ons - [Storage Views](https://docs.qubitro.com/add-ons/storage-views.md): Storage Views allow you to create and manage multiple time series data views per device, enabling structured data storage beyond the default Time Series Storage. - [Aggregated View](https://docs.qubitro.com/add-ons/aggregated-view.md): Aggregated View allows you to store aggregated data separately from raw time series storage. - [Archived Views](https://docs.qubitro.com/add-ons/archived-views.md): Archived Views automatically archive device data at scheduled intervals per device, preserving historical records based on the selected schedule. - [Blob Storage](https://docs.qubitro.com/add-ons/blob-storage.md): Blob Storage in Qubitro allows devices to store binary data such as images, audio, logs, or other large objects. - [Managed Email](https://docs.qubitro.com/add-ons/managed-email.md): The Managed Email Add-on is an optional managed service that allows you to send customized emails directly within Qubitro, without integrating or managing any third-party email provider. - [AI Companion](https://docs.qubitro.com/add-ons/ai-companion.md) - [Audit Log](https://docs.qubitro.com/add-ons/audit-log.md): The Audit Log provides a detailed record of actions performed within your Qubitro account. - [MCP Server](https://docs.qubitro.com/add-ons/mcp-server.md) --- # 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.qubitro.com/add-ons.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.