> For the complete documentation index, see [llms.txt](https://docs.openagrinet.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openagrinet.global/technical/ai-layer/supporting-multilingual-and-multimodal-access.md).

# Supporting Multilingual and Multimodal Access

The AI module is built to support multilingual and multimodal interactions, recognising the diversity of users across states and regions.

At the user level:

* Queries can be entered as text or voice
* Regional languages are supported at the input and output layers

Internally:

* Voice queries are processed using Automatic Speech Recognition (ASR) to convert speech into text, and Text-to-Speech (TTS) is used to deliver responses back in audio form where required.
* Queries are normalised into a common processing language to ensure consistency
* Responses are generated and translated back to the user’s preferred language

This separation allows OAN to scale language support without duplicating logic across use cases or states.


---

# 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.openagrinet.global/technical/ai-layer/supporting-multilingual-and-multimodal-access.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.
