> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/ai-in-umbraco/management-api/settings.md).

# Settings

API endpoints for managing global AI settings.

The Settings API allows you to configure system-wide defaults for Umbraco.AI.

## Endpoints

| Method | Endpoint                                                                                                    | Description                          |
| ------ | ----------------------------------------------------------------------------------------------------------- | ------------------------------------ |
| GET    | [`/umbraco/ai/management/api/v1/settings`](/ai-in-umbraco/management-api/settings/get.md)                   | Get current settings                 |
| PUT    | [`/umbraco/ai/management/api/v1/settings`](/ai-in-umbraco/management-api/settings/update.md)                | Update settings                      |
| GET    | [`/umbraco/ai/management/api/v1/settings/disclosure`](/ai-in-umbraco/management-api/settings/disclosure.md) | Get the AI disclosure notice setting |

## Base URL

```
/umbraco/ai/management/api/v1
```

## Settings Object

{% code title="Settings" %}

```json
{
    "defaultChatProfileId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "defaultEmbeddingProfileId": "d290f1ee-6c54-4b01-90e6-d701748f0851",
    "classifierChatProfileId": null,
    "defaultSpeechToTextProfileId": null,
    "defaultImageGenerationProfileId": null,
    "defaultDecisionProfileId": null,
    "disclosureNoticeMode": "Always"
}
```

{% endcode %}

## Properties

| Property                          | Type   | Description                                                             |
| --------------------------------- | ------ | ----------------------------------------------------------------------- |
| `defaultChatProfileId`            | GUID   | Default profile for chat operations                                     |
| `defaultEmbeddingProfileId`       | GUID   | Default profile for embedding operations                                |
| `classifierChatProfileId`         | GUID   | Optional profile for classification tasks                               |
| `defaultSpeechToTextProfileId`    | GUID   | Default profile for speech-to-text operations                           |
| `defaultImageGenerationProfileId` | GUID   | Default profile for image generation (experimental)                     |
| `defaultDecisionProfileId`        | GUID   | Default profile for decisions (experimental)                            |
| `disclosureNoticeMode`            | string | How the AI-generated notice is shown: `Always`, `Dismissible`, or `Off` |

{% hint style="info" %}
There is always exactly one settings record.
{% endhint %}

## Related

* [Settings Concept](/ai-in-umbraco/concepts/settings.md)
* [Managing Settings](/ai-in-umbraco/backoffice/managing-settings.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.umbraco.com/ai-in-umbraco/management-api/settings.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.