Go-Live Checklist

Before sending production traffic:

• Keep API keys, authorization headers, prompts, generated content, and raw provider errors out of application logs.
• Log response.provider, response.model, response.id, and response.policy_version_id on every request. These correlate behavior changes to provider, model, and policy shifts.
• Pass a seed value for requests whose output you need to reproduce, such as tests and eval suites. Check response.determinism.seed_honored to know whether the selected provider honored it.
• Handle errors by error.category, not just HTTP status code. See the Error reference for the full table.
• Track these rates in your analytics: upstream_error_rate, model_output_rate, and fallback_to_deterministic_rate.
• Pin the preferred model in your routing policy for requests whose behavior must not change without an explicit policy edit. Otherwise LatentKit can route to another healthy eligible model as policy, provider health, or failover state changes.

Minimum log payload

{
  "latentkit_request_id": "req_abc123",
  "provider": "openai",
  "model": "gpt-4o-mini",
  "policy_version_id": "pol_v_xyz789",
  "input_tokens": 1234,
  "output_tokens": 567,
  "seed_honored": true
}

For failures, log:

{
  "latentkit_request_id": "req_abc123",
  "error_code": "UPSTREAM_ERROR",
  "error_category": "upstream",
  "provider": "anthropic",
  "model": "claude-sonnet-4-6",
  "retryable": true
}

Related

• Response contract
• Determinism and reproducibility
• Error reference
• Routes & policies