Trinity Nano
trinity-nano
Last refreshed 2026-05-11. Next refresh: weekly.
Trinity Nano is worth evaluating for long context when its provider route and context window match the workload.
Decision context: Long context task fit, 1 tracked provider route, and research from 2026-01-01.
Use it for
- Teams evaluating long context
- Workloads that can use a 128K context window
- Buyers comparing 1 tracked provider route
Do not use it for
- Vision or document-understanding workloads
- Strict JSON or tool-calling flows
Cheapest output
-
Arcee AI per 1M tokens
Provider routes
1
Tracked API hosts
Quality / dollar
Unknown
No task benchmark coverage yet
Freshness
2026-01-01
Researched 140d ago
Top use-case fit
Long context
Included by capability and metadata signals in the decision map.
Provider price ladder
| Provider | Input / 1M | Output / 1M | Route |
|---|---|---|---|
| Arcee AI | - | - | ServerlessPartial |
Benchmark peer barsfor Long context
No task-mapped benchmark peers are available for this model yet.
Migration checks
No linked migration route is available for this model yet.
About
6B sparse MoE with ~1B active parameters per token and 128K context window. Trained on 10T tokens. Personality-forward chat model designed for edge deployment and fast inference; experimental/preview status. Open-source under Apache 2.0.
Trinity Nano has a 128K-token context window.
Capabilities
No model capability flags are currently sourced.