Skip to main content
Keys
  • One API key per environment and service, each with a credit_limit, so a runaway loop cannot drain the balance. See API keys.
  • Keys live in server-side secrets, never in browser or mobile code.
Balance
  • A low balance alert on the Credits page, set above a day of spend.
  • Enough balance for your peak concurrency: each running paid request reserves 0.05 credits. See Limits.
Models
  • Model ids copied from the catalog, with their supported_parameters and input_modalities checked. NagaAI drops parameters a model does not support without an error.
  • A fallback model for your main one, used when a request fails with 503. NagaAI already retries across providers of the same model, but it does not switch models for you.
Requests
  • A client timeout that fits your longest answers. Long reasoning requests can run for minutes.
  • For Responses, the full conversation in every call. NagaAI keeps no state.
  • A routing strategy if latency or cache hits matter to you.
Errors
  • Retries with backoff on 408, 429 and 503, honoring Retry-After. See Errors.
  • Stream handlers that expect an error event after content has started.
  • The x-request-id header of every response in your logs. Support uses it to find the request.