Skip to content

Using multiple models

Combine models by route, step, complexity, or risk.

Updated on Aug 09, 2026

You do not have to use the same model across the entire product. Because the text models share the same interface, your application can select the identifier per feature, step, or complexity.

By routeA stable model for each feature: support, analysis, extraction, or code.
By stepDifferent models to classify, retrieve context, produce, and review.
By complexityStart with efficiency and route hard cases to greater capability.
By riskReserve strict review and human confirmation for the highest-impact actions.
type Tarefa = 'analise' | 'conversa' | 'extracao';
const modelos: Record<Tarefa, string> = {
  analise: 'hinow/himax',
  conversa: 'hinow/hinova',
  extracao: 'hinow/higenesis',
};
const model = modelos[tarefa];

Keep the decision visible and versioned. Record the model, the prompt version, tokens, cost, result, and the reason for any escalation. Run the evaluation again before changing the default.

Take the strategy to agents

Connect tools, enforce limits, and validate actions.

Building agentsModel selection
Was this page helpful?