Which tier is best for debugging?
Start with Max for debugging from logs and failing tests.
The docs list debugging from logs and failing tests as a Max fit: it reasons before acting. If the bug is subtle (a race condition, memory issue, flaky test), move to Heavy.
If Max keeps failing on it, try Heavy; for small parts of the job, Flash is cheaper.
| Tier | Input / 1M | Output / 1M |
|---|---|---|
| Flash | $1.60 | $3.40 |
| Max | $1.80 | $3.80 |
| Heavy | $2.00 | $4.40 |
Good to know#
- SuperCosmos 1.1 is built to say "I don't know" rather than invent facts. How it's built to be honest
- SuperCosmos answers in your language, including Egyptian Arabic. Languages
- A request whose prompt is over 262K tokens bills its whole input at 1.5×; output prices don't change. Long-context pricing
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
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.