Should my app let users enter their own Clatter Labs key?
It's possible: each user would provide their key and Account ID, and their own credits and responsibility apply. But you'd be holding other people's secrets:
- store them encrypted, never in logs or analytics,
- send them only to
api.gateway.clatterlabs.xyz, - let users remove them at any time,
- tell users to create a dedicated key with a low rate limit for your app.
If you'd rather not handle secrets, use your own key and bill users yourself.
Good to know#
- Model ids:
supercosmos-flash,supercosmos-max,supercosmos-heavy(SuperCosmos 1.1). Which to call - If calls fail unexpectedly, check status.clatterlabs.com before debugging further.
- Every response has an
X-Request-Id; log it so a request can be found later. Why log it
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
- How do I protect my app from prompt injection?
- How does the abuse policy affect my app on the Model API?
- How should I store my key and Account ID for Python?
- How should I store my API key and Account ID in my code?Cosmos Agent API
- What if my app's users write in a language I can't read?SuperCosmos models
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.