Clatter LabsHelp Center

Why are Model API responses slow?

TroubleshootingUpdated

Things that make a reply take longer:

  • Effort: Max and Heavy reason first. In Benchmark 2, median time per task was about 3.5 s on Flash, 7.2 s on Max and 8.7 s on Heavy (measured with several requests in flight).
  • Long outputs: more tokens take more time.
  • Long prompts: more to read before answering.
  • Busy moments: check status.clatterlabs.com.

What helps: stream so text shows as it arrives; use Flash where depth isn't needed; set a sensible max_tokens; trim history.

Good to know#

  • Model ids: supercosmos-flash, supercosmos-max, supercosmos-heavy (SuperCosmos 1.1). Which to call
  • Every response has an X-Request-Id; log it so a request can be found later. Why log it
  • 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.