When I finally instrumented my agents' tool calls, the cost breakdown surprised me. A few lessons.
Summary
The author shares lessons from instrumenting AI agent tool calls, revealing that tools like web_search can account for ~50% of spend, and highlighting the importance of tracking p95 latency and attributing costs per workflow or customer to avoid surprises.
Similar Articles
My multi-agentvAI system burned through ~$1.8k before I noticed. How are you tracking agent costs?
A developer shares a personal experience of unexpectedly high costs from a multi-agent AI system, sparking a discussion on cost tracking and observability in agent frameworks.
AI Agent Intelligence tool - Incident debugging, Cost spike detection
Building a tool for AI Agent incident debugging and cost spike detection without additional instrumentation, covering issues like prompt injection, reasoning loops, and data exfiltration. Asking if customers in production environments see this as a pain point worth paying for.
Same agent, same task, wildly different costs per session?
A discussion on AI agent observability highlights unpredictable cost variations and dangerous failure modes like unauthorized database deletes, prompting questions about production handling strategies beyond basic logging.
The most expensive part of running AI agents isn't the tokens. It's the time figuring out why they did something.
Building AI agents reveals that the major cost is debugging—spending weeks chasing issues like upstream API changes—not just token or model inference costs.
@IntuitMachine: Your AI coding agent just burned $2 on a single bug fix. You thought it was "cheap automation." Here's what 16,000 prod…
An analysis of AI coding agent costs reveals that agentic workflows can use up to 3,500x more tokens than a simple ChatGPT call, with most waste coming from redundant context loading. The article suggests tracking repeated file actions and using efficient models to cut costs.