On this page
01
Keep Gateway Decisions Separate From Finance Decisions
LiteLLM is often adopted for gateway compatibility and model access. Cloptima focuses on AI FinOps: attribution, budget policy, reconciliation-ready records, and unit economics.
02
Inventory Current Keys And Teams
Map virtual keys, teams, apps, providers, and model permissions before creating Cloptima policies and reporting dimensions.
03
Run in parallel — forward LiteLLM usage
Keep LiteLLM serving traffic and forward its usage to Cloptima's LiteLLM ingest endpoint, so finance gets attribution and reconciliation while you evaluate. No app rewrite required to start.
bash
# Point LiteLLM logging / callbacks at Cloptima
https://api.cloptima.ai/v1/ai/integrations/litellm/events
# Authorization: Bearer clop_vk_dPXO67p…04
Move finance workflows
Bring budget controls, allocation, chargeback, and a reconciliation-ready ledger into Cloptima while preserving the execution stack that still works for your apps. Move enforcement to Cloptima's gateway only where request-path controls are required.