# Connect GigaCode to Void API

Connect Void API to GigaCode agents on GitVerse. Custom models have limited availability; this guide covers cloud sessions, not the CLI or IDE plugin.

Examples use MODEL_ID as a placeholder, not an available model. Replace it with an ID from the current catalog. Choose a model that supports the endpoint and features used by this tool; vision and tool calling are not universal.

[Current model catalog](https://void-api.tech/models)

## API key

Store your key in an environment variable.

### Environment variables

```
export VOID_API_KEY='void_your_key'
```

## Save the API key as a GitVerse secret

In repository settings → Secrets and variables, create the VOID_API_KEY secret. Store only your Void API key, without Bearer. Do not put the key in variables or repository files.



## Configuration

Create the AI_SESSION_MODELS variable with this JSON. Append to the existing array if a catalog already exists. Choose a model supporting streaming and tool calling; set optional limits and image support according to its capabilities.

### AI_SESSION_MODELS

```
[
  {
    "profile_id": "void-api",
    "name": "Void API",
    "auth_mode": "direct",
    "base_url": "https://void-api.tech/v1",
    "model": "MODEL_ID",
    "api_key_secret": "VOID_API_KEY"
  }
]
```

## Select the model in a new session

Refresh GitVerse, create a new session and select Void API before the first message. For GigaCode Developer, select it when assigning a task. Repository catalogs replace organization catalogs; existing sessions are unchanged. Do not append /chat/completions to base_url.



[Upstream documentation](https://gitverse.ru/docs/ai/gigacode-on-gitverse/custom-models)