Skip to content
TukaiDevelopers

Search the documentation

Console
Documentation menu

Guides

Going to production

The checklist before serving real users - keys, shared balance, actual limits, errors, data, support - and the case of agencies.

Verified on 4 October 2026Markdown versionReport a problem on this page

Checklist

  • A dedicated key for the production application, separate from your trial and development keys.
  • The key is server-side only (environment variable or secrets manager), never in a browser or a mobile app.
  • The key allows only the models used by the application.
  • A monthly cap is set on the key, at a level you are willing to lose if it leaks.
  • The account's entitlements are monitored (credits, plan usage limits): they are shared with the app and the Studio, and nothing reserves them for your application (see below).
  • Your code handles 402 (balance), 429 (rate or limits) and 5xx, with bounded, spaced-out retries — see Errors.
  • Client-side timeouts are long: a generation can take more than a minute. Retrying too quickly produces a second, billed generation.
  • You log the x-request-id header of each response, without logging the key.
  • You know how to revoke the key and deploy a new one quickly.
  • The chosen model still exists in the catalog (French), and you have planned what to do if it is withdrawn: Tukai never silently replaces one model with another.

The actual limits

LimitValueEnforced by
Rate per key, generation30 requests per minuteThe API (ratelimit-* headers)
Rate per key, token counting300 requests per minuteThe API
Monthly cap per keyThe one you setThe API, before each generation call (UTC calendar month)
Your plan's usage limitsThose of your subscriptionThe API, as for the chat: shared with the app
Account balanceYour balanceThe API (402 when it runs out)

There is currently no account-level spending cap, no spending alert, and no balance reserved for the API. Practical consequence: if the production application is critical, give it a Tukai account that is used for nothing else.

Data

What happens to the content of your requests, what is kept and what is not: see Data (French). For sensitive use, write to support before sending any data.

Agencies and contractors

If you develop for a client:

  • The Tukai account, the balance and the production keys must belong to the client. Create the keys from their account, never from yours.
  • Never share your own key with a client, and do not reuse one client's key for another.
  • When the project is handed over, the client revokes the keys you handled and creates new ones.
  • The terms of use provide for an invoice for each transaction, and an invoice in a company's name on request.

Support and service status

  • Support: service-client@tukhnanutha.com or +216 22 450 577. No response time is guaranteed.
  • There is no public service status page yet. A series of 503 or 504 errors should be reported to support with the relevant x-request-id values.