0044 — Broker owns usage, prices, and budgets
Token usage, model prices, and per-person budgets live in the broker service, not in billing.
Decided. Token consumption, model prices, realized cache savings, estimated routing savings,
and per-person budgets live in services/broker, in that service's own Postgres database. They
are not rows in accounting or billing.
Broker both relays LLM calls and accepts reported usage. Both paths land in one
broker_usage_records table.
Prompt-cache accounting records the tokens and dollars the provider already saved. Broker does not store or serve prompt prefixes. Routing savings are stored at write time as the requested model's counterfactual cost minus actual cost.
People are created on first sight from the Cloudflare Access identity. The default budget applies with no per-person row.
Canonical source: docs/decisions/0044-broker-usage-and-budgets.md.