> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/reference.md). # Reference - [Technical & support reference](https://docs.lleverage.ai/reference/technical-and-support.md): Technical lookup material for runtime behaviour, security review, compatibility and support. Operational and administrative guidance lives elsewhere. - [Runtime & security](https://docs.lleverage.ai/reference/technical-and-support/runtime-and-security.md): Technical reference for execution visibility and security-related runtime questions that do not belong in the everyday builder or operator path. - [Security reference](https://docs.lleverage.ai/reference/technical-and-support/runtime-and-security/security-and-performance.md): A conservative technical reference for reviewing access, credentials and data authority without substituting product documentation for formal assurance. - [Logging and monitoring reference](https://docs.lleverage.ai/reference/technical-and-support/runtime-and-security/logging-and-monitoring.md): Distinguish customer-facing execution Monitoring from deeper platform or security telemetry when investigating an operational or technical issue. - [Device Support & Compatibility](https://docs.lleverage.ai/reference/technical-and-support/device-support-and-compatibility.md) - [FAQ](https://docs.lleverage.ai/reference/faq.md) - [Product changelog](https://docs.lleverage.ai/reference/product-changelog.md): Current Lleverage product changes that materially affect how customers, operators and builders use the product. - [Historical release notes](https://docs.lleverage.ai/reference/historical-release-notes.md) - [August 2025](https://docs.lleverage.ai/reference/historical-release-notes/august-2025.md) - [June 2025](https://docs.lleverage.ai/reference/historical-release-notes/june-2025.md) - [May 2025](https://docs.lleverage.ai/reference/historical-release-notes/may-2025.md) - [April 2025](https://docs.lleverage.ai/reference/historical-release-notes/april-2025.md) - [March 2025](https://docs.lleverage.ai/reference/historical-release-notes/march-2025.md) - [February 2025](https://docs.lleverage.ai/reference/historical-release-notes/february-2025.md): Version 0.8 - - [January 2025](https://docs.lleverage.ai/reference/historical-release-notes/january-2025.md): Version 0.7 - - [December 2024](https://docs.lleverage.ai/reference/historical-release-notes/december-2024.md): Version 0.6 - - [November 2024](https://docs.lleverage.ai/reference/historical-release-notes/november-2024.md): Version 0.5 - - [October 2024](https://docs.lleverage.ai/reference/historical-release-notes/october-2024.md): Version 0.4 - - [September 2024](https://docs.lleverage.ai/reference/historical-release-notes/september-2024.md): Version 0.3 - 23 September 2024 - [August 2024](https://docs.lleverage.ai/reference/historical-release-notes/august-2024.md) - [July 2024](https://docs.lleverage.ai/reference/historical-release-notes/july-2024.md) - [Troubleshooting and support](https://docs.lleverage.ai/reference/troubleshooting-and-support.md): Use the product evidence available for an issue, separate operator, builder and administration problems, and escalate with enough context to investigate. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lleverage.ai/reference.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.