> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-ai-translate.md).

# How to use AI-translate

Learn how to seamlessly translate your product information into multiple languages using AI-translate. This page covers setup, configuration, and best practices for fast and accurate translations.

Our AI Translation model makes breaking language barriers effortless, enabling you to deliver your product information in any supported language without manual effort.\
Translate entire catalogs or specific attributes with speed and accuracy, ensuring your messaging stays consistent across markets.

By connecting your API key, you can automate translations directly in the PIM. Saving time, reducing errors, and reaching more customers worldwide. This guide will show you how to set it up, configure it for your needs, and start translating with ease.

### Guides

* [How to set up your AI-translation](/tutorials/guides/how-to-use-ai-translate/how-to-set-up-ai-translation.md)
* [How to AI-translate](/tutorials/guides/how-to-use-ai-translate/how-to-ai-translate.md)


---

# 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.struct.com/tutorials/guides/how-to-use-ai-translate.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.