> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/giot-by-gimasi.md). # GIoT by Gimasi English Guide Books
Journey to Getting Started with GIoTDALL·E 2024-12-09 11.13.25 - A realistic and text-free image representing an IoT environment with a step-by-step progression concept. The design should feature elements like smart.webpJourney to Getting Started with GIoT
Cover image
Platform User Guide BookPlatform User guide bookUntitled-6.png
Level Meter Full Device Guide BookLevel Meter Full Device Guide Booklanding page device LM.png
Low Cost Tracker Full Device Guide BookLow Cost Tracker Full Device Guide BookGuideBookLCT.png
Low Cost Tracker - Device Transport RulesLow Cost Tracker- Device Transport Rulesimage.png
Level Meter - Device Transport RulesLevel Meter- Device Transport Rulesimage.png
.PDF Guide BOOKsGuide Books .pdfImmagine 2024-11-29 170001.png
.PDF ConceptualConceptual .pdfImmagine 2024-11-29 170209.png
.PDF TechnicalAPI documetation.pdfimage.png
FAQs -FAQs - PlatformImmagine 2024-12-02 165250.png
--- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.g-iot.io/giot-by-gimasi.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 `build a script that syncs our docs to a CMS` 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.