Notifications
Clear all
Topic starter
01/07/2026 2:05 am
TL;DR: Cost per AI query turns AI spend into a governable unit, but rising usage, retrieval, premium models, and agentic loops can still inflate the true cost of each completed task, according to WitnessAI and the FinOps Foundation. Treating that metric as an AI risk management problem is now the practical path to cost control.
NHIMG editorial — based on content published by WitnessAI: cost per AI query as a financial metric and AI risk management problem
By the numbers:
- Enterprise generative AI spend grew from approximately $1.7 billion in 2023 to $37 billion in 2025.
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes, and as quickly as 9 minutes in some cases.
Questions worth separating out
Q: How should teams calculate the true cost per AI query?
A: Start with the visible model charge, then add the cost of retrieval, routing, review, remediation, and any compliance work created by the query.
Q: Why do AI bills rise even when token prices fall?
A: Lower token prices do not help if each query uses more context, more model turns, more premium routing, or more autonomous actions.
Q: What breaks when cost control is built only on invoice data?
A: Invoice-only control misses Shadow AI, compliance overhead, and agentic execution costs that never appear as a clean line item.
Practitioner guidance
- Attribute cost to the AI workflow, not just the model bill Break spend down by query, workflow, user, and agent so finance can see which activities create the highest fully loaded cost.
- Separate sanctioned AI from Shadow AI in reporting Use discovery and logging to identify unsanctioned tools, then assign their overhead to the business units or workflows that created the exposure.
- Apply runtime limits to agentic loops and tool calls Set policy boundaries on how many model calls, external actions, and data retrieval steps an agent can trigger before review or termination.
What's in the full article
WitnessAI's full research covers the operational detail this post intentionally leaves for the source:
- Model-by-model cost mechanics for retrieval-augmented and agentic workflows
- How the platform identifies Shadow AI usage across native apps and routed traffic
- Examples of intent-based routing and four-action policy decisions in practice
- Runtime inspection details for prompts, responses, and sensitive data handling
👉 Read WitnessAI's analysis of cost per AI query and AI risk →
Cost per AI query: why finance and IAM teams should care?
Explore further
01/07/2026 2:26 am
Cost per AI query is becoming the control plane for AI governance. Finance teams need a unit they can budget, but identity and security teams need the same unit to understand who or what is consuming AI services, through which workflow, and with what exposure. Once AI is treated as a governed workload rather than an ad hoc feature, the metric becomes a bridge between spend control and access control. Practitioners should treat per-query cost as a shared governance object, not a finance-only KPI.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap.
A question worth separating out:
Q: How do security teams govern agentic AI without blocking useful work?
A: Use intent-based policy, routing, and runtime guardrails so the agent can continue operating within explicit limits. Bound the number of tool calls, restrict sensitive data exposure, and require stronger controls when the workflow becomes customer-facing or action-taking. Governance should shape execution, not just review it after the fact.
👉 Read our full editorial: Cost per AI query shows why AI spend needs governance
