omni-usage-logs

Centralize and analyze API usage data across providers, models, and time ranges.

Updated Jun 6, 2026

Search Tags:#monitoring #analytics #logs #usage #export #provider #cost-tracking

Ready to run

npx skills add https://github.com/DevMHOne/nextroute --skill omni-usage-logs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: omni-usage-logs
Source: https://github.com/DevMHOne/nextroute/tree/main/skills/omni-usage-logs
Command: npx skills add https://github.com/DevMHOne/nextroute --skill omni-usage-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralize and analyze API usage data across all connections for visibility, cost control, and debugging.

Core Features & Use Cases

Detailed usage logs and analytics across providers and models
Filter by provider, model, time range, status, and cost
Export logs and aggregate token usage across all connections
Use case: quickly diagnose anomalous usage and generate consolidated reports

Quick Start

Filter usage by provider, model, and time range, then export the results.

Frequently Asked Questions about omni-usage-logs

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

FAQPage Schema

How do I track API usage logs across multiple providers?▼

You can track API usage logs across multiple providers by centralizing and analyzing data from all connections. The system aggregates logs across providers, models, and time ranges to give you consolidated operational visibility.

What is the best way to export consolidated API cost tracking data?▼

The best way to export API cost tracking data is to filter usage logs by provider, model, time range, status, and cost. This allows you to generate consolidated reports and aggregate token usage across all connections for export.

How do I diagnose anomalous API usage and token consumption?▼

To diagnose anomalous API usage, you can filter usage logs by provider, model, and time range to spot irregular patterns. Detailed analytics and per-connection usage endpoints help quickly identify unexpected token consumption or cost spikes.

Can I filter API usage analytics by model, time range, and status?▼

Yes, you can filter API usage analytics by provider, model, time range, status, and cost. This filtering capability supports operational monitoring and debugging to isolate specific usage events across all authenticated connections.

Does centralized API usage monitoring require authenticated requests for budget overview?▼

Yes, retrieving a budget overview and centralized API usage monitoring requires authenticated requests. Authentication ensures secure access to analytics, logs, and per-connection usage data across all integrated providers.

Why am I unable to see per-connection usage data across all providers?▼

Per-connection usage data requires authenticated requests to access the centralized analytics endpoints. Ensure your connections are properly authenticated to retrieve accurate logs and budget overviews across all providers.