What's the safest way to store Model API keys?
- Server only. Never in front-end code, mobile apps, public repos or screenshots.
- Secret manager or environment variables, not source files. Keep
.envout of git. - One key per service and environment, so you can revoke one without breaking others.
- Least permission: a Model API key needs only
models:invoke. - Low rate limits for keys that don't need high throughput limit the damage of a leak.
- Revoke first, rotate second if a key leaks.
Good to know#
- Your key's account is responsible for your end users' text under the Abuse policy. What it means for apps
- Model ids:
supercosmos-flash,supercosmos-max,supercosmos-heavy(SuperCosmos 1.1). Which to call - New accounts get $5 of free credit; top up from $1 to $800 per purchase in Console › Billing › Credits. Billing
Still need help?#
- General support: support@clatterlabs.com or team@clatterlabs.xyz
- Infrastructure questions, or permanent deletion of your data (your whole account or one service): infrastructure@clatterlabs.xyz
We usually reply within the first hour, and always within 24 hours. A full support team is with you.
Related articles
Still need help?
Tried the steps above and still stuck? Email us. We usually reply within the first hour, and always within 24 hours. A full support team is with you.
Infrastructure questions, or permanent deletion of your data
infrastructure@clatterlabs.xyzFor deleting your whole account or the data of one service.