Platform Capabilities & Constraints
A transparent breakdown of what our platform can (and cannot) extract from your API keys, categorized by provider.
Active Infrastructure (Supported Globally)
Because our platform acts as a reverse proxy, the following features work universally across all providers, regardless of their underlying API limitations.
| Capability | Description | Supported |
|---|---|---|
| Secure Proxy Rerouting | Hide your keys from client frontends using our endpoint. | |
| Fallback Load Balancing | Automatically route traffic to a secondary provider if the primary degrades. | |
| GitHub Leak Revocation | Instantly quarantine any key that appears in public repositories. |
Granular Usage & Billing Tracking
Unlike proxy routing, reading your exact total account spend or remaining credit balances requires explicit permission from the underlying provider. We categorize providers into three tracking tiers based on how strictly they restrict this data.
Zero-Setup Tracking
These providers allow us to track your full billing constraints and usage history directly from the API key itself. No extra configuration is needed. You plug it in, and we instantly sync your limits.
Manual Configuration Required
The provider's standard API keys do not grant access to billing data. To track spend on these platforms, you must provide a separate Organization API Key or explicitly enable Billing scopes in your provider settings.
Platform Limited
The provider's API structure completely blocks automated third-party billing extraction. We can securely proxy and route traffic to these models, but we cannot track your aggregate spend or pull credit limits into the unified dashboard.