omni-usage-logs

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.

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.

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.

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.

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.

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.