You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(pricing): apply LiteLLM request bands per request (#1305)
AgentsView currently flattens LiteLLM catalog rows, which undercounts long-context requests such as Codex above 272K input tokens and Claude above 200K, causing its totals to diverge from tools that honor those thresholds.
This preserves deterministic standard threshold metadata in fetched and embedded catalogs, then selects the highest eligible band for each request-scoped usage row. Aggregate-only rows stay on base rates because their request boundaries are unknown, and custom pricing remains deliberately flat.
Complete bands now survive SQLite, PostgreSQL, and DuckDB transport with atomic revisions and reproducible digests. Schema-v4 pricing provenance exposes both available bands and how many report rows selected each one, while service-tier-specific variants remain excluded when transcripts cannot identify the tier.
Co-authored-by: Marius van Niekerk <mariusvniekerk@users.noreply.github.com>
0 commit comments