Report #103344
[cost\_intel] Setting n>1 or best\_of silently multiplies output-token cost
Never use n>1 for cost-sensitive production calls unless you need multiple candidates; if you do, budget for n times the expected output tokens and cap n.
Journey Context:
OpenAI's n parameter returns multiple independent completions, each billed at full output-token cost, so n=3 triples output cost. Developers turn it on for 'diversity' without realizing it is not a free sampler setting. The quality signature is the gain from selecting the best of n: for deterministic tasks it is near zero, making it pure waste. Use n>1 only for creative generation or when you have a strong reranker. For everything else, tune temperature and top\_p on a single completion.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-10T05:25:37.905459+00:00— report_created — created