Hy3 vs Jev
At a Glance
| Compare |  Hy3Tencent |  JevTypeSafe |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $0.0825Openrouter ↗ · Sep 22, 2026 | $0.042TypeSafe ↗ · Sep 17, 2026 |
| Output priceFrom · USD / 1M tokens | $0.33Openrouter ↗ · Sep 22, 2026 | $0.000TypeSafe ↗ · Sep 17, 2026 |
| Context windowMaximum documented tokens | 262K | 64K |
| Model facts checked | Aug 28, 2026View model evidence → | Sep 17, 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
Side-by-Side Facts
| Field | Hy3 | Jev |
|---|---|---|
| Developer | Tencent | TypeSafe |
| Family | Hy3 | Jev |
| Model | Hy3 | Jev |
| Version | Hy3 | Jev |
| Lifecycle | active | active |
| Released | Unknown | 2026-09-15 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text | Text, Model-specific input |
| Output modalities | Text | Model-specific input |
| Context window | 262K | 64K |
| Total parameters | 298.8B | Unknown |
| Active parameters | 21B | Unknown |
| License | apache-2.0 | Unknown |
| Open weights | Yes | No |
| API available | Yes | Yes |
| Self-hostable | Yes | No |
| Provider access | Deepinfra (Standard), Hugging Face (Standard), Openrouter (Standard) | TypeSafe (Standard) |
| Capabilities | chat, generation, tools | calibrated-confidence, parallel-evaluation, structured_outputs, typed-decisions |
| Maximum Choice cardinality | Unknown | 255 options |
| Default request rate limit | Unknown | 1200 requests per minute |
| State plus longest question limit | Unknown | 32000 tokens |
| Combined state and questions limit | Unknown | 64000 tokens |
| Default token rate limit | Unknown | 250000 tokens per second |
Hy3 Capabilities
Jev Capabilities
Related Comparisons
All text comparisons →| A | Pair | B | Context |
|---|---|---|---|
 GPT-6 AstraOpenAI | vs | Hy3Tencent | cross-developer peerstext |
Claude Fable 5.1Anthropic | vs | Hy3Tencent | cross-developer peerstext |
 Gemini 3.1 ProGoogle DeepMind | vs | Hy3Tencent | cross-developer peerstext |
 DeepSeek-V4.1-FlashDeepSeek | vs | Hy3Tencent | cross-developer peerstext |
Hy3Tencent | vs | Grok 4.6xAI | cross-developer peerstext |
 Qwen3.8-MaxQwen | vs | Hy3Tencent | cross-developer peerstext |
 Kimi-K3Moonshot AI | vs | Hy3Tencent | cross-developer peerstext |
 MiniMax-M3MiniMax | vs | Hy3Tencent | cross-developer peerstext |
Hy3Tencent | vs |  GLM-5.3Z.ai | cross-developer peerstext |
Hy3Tencent | vs | Hy4 previewTencent | family variantstext |
Seed 2.1 ProByteDance Seed | vs | Hy3Tencent | cross-developer peerstext |
 Mistral Large 3Mistral AI | vs | Hy3Tencent | cross-developer peerstext |
Primary Evidence
Sources and Freshness
Questions
Hy3 vs Jev FAQs
Is Hy3 or Jev better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Hy3 and Jev, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Hy3 or Jev?+
Hy3 is $0.0825 and Jev is $0.042 per million tokens, so Jev is cheaper on this metric. Hy3 is $0.33 and Jev is $0.000 per million tokens, so Jev is cheaper on this metric.
Which has a larger context window, Hy3 or Jev?+
Hy3 has the larger sourced context window. Hy3 supports 262K and Jev supports 64K.
Which performs better in benchmarks, Hy3 or Jev?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Hy3 or Jev be self-hosted?+
Hy3 is the only model in this pair currently marked as self-hostable. Hy3 is open weight; Jev is not marked open weight.
Can Hy3 and Jev understand images?+
Hy3 is not documented with image input; Jev is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Hy3 or Jev?+
Neither has a larger sourced maximum output. Hy3 is — and Jev is —.
Do Hy3 and Jev support reasoning and tool use?+
Hy3: tool calling. Jev: none of these features are definitively sourced. Feature support does not establish relative quality.
Which is available from more inference providers, Hy3 or Jev?+
Hy3 has 3 sourced provider routes; Jev has 1, so Hy3 has broader tracked availability.
Which offers better value, Hy3 or Jev?+
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.