Clatter LabsHelp Center

How should my app degrade if Heavy is slow or busy?

How-toUpdated
  • Stream Heavy replies so users see progress.
  • Set a timeout that fits your product; if Heavy runs past it or answers model_overloaded, retry the same request on Max (or Flash).
  • Tell the user when you've fallen back, if quality matters to them.
  • Log fallbacks to see how often they happen.

All tiers share the same window and message format, so the fallback request is identical apart from the model id.

Good to know#

  • If calls fail unexpectedly, check status.clatterlabs.com before debugging further.
  • Your key's account is responsible for your end users' text under the Abuse policy. What it means for apps
  • Base URL: https://api.gateway.clatterlabs.xyz/v1, with Authorization: Bearer clsk_... and X-Clatter-Account: CL-... on every call. Quick reference

Still need help?#

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.xyz
For deleting your whole account or the data of one service.