Clatter LabsHelp Center

My stream arrives all at once instead of word by word. Why?

TroubleshootingUpdated

The Model API sends events as they're produced, so all-at-once output is almost always buffering on your side:

  • cURL: add -N.
  • Reverse proxies: turn off response buffering for that route.
  • Web frameworks: use a streaming response type and flush after each write.
  • Your code: make sure you read the stream as it arrives (for chunk in stream), not after collecting it.
  • Check you actually sent "stream": true.

On Max and Heavy, the first visible text can take longer because the model reasons first; print reasoning_content too to see activity.

Good to know#

  • New accounts get $5 of free credit; top up from $1 to $800 per purchase in Console › Billing › Credits. Billing
  • Keep keys on your server, never in a browser or mobile app. Why
  • Retry only 429 and 5xx errors, with backoff; honour Retry-After when it's sent. Which errors to retry

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.