Choosing the Right Model

Selecting the optimal UltraSafe model for your application involves balancing four key considerations: capabilities, speed, cost, and domain expertise. This guide helps you make an informed decision based on your specific requirements.

Establish Key Criteria

When choosing a UltraSafe model, we recommend first evaluating these factors:

🎯 Capabilities

What level of reasoning complexity and specific features will you need the model to have? Consider whether you need general intelligence or specialized domain expertise.

⚡ Speed

How quickly does the model need to respond in your application? Consider user experience expectations and real-time requirements.

💰 Cost

What's your budget for both development and production usage? Higher capability models typically cost more per token.

🎓 Domain

Does your use case require specialized expertise in healthcare, finance, coding, or psychology? Expert models excel in their domains.

Pro Tip: Knowing these answers in advance will make narrowing down and deciding which model to use much easier.

Choose the Best Model to Start With

There are two general approaches you can use to start testing which UltraSafe model best works for your needs.

Option 1: Start with a Fast, Cost-Effective Model

For many applications, starting with a faster, more cost-effective model like ultrasafe/usf-mini can be the optimal approach:

  1. Begin implementation with ultrasafe/usf-mini
  2. Test your use case thoroughly
  3. Evaluate if performance meets your requirements
  4. Upgrade only if necessary for specific capability gaps

This approach allows for quick iteration, lower development costs, and is often sufficient for many common applications.

This approach is best for:

  • Initial prototyping and development
  • Applications with tight latency requirements
  • Cost-sensitive implementations
  • High-volume, straightforward tasks

Option 2: Start with the Most Capable Model

For complex tasks where intelligence and advanced capabilities are paramount, you may want to start with the most capable model and then consider optimizing to more efficient models down the line:

  1. Implement with ultrasafe/usf-pro or expert models
  2. Optimize your prompts for these models
  3. Evaluate if performance meets your requirements
  4. Consider increasing efficiency by optimizing workflow over time

This approach is best for:

  • Complex reasoning tasks
  • Scientific or mathematical applications
  • Tasks requiring nuanced understanding
  • Applications where accuracy outweighs cost considerations
  • Advanced coding and system design
  • Domain-specific expert knowledge requirements

Model Selection Matrix

When you need...We recommend starting with...Example use cases
Highest intelligence and reasoning, superior capabilities for the most complex tasksultrasafe/usf-proMulti-agent frameworks, complex codebase refactoring, nuanced creative writing, complex financial or scientific analysis
Balance of intelligence and speed, strong performance with faster response timesultrasafe/usf-baseComplex customer chatbot inquiries, content generation, straightforward agentic loops, data analysis
Fast responses at lower cost, optimized for high volume, straightforward applicationsultrasafe/usf-miniBasic customer support, high volume formulaic content generation, straightforward data extraction
Medical and healthcare expertiseultrasafe/usf-healthcareMedical Q&A, clinical guidelines, health information, medical research assistance
Financial and economic analysisultrasafe/usf-financeInvestment analysis, financial planning, market analysis, economic modeling
Programming and software developmentultrasafe/usf-codeCode generation, debugging, technical problem-solving, system architecture
Psychology and mental health applicationsultrasafe/usf-psychologyTherapeutic support, psychological assessment, mental health guidance, behavioral analysis

Expert vs General Models

🎓 Choose Expert Models When:

  • • Your use case falls clearly within a specific domain
  • • You need specialized knowledge and terminology
  • • Accuracy in the domain is critical
  • • You want to avoid off-topic responses
  • • Domain-specific reasoning is required

🌐 Choose General Models When:

  • • Your use case spans multiple domains
  • • You need flexibility in conversation topics
  • • General reasoning is more important than expertise
  • • You're building a general-purpose assistant
  • • Your requirements may evolve over time

Important: Expert Model Limitations

Expert models are designed to only answer questions within their specific domain of expertise. If users ask about topics outside their domain, they will politely decline and suggest consulting a different expert or general assistant. Plan your user experience accordingly.

Decide Whether to Upgrade or Change Models

To determine if you need to upgrade or change models, follow this systematic approach:

1. Create Benchmark Tests

Having a good evaluation set is the most important step in the process. Create test cases that represent your real-world usage:

  • Collect representative prompts from your actual use case
  • Define success criteria and quality metrics
  • Include edge cases and challenging scenarios
  • Set up automated testing where possible

2. Test with Your Actual Data

Use your real prompts and data to compare performance across models:

  • Test the same prompts across multiple models
  • Measure response quality, accuracy, and relevance
  • Track response times and costs
  • Gather feedback from actual users when possible

3. Compare Performance Metrics

Accuracy of Responses

Correctness, factual accuracy, relevance to the query

Response Quality

Clarity, completeness, usefulness, style consistency

Edge Case Handling

Graceful degradation, error handling, out-of-scope requests

4. Weigh Performance and Cost Tradeoffs

Consider the business impact of model choice:

Performance Factors

  • • User satisfaction and experience
  • • Task completion rates
  • • Response speed requirements
  • • Quality of outcomes

Cost Factors

  • • Token usage and pricing
  • • Development time savings
  • • Support and maintenance costs
  • • Scale and volume projections

Best Practices for Model Selection

🔬 Testing Strategy

  • • Start with a smaller, faster model for prototyping
  • • Use A/B testing to compare models in production
  • • Test with diverse, representative data
  • • Measure both quantitative and qualitative metrics

📊 Monitoring & Optimization

  • • Monitor model performance continuously
  • • Track cost per use case or user interaction
  • • Set up alerts for quality degradation
  • • Regularly review and update your model choice

🎯 Domain Considerations

  • • Consider regulatory requirements for your domain
  • • Evaluate need for specialized terminology
  • • Plan fallback strategies for expert models
  • • Test cross-domain scenarios if applicable

🚀 Scaling Considerations

  • • Plan for volume growth and cost implications
  • • Consider caching strategies for common queries
  • • Implement proper rate limiting and error handling
  • • Design for easy model switching if needed