cached_per_1k in a price charges the prompt tokens the answer counts as cached_tokens at their own rate; zero keeps charging them as prompt tokens. The count reaches the cost and not a column: CostMicros holds what it changed. Cached beyond the prompt is clamped, an engine's miscount rather than a refund. BACKLOG L5. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
73e1bb6733
commit
ed0d1ec0ad
12 files changed
+85
-11
No files matched your search
+5
-1
@@ -1741,7 +1741,11 @@ used, and in priority tiers.
|
||||
- Done when: with two replicas of one model, one on a slower card, `latency`
|
||||
sends most of the traffic to the faster and the slower still gets some.
|
||||
|
||||
### L5. Prices by kind and by cache (S–M)
|
||||
### L5. Prices by kind and by cache (S–M) — done 2026-10-25
|
||||
`cached_per_1k`, charged on the answer's `cached_tokens`. A budget in money was already
|
||||
there (`keys limits --budget`). Not done: cache-write and audio/video token prices —
|
||||
no engine llmgw runs reports them, and no provider it reaches is billed by them yet.
|
||||
The original item follows.
|
||||
`catalog` prices are per million input/output tokens and per picture/mesh.
|
||||
Kong prices cached reads and cache writes apart, and audio, image and video
|
||||
tokens apart, and limits by cost.
|
||||
|
||||
Reference in new issue
Block a user