> 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/run-operations/agent/agent-faq.md).

# Agent FAQ

Answers to common questions about using, trusting and configuring the Lleverage Agent.

These questions come from customer onboarding, prospect conversations and day-to-day Agent use.

Choose the area that matches your question:

* **Everyday use** — what the Agent is for, Agent vs Workflow, voice, Channels and where to start.
* **Context, memory and learning** — what the Agent knows, what it remembers and how corrections become better future behavior.
* **Access, control and trust** — systems, credentials, permissions, approvals, verification and what happens when the Agent is wrong.
* **Building and automation** — Skills, self-serve building, how much setup is needed and when work becomes a Workflow.

The FAQ gives the short answer and links into the canonical documentation when you need more detail.


---

# 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/run-operations/agent/agent-faq.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.