Agentic
Like-for-like- GPT-5.2
- 42.9
- Supported · #104/152
- Inkling-Small
- 36.9
- Supported · #128/152
- Basis
- BenchAlign lane · 4 vs 5 public rows
- Reading
- GPT-5.2 leads · intervals overlap
GPT-5.2 vs Inkling-Small
Updated September 10, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload.
Decision reading
GPT-5.2 has the higher public score estimate, 64.88 versus 59.25, but the 90% score intervals overlap. Treat that as a lead, not a settled winner.
7 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.
Coding work
Code generation, repair, and software-engineering tasks
GPT-5.2
GPT-5.2 leads on the public coding lane, 46.4 to 43.8, with Supported evidence for both models, although the 90% intervals overlap.
Confidence: limited
Agentic work
Tool use, computer use, and multi-step task completion
GPT-5.2
GPT-5.2 leads on the public agentic lane, 42.9 to 36.9, with Supported evidence for both models, although the 90% intervals overlap.
Confidence: limited
Long documents
Prompts that approach the documented context limit
Inkling-Small
Inkling-Small has the larger documented context window.
Confidence: documented
Show secondary and unsupported calls
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
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
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
18 Inkling-Small only
- Shared results
- 7
- GPT-5.2 only
- 8
- Inkling-Small only
- 18
- Like-for-like categories
- 4 / 8
1 category rests 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
Like-for-like- GPT-5.2
- 46.4
- Supported · #81/151
- Inkling-Small
- 43.8
- Supported · #97/151
- Basis
- BenchAlign lane · 3 vs 6 public rows
- Reading
- GPT-5.2 leads · intervals overlap
Knowledge
Like-for-like- GPT-5.2
- 61.7
- Supported · #30/183
- Inkling-Small
- 56.5
- Supported · #46/183
- Basis
- BenchAlign lane · 1 vs 6 public rows
- Reading
- GPT-5.2 leads · intervals overlap
Multimodal
Like-for-like- GPT-5.2
- 66.3
- #23/48
- Inkling-Small
- 48.8
- #39/48
- Basis
- Provisional lane · 2 vs 2 weighted rows
- Reading
- GPT-5.2 leads
Instruction following
Directional only- GPT-5.2
- 92.6
- #14/123
- Inkling-Small
- 89.6
- #25/123
- Basis
- Provisional lane · 0 vs 1 weighted rows
- Reading
- Directional only
Reasoning
Not comparable- GPT-5.2
- 53.7
- Unranked · 3 rankable rows
- Inkling-Small
- 42.7
- Unranked · 3 rankable rows
- Basis
- Provisional lane · 1 vs 1 weighted rows
- Reading
- Not comparable
Math
Not comparable- GPT-5.2
- 57.5
- Unranked · 2 rankable rows
- Inkling-Small
- 76.9
- Unranked · 2 rankable rows
- Basis
- Provisional lane · 2 vs 2 weighted rows
- Reading
- Not comparable
Multilingual
Not comparable- GPT-5.2
- Not ranked
- Inkling-Small
- Not ranked
- Basis
- Provisional lane · 0 vs 0 weighted rows
- Reading
- Not comparable
| Category | GPT-5.2 | Inkling-Small | Basis | Reading |
|---|---|---|---|---|
| Agentic | 42.9Supported · #104/152 | 36.9Supported · #128/152 | Like-for-likeBenchAlign lane · 4 vs 5 public rows | GPT-5.2 leads · intervals overlap |
| Coding | 46.4Supported · #81/151 | 43.8Supported · #97/151 | Like-for-likeBenchAlign lane · 3 vs 6 public rows | GPT-5.2 leads · intervals overlap |
| Knowledge | 61.7Supported · #30/183 | 56.5Supported · #46/183 | Like-for-likeBenchAlign lane · 1 vs 6 public rows | GPT-5.2 leads · intervals overlap |
| Multimodal | 66.3#23/48 | 48.8#39/48 | Like-for-likeProvisional lane · 2 vs 2 weighted rows | GPT-5.2 leads |
| Instruction following | 92.6#14/123 | 89.6#25/123 | Directional onlyProvisional lane · 0 vs 1 weighted rows | Directional only |
| Reasoning | 53.7Unranked · 3 rankable rows | 42.7Unranked · 3 rankable rows | Not comparableProvisional lane · 1 vs 1 weighted rows | Not comparable |
| Math | 57.5Unranked · 2 rankable rows | 76.9Unranked · 2 rankable rows | Not comparableProvisional lane · 2 vs 2 weighted rows | Not comparable |
| Multilingual | 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.
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
- GPT-5.2 has the higher public score estimate, 64.88 versus 59.25, but the 90% score intervals overlap.
- 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 evidence33 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
Terminal-Bench 2.1 (Vals)
GPT-5.2—Inkling-Small55.1%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
LiveCodeBench (Vals)
GPT-5.2—Inkling-Small85.9%SourceNot directly comparable
SWE-bench (Vals)
GPT-5.2—Inkling-Small82.2%SourceNot directly comparable
Reasoning
Knowledge
GPQA
GPT-5.292.4%SourceInkling-Small89.5%SourceGPT-5.2 leads this result
GPQA-D
GPT-5.2—Inkling-Small89.5%SourceNot directly comparable
HLE
GPT-5.2—Inkling-Small47.8%SourceNot directly comparable
HLE w/o tools
GPT-5.2—Inkling-Small31.6%SourceNot directly comparable
GPQA Diamond (Vals)
GPT-5.2—Inkling-Small83.6%SourceNot directly comparable
MMLU-Pro (Vals)
GPT-5.2—Inkling-Small85.6%SourceNot directly comparable
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?
GPT-5.2 has the higher public score estimate, 64.88 versus 59.25, but the 90% score intervals overlap. The higher estimate is not a decisive winner because the uncertainty ranges overlap.
Which is better for coding, GPT-5.2 or Inkling-Small?
GPT-5.2 leads the public coding lane, 46.4 to 43.8, with Supported evidence for both models, although the 90% intervals overlap.
Which is better for agentic tasks, GPT-5.2 or Inkling-Small?
GPT-5.2 leads the public agentic tasks lane, 42.9 to 36.9, with Supported evidence for both models, although the 90% intervals overlap.
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 September 10, 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.