Docs
API key safety
Create, store, rotate, and revoke EasyAI API keys without exposing credentials in client code or public repositories.
Create and store a key
Create keys from the console API Keys page. Copy a new key into a server-side secret manager or environment variable immediately; treat it like a password.
Never commit a key to Git, place it in a browser bundle, or embed it in mobile and desktop binaries. Client applications should call your own backend instead.
EASYAI_API_KEY=sk-...Rotate a compromised key
If a key appears in logs, source control, a ticket, or a public URL, revoke it first and create a replacement. Review recent usage in the console and remove the leaked value from logs and history where possible.
Limit exposure
Use separate keys for development, staging, and production. Keep permissions and quotas as narrow as the console allows, and rotate keys when a team member or integration changes.