Supported endpoints
Chat, legacy completions, models, balance, and usage are served. Embeddings, images, assistants, and batches are not.
OpenBroker serves a small OpenAI-compatible surface. Other OpenAI routes are not offered.
Served
| Method and path | Auth | Role |
|---|---|---|
POST /v1/chat/completions | obk- key | Chat. The body is forwarded, including tools. |
POST /v1/completions | obk- key | One string prompt. See Legacy completions. |
GET /v1/models | None | Live model ids. |
GET /v1/balance | obk- key | Ledger and what a new request can spend. |
GET /v1/usage | obk- key | One page of your requests. |
GET /v1/usage/summary | obk- key | Totals for a UTC date range. |
GET /v1/usage/{id} | obk- key | One request. |
Not served
These are not OpenBroker routes. A client that calls them does not get a completion:
- Embeddings (
/v1/embeddings) - Images, audio, speech, and transcriptions
- Assistants, threads, files, fine-tuning, and batches
- Moderations
messages are forwarded as you send them. A model can still reject a field, including a tool call or an image part. That rejection comes back as the upstream response.
Public reads that are not inference
No API key:
GET https://api.openbroker.gonka.gg/api/status— the status snapshot. See How much to send.- The website pages /status and /stats.
A dashboard sign-in is a browser session. It is not a bearer key for /v1.