Reasoning
Like-for-like- GPT-5.2
- 52.9
- Inkling-Small
- 40.1
- Weighted basis
- 1 vs 1 rows
- Reading
- GPT-5.2 leads
Model comparison
GPT-5.2 vs Inkling-Small
Updated July 30, 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.
7 results are shared. Category rows based on different benchmark sets are marked directional and do not name a winner.
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.
Long documents
Prompts that approach the documented context limit
Inkling-Small
Inkling-Small has the larger documented context window.
Confidence: documented
Chat turn cost
1K fresh input + 500 output tokens
Inkling-Small
Inkling-Small 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
Inkling-Small
Inkling-Small has the lower estimated token cost for this stated workload. GPT-5.2 has no published cached-input rate, so cached tokens use its listed input rate.
Confidence: rate-fallback
Show secondary and unsupported calls
Repository review cost
50K fresh input + 3K output tokens
Inkling-Small
Inkling-Small 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
The category averages use different weighted benchmark sets, so they are directional rather than like-for-like.
Confidence: limited
Agentic work
Tool use, computer use, and multi-step task completion
Not enough matched evidence
The category averages use different weighted benchmark sets, so they are directional rather than like-for-like.
Confidence: limited
What is actually comparable
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
8 GPT-5.2 only
7 Shared
13 Inkling-Small only
- Shared results
- 7
- GPT-5.2 only
- 8
- Inkling-Small only
- 13
- Like-for-like categories
- 2 / 8
3 categories use different evidence sets. Those rows remain visible for coverage context but do not name a winner.
Category results, on a stated basis
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.
Multimodal
Like-for-like- GPT-5.2
- 80.4
- Inkling-Small
- 76.6
- Weighted basis
- 2 vs 2 rows
- Reading
- GPT-5.2 leads
Agentic
Directional only- GPT-5.2
- 55.7
- Inkling-Small
- 70.1
- Weighted basis
- 2 vs 2 rows
- Reading
- Directional only
Coding
Directional only- GPT-5.2
- 70.6
- Inkling-Small
- 62.4
- Weighted basis
- 2 vs 3 rows
- Reading
- Directional only
Knowledge
Directional only- GPT-5.2
- 92.4
- Inkling-Small
- 53.4
- Weighted basis
- 1 vs 2 rows
- Reading
- Directional only
Math
Not comparable- GPT-5.2
- 35.2
- Inkling-Small
- 92.9
- Weighted basis
- 2 vs 2 rows
- Reading
- Not comparable
Multilingual
Not comparable- GPT-5.2
- Not measured
- Inkling-Small
- Not measured
- Weighted basis
- 0 vs 0 rows
- Reading
- Not comparable
Instruction following
Not comparable- GPT-5.2
- Not measured
- Inkling-Small
- 82.2
- Weighted basis
- 0 vs 1 rows
- Reading
- Not comparable
| Category | GPT-5.2 | Inkling-Small | Weighted basis | Reading |
|---|---|---|---|---|
| Reasoning | 52.9 | 40.1 | Like-for-like1 vs 1 rows | GPT-5.2 leads |
| Multimodal | 80.4 | 76.6 | Like-for-like2 vs 2 rows | GPT-5.2 leads |
| Agentic | 55.7 | 70.1 | Directional only2 vs 2 rows | Directional only |
| Coding | 70.6 | 62.4 | Directional only2 vs 3 rows | Directional only |
| Knowledge | 92.4 | 53.4 | Directional only1 vs 2 rows | Directional only |
| Math | 35.2 | 92.9 | Not comparable2 vs 2 rows | Not comparable |
| Multilingual | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Instruction following | Not measured | 82.2 | Not comparable0 vs 1 rows | Not comparable |
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.
ARC-AGI-2
Reasoning
BrowseComp
Agentic
MMMU-Pro
Multimodal
GPQA
Knowledge
CharXiv
Multimodal
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
- GPT-5.2
- $0.00875
- Fits in one request
- Inkling-Small
- $0.0013
- Fits in one request
Inkling-Small has the lower modeled cost
Costs use the listed standard API rates.
Repository review
50K fresh input + 3K output tokens
- GPT-5.2
- $0.1295
- Fits in one request
- Inkling-Small
- $0.03332
- Fits in one request
Inkling-Small has the lower modeled cost
Costs use the listed standard API rates.
Cache-heavy agent loop
200K cached + 20K fresh input + 10K output tokens
- GPT-5.2
- $0.525
- Fits in one request
- Cached input priced at the published list-input rate
- Inkling-Small
- $0.0492
- Fits in one request
Inkling-Small has the lower modeled cost
GPT-5.2 has no published cached-input rate, so cached tokens use its listed input rate.
Specification differences
Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.
SpecificationGPT-5.2Inkling-Small
Context window
Maximum documented context; output-token limits may be lower.
GPT-5.2
400K
Inkling-Small
1M
API model ID
GPT-5.2
Not sourced
Inkling-Small
Not sourced
Cached-input rate
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
GPT-5.2
Not published
Inkling-Small
$0.116 per 1M cached input tokens
Documented inputs
GPT-5.2
Not sourced
Inkling-Small
Not sourced
Documented outputs
GPT-5.2
Not sourced
Inkling-Small
Not sourced
Provider availability
GPT-5.2
Not sourced
Inkling-Small
Not sourced
Reasoning profile
GPT-5.2
Reasoning
Inkling-Small
Hybrid
Weight access
GPT-5.2
Proprietary
Inkling-Small
Open Weight
License
GPT-5.2
Proprietary
Inkling-Small
Open Weight
Release date
GPT-5.2
2025-12-11
Inkling-Small
2026-07-30
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.1295 vs $0.03332. Cache-heavy agent loop: $0.525 vs $0.0492.
- Context tradeoff
- Inkling-Small has the larger documented window (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 evidence28 rows
Agentic
BrowseComp
GPT-5.265.8%SourceInkling-Small77.4%SourceInkling-Small leads this result
OSWorld-Verified
GPT-5.247.3%SourceInkling-Small—Not directly comparable
Gert Labs
GPT-5.246.54%SourceInkling-Small—Not directly comparable
JobBench
GPT-5.234.3%SourceInkling-Small—Not directly comparable
Terminal-Bench 2.0
GPT-5.2—Inkling-Small64.7%SourceNot directly comparable
MCP Atlas
GPT-5.2—Inkling-Small79.6%SourceNot directly comparable
Toolathlon-Verified
GPT-5.2—Inkling-Small54.4%SourceNot directly comparable
Coding
SWE-bench Verified
GPT-5.280%SourceInkling-Small80.2%SourceInkling-Small leads this result
SWE-bench Pro
GPT-5.255.6%SourceInkling-Small55.9%SourceInkling-Small leads this result
Vibe Code Bench
GPT-5.253.50%SourceInkling-Small—Not directly comparable
Terminal-Bench 2.0
GPT-5.2—Inkling-Small64.7%SourceNot directly comparable
SciCode
GPT-5.2—Inkling-Small48.7%SourceNot directly comparable
Reasoning
Knowledge
Math
Multimodal
MMMU-Pro
GPT-5.279.5%SourceInkling-Small74%SourceGPT-5.2 leads this result
MathVision
GPT-5.283.0%SourceInkling-Small—Not directly comparable
CharXiv
GPT-5.282.1%SourceInkling-Small81.3%SourceGPT-5.2 leads this result
V*
GPT-5.275.9%SourceInkling-Small—Not directly comparable
CharXiv w/o tools
GPT-5.2—Inkling-Small77.4%SourceNot directly comparable
Instruction following
IFBench
GPT-5.2—Inkling-Small82.2%SourceNot directly comparable
Frequently asked questions
Which is better, GPT-5.2 or Inkling-Small?
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, GPT-5.2 or Inkling-Small?
The current coding averages use different weighted benchmark sets, so BenchLM does not name a winner from them. Read the shared benchmark rows directly and test the models on the same task set.
Which is better for agentic tasks, GPT-5.2 or Inkling-Small?
The current agentic tasks averages use different weighted benchmark sets, so BenchLM does not name a winner from them. Read the shared benchmark rows directly and test the models on the same task set.
Which costs less, GPT-5.2 or Inkling-Small?
For the stated presets, chat costs $0.00875 on GPT-5.2 and $0.0013 on Inkling-Small; repository review costs $0.1295 and $0.03332; the cache-heavy agent loop costs $0.525 and $0.0492. GPT-5.2 has no published cached-input rate, so cached tokens use its listed input rate.
Which has the larger context window, GPT-5.2 or Inkling-Small?
Inkling-Small has the larger documented context window: 1M, compared with 400K.
Related comparisons
Last updated July 30, 2026
Watch GPT-5.2 vs Inkling-Small
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 2,000+ readers.