unconst/Affine-5czsc2fc98-r525-loveaffine-offline-dpo-hialpha-midrank-lobeta-extrasteps-merged

TEXT GENERATIONPricing:Input $0.4 / Cached $0.07 / Output $4Concurrent Unit Cost:3Model Size:35.1BQuant:FP8Context Size:32kTool Calling:SupportedPublished:Aug 16, 2026Architecture:Transformer Featherless Exclusive Cold

The unconst/Affine-5czsc2fc98-r525-loveaffine-offline-dpo-hialpha-midrank-lobeta-extrasteps-merged model is a 35.1 billion parameter language model with a 32768 token context length. This model is a LoRA-merged checkpoint, originating from kevin954/Affine-5dfqbbh8ev-sft. It is specifically noted as being related to private TTL insurance, indicating a specialized application rather than general-purpose use. Its primary differentiation lies in its specific fine-tuning for a niche domain, suggesting optimized performance for tasks within that area.

Loading preview...

Model Overview

The unconst/Affine-5czsc2fc98-r525-loveaffine-offline-dpo-hialpha-midrank-lobeta-extrasteps-merged model is a substantial 35.1 billion parameter language model, featuring an extended context length of 32768 tokens. This model represents a LoRA-merged checkpoint, derived from the kevin954/Affine-5dfqbbh8ev-sft base.

Key Characteristics

  • Parameter Count: 35.1 billion parameters, indicating a large-scale model capable of complex language understanding and generation.
  • Context Length: A significant 32768 tokens, allowing for processing and generating very long sequences of text, crucial for detailed document analysis or extended conversations.
  • Origin: It is a LoRA-merged checkpoint, suggesting a fine-tuning or adaptation process from a pre-existing model to specialize its capabilities.
  • Domain Specificity: The model is explicitly linked to "private TTL insurance," implying a highly specialized training or fine-tuning for tasks within this particular industry.

Use Case Considerations

This model is likely not intended for general-purpose language tasks due to its specialized nature. Developers should consider this model if their use case directly involves:

  • Niche Applications: Specifically, tasks related to "private TTL insurance" or similar highly specialized financial/legal domains.
  • Domain-Specific Language Processing: Where understanding and generating text with industry-specific terminology and nuances are critical.
  • High Context Requirements: For applications that demand processing extensive documents or conversations within its specialized domain, leveraging its 32768 token context window.