How are teams attributing LLM/agent spend back to actual workstreams or repos?
Curious how FinOps teams are thinking about LLM/agent usage attribution.
The spend number itself seems relatively easy to capture if everything flows through an API gateway, vendor usage export, proxy, or billing report.
The harder part seems to be tying that spend back to the actual work it supported.
For example:
- an agent task fans out into multiple model calls
- the cost lands on whatever service key or proxy path fired the request
- the model call may not know the story, workstream, repo, branch, or business context
- leadership can see total spend, but not what work that spend supported
One pattern I’ve heard is tagging at the orchestration/task layer instead of the individual model-call layer, so the cost follows the outcome rather than just the API request.
For teams dealing with this:
How are you attributing LLM or agent spend today?
Are you tagging usage up front by task/workstream/story/repo?
Are you reconciling it after the fact from logs, traces, Jira/GitHub data, or usage exports?
Or is this still mostly unresolved?
I’m exploring this problem and trying to understand where the attribution layer should live before overbuilding the wrong solution.