API Compatibility
Managed keys provide OpenAI-compatible access through the Gonka Broker proxy. This page documents what is currently supported.
Base URL
Section titled “Base URL”https://proxy.gonkabroker.com/v1Supported endpoints
Section titled “Supported endpoints”| Endpoint | Status |
|---|---|
POST /chat/completions | Supported |
POST /completions | Supported (legacy) |
GET /models | Supported |
Chat Completions parameters
Section titled “Chat Completions parameters”The following parameters are supported in /v1/chat/completions requests:
| Parameter | Supported |
|---|---|
model | Yes |
messages | Yes |
temperature | Yes |
top_p | Yes |
max_tokens | Yes |
stream | Yes |
stop | Yes |
presence_penalty | Yes |
frequency_penalty | Yes |
tools | Yes |
tool_choice | Yes |
Message content format
Section titled “Message content format”The content field in messages supports both formats:
- String — plain text value (
"content": "Hello") - Array — structured content parts (
"content": [{"type": "text", "text": "Hello"}])
Both formats are fully supported. However, only text content parts are available — image and other multimodal content types are not supported.
Response format
Section titled “Response format”Responses follow the OpenAI Chat Completions response format, including:
id— unique response identifierobject—"chat.completion"choices— array of completion choicesusage— token usage statistics
Streaming responses use Server-Sent Events (SSE), matching the OpenAI streaming format.
Not yet supported
Section titled “Not yet supported”The following OpenAI features are not currently available:
- Embeddings API
- Images API
- Audio API (TTS, STT)
- Assistants API
- Fine-tuning API
- Vision (image inputs)
- JSON mode / structured outputs
These may be added in future releases. Check back for updates.