Teams see LLM bills jump 2-3x after deploys — how do you catch cost regressions?
Junior-Guitar-290 · reddit · 2026-11-19
OP highlights a common failure: LLM bills silently jump 2-3x after a deploy with no traffic change, usually from tiny changes — a timestamp breaking prompt caching, a model swap, more retrieval chunks, or a bumped retry limit, sometimes unnoticed for weeks. They ask practitioners what caused their last cost spike, how they detect these today, and whether same-day detection or pre-ship checks are preferable.
More from coding & agent
- Biohub launches MCP server to run protein models ESMC and ESMFold2 inside Claude, ChatGPT, Cursor — AllThingsApx · 2026-11-19
- Designers need a prototype playground: a copyable prompt-based AI design workflow — round · 2026-11-19
- NVIDIA post-trained Nemotron with Factory's agent harness inside its air-gapped network — maddiehfaulkner · 2026-11-19
- LangChain's Deep Agents hits 50M downloads a year after betting on open agent harness — LangChain · 2026-11-19
- Running 15 AI Agents All Day Is Context-Switching Fatigue, IBM Engineer Explains — TejasKumar_ · 2026-11-19
- Dev's AI-native macOS dock with agent-managed modes flops; pivoting to to-do approach — trq212 · 2026-11-19