AI
Budget checks run before a provider call
Budget checks run before a provider call and use ledger totals from tenant-scoped usage rows. The proof keeps all spend local and deterministic.
Budget checks run before a provider call, so blocked requests do not spend more tokens.
Tenant, user, feature, model policy, prompt version, tokens, cost, latency, and outcome are required for ledger joins.
Per-school monthly budget, feature budgets, per-user daily run limits, per-user token limits, and feature kill switches all participate in enforcement.
Warnings can allow a request while still surfacing spend risk before a hard budget block.