API Key Health validates stored credentials against provider-specific endpoints and turns the response into clear states such as working, invalid, degraded, low quota, rotation needed, or provider-limited.
Provider-specific validation adapters
Wrong-provider hints where safe
Masked metadata in the dashboard
Each solution page is written to answer a real search question while still explaining exactly what API Key Health can and cannot see from provider APIs.
Validate a key immediately during Add Key.
Re-check keys from the dashboard.
Store the latest health state and last-checked timestamp.
Use provider-specific handling for APIs such as Gemini, OpenAI, SerpApi, ElevenLabs, and Apify.
Paste the key into the Add Key flow.
Select the provider that should own the key.
Run validation before saving.
Review status and fix wrong-provider or invalid-key states.
These pages use clear answers, schema, internal links, and provider-specific language so crawlers can understand the product without guessing.
Where safe, API Key Health can suggest a likely provider family based on non-secret key patterns or validation responses. If confidence is low, it simply reports the key as invalid.
No. The dashboard works with masked key data and safe metadata. Provider validation happens through authorized server flows.