Should I cache Model API responses?

If many users ask the same thing (an FAQ bot, a fixed summary), caching answers in your own system saves cost and makes replies instant. Clatter Labs doesn't publish a prompt-caching discount, so your own cache is the way to save on repeats.

Don't cache answers that depend on personal data, live information or conversation history, and set an expiry so answers refresh.

Good to know#

• Every response has an X-Request-Id; log it so a request can be found later. Why log it
• Each key has its own limit: 10, 30 (default), 60 or 120 requests per minute. Rate limits
• 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?#

• 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.