Agentic
Not comparable- Hy3
- 47.8
- Estimated · #67/152
- Inworld Realtime TTS-2
- Not ranked
- Basis
- BenchAlign lane · 0 vs 0 public rows
- Reading
- Not comparable
Hy3 vs Inworld Realtime TTS-2
Updated September 10, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload.
Decision reading
The public evidence has no benchmark result shared by both models, so it does not support a quality verdict. Use the documented cost, context, and runtime rows instead.
0 results are shared. Category rows resting on Estimated evidence or different benchmark sets are marked directional and do not name a winner.
Share or export
Which one for your work
Recommendations appear only when a shared evidence basis or an explicit operating constraint supports the call. Secondary and unsupported use cases stay disclosed below the initial list.
No workload recommendation clears the current evidence threshold.
Use the matched evidence, workload costs, and sourced specifications below instead of treating a point score as a universal answer.
Show secondary and unsupported calls
Coding work
Code generation, repair, and software-engineering tasks
Not enough matched evidence
Inworld Realtime TTS-2 is not ranked on the public lane for coding, so no winner is named for coding.
Confidence: limited
Agentic work
Tool use, computer use, and multi-step task completion
Not enough matched evidence
Inworld Realtime TTS-2 is not ranked on the public lane for agentic, so no winner is named for agentic.
Confidence: limited
Long documents
Prompts that approach the documented context limit
Not enough matched evidence
A complete context comparison is not sourced.
Confidence: limited
Chat turn cost
1K fresh input + 500 output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Confidence: listed-rates
Cache-heavy agent loop cost
200K cached + 20K fresh input + 10K output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Confidence: listed-rates
Repository review cost
50K fresh input + 3K output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Confidence: listed-rates
What is actually comparable
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
Evidence parity totals are not available.
- Shared results
- 0
- Hy3 only
- 0
- Inworld Realtime TTS-2 only
- 0
- Like-for-like categories
- 0 / 8
Category results, on a stated basis
Each row shows the public-lane category score for both models: the BenchAlign lane for agentic, coding, and knowledge, and the weighted public rows elsewhere, with the same rank each model page reports. A row is like-for-like only when both scores rest on Supported evidence or the same weighted set. Directional and not-comparable rows remain visible, but they never receive a winner.
Coding
Not comparable- Hy3
- 58.1
- Supported · #29/151
- Inworld Realtime TTS-2
- Not ranked
- Basis
- BenchAlign lane · 0 vs 0 public rows
- Reading
- Not comparable
Reasoning
Not comparable- Hy3
- 75.3
- Unranked · 2 rankable rows
- Inworld Realtime TTS-2
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
Knowledge
Not comparable- Hy3
- 56.2
- Estimated · #48/183
- Inworld Realtime TTS-2
- Not ranked
- Basis
- BenchAlign lane · 0 vs 0 public rows
- Reading
- Not comparable
Math
Not comparable- Hy3
- Not ranked
- Inworld Realtime TTS-2
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
Multilingual
Not comparable- Hy3
- Not ranked
- Inworld Realtime TTS-2
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
Multimodal
Not comparable- Hy3
- Not ranked
- Inworld Realtime TTS-2
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
Instruction following
Not comparable- Hy3
- Not ranked
- Inworld Realtime TTS-2
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
| Category | Hy3 | Inworld Realtime TTS-2 | Basis | Reading |
|---|---|---|---|---|
| Agentic | 47.8Estimated · #67/152 | Not ranked | Not comparableBenchAlign lane · 0 vs 0 public rows | Not comparable |
| Coding | 58.1Supported · #29/151 | Not ranked | Not comparableBenchAlign lane · 0 vs 0 public rows | Not comparable |
| Reasoning | 75.3Unranked · 2 rankable rows | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Knowledge | 56.2Estimated · #48/183 | Not ranked | Not comparableBenchAlign lane · 0 vs 0 public rows | Not comparable |
| Math | Not ranked | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Multilingual | Not ranked | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Multimodal | Not ranked | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Instruction following | Not ranked | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
Ranks count the models scored in each category’s lane, so the agentic, coding, and knowledge denominators (BenchAlign) differ from the provisional-lane categories. Unranked scores sit on the lane’s scale but never name a winner. Like-for-like rows within 0.5 points read as a practical tie.
Shape of the matched evidence
Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.
A shared-evidence shape is not available.
BenchLM does not draw a radar or infer missing axes when the matched evidence is too sparse.
What each workload costs
Three fixed token mixes turn per-token rates into comparable decisions. Each scenario states context fit and whether cached input had to fall back to the published list-input rate.
Chat turn
1K fresh input + 500 output tokens
- Hy3
- Self-hosted; infrastructure cost varies
- Fits in one request
- Inworld Realtime TTS-2
- API rate not published
- Fit state unavailable
Hy3 has no comparable published API token rate. Inworld Realtime TTS-2 has no comparable published API token rate.
Repository review
50K fresh input + 3K output tokens
- Hy3
- Self-hosted; infrastructure cost varies
- Fits in one request
- Inworld Realtime TTS-2
- API rate not published
- Fit state unavailable
Hy3 has no comparable published API token rate. Inworld Realtime TTS-2 has no comparable published API token rate.
Cache-heavy agent loop
200K cached + 20K fresh input + 10K output tokens
- Hy3
- Self-hosted; infrastructure cost varies
- Fits in one request
- Cached-input rate unavailable
- Inworld Realtime TTS-2
- API rate not published
- Fit state unavailable
- Cached-input rate unavailable
Hy3 has no comparable published API token rate. Inworld Realtime TTS-2 has no comparable published API token rate.
Specification differences
Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.
SpecificationHy3Inworld Realtime TTS-2
Context window
Maximum documented context; output-token limits may be lower.
Hy3
256K
Inworld Realtime TTS-2
N/A
API model ID
Hy3
Not sourced
Inworld Realtime TTS-2
inworld-tts-2
Inworld model documentationCached-input rate
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
Hy3
No comparable hosted API rate
Inworld Realtime TTS-2
No comparable hosted API rate
Inworld model documentationDocumented inputs
Hy3
Not sourced
Inworld Realtime TTS-2
Not sourced
Documented outputs
Hy3
Not sourced
Inworld Realtime TTS-2
Not sourced
Provider availability
Hy3
Not sourced
Inworld Realtime TTS-2
Not sourced
Reasoning profile
Hy3
Reasoning
Inworld Realtime TTS-2
Non-Reasoning
Weight access
Hy3
Open Weight
Inworld Realtime TTS-2
Proprietary
License
Hy3
Open Weight
Inworld Realtime TTS-2
Proprietary
Release date
Hy3
2026-07-06
Inworld Realtime TTS-2
2026-08-31
If you already use one of these models
- Deployment change
- The models list different providers, so authentication, endpoint behavior, limits, and feature support may change.
- Quality signal
- The public evidence has no benchmark result shared by both models, so it does not support a quality verdict.
- Workload cost
- A complete comparable API-rate estimate is not available for both models.
- Context tradeoff
- A complete documented context comparison is not available.
Run the same representative tasks against both endpoints before changing production traffic.
Frequently asked questions
Which is better, Hy3 or Inworld Realtime TTS-2?
The public evidence has no benchmark result shared by both models, so it does not support a quality verdict. The page therefore keeps the decision tied to the specific documented workload.
Which is better for coding, Hy3 or Inworld Realtime TTS-2?
Inworld Realtime TTS-2 is not ranked on the public lane for coding, so no winner is named for coding.
Which is better for agentic tasks, Hy3 or Inworld Realtime TTS-2?
Inworld Realtime TTS-2 is not ranked on the public lane for agentic tasks, so no winner is named for agentic tasks.
Which costs less, Hy3 or Inworld Realtime TTS-2?
Both models do not have comparable published API token rates, so this page does not name a universal price winner.
Which has the larger context window, Hy3 or Inworld Realtime TTS-2?
A complete documented context-window comparison is not available.
Related comparisons
Last updated September 10, 2026
Watch Hy3 vs Inworld Realtime TTS-2
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 2,000+ readers.