The go-live checklist
Ten minutes of checks before launch saves you a bad night.
7 minLesson 9 of 90 of 2 steps
You now know what you need. This last short lesson is a list to read once before going live.
Keys
- Each service and each environment (development and production) has its own key.
- Keys live in environment variables or a secrets store, never in code or the repository.
- Every key has a monthly or daily cap.
- Expiry dates of important keys are in your calendar.
Money
- The balance covers a few peak days and the low-balance alert is on.
- The account's email is verified and notifications reach someone who'll act.
max_tokensis realistic for each kind of request.
Reliability
- Critical models have a fallback.
- 429 and 503 are retried with a growing delay, and
retry-afteris honoured. - You write full model ids, not aliases.
- Requests that must not repeat send
Idempotency-Key. - The client timeout is long enough for slow models.
Seeing what happens
- You log each request's
x-request-id. - You send
X-Titleso usage shows per application. - You know how to filter Usage & logs.
If you do only one thing on this list: put a cap on every key.
Team
- Whoever leaves is removed from the organization at once, and their keys are turned off.
- Guardrails are defined for sensitive data and allowed models.
Run the checklist0 of 2 steps
- Go through the list for one real service.
- For each "no", write down one small task.
What you learned
- Separate keys, caps, fallbacks and proper retries.
- Keep the
x-request-id. - Wherever you get stuck, open a ticket from Support.
Keep your place
Sign in to the panel and each lesson and your path are saved, so you continue from the same spot on any device.