Skip to main content

Why tag requests

Usage reporting groups by model. If you run invoice extraction and support-ticket triage against the same model, their spend lands in one bucket and you cannot tell which job costs what, or which one started failing. A workload tag fixes that. Send an optional name with each request and Valar records it on the usage ledger, so every job gets its own line in usage and spend even when several jobs share a model.

How it works

Send a valar_workload key inside the request’s metadata object:
That’s it. There is nothing to pre-register: the first tagged request creates the workload in your reporting.

Rules

default: untagged
Omit the key and nothing changes. Untagged requests are recorded exactly as before and appear as one “Untagged” bucket in the dashboard.
lowercase slug, max 64 chars
Tags are lowercased, whitespace becomes -, and anything outside a-z 0-9 . _ - is dropped. So "Invoice Extraction" and "invoice-extraction" are the same workload. A caller who types a human name and one who sends a slug agree instead of splitting spend across two buckets.
keep them stable
Reporting joins on the normalized name across time. Renaming a workload starts a new one; the old name keeps its history.
label only
The tag does not change model selection, price, or output. The metadata echoed back on the response is byte-identical to what you sent, original casing included.

Where you see it

The Usage and Serverless pages in the dashboard both have a Workload filter. It lists the tags your requests carried in the selected period: pick one to narrow every card, chart and table on the page to that workload, or pick Untagged for the requests sent without a tag. On Usage it combines with the other filters, so you can see one workload’s spend by model, by key or by product, for the selected workspace or across your whole organization.