API keys
obk- keys authenticate inference, balance, and usage. The secret is shown once.
Inference uses a bearer key with the prefix obk-.
Authorization: Bearer obk-YOUR_API_KEYCreate and delete
Keys are created on the dashboard, under API access & keys, and only after the account is active. You can create more than one. Each secret is shown in full once. OpenBroker stores a hash, so a lost key cannot be displayed again. Create a new one.
Deleting a key takes effect immediately. Requests that still send it receive 401 invalid API key.
Renaming a key changes the label in the dashboard. It does not change the secret.
What a key can call
| Call | Auth |
|---|---|
POST /v1/chat/completions | obk- key |
POST /v1/completions | obk- key |
GET /v1/balance | obk- key |
GET /v1/usage and GET /v1/usage/summary and GET /v1/usage/{id} | obk- key |
GET /v1/models | Public. No key. |
The key is scoped to one broker account. It cannot read another account's usage or balance.
What is not an API key
Dashboard sessions use a different token prefix (obs-, or a legacy obt- dashboard token). Those sign the browser into /dashboard. They are not accepted on the inference API.
There is no per-key request quota in OpenBroker. A 429 comes from gateway concurrency, not from a plan attached to the key. See Errors.