The cost of a serverless agent isn't the Lambda. It's the loop.
When I moved Wingman onto Lambda, I assumed the thing I'd have to watch was compute duration. That's the serverless mental model everyone starts with: you pay per millisecond, so keep the function fas
Responses
Markdown supported · ⌘↵ to post
Kartik N V J K
AI Developer | Making AI reliable, trustworthy & accessible to everyone | Active community contributor
The framing that the retry loop, not Lambda duration, drives cost lands hard, since a worker-evaluator that bounces back five times quietly multiplies token spend per request. I now log the attempt count per invocation as a first-class metric, because a rising average predicts a bad prompt long before the bill does. Do you cap retries by count alone, or on an evaluator confidence delta too?