> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/support-and-training/ai-search.md).

# AI Search

Better Building's AI Search is your first place to go when a question arises and you need a quick answer. When engaging with Better Building's AI Search, you have the ability to ask direct questions from our docs. If you cannot find an answer here, please issue a Support Ticket.

## Create an AI Search

{% stepper %}
{% step %}

### Ask a Question

An AI Search is undertaken on the upper ribbon in our docs. Simply type your question and you will get two responses, one from the AI Search and the other from the relevant area within our docs. For example, 'How do i add a Design to my Project?' will return the following results. 

{% hint style="danger" %}
Note, while Better Building's AI Search is reliable, AI applications can make errors.
{% endhint %}
{% endstep %}

{% step %}

### Review Answers

Next, left click the blue arrow to review the answer. Importantly, the AI Search only sources information from our docs, so please refer to the 'Sources' for the original article. In this example, 4 steps are returned to illustrate how to a Design to my Project., with additional links to related subject matter below.
{% endstep %}
{% endstepper %}


---

# 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.betterbuilding.io/support-and-training/ai-search.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.