What it is
LLM cost attribution captures every LLM call at the moment it happens, tags it with the operational context that drove it (task ID, agent ID, process ID, skill ID, account ID), resolves it to a real dollar cost using a maintained model-pricing table, and rolls it up into views finance and operations leaders can actually use: cost per task, cost per agent, cost per process run, cost per skill, vendor share by workload type. It is structurally different from what any individual LLM vendor console can show — vendor consoles only see their own slice and have no view of "which task" or "which agent" drove the call. Cross-vendor cost attribution must be done at a layer above all vendors, typically through an LLM gateway plus a structured event SDK.
Why it matters
AI bills are climbing across organizations and most teams cannot answer the basic question of where the spend is going. Vendor consoles show vendor totals, not workload economics. Without cost attribution, leaders cannot tell which agents are profitable, which workloads to scale, which to retire, or which models are over- or under-priced for the work being done. With it, AI spend becomes a managed line item — comparable to cloud spend in 2015, when FinOps emerged as a discipline. The teams that get attribution right early compound: they know which workloads are worth scaling and which are leaking. The teams that don't will fly blind into the period (likely 2027) when AI spend becomes large enough that finance pays attention.
Key components
- Capture layer — LLM gateway and/or vendored SDK that records every call with structured tags
- Pricing layer — maintained model-pricing table mirroring vendor billing rules
- Attribution hierarchy — account → process → process run → task → agent action → LLM call
- Operational rollups — cost per task, per agent, per process run, per skill
- Vendor share analytics — cross-vendor breakdown by workload type
How it connects
In an Agentforce deployment, every Agent Action — whether it's summarizing a case, drafting an email, or running a sales play — triggers one or more LLM calls that Salesforce's native reporting won't break down by cost. Layering cost attribution on top of Agentforce lets you see exactly which agents and automations are driving your AI bill, so you can make scaling decisions grounded in unit economics rather than gut feel.
Good to know
Salesforce's Einstein and Agentforce usage dashboards show activity volume, not dollar cost per workload — so even heavy Salesforce shops need an attribution layer outside the platform to get true spend visibility. Start by instrumenting your highest-volume agents first; that's typically where 80% of the cost is hiding.
Related terms
Agent Observability
The practice of inspecting, debugging, and understanding AI agent behavior at runtime by consuming agent telemetry — traces, metrics, logs, and events — through dashboards, alerts, and evaluation tools.
Agent Operations
The discipline of running AI agents in production — capturing what they do, attributing what it costs, evaluating what they produce, and intervening when something goes wrong. The operational layer above agent observability and orchestration.
Agent Telemetry
The runtime data emitted by an AI agent — every decision, tool call, input, output, latency, and cost — used to monitor reliability, quality, and spend in production.
BYOK (Bring Your Own Key)
A model where users provide their own API keys for AI services (like OpenAI, Anthropic, or other LLM providers) instead of relying on the platform's bundled AI.
LLM Gateway
A unified proxy in front of multiple LLM providers that captures every call, enforces policy, and lets a single application talk to Anthropic, OpenAI, xAI, Gemini, and local models through one interface.