> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/ai-and-agents/agents.md). # Agents What an agent is in ilert, and what the AI SRE and voice agents each do. **Agents** are ilert's autonomous components that execute complex reasoning loops and tool calls to perform end-to-end tasks. They are designed to **investigate, act, and collaborate** during incidents — securely and transparently.

Agent	Purpose	Example Actions
AI SRE	Root cause analysis Resolution and mitigation	Correlates data across logs, metrics, deployments, and GitHub commits to determine root cause. Executes or suggests mitigation steps (rollback, restart, or PR creation), updates status pages.
Voice Agent	Incident intake and call routing	Handles inbound calls via natural conversation, recognizes intent, gathers context, and routes call by intent.

--- # 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.ilert.com/ai-and-agents/agents.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.