> For the complete documentation index, see [llms.txt](https://docs.direqt-search.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.direqt-search.com/search-bars/integrating-your-search-bar-with-direqt.md).

# Integrating Your Search Bar with Direqt

How to run AI Search with your pre-existing search bar

You might already have a search bar on your site, or maybe you'd like to build a custom one for use with AI Search. Direqt can integrate with any search bar.

***

Add the CSS class below to your existing search input to integrate it with Direqt.&#x20;

```css
direqt-search-input
```

For example:

| Existing                                   | New                                                                    |
| ------------------------------------------ | ---------------------------------------------------------------------- |
| `<input type="text" placeholder="Search">` | `<input type="text" placeholder="Search" class="direqt-search-input">` |

{% hint style="success" %}
Your search bar placeholder text should now read "Ask \[Site Name]".  You can customize this text on the **Style** page of the dashboard.
{% endhint %}

Direqt will automatically detect this class and respond to all inputs from your search bar.


---

# 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.direqt-search.com/search-bars/integrating-your-search-bar-with-direqt.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.
