Configure (Vault + your own AI accounts)

Vault

The published stratos CLI never handles your provider keys at all: completions go through YOUR gateway via STRATOS_GATEWAY_URL, so the key stays wherever your endpoint keeps it. On a full Atmosphere node, provider keys are sealed in the runtime's vault (AES-256-GCM, machine-local 0600 master key, derived keys zeroed after use) during the daemon's setup — config stores only an opaque handle; the plaintext key never appears in config, env, or logs.

# the CLI's spend path is bring-your-own-endpoint:
STRATOS_GATEWAY_URL=http://127.0.0.1:11434/v1/chat/completions \
  stratos complete <ws/proj/wf/task> "prompt" --model gemma2:2b

Cost gate (your own AI accounts)

All spend flows through a single route — /v1/chat/completions — guarded by a cost gate. Nothing else can spend on your behalf.

Owner-gating (fail-closed)

Command authority is owner-gated and fails closed: if no owner is set, the agent has no command authority at all. There is no implicit-trust default.