Notifications
Clear all
Topic starter
09/06/2026 11:43 pm
TL;DR: AI chargeback breaks down when token use, model calls, and latency tiers are not captured at the gateway and attributed by team or application, according to Kong. The governance challenge is not billing alone, but building reliable usage identity so AI consumption can be measured, explained, and acted on.
NHIMG editorial — here’s why we think this discussion matters
Questions worth separating out
Q: How should teams attribute AI usage to the right cost centre?
A: Teams should attribute AI usage at the request layer by tagging each call with a stable owner such as team, tenant, product, or application.
Q: Why do AI chargeback programmes fail without gateway metering?
A: They fail because token consumption, model calls, and latency are scattered across applications and cannot be reconciled reliably after the fact.
Practitioner guidance
- Meter AI usage at the gateway layer Capture token counts, model calls, request volume, and latency where traffic crosses the AI entry point so every request is observable before aggregation.
- Standardise attribution metadata Require team, tenant, product, or application tags on every AI request so finance and security can map consumption to a clear owner.
- Start with showback where ownership is unclear Publish usage summaries to business owners before enforcing internal billing so the organisation can validate attribution and reduce disputes.
What to expect at the briefing
Kong's full webinar covers the operational detail this post intentionally leaves for the source:
- Gateway metering patterns for capturing token usage, model calls, and latency at the enforcement point
- Practical request-tagging approaches for mapping AI consumption to teams, products, tenants, or applications
- The reporting flow for turning per-request telemetry into monthly summaries that Finance can use
- How to decide when to use showback first and when internal chargeback is mature enough to enforce
👉 Watch Kong's webinar on building AI chargeback from metering to billing →
AI chargeback at the gateway layer: what Finance teams need?
Explore further
10/06/2026 2:10 am
AI chargeback is an identity governance problem before it is a finance problem. The webinar correctly frames token consumption as infrastructure plumbing, but the deeper issue is that AI usage must be tied to accountable non-human or autonomous identities before any cost model is trustworthy. If the organisation cannot identify which workload, agent, or team is generating a request, it cannot govern spend, privilege, or accountability. The practitioner implication is that usage attribution must be built into identity and access design, not added after billing fails.
A few things that frame the scale:
- 44% of NHI tokens are exposed in the wild, being sent or stored over platforms like Teams, Jira tickets, Confluence pages, and code commits, according to The 2025 State of NHIs and Secrets in Cybersecurity.
- 62% of all secrets are duplicated and stored in multiple locations, causing unnecessary redundancy and increasing the risk of accidental exposure.
A question worth separating out:
Q: What is the difference between chargeback and showback for AI platforms?
A: Chargeback bills internal consumers for their AI usage, while showback only reports it back to them. Showback is usually the maturity step before chargeback because it exposes demand, cost, and behaviour without forcing immediate financial transfer. That makes it easier to correct ownership and usage patterns first.
👉 Read our full editorial: AI chargeback needs gateway-level metering, not spreadsheet estimates
