# Building a Search Assistant

Creating a search assistant can be approached in various ways depending on the different requirements and levels of complexity. In this guide, we’ll explore three main approaches to building a search assistant:

1. [**Single Agent with a Clear Role**](https://app.gitbook.com/o/vHUGvM3XTUTApXWHNTrY/s/TbBxR0Ob7RUmbvHZkQi2/~/changes/82/examples/building-a-search-assistant/approach-1-single-agent-with-a-defined-role) – А streamlined, straightforward method.
2. [**Adaptive Orchestrator with Multiple Agents**](https://app.gitbook.com/o/vHUGvM3XTUTApXWHNTrY/s/TbBxR0Ob7RUmbvHZkQi2/~/changes/82/examples/building-a-search-assistant/approach-2-adaptive-orchestrator-with-multiple-agents) – А multi-agent system with dedicated roles.
3. [**Custom Logic Pipeline**](https://app.gitbook.com/o/vHUGvM3XTUTApXWHNTrY/s/TbBxR0Ob7RUmbvHZkQi2/~/changes/82/examples/building-a-search-assistant/approach-3-custom-logic-pipeline-with-a-straightforward-workflow) – А pipeline-driven approach for more granular control and customization.

Each approach offers its unique strengths, and the decision will depend on factors such as scalability, flexibility, and specific project requirements.


---

# Agent Instructions: 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:

```
GET https://docs.getdynamiq.ai/examples/building-a-search-assistant.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.