LLM Enrichment

Vantage LLM Enrichment attributes your model-provider spend to the teams, users, applications, and features that generated it. Each source delivers per-request token usage and the tags you attach; Vantage joins that usage to your provider costs and splits each matching cost row into enriched, tagged rows you can filter and group in Cost Reports, Virtual Tags, Budgets, and Cost Alerts. This surfaces attribution the provider bill never itemized, even when many applications share one API key. Choose the source that matches how your LLM traffic is delivered:

​

How It Works

However usage reaches Vantage, every source runs through the same pipeline and joins to your provider costs during that provider’s cost ingestion.

​

How Cost Rows Are Split

For each matched cost row, the cost is allocated proportionally across the tag slices present in your usage, weighted by token usage: $$\text{attributed cost} = \text{cost row} \times \frac{\text{slice tokens}}{\text{total matched tokens for row}}$$ Splits are additive: the sum of the enriched rows always equals the original cost row to the cent. Existing provider-level reports continue to show the same totals; enrichment only makes new dimensions available on the underlying rows.

​

Enrichment Tags

Once enrichment runs, a single provider cost line is split into multiple rows, each carrying enrichment tags. You can filter and group by these tags anywhere tags are supported: Cost Reports, Virtual Tags, Budgets, and Cost Alerts. Because enrichment splits (allocates) your provider costs, enrichment tags behave like Vantage’s cost allocation tags: you can build a Virtual Tag on them, but a cost can be allocated only once, so an enrichment tag can belong to only one allocation chain. Enriched rows carry two kinds of tags: the tags you attach to your requests, and the Vantage-managed vntg:ai:* tags that Vantage derives. Your own tag keys appear exactly as you send them, with no provider prefix, so a key like team lines up across every provider and you can group your entire AI stack by one tag. The dimensions Vantage derives carry a vntg:ai: prefix to keep them distinct and consistent across providers. Each source also promotes provider-specific vntg:ai:* tags where the data supports them (for example, vntg:ai:service_tier, vntg:ai:provider_region, vntg:ai:operation, or vntg:ai:principal_id); see each source’s page for its exact set and Managed AI Tags for the full cross-provider schema. Enrichment tags behave like any other provider tag in the console:

• To group: open the Group By menu, select Tag, and choose the tag key, for example vntg:ai:model or a tag key such as team.
• To filter: open the Filters menu, click New Rule, select Tag, choose the Tag Key, then pick an operator and one or more values.

The tag keys appear in the Tag Key dropdown once enriched costs exist. If you use a handful of keys often, mark them as preferred tags so they sort to the top of these menus.

​

Data Freshness and Backfill

Enrichment runs as part of each provider’s existing cost ingestion, so it follows that provider’s refresh cadence. Recent days are reprocessed within a rolling three-day window so late-arriving usage is picked up. See the provider data refresh documentation for per-provider timing. A billing period is enriched whenever it is processed while an active source exists, for as long as the matching usage remains available to Vantage. Re-enrichment reads the already-normalized cost data, so it does not require a full cost re-import. Backfill behavior varies by source; see each source’s page for specifics.

​

Import History

Every source records an Import History for each run, showing how much of your logged usage became enriched cost and where the rest went. See LLM Enrichment Import History for how to read every column, status, and disposition.