Documentation

Choose models for support, translation, code, and images in the NexoRouter documentation.

Choose models for support, translation, code, and images

Pick a model from the current NexoRouter catalog with a small test set. Do not treat a marketing name, a screenshot, or an unofficial ranking as the source of truth.

Shared checklist

For every candidate:

  1. Confirm it appears in Models or GET /v1/models.
  2. Copy the exact catalog ID. Examples currently documented elsewhere include kimi-k2.6, gpt-5.5, gpt-5.6-luna, and grok-4.3 when they are listed as Available.
  3. Open the model profile and note capability, endpoint, billing unit, and published rates.
  4. Confirm the API key scope allows that ID.
  5. Run the same short prompts and read Usage Logs for quality, cost, latency, status, and request ID.

Do not invent a winner from one prompt. If an ID is not in Models, it is not a current public option.

Match the task to a capability

TaskWhat to look for in ModelsHow to test
Customer supportChat models that follow instructions in the customer language20 to 50 real tickets: greetings, policy questions, refusals, and handoff
TranslationChat models; compare source and target language qualityThe same paragraph in both directions, including names and formatting
CodeChat models; tool calling only if you verify it separatelyA small repo task plus a known-fail prompt
ImagesModels whose profile lists an image or media capability and endpointOne small generation using that profile's endpoint, not Chat Completions by default

China-developed and global families can both be valid. Compare them with the same test set. See China-developed and global models.

grok-4.3 is a live Available chat option when it appears in Models. Do not use retired or 404 profile URLs as examples.

Keep billing units comparable

Chat models usually publish separate input and output rates per million tokens. Image and other media models can use a different unit and a different endpoint.

Do not compare a chat token price with a media unit price. Read the profile before estimating cost.

Promote with controls

  1. Keep the first production key scoped to the chosen ID when possible.
  2. Set max_tokens or the media equivalent.
  3. Watch Usage Logs after the first live day.
  4. Keep a fallback ID that already passed the same test set.