r/tokenomics

I keep coming back to a number I read this week from a public agent-failure trace study. Failed runs spent roughly 58 percent of their tokens after the first warning signal appeared, meaning an explicit tool error or a repeat tool call with identical arguments. The model already had enough evidence to stop and it kept going. That is not a model quality problem. It is a budget-discipline problem, and I think most FinOps setups today do not have the surface to catch it.

The same reading dropped two other data points I have not been able to shake. Anthropic's Dynamic Workflows can run up to 16 concurrent subagents with 1000 total in a single run. If your kill switch is a monthly bill anomaly rule, that ceiling can produce a very expensive Wednesday afternoon before your Thursday dashboard flags anything. And a suggestion I liked more than I expected: three cost classes as the budgeting unit. High-volume low-value work capped at cents. Standard knowledge work worth roughly $50 of human labor gets a $5 budget. High-value work worth $5,000 gets $500, because starving the agent is more expensive than feeding it. Named owner per agent. Breaker built in.

The reason this bugs me is that the FinOps industry keeps saying "attribution" as if the hard part is knowing who spent the tokens. In practice the harder part is knowing when to trip the breaker mid-run. The trace study says the signal is there. The tooling is not.

So a real question. How is your team handling this today? Are you actually cutting runs off mid-flight when the failure signal fires, or are you catching it in the next day's cost review and eating the burn?

Hello everyone, currently digging into workflow-layer economics and trying to figure out how people track unexpected runtime spikes at scale.

At an early stage simple margin buffers are fine because volume is bounded. But once you move past basic apps, factors like failed loops, retries, and context window inflation create a ton of cost variance that is hard to forecast or map to clean client billing.

For those running agent or voice workflows in production, or working on complex ai products what do you currently use to understand costs and failures at the individual workflow level?

More importantly, what's something you still can't easily answer with your current setup? Like why did a specific workflow suddenly cost 2x more, or which exact customer trigger is driving the increase? Are you guys just manually digging through raw api logs to catch leakage like infinite loops, or has it not become a big enough issue for your teams yet?

Curious to hear how other teams handle the infrastructure discipline here.