Short answer: The factors that increase LLM API spend beyond token cost are high-tier model selection, unnecessary feature usage, redundant calls, and retries that repeat accepted work; control them with token budgets, quality gates, and bounded backoff.
A gaming team answering questions from a private knowledge base should control spend at the request boundary: choose the smallest model that meets the quality target, count tokens before expensive work, and make retries deliberate. The bill grows when a high-tier model is selected unnecessarily, a failed request is retried too aggressively, or one question causes redundant calls.
This is a runbook for putting those checks around a Go service. Keep retrieval and answer generation separate, measure the input before model selection, and make every retry visible in the request budget.…