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
{{ message }}
Repository navigation
Commit b647ec7
Browse filesBrowse the repository at this point in the historyBrowse files
fix(cost): bill the TTL split on the telemetry recompute and in tier blocks
What:
- Pass `cacheWrite1h`/`cacheWrite12h` to the cost call inside `captureUsageData`.
The bag already carried them and fed the shared accumulator vars, but the
telemetry recompute passed only the aggregate write count, so a cancelled
request's telemetry billed every write at the short-TTL rate.
- Add `cacheWritesPrice1h`/`cacheWritesPrice12h` to the `tiers` schema and to the
four Anthropic and four Bedrock 1M-context tier blocks, derived from each
tier's own input price.
- Carry the tier's TTL rates through all three tier-merge seams (anthropic,
anthropic-vertex, bedrock) and derive them from the tier input price in the
OpenAI service-tier seam, so a flex/priority or 1M-context write is not billed
at the base tier's TTL rate.
Why:
Two under-reports survived the first pass. `captureUsageData` recomputes cost for
telemetry when a provider yields no final cost chunk (the cancelled-stream path),
and it dropped the split: 100k 1h tokens at claude-3-5-sonnet billed 0.375
instead of 0.6. Separately, the 1M-context tier merge overrode `inputPrice` but
not the TTL rate, so the entry-level rate derived from the 200K input price
survived: a 1M-context 1h write billed 6.0 instead of the tier's 12.0, a 50%
under-report.
Impact:
Both paths now bill at the correct TTL rate. Three new tests fail on the
pre-fix code (0.375 vs 0.6, and 6 vs 12); a fourth asserts the tier rate reaches
the cost function. No request shape changes.
0 commit comments