Clatter LabsHelp Center

Why do I get 400 unsupported_content?

TroubleshootingUpdated

You sent content SuperCosmos can't read, almost always an image part. SuperCosmos reads text only.

Code: unsupported_content · HTTP status: 400

Message content must be a string or an array of {"type": "text"} parts.

Common causes#

  • an image_url part in a user message
  • an audio or file part
  • a library that adds image parts automatically (for example from a chat UI with attachments)

How to fix it#

  1. Remove non-text parts from messages.
  2. If you need the model to work with an image, describe it in text or extract the text from it first.
  3. If your UI allows attachments, block image uploads for SuperCosmos conversations.

Should my code retry?#

Not retryable: the same content fails every time.

The error body uses the OpenAI shape, so OpenAI SDKs raise it as an exception you can catch:

{"error": {"message": "...", "type": "...", "code": "unsupported_content", "param": null}}

Every response also carries an X-Request-Id. Keep it in your logs; it's the quickest way for support to find a request.

See the full list in the Model API 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.