Xavier

​

Key specifications

​

Distinctive features

• Thinking tokens: Outputs explicit reasoning tokens that show the model’s step-by-step thinking process
• Emotional reasoning: Particularly strong at understanding and reasoning about emotional contexts
• Multi-step planning: Excels at breaking down complex problems into manageable steps
• Deliberate processing: Takes more time to generate responses but produces more thoughtful results

​

Use cases

• Mental health support applications
• Complex decision support systems
• Educational tools requiring step-by-step explanations
• Research assistance requiring nuanced reasoning
• Relationship coaching and conflict resolution
• Content that requires emotional intelligence and sensitivity

​

Example usage

import OpenAI from "openai";

const openai = new OpenAI({
  baseURL: "https://api.animusai.co/v2",
  apiKey: process.env.ANIMUS_API_KEY,
});

const completion = await openai.chat.completions.create({
  model: "xavier-r1",
  messages: [
    { 
      role: "system", 
      content: "You are Xavier, an assistant that shows step-by-step reasoning and has strong emotional intelligence." 
    },
    {
      role: "user",
      content: "I'm having a conflict with my colleague. They keep interrupting me in meetings, and I'm getting frustrated. How should I approach this situation?",
    },
  ],
});

console.log(completion.choices[0].message);

​

Performance considerations

• Increased token usage: The explicit reasoning process uses more tokens than standard responses
• Longer generation time: Takes more time to generate responses due to the additional reasoning steps
• Higher resource utilization: May require more computational resources for optimal performance

​

Access and availability

​

Best practices

• Be specific: Provide clear instructions about the reasoning you want to see
• Allow sufficient time: Expect and plan for slightly longer response times
• Consider context limits: Be mindful of the 8,000 token context window, especially with reasoning tokens
• Optimize token usage: For simpler tasks, consider using Vivian instead to save on token costs