# Orca

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

Language: en

> Use aicentos in Orca — add an OpenAI-compatible custom endpoint

Orca supports configuring a custom OpenAI-compatible service. Point the Base URL at aicentos and fill in the API Key, and the models aicentos offers become available in Orca.

## Prerequisites

First create a dedicated key for Orca on the console's "API Keys" page (naming it `orca` 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 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 Orca's settings page and go to the model / provider configuration area.
* Add a new provider and choose the OpenAI-compatible type (OpenAI Compatible / Custom OpenAI).
* 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 set it as the default model.

## Test

Start a new conversation and send a simple prompt; confirm it returns normally. If the model dropdown is empty, type the Model ID manually instead.

## Notes

* The Base URL only goes up to `/v1`; do not extend it to the full `/v1/chat/completions` path.
* If the settings do not take effect right away after saving, restart Orca once.
* If your Orca version only supports the built-in official providers and has no custom Base URL entry, that version cannot connect to third-party endpoints; switch to another client that supports a custom Base URL.
* Common causes of connection failures: a wrong Base URL, leading/trailing spaces in the key, a nonexistent model name, or an insufficient account balance.