Gateway administration
API keys
Review issued credentials and control access.
| Key / Owner | Status | Created / Expires | Spend | Actions |
|---|
| Time | Actor / Action | Target / Reason | Outcome |
|---|
Up to 93 days, inclusive in UTC. Totals cover the full filtered range, not just the visible page. LiteLLM's daily rollups may lag recent requests; spend is an estimate, not a provider invoice.
Usage breakdown
| Provider | Requests | Input tokens | Output tokens | Total tokens | Spend (USD) | Failed |
|---|
Request history
Request metadata recorded by LiteLLM. Prompts, responses, and credentials are not displayed. Models are recorded upstream names; provider-default changes do not rewrite history.
| Time / Request | User | Model | Tokens | Cost | Status |
|---|
User limits are shared across all that user's keys; key limits apply in addition. Alerts compare current LiteLLM spend with each individual cap, not the Usage date range. Spend may lag requests and concurrent requests can exceed a cap. No external notifications are sent.
| User / Key | Scope | Spend / Cap (USD) | Budget status | Reset schedule | RPM / TPM | Action |
|---|
Provider defaults
Admin-managedChoose where each provider's default alias sends new requests. Explicit model aliases are unchanged. Changes can affect cost and model capabilities.
Developer access policy
Default limits are shared across each Workspace user's keys. Key and team limits may also apply; inspect a key for its assigned policy. Budget exhaustion still stops requests.
Configured models
Model RPM/TPM are gateway deployment limits when configured; provider quotas are separate.
| Alias / Upstream | Provider | Developer access | Model RPM / TPM | Input / Output tokens |
|---|