WeSearch

A 3-step agent cost me $4.20. agenttrace showed me the O(n ) tool call hiding in plain sight.

·4 min read · 0 reactions · 0 comments · 16 views
#ai#observability#cost-optimization
A 3-step agent cost me $4.20. agenttrace showed me the O(n ) tool call hiding in plain sight.
TL;DR · WeSearch summary

A recent experience with a 3-step agent revealed unexpected costs due to inefficient tool calls. The author utilized agenttrace to analyze and optimize the process, reducing the cost significantly. The issue stemmed from the model's handling of input tokens, which led to excessive calls and increased expenses.

Key facts
Original article
DEV.to (Top)
Read full at DEV.to (Top) →
Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3915555) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Mukunda Rao Katta Posted on May 21 A 3-step agent cost me $4.20. agenttrace showed me the O(n ) tool call hiding in plain sight. #hermesagent #ai #llm #observability I ran a small agent. Three steps. One web search, one summarize, one cite-check. I had budgeted maybe 12 cents. The bill at the end of the run was $4.20. I knew something was off but the per-call invoice line items were not telling me anything useful. They were just a list of messages.create calls.

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from DEV.to (Top)