> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/infinity/spec-sheet/site-search/autocomplete-1.md).

# Autocomplete

| Feature                        | Description                                                                                                                                                                                                                                                 |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Popular query suggestions**  | Query terms, ranked by popularity. Popularity of suggestions are determined by the frequency of searches for that term. The term's popularity is built up by previous searches for that term that led to a good textual match.                              |
| **Scoped autocomplete**        | The top autocomplete suggestion can be presented with facets (or scopes in other words). To enable users to apply a facet, directly from the search bar. Typically the facets used are brand or category. (e.g. "Prada in Accessories" or "Prada in Shoes") |
| **Keyword redirects**          | If a user enters a pre-defined keyword (e.g. opening hours), they are redirected to a specified URL immediately after pressing enter. The engine returns a link to use for the redirect.                                                                    |
| **Products in autocomplete**   | Products are returned (along side queries) when a user starts to type in the search box. If a user starts to type "airp" in the search bar, the engine will respond with the "Airpods" product.                                                             |
| **Other data in Autocomplete** | Other things than queries and products can be returned. For example results within categories, brands or other content. This can be used to create a rich Autocomplete experience.                                                                          |


---

# 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.fact-finder.com/infinity/spec-sheet/site-search/autocomplete-1.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.
