NexoRouter

Documentation

Model Lifecycle in the NexoRouter documentation.

Model Lifecycle

Status: Operational guidance.

Model availability can change when upstream providers update, rename, throttle, or retire models. Build integrations so the model ID is configurable.

Production practices

  • Keep model IDs in config, not hard-coded deep in business logic.
  • Use one fallback model for non-critical tasks.
  • Check Models before rollout.
  • Watch Usage Logs for model_not_found spikes.
  • Avoid undocumented aliases in production.

When a model changes

  1. Confirm the exact model ID in Models.
  2. Check whether the API key model scope still includes it.
  3. Run a small chat/completions request.
  4. Update tool configs.
  5. Monitor cost and latency after the change.
Model Lifecycle — NexoRouter