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 avalar_workload key inside the request’s metadata object:
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 routing, model selection, price, or output. The
metadata echoed
back on the response is byte-identical to what you sent, original casing included.