Platform Capabilities & Constraints
A transparent breakdown of what our platform can (and cannot) extract from your API keys, categorized by provider.
Current Monitoring Capabilities
API Key Health stores and validates credentials for monitoring workflows. It does not currently proxy or reroute application traffic; available health and usage data still depends on each provider's API.
| Capability | Description | Supported |
|---|---|---|
| Encrypted Credential Storage | Protect saved API keys with AES-256-GCM encryption and workspace-based access controls. | |
| Provider Health Monitoring | Run provider validation checks and surface degraded, unauthorized, or rate-limited states. | |
| Leak Rotation Alerts | Flag provider-reported leaked or compromised keys for immediate rotation. GitHub repository scanning requires a connected GitHub source. |
Granular Usage & Billing Tracking
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 still validate saved credentials and report available provider health signals, but we cannot track your aggregate spend or pull credit limits into the unified dashboard.