Instruction following
Directional only- LFM2.5-230M
- 50.1
- Muse Glimmer 30B
- 77.0
- Weighted basis
- 2 vs 1 rows
- Reading
- Directional only
Provider changes are easy to miss. Radar watches releases, pricing, deprecations, and incidents at the source.Provider changes are easy to miss.
See RadarModel comparison
Updated August 10, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload.
At least one model is not scored in the current public ranking lane, so the page does not name an overall quality winner.
1 results are shared. Category rows based on different benchmark sets are marked directional and do not name a winner.
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.
Prompts that approach the documented context limit
Muse Glimmer 30B
Muse Glimmer 30B has the larger documented context window.
Confidence: documented
Code generation, repair, and software-engineering tasks
Not enough matched evidence
No shared weighted benchmark basis supports a winner.
Confidence: limited
Tool use, computer use, and multi-step task completion
Not enough matched evidence
No shared weighted benchmark basis supports a winner.
Confidence: limited
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
200K cached + 20K fresh input + 10K output tokens
Not enough matched evidence
The page does not recommend a cost winner because at least one model cannot fit the stated workload in one request. LFM2.5-230M does not fit this workload in one request. Muse Glimmer 30B does not fit this workload in one request. LFM2.5-230M has no comparable published API token rate. Muse Glimmer 30B has no comparable published API token rate.
Confidence: listed-rates
50K fresh input + 3K output tokens
Not enough matched evidence
The page does not recommend a cost winner because at least one model cannot fit the stated workload in one request. LFM2.5-230M does not fit this workload in one request. LFM2.5-230M has no comparable published API token rate. Muse Glimmer 30B has no comparable published API token rate.
Confidence: listed-rates
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
1 category uses different evidence sets. Those rows remain visible for coverage context but do not name a winner.
Each row states whether both averages use the same weighted benchmark set. Directional and not-comparable rows remain visible, but they never receive a winner in this template.
| Category | LFM2.5-230M | Muse Glimmer 30B | Weighted basis | Reading |
|---|---|---|---|---|
| Instruction following | 50.1 | 77.0 | Directional only2 vs 1 rows | Directional only |
| Agentic | Not measured | 65.9 | Not comparable0 vs 1 rows | Not comparable |
| Coding | Not measured | 57.8 | Not comparable0 vs 3 rows | Not comparable |
| Reasoning | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Knowledge | 21.2 | Not measured | Not comparable2 vs 0 rows | Not comparable |
| Math | Not measured | 94.7 | Not comparable0 vs 1 rows | Not comparable |
| Multilingual | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Multimodal | Not measured | 75.7 | Not comparable0 vs 2 rows | Not comparable |
Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.
Too few matched category axes support a radar. The ruled list below shows only shared benchmark results; positions use each benchmark’s normalized display scale when available.
IFBench
Instruction following
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.
1K fresh input + 500 output tokens
LFM2.5-230M has no comparable published API token rate. Muse Glimmer 30B has no comparable published API token rate.
50K fresh input + 3K output tokens
LFM2.5-230M does not fit this workload in one request. LFM2.5-230M has no comparable published API token rate. Muse Glimmer 30B has no comparable published API token rate.
200K cached + 20K fresh input + 10K output tokens
LFM2.5-230M does not fit this workload in one request. Muse Glimmer 30B does not fit this workload in one request. LFM2.5-230M has no comparable published API token rate. Muse Glimmer 30B has no comparable published API token rate.
Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.
Maximum documented context; output-token limits may be lower.
LFM2.5-230M
32K
Muse Glimmer 30B
131K
LFM2.5-230M
Not sourced
Muse Glimmer 30B
Not sourced
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
LFM2.5-230M
No comparable hosted API rate
Muse Glimmer 30B
No comparable hosted API rate
LFM2.5-230M
Not sourced
Muse Glimmer 30B
Not sourced
LFM2.5-230M
Not sourced
Muse Glimmer 30B
Not sourced
LFM2.5-230M
Not sourced
Muse Glimmer 30B
Not sourced
LFM2.5-230M
Non-Reasoning
Muse Glimmer 30B
Reasoning
LFM2.5-230M
Open Weight
Muse Glimmer 30B
Open Weight
LFM2.5-230M
Open Weight
Muse Glimmer 30B
Open Weight
LFM2.5-230M
2026-06-25
Muse Glimmer 30B
2026-08-10
Run the same representative tasks against both endpoints before changing production traffic.
The full public result ledger is available for audit without forcing a wide desktop table onto a phone.
BFCL v4
Not directly comparable
MCP Atlas
Not directly comparable
DeepSearchQA
Not directly comparable
skillsBench
Not directly comparable
OSWorld-Verified
Not directly comparable
SWE-bench Pro
Not directly comparable
SWE-bench Verified
Not directly comparable
Terminal-Bench 2.1
Not directly comparable
SciCode
Not directly comparable
AIME26
Not directly comparable
At least one model is not scored in the current public ranking lane, so the page does not name an overall quality winner. The page therefore keeps the decision tied to the specific documented workload.
The published evidence does not provide a shared weighted coding basis for both models, so BenchLM does not name a coding winner.
The published evidence does not provide a shared weighted agentic tasks basis for both models, so BenchLM does not name a agentic tasks winner.
Both models do not have comparable published API token rates, so this page does not name a universal price winner.
Muse Glimmer 30B has the larger documented context window: 131K, compared with 32K.
Last updated August 10, 2026
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 2,000+ readers.