Bring your LiteLLM records into a shared view of customer activity, requests, and spend. Start with the dashboard and logs, then add AI analysis to investigate customer experience and plan useful follow-up.
Request access if you’re new to LiteLedger. Sign in with your organization’s configured identity provider. Workspace access is approved by an administrator or through a pre-authorized domain. Have a workspace administrator complete the connection and sync steps below.
Enter the Base URL and choose Save URL. Expand Shared workspace key, enter the key, and choose Save shared key. These settings connect your workspace to one shared dataset.
Choose Test Connection. A successful result shows Connected to followed by your proxy URL. This checks access to the key-list endpoint; use the permissions listed above when choosing your connection key.
Choose Sync to import your proxy records. Follow the progress display as LiteLedger loads and prepares the data. When the run completes, explore your customer list, dashboard, request logs, and spend breakdowns. These views use synced records and work without an AI provider key.
Configure a supported AI provider for analysis and Ask. The provider settings are separate from your data-source connection. Add guides and terminology in Settings → Product Knowledge to give the analysis your product context. Review AI usage and costs →
In Automatic Sync, enable the daily schedule, choose a time and timezone, and select Save time. Workspace administrators manage the schedule; the panel shows the last automatic run and the next scheduled time.
The first sync imports available detailed request records and daily activity totals. How far back each reaches depends on your proxy’s retained history; daily totals can extend beyond the conversations available to read.
LiteLedger keeps synced request records by default, so your history builds with continued syncing. Workspace admins can configure detailed-record retention in Settings → Data Governance.
Explore a sample report to see the signals, session evidence, and recommended actions that analysis brings together.
Add product context · Explore data handling and access controls