> For the complete documentation index, see [llms.txt](https://guide.allibee.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.allibee.ai/en/clm/ai-contract-review/translate.md).

# AI Translation

Translate contracts between English and Korean instantly.

### How to use the translation feature

<figure><img src="https://3451208694-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qHtZ4dsbnHJVnzJVk59%2Fuploads%2FksUEn8pB87McvMl2OKKL%2FAI%20Contract%20Review-%EB%B2%88%EC%97%AD.png?alt=media&amp;token=abbdd83d-142a-4c2f-91b0-65f9e5d94172" alt=""><figcaption></figcaption></figure>

* Drag the section of the contract that needs translation to use the translation feature.
* If your workspace language is set to Korean, you can translate English contracts into Korean. Conversely, if it is set to English, you can translate Korean contracts into English.
* You can translate up to 2,000 characters at a time between Korean and English.

{% hint style="warning" %}
Contract Translation uses AI credits.
{% endhint %}

***

### How to Change Language Settings

<figure><img src="https://3451208694-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qHtZ4dsbnHJVnzJVk59%2Fuploads%2FeKIfcwg0UPrdL5v6AT98%2FEN%20%EC%96%B8%EC%96%B4%20%EC%84%A4%EC%A0%95.png?alt=media&amp;token=3cd70804-6425-4d6d-bc5a-18240c5f67e8" alt=""><figcaption></figcaption></figure>

* Click Profile Settings in the top-right corner of your workspace.
* Select your preferred language (Korean or English) in the pop-up.
* Changes will be applied immediately to your workspace.


---

# 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://guide.allibee.ai/en/clm/ai-contract-review/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.