> For the complete documentation index, see [llms.txt](https://defai-solyai.gitbook.io/solyai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://defai-solyai.gitbook.io/solyai/the-soly-ai-ecosystem/the-ecosystem/agent-builder-customization-and-scalability.md).

# Agent Builder: Customization and Scalability

The Agent Builder empowers users and developers to create and deploy tailored AI agents.

* No-Code Interface: Users can design agents by defining their roles, expertise, and instructions, without needing technical expertise.
* Advanced Tooling: Developers can integrate specialized tools, such as data retrieval, on-chain analytics, and financial modeling, to enhance agent capabilities.
* Flow Design: Comprehensive design options allow the creation of multi-step workflows, enabling agents to handle intricate operations like yield farming or multi-chain asset bridging.

Agents created through the Agent Builder can be shared within the Agent Hub, fostering innovation and monetization opportunities for creators.

<br>


---

# 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://defai-solyai.gitbook.io/solyai/the-soly-ai-ecosystem/the-ecosystem/agent-builder-customization-and-scalability.md?ask=<question>&goal=<endgoal>
```

`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.