# Jcode

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

Language: en

> Use aicentos in Jcode — specify an OpenAI-compatible endpoint through the configuration file

Jcode can point at an OpenAI-compatible API service through a configuration file. Set the Base URL to aicentos and fill in the API Key, and the models aicentos offers become available in Jcode.

## Prerequisites

First create a dedicated key for Jcode on the console's "API Keys" page (naming it `jcode` 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 Jcode's configuration file (usually under the user configuration directory, e.g. `~/.jcode/config.json`).
* Add an OpenAI-compatible provider entry.
* Set `baseURL` / `baseUrl` to: `https://aicentos.com/v1`
* Set `apiKey` to the key created in the console.
* Set `model` to a model name from the Model Gallery in the console (see [Supported models](https://docs.aicentos.com/en/billing/models-list)).
* Save and restart Jcode for the configuration to take effect.

Reference structure:

```json
{
  "provider": "openai",
  "baseUrl": "https://aicentos.com/v1",
  "apiKey": "sk-your-key",
  "model": "gpt-4o"
}
```

If your version keeps the configuration at `~/.config/jcode/config.json`, edit the file with the same name at that path instead.

## Test

After restarting, start a new session and send a simple prompt; a normal response means the integration works.

## Notes

* Field naming (`baseUrl` / `base_url`) may differ between versions; follow the field names in your local configuration template.
* The Base URL only goes up to `/v1`; do not extend it to the full API path.
* If your Jcode version offers no custom Base URL entry, that version cannot connect to third-party endpoints; switch to another client that supports a custom Base URL.
* Never commit the key to version control; reference it through an environment variable if necessary.