My agent is too damn expensive! What do you wish you knew about your LLM token burn?
Summary
A discussion post about the high costs of running LLM agents, with users sharing frustrations and seeking advice on tracking token spending and improving efficiency.
Similar Articles
What I'm Finding About LLM Code Style and Token Costs
The article discusses how LLM code style choices affect token consumption and costs, offering optimizations such as using Web API standards and simpler indentation to reduce output tokens.
@LangChain: Reining in LLM spend gets harder once your team has started using multiple agents calling multiple models. Without the …
The article provides a walkthrough on setting and enforcing cost controls using LangSmith LLM Gateway to manage expenses when using multiple LLM agents.
If you run agents in production, can you tell which step is burning your budget?
A user on r/LLMDevs discusses the challenge of attributing costs in multi-step AI agent runs, where SDK logging only reflects final results, making it hard to identify which step is burning the budget.
What Does a Token Cost? A Mixture-of-Agents Measurement of Sufficient Per-Token Compute
This paper measures the per-token 'sufficient compute' of LLMs using a Mixture-of-Agents panel of fifteen models across Qwen, OLMo, and R1-distilled families, finding a 0.5B agent reproduces 92-95% of reference tokens while the costliest 10% of tokens account for 64-80% of FLOPs. The resulting per-token compute map improves model routing latency from 7.59s to 5.12s and enables speculative drafting with 32.6% fewer draft tokens than fixed-window baselines.
Subagents Account for Most Token Costs in Long Agent Runs: Fixes That Cut Usage 70 to 90 Percent in Practice
The article analyzes a 2026 paper by Bai et al. showing that subagents and context bloat cause token costs in long agent runs to be ~1000x higher than chat, and presents three practical fixes (PLAN.md, read budget, out-of-band notes) that reduce token usage by 70-90%.