> 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/pim3/reference/settings/ai-assistant/text-generation.md).

# Text generation

Configure the text generation assistant

You can configure the Text generation assistant through [Settings](https://docs.struct.com/pim3/reference/settings.md) > [Ai assistant](https://docs.struct.com/pim3/reference/settings/ai-assistant.md) > [Text generation](https://docs.struct.com/pim3/reference/settings/ai-assistant/text-generation.md).

### Enable text generation assistant

Determines whether the text generation assistant is enabled for users to use when working with texts in PIM.

### Text generator engine

The engine to use for text generation.

### API key

The API key for your Open AI account.

### Organization id

The organization id from your Open AI account you want to use.

### Assistant Id

The id of the Open AI assistant (typically looks something like this: asst\_C3ZdvO9dMkbKSv78eNmCw5vq).

### Model name

The name of the fine tuned model you want to use (typically looks something like this: ft:gpt-3.5-turbo-1106:struct:struct-ex1:9FHMEm9n).


---

# 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/pim3/reference/settings/ai-assistant/text-generation.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.
