> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-ai/ai-agent-configuration.md). # AI Agent Configuration The following section outlines the steps required to configure the AI agent. ### Agent Settings * Navigate to **`Global Settings`** -> Search for **`AI Agent Settings`** and click on **`Configure Settings`** action item. * Update the following settings based on the requirement - | Settings key | Description | | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`AI_AGENT_API_KEY`** | The authentication key issued by the AI agent provider. | | **`AI_PROVIDER`** | The name of the AI provider (e.g., **`ANTHROPIC`**, **`OPENAI`**). | | **`AI_MODEL`** | The specific model of the configured **`AI PROVIDER`** that will be used for code generation. | | **`VECTOR_DB_URL`** | The endpoint URL of the vector database service. | | **`VECTOR_DB_TOKEN`** | The authentication token used to access the vector database. | | **`VECTOR_DB_SEARCH_TOKEN`** | The token used specifically for search/query operations in the vector database. | | **`MULE_VECTOR_DB_COLLECTION_NAME`** | The name of the vector database collection containing MuleSoft related embeddings. | | **`API_VECTOR_DB_COLLECTION_NAME`** | The name of the vector database collection containing API related embeddings.. | | **`MULE_AGENT_VALIDATOR_CMD`** | The maven command to be executed for validating the project. | | **`MAVEN_SETTINGS_XML`** | The Maven settings.xml configuration used for dependency resolution and repository authentication. | | **`MULE_SPECIFICATIONS`** | Organization specific guidelines and standards that the AI agent must follow while generating the mule project. | | **`API_SPECIFICATIONS`** | Organization specific guidelines and standards that the AI agent must follow while generating the API specification. | | **`DOC_SPECIFICATIONS`** | Organization specific guidelines and standards that the AI agent must follow while generating the documentation. | | **`_TEMPLATE_URL`** | Location of the initial template to be used for generating the project. For Example - **`MULE_API_PROJECT_TEMPLATE_URL`** represents the template to be used for generating the mule project. This setting is application only while generating new projects and not while editing an existing project. | * Save the configuration. ### See Also * [Automation Tasks](/product-guides/integral-zone/iz-suite/iz-ai/automation-tasks.md) * [Automation Task Logs](/product-guides/integral-zone/iz-suite/iz-ai/automation-task-logs.md) --- # 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-ai/ai-agent-configuration.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.