Topic starter
18/08/2026 2:59 pm
TL;DR: AI tokenomics in agentic systems must be measured from production telemetry, because one user request fans out into retrievals, retries, tool calls, and sub-agent runs that spreadsheet models systematically miss, according to Fiddler. The practical implication is that teams need span-level cost attribution to connect token spend to the agent, step, tenant, and outcome, not just the invoice.
Editorial analysis by NHI Mgmt Group, based on content published by Fiddler: “How to Model AI Tokenomics for Agentic Systems in Production”.
Key questions
Q: What breaks when AI tokenomics is modeled with spreadsheets instead of production telemetry?
A: Spreadsheets break when they assume one request equals one model call.
Q: Why do agentic systems make token cost harder to predict in production?
A: Because the work is no longer linear.
Q: How do teams know whether token spend is actually producing value?
A: They need both cost and outcome in the same model.
Practitioner guidance
- Instrument token spans at runtime Capture input, output, and reasoning tokens for every span as the run executes, along with the agent, tenant, model, and outcome.
- Resolve pricing at request time Store the unit price used for each span when the request is processed so later provider pricing changes do not rewrite historical cost.
- Join gateway and agent telemetry Correlate gateway logs with agent-side traces so sub-agent calls and internal tool loops are included in the cost model.
Bottom line: Agentic systems break single-call cost models because one user request can expand into multiple paid steps before any answer is returned.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
18/08/2026 3:39 pm
AI tokenomics becomes a governance problem once agentic systems move into production. The article shows that cost cannot be managed from static forecasts when one request expands into a chain of model calls, retries, and tools. The broader lesson is that runtime behaviour must be measured where it happens, because that is where attribution and accountability begin. Practitioners should treat token telemetry as an operating control, not a finance afterthought.
A question worth separating out:
Q: How should organisations attribute AI spend when usage is spread across tools and agents?
A: Start by tagging AI activity at the interaction level, not just the infrastructure level. Track team, environment, workload, and model path so finance can separate training, inference, and embedded usage. If one request can trigger many model calls, attribution has to follow the workflow, otherwise showback and chargeback will both misstate who used what.
👉 Read our full editorial: AI tokenomics needs span-level telemetry, not spreadsheet forecasts