Olmo 3.1 32B Instruct vs Hy3
At a Glance
| Compare | Hy3Tencent | |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | Not reported | $0.13Deepinfra ↗ · Sep 23, 2026 |
| Output priceFrom · USD / 1M tokens | Not reported | $0.528Openrouter ↗ · Sep 23, 2026 |
| Context windowMaximum documented tokens | 66K | 262K |
| Model facts checked | Aug 28, 2026View model evidence → | Aug 28, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
| Benchmark | Olmo-3.1-32B-Instruct | Hy3 |
|---|---|---|
| LMArena Text Arenatext-2026-09-13-d25aabda0010 · arena_rating · leader | 1,311.8391% of row best · rating · olmo-3.1-32b-instruct; 95% CI [1305.66595265, 1318.00150818]; votes 11452; rank 227 | 1,440.58100% of row best · rating · hy3; 95% CI [1433.39024152, 1447.77894384]; votes 8047; rank 65 |
| Overall ResultCounted from the protocol-matched rows above | 0 benchmark winsNo overall winner | 1 benchmark winNo overall winner |
Third-party benchmark Only like-for-like primary-publisher results are shown; raw scores, relative scores, configuration, and token spend remain visible.
Side-by-Side Facts
| Field | Olmo-3.1-32B-Instruct | Hy3 |
|---|---|---|
| Developer | Ai2 | Tencent |
| Family | Olmo 3 1 32b Instruct | Hy3 |
| Model | Olmo-3.1-32B-Instruct | Hy3 |
| Version | Olmo-3.1-32B-Instruct | Hy3 |
| Lifecycle | active | active |
| Released | Unknown | Unknown |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text | Text |
| Output modalities | Text | Text |
| Context window | 66K | 262K |
| Total parameters | 32.2B | 298.8B |
| Active parameters | Unknown | 21B |
| License | apache-2.0 | apache-2.0 |
| Open weights | Yes | Yes |
| API available | Unknown | Yes |
| Self-hostable | Yes | Yes |
| Provider access | Unknown | Deepinfra (Standard), Hugging Face (Standard), Openrouter (Standard) |
| Capabilities | chat, generation, tools | chat, generation, tools |
Olmo 3.1 32B Instruct Capabilities
Hy3 Capabilities
Primary Evidence
Sources and Freshness
Questions
Olmo 3.1 32B Instruct vs Hy3 FAQs
Is Olmo 3.1 32B Instruct or Hy3 better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Olmo 3.1 32B Instruct and Hy3, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Olmo 3.1 32B Instruct or Hy3?+
Only Hy3 has a directly sourced input price: $0.0825 per million tokens. Only Hy3 has a directly sourced output price: $0.33 per million tokens.
Which has a larger context window, Olmo 3.1 32B Instruct or Hy3?+
Hy3 has the larger sourced context window. Olmo 3.1 32B Instruct supports 66K and Hy3 supports 262K.
Which performs better in benchmarks, Olmo 3.1 32B Instruct or Hy3?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Olmo 3.1 32B Instruct or Hy3 be self-hosted?+
Both models have the same recorded self-hosting status: supported. Olmo 3.1 32B Instruct is open weight; Hy3 is open weight.
Can Olmo 3.1 32B Instruct and Hy3 understand images?+
Olmo 3.1 32B Instruct is not documented with image input; Hy3 is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Olmo 3.1 32B Instruct or Hy3?+
Neither has a larger sourced maximum output. Olmo 3.1 32B Instruct is 33K and Hy3 is —.
Do Olmo 3.1 32B Instruct and Hy3 support reasoning and tool use?+
Olmo 3.1 32B Instruct: tool calling. Hy3: tool calling. Feature support does not establish relative quality.
Which is available from more inference providers, Olmo 3.1 32B Instruct or Hy3?+
Olmo 3.1 32B Instruct has 0 sourced provider routes; Hy3 has 3, so Hy3 has broader tracked availability.
Which offers better value, Olmo 3.1 32B Instruct or Hy3?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.