> 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)
- [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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lleverage.ai/reference.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.
