Cost transparency
LivePer-request token + cost log. Export to CSV for chargeback.
- ✓Per-request logging — tokens, cost, latency, model
- ✓Filter by user, workspace, feature, document
- ✓CSV export
- ✓Webhook export to external usage systems (enterprise)
What it is.
Every LLM call is logged with input tokens, output tokens, cached tokens, model used, latency, and cost. Admins can filter the log by user, workspace, feature, or document.
CSV export means you can roll these up into your own chargeback or budgeting systems.
Three steps.
End to end.
Any LLM call is logged automatically.
Admin → Usage. Filter by date, user, workspace, feature, model.
CSV export for chargeback, budget reconciliation, or external dashboards.
What you get.
- ✓Per-request logging — tokens, cost, latency, model
- ✓Filter by user, workspace, feature, document
- ✓CSV export
- ✓Webhook export to external usage systems (enterprise)
Quick answers.
Yes — the Intelligence API has a /usage endpoint that returns the same data programmatically.
More in AI Controls & Guardrails.
We do not train models on customer content without explicit opt-in. Default is off.
User-pasted text is sanitised before reaching the LLM.
Daily and monthly cost ceilings per organisation. Soft warnings, hard cutoffs.
Stable prompt prefixes are cached. Faster responses, lower bill, passed to you.