LiteLLM spend tracking, attributed per person
If your AI traffic already runs through a LiteLLM gateway, Acticly pulls the billed spend straight from it and attributes it to people. One admin connects it once, and every tool behind the gateway is covered — with nothing for developers to install.
What Acticly reads
- Billed spend from your gateway, pulled on a schedule. Acticly connects out to you; you do not push to us.
- The principal each spend record belongs to, so cost lands on a person rather than a pool.
- Gateway health, re-checked every 15 minutes.
What you get
- Per-person cost for every tool routed through the gateway — including tools that have no telemetry of their own.
- One total across agents, models, and providers instead of several invoices.
- Spend controls that can act on the gateway. Every organization starts in dry-run: the loop computes and logs, and nothing reaches your gateway until you turn it on deliberately.
- Unmatched gateway principals surfaced in the existing identity-mapping screen, so attribution gaps are visible rather than silent.
How to connect
One admin, once, from Integrations. Supply the gateway base URL and a read key; Acticly probes what your gateway supports and tells you what it found before anything is stored as working.
Acticly → Integrations → AI → Connect a usage source
Base URL https://litellm.your-company.internal
Read key sk-... (read-only is enough to ingest)
Management key optional — only needed for spend controls
Leave it out and Acticly can report but never act.What this does not cover
- Traffic that does not go through the gateway. If a developer calls a provider directly, the gateway never sees it and neither do we.
- Prompt or completion content.
- Any change to your gateway by default. Enforcement ships in dry-run for every organization.