> For the complete documentation index, see [llms.txt](https://docs.ixkio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixkio.com/modules/tapai/tapai-languages.md).

# TapAI Languages

TapAI understands questions asked in non-English language and will normally respond in the same language. This is the case even if your Reference Material is only in English.&#x20;

The normal TapAI process is that TapAI responds with 'Please wait' after the question has been asked. At the moment, this is only in English. However, the final answer to the question is usually int the same language as the question.&#x20;

We generally recommend using only a single language in your Reference Material and let TapAI understand best the question and answer.&#x20;

In most cases, if you are using TapAI Voice, the accent will be good enough for the language chosen.&#x20;

{% hint style="info" %}
It's not currently possible to change the voice/default accent of the TapAI response. We are working on an update for later in 2026 where you can choose your response.&#x20;
{% endhint %}


---

# 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.ixkio.com/modules/tapai/tapai-languages.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.
