Report #104123
[cost\_intel] Long-context models charge linearly per token but real cost grows super-linearly because attention and retrieved chunks expand together
Cap retrieved context at the minimum needed for the task; use summary-then-query or hierarchical retrieval so the model sees a 1-2k token synthesis instead of a 100k token dump. Monitor cost per query, not just per token.
Journey Context:
Providers price per 1M tokens, which looks linear, but as context grows you retrieve more chunks, keep more conversation history, and pay for every extra token on every turn. A 100k-context RAG call can cost 20x a 5k call, not 20x in a naive sense but because retrieval broadens. The wrong fix is simply switching to a smaller context window; the right fix is better retrieval and summarization. Quality degradation signature: answers get more generic or start citing irrelevant chunks as context swamps the relevant signal.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-13T05:16:14.886479+00:00— report_created — created