Omni Usage Logs
Access detailed call logs and usage analytics. Filter by provider, model, time range, status, and cost. Export logs and aggregate token usage across all connections.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Omni Usage Logs when an AI agent needs a reusable SKILL.md workflow for this job: Access detailed call logs and usage analytics. Filter by provider, model, time range, status, and cost. Export logs and aggregate token usage across all connections.
When not to use it
Skip Omni Usage Logs when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/omni-usage-logs # Save SKILL.md to ~/.claude/skills/omni-usage-logs/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/omni-usage-logs/SKILL.md. For a shared project, commit the folder at .claude/skills/omni-usage-logs/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Omni Usage Logs skill for this task: Use Omni Usage Logs when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->
## Overview
Access detailed call logs and usage analytics. Filter by provider, model, time range, status, and cost. Export logs and aggregate token usage across all connections.
## Authentication
All requests require a valid Bearer token or session cookie. Obtain a token via `POST /api/auth/login` or configure `REQUIRE_API_KEY=false` for local development.
## Endpoints
### GET /api/usage/analytics
Get usage analytics
```bash curl http://localhost:20128/api/usage/analytics \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/call-logs
Get call logs
```bash curl http://localhost:20128/api/usage/call-logs \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/call-logs/filters
Get call log filter options
Distinct providers, models, accounts and API keys seen in call logs, plus every configured API key (id and name only). Feeds the Logs tab filter dropdowns.
```bash curl http://localhost:20128/api/usage/call-logs/filters \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/call-logs/{id}
Get a specific call log
```bash curl http://localhost:20128/api/usage/call-logs/{id} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/{connectionId}
Get usage for a specific connection
```bash curl http://localhost:20128/api/usage/{connectionId} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/history
Get usage history
```bash curl http://localhost:20128/api/usage/history \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/logs
Get usage logs
```bash curl http://localhost:20128/api/usage/logs \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/proxy-logs
Get proxy logs
```bash curl http://localhost:20128/api/usage/proxy-logs \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/request-logs
Get request logs
```bash curl http://localhost:20128/api/usage/request-logs \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/budget
Get usage budget status
Returns current budget limits and consumption.
```bash curl http://localhost:20128/api/usage/budget \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/usage/budget
Configure usage budget
Set or update budget limits for usage tracking.
```bash curl -X POST http://localhost:20128/api/usage/budget \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/usage/cache-health
Get prompt-cache health summary
Summarizes the `write/read` cache ratio from `call_logs` for a time window: distribution (p50/p90/p99/max of cache-write tokens), warm/cold/rewrite/uncached call counts, the "heavy write" outlier share (10x the window median, floored at 1024 tokens — Anthropic's cache-creation minimum), and a per-model breakdown. Only successful (`status = 200`) calls with a non-null cache column are counted.
```bash curl http://localhost:20128/api/usage/cache-health \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/model-latency-stats
Get per-model/provider latency statistics
Aggregates `usage_history` rows into per-(provider, model) latency stats (avg/p50/p95/p99, std-dev, TTFT, tokens/sec) over a rolling window. Falls back from successful-only to all-sample rows when the successful count is below `minSamples`.
```bash curl http://localhost:20128/api/usage/model-latency-stats \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/log-export/types
List log-export destination types
Returns every registered destination type with the config field descriptors the dashboard renders its form from. Adding a destination type needs no UI change.
```bash curl http://localhost:20128/api/log-export/types \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/log-export/destinations
List log-export destinations
Secrets are redacted; a stored secret is returned as the literal `__stored__`.
```bash curl http://localhost:20128/api/log-export/destinations \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/log-export/destinations
Create a log-export destination
The config object is validated against the destination type's own schema. Secret keys declared by the type are encrypted at rest and never echoed back.
```bash curl -X POST http://localhost:20128/api/log-export/destinations \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/log-export/destinations/{id}
Read one log-export destination
```bash curl http://localhost:20128/api/log-export/destinations/{id} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### PUT /api/log-export/destinations/{id}
Update a log-export destination
Sending `__stored__` for a secret keeps the stored credential. The destination type is immutable after creation.
```bash curl -X PUT http://localhost:20128/api/log-export/destinations/{id} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### DELETE /api/log-export/destinations/{id}
Delete a log-export destination
Removes the destination and its export cursor.
```bash curl -X DELETE http://localhost:20128/api/log-export/destinations/{id} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/log-export/destinations/{id}/test
Test a log-export destination
Probes credentials and reachability without writing rows. A failed probe is reported as 200 with `ok: false` and an operator-facing reason.
```bash curl -X POST http://localhost:20128/api/log-export/destinations/{id}/test \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### POST /api/log-export/destinations/{id}/run
Run a log-export destination now
Drains pending call logs into this destination using the same cursor semantics as the hourly job.
```bash curl -X POST http://localhost:20128/api/log-export/destinations/{id}/run \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/log-export/status
Log-export scheduler status
Cron expression, recent job runs, and the per-destination backlog.
```bash curl http://localhost:20128/api/log-export/status \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/budget/bulk
GET usage › budget › bulk
```bash curl http://localhost:20128/api/usage/budget/bulk \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/codex-reset-credit
GET usage › codex reset credit
```bash curl http://localhost:20128/api/usage/codex-reset-credit \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/usage/codex-reset-credit
POST usage › codex reset credit
```bash curl -X POST http://localhost:20128/api/usage/codex-reset-credit \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/usage/combo-forecast
GET usage › combo forecast
```bash curl http://localhost:20128/api/usage/combo-forecast \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/combo-health
GET usage › combo health
```bash curl http://localhost:20128/api/usage/combo-health \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/combo-health-autopilot
GET usage › combo health autopilot
```bash curl http://localhost:20128/api/usage/combo-health-autopilot \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/combo-health-dashboard
GET usage › combo health dashboard
```bash curl http://localhost:20128/api/usage/combo-health-dashboard \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/combo-scoring-inspector
GET usage › combo scoring inspector
```bash curl http://localhost:20128/api/usage/combo-scoring-inspector \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/combo-trace/{id}
GET usage › combo trace › <id>
```bash curl http://localhost:20128/api/usage/combo-trace/{id} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/om-usage
GET usage › om usage
```bash curl http://localhost:20128/api/usage/om-usage \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/provider-limits
GET usage › provider limits
```bash curl http://localhost:20128/api/usage/provider-limits \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/usage/provider-limits
POST usage › provider limits
```bash curl -X POST http://localhost:20128/api/usage/provider-limits \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/usage/provider-window-costs
GET usage › provider window costs
```bash curl http://localhost:20128/api/usage/provider-window-costs \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/quota
GET usage › quota
```bash curl http://localhost:20128/api/usage/quota \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/requests-by-provider-date
GET usage › requests by provider date
```bash curl http://localhost:20128/api/usage/requests-by-provider-date \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/route-explain/{id}
GET usage › route explain › <id>
```bash curl http://localhost:20128/api/usage/route-explain/{id} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/token-limits
GET usage › token limits
```bash curl http://localhost:20128/api/usage/token-limits \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/usage/token-limits
POST usage › token limits
Save a per-key token limit. A key holds one limit per scope and reset interval, so daily, weekly and monthly limits for the same scope coexist. Without `id`, a new limit is added (or the key's limit for the same scope and interval is updated); with `id`, that limit is updated.
```bash curl -X POST http://localhost:20128/api/usage/token-limits \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### DELETE /api/usage/token-limits
DELETE usage › token limits
```bash curl -X DELETE http://localhost:20128/api/usage/token-limits \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/usage/utilization
GET usage › utilization
```bash curl http://localhost:20128/api/usage/utilization \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
## Payloads
See the full OpenAPI specification at `GET /api/openapi/spec` or `docs/openapi.yaml` for detailed request/response schemas.
Intended uses
- Use Omni Usage Logs when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.