# Mux

Source: https://docs.aicentos.com/en/clients/mux

Language: en

> Use aicentos in Mux — add a custom OpenAI-compatible provider

Mux supports adding custom OpenAI-compatible providers. Point the Base URL at aicentos and the models aicentos offers become usable in Mux sessions.

## Prerequisites

First create a dedicated key for Mux on the console's "API Keys" page (naming it `mux` makes usage easier to track).

* Console: [https://aicentos.com](https://aicentos.com)
* Create a key: [https://aicentos.com/keys](https://aicentos.com/keys)
* Wallet top-up: [https://aicentos.com/wallet](https://aicentos.com/wallet)
* Docs site: [https://docs.aicentos.com](https://docs.aicentos.com)

## Configuration to fill in

| Field         | Value                                              |
| ------------- | -------------------------------------------------- |
| Provider type | OpenAI Compatible                                  |
| Base URL      | `https://aicentos.com/v1`                          |
| API Key       | The key created in the console                     |
| Model         | A model name from the Model Gallery in the console |

## Setup steps

* Open Mux's settings and go to the Providers / Models area.
* Choose to add a custom provider, with the type set to **OpenAI Compatible**.
* Enter the API Key.
* For Base URL enter: `https://aicentos.com/v1`
* For Model enter a model name from the Model Gallery in the console (see [Supported models](https://docs.aicentos.com/en/billing/models-list)).
* Save it and set it as the provider for the current session.

## Test

Start a new session and send a simple prompt. A normal response means the integration works. If the model list does not show the model you entered automatically, type the Model ID manually and try again.

## Notes

* Enter the Base URL only up to `/v1`; do not extend it to the full `/v1/chat/completions` path.
* Setting names may differ slightly between versions, but the OpenAI-compatible configuration always revolves around three fields: Base URL, API Key and Model.
* A wrong Base URL, a key with stray spaces, or an insufficient balance usually shows up as 401 / 403 / 402 errors — check them one by one.
* If your Mux version only offers a fixed set of company options and cannot take a custom Base URL, that version does not support third-party endpoints; switch to another client that supports a custom Base URL.