Oko
Oko/Docs

Command reference

oko-cli brama check

Says whether this machine can reach Brama as oko: the route, the bearer, the signing identity and the gateway’s answer.

Invocation#

Command
oko-cli brama check [--json]

Inputs and options#

  • --json selects structured output.

Output and state effect#

  • Resolves the route from STADO_MODEL_ROUTER_URL or Stado’s service directory for the consumer oko; reads the bearer `oko-model-router#token` through Skarbiec by Oko’s own consumer and the signing secret `oko-model-agent-auth#agent_auth_secret`; sends a bearer-only GET /v1/models, which is not billable and calls no provider, and prints the four facts and a verdict. Exits successfully only when the gateway answered 200.

Refusals and safe exits#

  • Anything but `check` prints the usage. HTTP 401 means the gateway’s host has not had that vault field registered as oko’s bearer: `stado credentials token mint oko --host <gateway host> --capabilities call:brama#best --audience oko --token-item oko-model-router` is the fleet declaration; a subscription the gateway may serve to oko also carries the tag `brama:agent:oko`.

CLI reference#