> For the complete documentation index, see [llms.txt](https://cerebro-3.gitbook.io/cerebro-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cerebro-3.gitbook.io/cerebro-docs/ai-inference-marketplace/ai-agents.md). # AI Agents AI agents are an important part of the future Cerebro is designed for. Traditional software waits for a user to give it an instruction. An autonomous AI agent can perform tasks independently. An agent may need to: * Research information * Write software * Execute transactions * Analyse markets * Communicate with other agents * Use external APIs * Run continuously All of these activities can require inference. This creates a new problem: #### Who pays for the agent's intelligence? Cerebro aims to provide an economic layer that can eventually allow agents to manage and consume inference resources themselves. In the longer term, an agent could potentially have: * Its own inference balance * Spending limits * Access credentials * A wallet * The ability to select inference providers * The ability to pay for its own computation This creates the possibility of an economy where AI agents are not just users of software. --- # 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://cerebro-3.gitbook.io/cerebro-docs/ai-inference-marketplace/ai-agents.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.