Unverified50% confidenceFactExact time
After an API key leaks, merely creating a new key does not invalidate the old one, which remains valid on the provider side until it is explicitly revoked.
1
Sources
50%
Confidence
Long-term
Relevance
10/17/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedPasskeys are not always exportable by design, and some passkeys may need to be re-registered in new tools during migration.76% similarUnverifiedAPI Keys are designed with no concept of expiration and remain valid long-term once generated; whereas tokens have an expiration time and require re-login to obtain after expiry.72% similarUnverifiedWhen rotating the master key in LiteLLM, if there is no salt key, use POST /key/regenerate with new_master_key (back up the database first); if there is a salt key, do not call that endpoint, just replace the key and restart.71% similarUnverifiedAn API Key is usually displayed in full only once upon creation, so it must be saved promptly.71% similarUnverifiedThe update fixes an issue where claude.ai Enterprise/Team users with leftover old API keys could not load managed settings, and makes the /status command able to mark currently inactive credentials67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1055682API
curl https://kongchang.com/api/v1/knowledge/claims/1055682MCP
get_claim(id=1055682)