Agentic
Directional only- Inkling
- 40.7
- Supported · #119/151
- Laguna S 2.1
- 48.2
- Estimated · #77/151
- Basis
- BenchAlign lane · 4 vs 2 public rows
- Reading
- Directional only
Inkling vs Laguna S 2.1
Updated September 4, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload.
Decision reading
At least one model is not scored in the current public ranking lane, so the page does not name an overall quality winner.
3 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.
Chat turn cost
1K fresh input + 500 output tokens
Laguna S 2.1
Laguna S 2.1 has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.
Confidence: listed-rates
Cache-heavy agent loop cost
200K cached + 20K fresh input + 10K output tokens
Laguna S 2.1
Laguna S 2.1 has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.
Confidence: listed-rates
Show secondary and unsupported calls
Repository review cost
50K fresh input + 3K output tokens
Laguna S 2.1
Laguna S 2.1 has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.
Confidence: listed-rates
Coding work
Code generation, repair, and software-engineering tasks
Not enough matched evidence
Laguna S 2.1 is scored on Estimated evidence for coding, so the reading is directional rather than like-for-like.
Confidence: limited
Agentic work
Tool use, computer use, and multi-step task completion
Not enough matched evidence
Laguna S 2.1 is scored on Estimated evidence for agentic, so the reading is directional rather than like-for-like.
Confidence: limited
Long documents
Prompts that approach the documented context limit
No clear pick
The documented context windows are equal.
Confidence: documented
What is actually comparable
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
18 Inkling only
3 Shared
3 Laguna S 2.1 only
- Shared results
- 3
- Inkling only
- 18
- Laguna S 2.1 only
- 3
- Like-for-like categories
- 0 / 8
2 categories rest on Estimated evidence or different evidence sets. Those rows remain visible for coverage context but do not name a winner.
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
Directional only- Inkling
- 41.4
- Supported · #132/183
- Laguna S 2.1
- 47.8
- Estimated · #87/183
- Basis
- BenchAlign lane · 6 vs 4 public rows
- Reading
- Directional only
Reasoning
Not comparable- Inkling
- 73.7
- Unranked · 2 rankable rows
- Laguna S 2.1
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
Knowledge
Not comparable- Inkling
- 58.5
- Supported · #45/181
- Laguna S 2.1
- Not ranked
- Basis
- BenchAlign lane · 6 vs 0 public rows
- Reading
- Not comparable
Math
Not comparable- Inkling
- 78.9
- Unranked · 1 rankable row
- Laguna S 2.1
- Not ranked
- Basis
- Provisional lane · 1 vs 0 weighted rows
- Reading
- Not comparable
Multilingual
Not comparable- Inkling
- Not ranked
- Laguna S 2.1
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
Multimodal
Not comparable- Inkling
- 48.7
- #38/48
- Laguna S 2.1
- Not ranked
- Basis
- Provisional lane · 2 vs 0 weighted rows
- Reading
- Not comparable
Instruction following
Not comparable- Inkling
- 85.2
- #43/120
- Laguna S 2.1
- Not ranked
- Basis
- Provisional lane · 1 vs 0 weighted rows
- Reading
- Not comparable
| Category | Inkling | Laguna S 2.1 | Basis | Reading |
|---|---|---|---|---|
| Agentic | 40.7Supported · #119/151 | 48.2Estimated · #77/151 | Directional onlyBenchAlign lane · 4 vs 2 public rows | Directional only |
| Coding | 41.4Supported · #132/183 | 47.8Estimated · #87/183 | Directional onlyBenchAlign lane · 6 vs 4 public rows | Directional only |
| Reasoning | 73.7Unranked · 2 rankable rows | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Knowledge | 58.5Supported · #45/181 | Not ranked | Not comparableBenchAlign lane · 6 vs 0 public rows | Not comparable |
| Math | 78.9Unranked · 1 rankable row | Not ranked | Not comparableProvisional lane · 1 vs 0 weighted rows | Not comparable |
| Multilingual | Not ranked | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Multimodal | 48.7#38/48 | Not ranked | Not comparableProvisional lane · 2 vs 0 weighted rows | Not comparable |
| Instruction following | 85.2#43/120 | Not ranked | Not comparableProvisional lane · 1 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.
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.
Terminal-Bench 2.0
Agentic
SWE-bench Pro
Coding
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
- Inkling
- $0.00421
- Fits in one request
- Laguna S 2.1
- $0.0002
- Fits in one request
Laguna S 2.1 has the lower modeled cost
Costs use the listed standard API rates.
Repository review
50K fresh input + 3K output tokens
- Inkling
- $0.10754
- Fits in one request
- Laguna S 2.1
- $0.0056
- Fits in one request
Laguna S 2.1 has the lower modeled cost
Costs use the listed standard API rates.
Cache-heavy agent loop
200K cached + 20K fresh input + 10K output tokens
- Inkling
- $0.159
- Fits in one request
- Laguna S 2.1
- $0.006
- Fits in one request
Laguna S 2.1 has the lower modeled cost
Costs use the listed standard API rates.
Specification differences
Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.
SpecificationInklingLaguna S 2.1
Context window
Maximum documented context; output-token limits may be lower.
Inkling
1M
Laguna S 2.1
1M
API model ID
Inkling
Not sourced
Laguna S 2.1
Not sourced
Cached-input rate
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
Inkling
$0.374 per 1M cached input tokens
Laguna S 2.1
$0.01 per 1M cached input tokens
Documented inputs
Inkling
Not sourced
Laguna S 2.1
Not sourced
Documented outputs
Inkling
Not sourced
Laguna S 2.1
Not sourced
Provider availability
Inkling
Not sourced
Laguna S 2.1
Not sourced
Reasoning profile
Inkling
Hybrid
Laguna S 2.1
Reasoning
Weight access
Inkling
Open Weight
Laguna S 2.1
Open Weight
License
Inkling
Open Weight
Laguna S 2.1
Open Weight
Release date
Inkling
2026-07-15
Laguna S 2.1
2026-07-21
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
- At least one model is not scored in the current public ranking lane, so the page does not name an overall quality winner.
- Workload cost
- Repository review: $0.10754 vs $0.0056. Cache-heavy agent loop: $0.159 vs $0.006.
- Context tradeoff
- Both models list 1M.
Run the same representative tasks against both endpoints before changing production traffic.
Benchmark evidence
The full public result ledger is available for audit without forcing a wide desktop table onto a phone.
Browse raw public benchmark evidence24 rows
Agentic
Terminal-Bench 2.0
Inkling63.8%SourceLaguna S 2.170.2%SourceLaguna S 2.1 leads this result
BrowseComp
Inkling77.1%SourceLaguna S 2.1—Not directly comparable
MCP Atlas
Inkling74.1%SourceLaguna S 2.1—Not directly comparable
Terminal-Bench 2.1 (Vals)
Inkling47.6%SourceLaguna S 2.1—Not directly comparable
Toolathlon-Verified
Inkling—Laguna S 2.149.7%SourceNot directly comparable
Coding
SWE-bench Verified
Inkling77.6%SourceLaguna S 2.1—Not directly comparable
SWE-bench Pro
Inkling54.3%SourceLaguna S 2.159.4%SourceLaguna S 2.1 leads this result
Terminal-Bench 2.0
Inkling63.8%SourceLaguna S 2.170.2%SourceLaguna S 2.1 leads this result
FrontierSWE v2
Inkling4.1%SourceLaguna S 2.1—Not directly comparable
LiveCodeBench (Vals)
Inkling85.5%SourceLaguna S 2.1—Not directly comparable
SWE-bench (Vals)
Inkling77.6%SourceLaguna S 2.1—Not directly comparable
SWE Multilingual
Inkling—Laguna S 2.178.5%SourceNot directly comparable
deepSwe
Inkling—Laguna S 2.140.4%SourceNot directly comparable
Knowledge
GPQA
Inkling87.9%SourceLaguna S 2.1—Not directly comparable
GPQA-D
Inkling87.9%SourceLaguna S 2.1—Not directly comparable
HLE
Inkling46%SourceLaguna S 2.1—Not directly comparable
HLE w/o tools
Inkling30%SourceLaguna S 2.1—Not directly comparable
GPQA Diamond (Vals)
Inkling87.1%SourceLaguna S 2.1—Not directly comparable
MMLU-Pro (Vals)
Inkling86.3%SourceLaguna S 2.1—Not directly comparable
Math
AIME26
Inkling97.1%SourceLaguna S 2.1—Not directly comparable
Multimodal
Instruction following
IFBench
Inkling79.8%SourceLaguna S 2.1—Not directly comparable
Frequently asked questions
Which is better, Inkling or Laguna S 2.1?
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.
Which is better for coding, Inkling or Laguna S 2.1?
Laguna S 2.1 scores higher for coding on the public lane, 47.8 to 41.4. Laguna S 2.1 is scored on Estimated evidence for coding, so the reading is directional rather than like-for-like. BenchLM does not name a winner for coding from a directional reading; read the shared benchmark rows directly and test the models on the same task set.
Which is better for agentic tasks, Inkling or Laguna S 2.1?
Laguna S 2.1 scores higher for agentic tasks on the public lane, 48.2 to 40.7. Laguna S 2.1 is scored on Estimated evidence for agentic tasks, so the reading is directional rather than like-for-like. BenchLM does not name a winner for agentic tasks from a directional reading; read the shared benchmark rows directly and test the models on the same task set.
Which costs less, Inkling or Laguna S 2.1?
For the stated presets, chat costs $0.00421 on Inkling and $0.0002 on Laguna S 2.1; repository review costs $0.10754 and $0.0056; the cache-heavy agent loop costs $0.159 and $0.006. Costs use the listed standard API rates.
Which has the larger context window, Inkling or Laguna S 2.1?
Both models list the same context window, 1M.
Related comparisons
Last updated September 4, 2026
Watch Inkling vs Laguna S 2.1
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 2,000+ readers.