What we collect.
Every source is stored the same way, so a gateway, a bill and a seat license add up to one number. Here is what a line of it carries, and what it cannot carry at all.
What it carries
- When and what
- The instant, the vendor, and the model as the vendor names it.
- Who it belongs to
- The application or key that called, and the agent, workflow and team once attribution has given it one.
- The levels above the team
- Department and business unit are read from the organization chart each time, never written down. A reorganization rewrites no history.
- How much
- Tokens in, out and served from cache, by the vendor's own count; calls; or seats and days where the seat is the unit.
- How it went
- Whether it succeeded, how long it took, and which attempt it was. Retry opportunities use this.
- What it cost
- The ledger's figure, what the source itself said where it said anything, and which rate card priced it.
- A shape, never a text
- A prompt is kept as a hash of its shape so the caching and prompt-size opportunities can compare calls. A seat holder is a hash. Neither can be read back into what it came from.
For governance
Beside the usage record: the AI apps in a directory you connect, by name and count; who holds each AI seat; three vendor settings, as on or off; and the documents you list, as links. Governance and compliance says what each one is for.
Never held
There is nowhere to put any of these. A connector that received one would have no field for it. A test fails the build if one is added.
- prompts
- completions
- conversations
- transcripts
- documents
- source code
So if Valistry is breached, your AI vendors’ prompts and replies are not there to take.
Money
Every amount is an integer number of millionths of a dollar. Sums are exact, and every grouping on every screen adds back to the same total.
A rate card names the version that priced a line, and a price never changes without a person reading the diff.