view-usage

Query daily spend and token activity from a LiteLLM proxy.

77|12|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/BerriAI/litellm-skills --skill view-usage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: view-usage
Source: https://github.com/BerriAI/litellm-skills/tree/main/view-usage
Command: npx skills add https://github.com/BerriAI/litellm-skills --skill view-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Live LiteLLM proxies generate daily spend and token activity data across users, teams, and models; this skill centralizes visibility for cost management and performance auditing.

Core Features & Use Cases

  • Overview: Retrieve daily spend, token counts, and API requests for any entity (user, team, org, or model).
  • Drill-down: Break down metrics by model, team, or organization to identify cost drivers.
  • Auditing & Planning: Produce date-range summaries for billing, governance, and capacity planning.

Quick Start

Ask for a date range, run the correct endpoint, and display a table of daily spend, tokens, and requests.

Frequently Asked Questions about view-usage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor daily spend and token usage on my LiteLLM proxy?

To track LiteLLM proxy daily spend and token usage, query endpoints like /user/daily/activity or /team/daily/activity using a Bearer token. This returns JSON payloads containing daily spend, token counts, and API requests for your specified date range.

Can I break down LiteLLM proxy costs by team, organization, or user?

Yes, you can break down LiteLLM proxy costs by team, organization, user, or tag. The skill supports these drill-down views to identify cost drivers and produce date-range summaries for billing and capacity planning.

What do I need to query LiteLLM proxy daily activity data?

You need a running LiteLLM proxy, a valid Bearer token for authentication, and Python 3 with curl. These allow you to access proxy activity endpoints and retrieve JSON formatted usage metrics.

How does retrieving proxy usage data handle large date ranges?

Retrieving proxy usage data handles large date ranges by returning a JSON payload that includes pagination metadata. This ensures queries over extended periods return structured results without overwhelming the response.

What is the best way to audit API request costs across different models?

The best way to audit API request costs across models is to query your LiteLLM proxy daily activity endpoints. This provides centralized token counts and daily spend views to identify cost drivers for governance and billing.