Agentic
Not comparable- Granite-4.0-H-350M
- Not ranked
- LFM2.5-1.2B-JP-202606
- Not ranked
- Basis
- BenchAlign lane · 0 vs 0 public rows
- Reading
- Not comparable
Granite-4.0-H-350M vs LFM2.5-1.2B-JP-202606
Updated September 4, 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
LFM2.5-1.2B-JP-202606 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
Granite-4.0-H-350M and LFM2.5-1.2B-JP-202606 are 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
No clear pick
The documented context windows are equal.
Confidence: documented
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
The page does not recommend a cost winner because at least one model cannot fit the stated workload in one request. Granite-4.0-H-350M does not fit this workload in one request. LFM2.5-1.2B-JP-202606 does not fit this workload in one request. Granite-4.0-H-350M has no comparable published API token rate. LFM2.5-1.2B-JP-202606 has no comparable published API token rate.
Confidence: listed-rates
Repository review cost
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. Granite-4.0-H-350M does not fit this workload in one request. LFM2.5-1.2B-JP-202606 does not fit this workload in one request. Granite-4.0-H-350M has no comparable published API token rate. LFM2.5-1.2B-JP-202606 has no comparable published API token rate.
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
- Granite-4.0-H-350M only
- 0
- LFM2.5-1.2B-JP-202606 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- Granite-4.0-H-350M
- 43.6
- Estimated · #122/183
- LFM2.5-1.2B-JP-202606
- Not ranked
- Basis
- BenchAlign lane · 0 vs 0 public rows
- Reading
- Not comparable
Reasoning
Not comparable- Granite-4.0-H-350M
- 21.0
- Unranked · 2 rankable rows
- LFM2.5-1.2B-JP-202606
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
Knowledge
Not comparable- Granite-4.0-H-350M
- 35.2
- Estimated · #162/181
- LFM2.5-1.2B-JP-202606
- Not ranked
- Basis
- BenchAlign lane · 0 vs 0 public rows
- Reading
- Not comparable
Math
Not comparable- Granite-4.0-H-350M
- Not ranked
- LFM2.5-1.2B-JP-202606
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
Multilingual
Not comparable- Granite-4.0-H-350M
- Not ranked
- LFM2.5-1.2B-JP-202606
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
Multimodal
Not comparable- Granite-4.0-H-350M
- Not ranked
- LFM2.5-1.2B-JP-202606
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
Instruction following
Not comparable- Granite-4.0-H-350M
- 28.5
- #117/120
- LFM2.5-1.2B-JP-202606
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
| Category | Granite-4.0-H-350M | LFM2.5-1.2B-JP-202606 | Basis | Reading |
|---|---|---|---|---|
| Agentic | Not ranked | Not ranked | Not comparableBenchAlign lane · 0 vs 0 public rows | Not comparable |
| Coding | 43.6Estimated · #122/183 | Not ranked | Not comparableBenchAlign lane · 0 vs 0 public rows | Not comparable |
| Reasoning | 21.0Unranked · 2 rankable rows | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Knowledge | 35.2Estimated · #162/181 | 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 | 28.5#117/120 | 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
- Granite-4.0-H-350M
- Self-hosted; infrastructure cost varies
- Fits in one request
- LFM2.5-1.2B-JP-202606
- API rate not published
- Fits in one request
Granite-4.0-H-350M has no comparable published API token rate. LFM2.5-1.2B-JP-202606 has no comparable published API token rate.
Repository review
50K fresh input + 3K output tokens
- Granite-4.0-H-350M
- Self-hosted; infrastructure cost varies
- Does not fit in one request
- LFM2.5-1.2B-JP-202606
- API rate not published
- Does not fit in one request
Granite-4.0-H-350M does not fit this workload in one request. LFM2.5-1.2B-JP-202606 does not fit this workload in one request. Granite-4.0-H-350M has no comparable published API token rate. LFM2.5-1.2B-JP-202606 has no comparable published API token rate.
Cache-heavy agent loop
200K cached + 20K fresh input + 10K output tokens
- Granite-4.0-H-350M
- Self-hosted; infrastructure cost varies
- Does not fit in one request
- Cached-input rate unavailable
- LFM2.5-1.2B-JP-202606
- API rate not published
- Does not fit in one request
- Cached-input rate unavailable
Granite-4.0-H-350M does not fit this workload in one request. LFM2.5-1.2B-JP-202606 does not fit this workload in one request. Granite-4.0-H-350M has no comparable published API token rate. LFM2.5-1.2B-JP-202606 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.
SpecificationGranite-4.0-H-350MLFM2.5-1.2B-JP-202606
Context window
Maximum documented context; output-token limits may be lower.
Granite-4.0-H-350M
32K
LFM2.5-1.2B-JP-202606
32K
API model ID
Granite-4.0-H-350M
Not sourced
LFM2.5-1.2B-JP-202606
Not sourced
Cached-input rate
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
Granite-4.0-H-350M
No comparable hosted API rate
LFM2.5-1.2B-JP-202606
No comparable hosted API rate
Documented inputs
Granite-4.0-H-350M
Not sourced
LFM2.5-1.2B-JP-202606
Not sourced
Documented outputs
Granite-4.0-H-350M
Not sourced
LFM2.5-1.2B-JP-202606
Not sourced
Provider availability
Granite-4.0-H-350M
Not sourced
LFM2.5-1.2B-JP-202606
Not sourced
Reasoning profile
Granite-4.0-H-350M
Non-Reasoning
LFM2.5-1.2B-JP-202606
Non-Reasoning
Weight access
Granite-4.0-H-350M
Open Weight
LFM2.5-1.2B-JP-202606
Open Weight
License
Granite-4.0-H-350M
Open Weight
LFM2.5-1.2B-JP-202606
Open Weight
Release date
Granite-4.0-H-350M
2025-10-28
LFM2.5-1.2B-JP-202606
2026-05-26
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
- Both models list 32K.
Run the same representative tasks against both endpoints before changing production traffic.
Frequently asked questions
Which is better, Granite-4.0-H-350M or LFM2.5-1.2B-JP-202606?
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, Granite-4.0-H-350M or LFM2.5-1.2B-JP-202606?
LFM2.5-1.2B-JP-202606 is not ranked on the public lane for coding, so no winner is named for coding.
Which is better for agentic tasks, Granite-4.0-H-350M or LFM2.5-1.2B-JP-202606?
Granite-4.0-H-350M and LFM2.5-1.2B-JP-202606 are not ranked on the public lane for agentic tasks, so no winner is named for agentic tasks.
Which costs less, Granite-4.0-H-350M or LFM2.5-1.2B-JP-202606?
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, Granite-4.0-H-350M or LFM2.5-1.2B-JP-202606?
Both models list the same context window, 32K.
Related comparisons
Last updated September 4, 2026
Watch Granite-4.0-H-350M vs LFM2.5-1.2B-JP-202606
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 2,000+ readers.