-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Omniroute Quota Telemetry
github-actions[bot] edited this page Aug 23, 2026
·
1 revision
OmniRoute separates provider quota telemetry from Ghostlight accounting.
-
healthymeans a source reported usable remaining capacity. -
approaching_limitmeans a source reported remaining capacity at or below the configured threshold. -
exhaustedis emitted only when a source reports zero capacity or usage at its limit. -
unavailablemeans a supported source failed to return data. -
unknownmeans no supported source exists or no provider limit is known.
Unknown is not exhausted and does not disable a provider.
Sources are preferred in this order: official provider API, authenticated usage API, explicitly mapped response headers, administrator configuration, local estimates, unknown. Local estimates are never presented as provider billing data.
Response headers are parsed only through an explicit provider mapping. Generic header names are not assumed globally.
OmniRoute · Website · npm · Docker Hub
- Setup Guide
- User Guide
- Features
- Quick Start (Docker)
- Electron Desktop App
- Termux (Android)
- PWA Guide
- MCP Server
- A2A Server
- Agent Protocols
- OpenCode Plugin
- Webhooks
- Cloud Agents
- Skills
- Memory
- Evals
- Gamification
- Guardrails
- Compliance
- Error Sanitization
- Public Credentials
- Route Guard Tiers
- Stealth Guide
- CLI Token Auth