# Pi

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

Language: en

> Use aicentos in Pi — configure a custom OpenAI-compatible endpoint

Pi supports specifying a custom OpenAI-compatible API address. Point the Base URL at aicentos and fill in the API Key, and the models aicentos offers become available in Pi.

## Prerequisites

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

* Console: [https://aicentos.com](https://aicentos.com)
* Create a key: [https://aicentos.com/keys](https://aicentos.com/keys)
* Top up when the balance runs out: [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 | 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 Pi's settings and find the API / model configuration area.
* Choose the custom OpenAI-compatible provider.
* Enter `https://aicentos.com/v1` as the Base URL.
* Enter the key created in the console as the API Key.
* Enter a model name from the Model Gallery in the console as the Model (see [Supported models](https://docs.aicentos.com/en/billing/models-list)).
* Save and select that model in the session.

## Test

Run one simple conversation round and confirm it returns normally. Use `/model` or the settings page to confirm the current model really comes from aicentos rather than the built-in default provider.

## Notes

* The Base URL only goes up to `/v1`; do not write the full API path.
* If Pi also keeps the built-in provider around, make sure you switch back to the one you created — otherwise requests will not go through aicentos.
* If your Pi version offers no custom Base URL, third-party endpoints cannot be connected; switch to another client that supports a custom Base URL.
* Creating a separate key for this client is recommended, so usage can be told apart per key in the console.