> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user/ai-dashboard/train-an-ai-agent-with-our-data-or-docs-or-file.md).

# Train an AI Agent with our data or docs or file

### Step 1: Select Your AI Agent

* Go to the "AI agents" section in your dashboard.​
* Choose the specific agent you want to train.​

### Step 2: Upload Your File

* Click on the "Upload File" button for your chosen agent.​
* Drag and drop your file into the upload area, or select it manually from your device.​
* Ensure the file name does not contain spaces; use underscores if needed.​

### Step 3: Start the Upload

* Click "Upload" after selecting your file.​
* The upload may take seconds or minutes, depending on the file size and number of pages.​

### Step 4: Training Completion

* Once the file is uploaded, the AI agent is automatically trained using the content from your file.​

### Step 5: Add More Files (Optional)

* You can repeat the process to add multiple files to the same AI agent for additional training.​

{% embed url="<https://youtu.be/o5xyws1rmpI>" %}


---

# 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://helpdocumentation.gitbook.io/user/ai-dashboard/train-an-ai-agent-with-our-data-or-docs-or-file.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.