Costs and Observability
Inspect spend, budgets, usage limits, traces, metrics, and anomaly rules from the CLI.
Cost and observability commands read the same meters and telemetry exporters as the Cost screen and Activity traces view.
All verbs require sidecar reachability unless noted.
Cost summary
Aggregate spend for the configured window (default: recent hours).
Breakdown
groupBy is required by the sidecar contract (provider, role, workspace, …).
Budgets and alerts
costs list returns itemized rows suitable for CSV piping; costs alerts surfaces budget threshold breaches.
Tenant usage meter
Cloud tenants expose backend-computed usage limits (do not recompute limits in scripts):
usage watch exits non-zero when status is blocked or exceeded — useful in CI guardrails.
Per-run cost
For a single execution, use the runs cockpit:
Token and USD fields appear in the enriched run detail payload.
Observability
Metrics ids include tokens.in, tokens.out, cost.totalUsd, errors.count, and p99.latencyMs.
Anomaly rules
Companion to observability — lists structured anomaly rules and paused state.
Live tails
Poll-based streaming (ADR-0133) — safe for CI with deadlines:
Set AKOS_STREAM_INTERVAL_MS to tune poll cadence.
Interactive shell shortcuts
In akos chat --interactive or --tui, slash commands mirror these surfaces:
/cost— spend summary for the session window/runs,/run <id>,/watch <id>,/logs <id>— run inspection/tail <id>— snapshot status + recent events
See Command reference › Interactive shell.
Related topics
- Cost in the app — budgets, billing tab, spend charts.
- Activity — run list, traces, observability health.
- Flows and Runs —
runs show,runs watch, retention prune. - Dashboard — live cost summary card.
- Command reference — full
costs,usage, andobservabilitytables.