> For the complete documentation index, see [llms.txt](https://docs.valohai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valohai.com/project-gallery/nlp-and-llm/rag-doc-example.md).

# End to end RAG pipeline with Documentation

## Overview

This example shows how to build your own RAG Doctor :woman\_health\_worker::

* Build an embeddings database from documentation CSVs
* Query the database with LLMs
* Serve the RAG model as an API endpoint

### Steps

{% stepper %}
{% step %}
**Data Preparation**

Compile CSV documentation and create an embeddings database, ensuring data is organized for efficient retrieval.
{% endstep %}

{% step %}
**Embedding Database**

Utilize Large Language Models (LLMs) to build and query the embeddings database effectively.
{% endstep %}

{% step %}
**API Deployment**

Configure and deploy the RAG model as an API endpoint to facilitate seamless interaction and integration.
{% endstep %}
{% endstepper %}

### GitHub Repository

The repository walks you through how to go through the above steps:

{% embed url="<https://github.com/valohai/rag-doc-example>" %}


---

# 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.valohai.com/project-gallery/nlp-and-llm/rag-doc-example.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.