Coding work
Code generation, repair, and software-engineering tasks
GPT-5.5
GPT-5.5 has the higher public coding point estimate, 62.1 to 34, with Supported evidence for both models. The conditional ranges do not establish rank confidence.
Updated October 14, 2026. Rank says GPT-5.5 is ahead. Price, access, and your workload can each overturn that. Public scores include evidence status and uncertainty.
Both of these models will change. Get the price, version and retirement notices for the pair, each with its source. Follow model changes
GPT-5.5 has the higher public score estimate, 68.42 versus 52.13, but the 90% score intervals overlap. Treat that as a lead, not a settled winner. 15 results are shared. Category rows resting on Estimated evidence or 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.
Code generation, repair, and software-engineering tasks
GPT-5.5
GPT-5.5 has the higher public coding point estimate, 62.1 to 34, with Supported evidence for both models. The conditional ranges do not establish rank confidence.
Tool use, computer use, and multi-step task completion
GPT-5.5
GPT-5.5 has the higher public agentic point estimate, 61.5 to 36.2, with Supported evidence for both models. The conditional ranges do not establish rank confidence.
1K fresh input + 500 output tokens
Inkling
Inkling has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.
200K cached + 20K fresh input + 10K output tokens
Inkling
Inkling has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.
50K fresh input + 3K output tokens
Inkling
Inkling has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.
Prompts that approach the documented context limit
No clear pick
The documented context windows are equal.
Choose a job from the LLM Selector's task catalog to see the category row it rests on, under the same basis rules as the table below. A directional row stays directional; choosing a job never creates a winner.
The same task catalog as the LLM Selector. Each job names the evidence surface it rests on; nothing here adds a new score.
Like-for-like · BenchAlign v5.8
GPT-5.5 has the higher coding point estimate. Conditional score ranges do not establish rank confidence.
Coding scores combine specific tasks and setups. Match the editor, harness, and effort to your workflow.
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
3 categories rest on Estimated evidence or different evidence sets. Those rows remain visible for coverage context but do not name a winner.
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.
FrontierMath v2 (Tier 4)Math
Normalized gap 67.6FrontierMath v2 (Tiers 1-3)Math
Normalized gap 51.9HLE w/o toolsKnowledge
Normalized gap 11.4MMMU-ProMultimodal
Normalized gap 7.7BrowseCompAgentic
Normalized gap 7.3Each row shows the public-lane category score for both models: the BenchAlign v5.8 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.
| Category | GPT-5.5 | Inkling | Basis | Reading |
|---|---|---|---|---|
| Agentic | 61.5Supported · #21/124 | 36.2Supported · #72/124 | Like-for-likeBenchAlign v5.8 lane · 14 vs 5 public rows | GPT-5.5 leads |
| Coding | 62.1Supported · #15/149 | 34.0Supported · #80/149 | Like-for-likeBenchAlign v5.8 lane · 10 vs 6 public rows | GPT-5.5 leads |
| Knowledge | 71.4Supported · #14/181 | 54.5Supported · #62/181 | Like-for-likeBenchAlign v5.8 lane · 6 vs 6 public rows | GPT-5.5 leads · intervals overlap |
| Reasoning | 70.4#21/29 | 79.0#14/29 | Directional onlyProvisional lane · 2 vs 0 weighted rows | Directional only |
| Multimodal | 75.5#23/54 | 67.5#35/54 | Directional onlyProvisional lane · 2 vs 2 weighted rows | Directional only |
| Instruction following | 93.3#8/128 | 87.6#35/128 | Directional onlyProvisional lane · 0 vs 1 weighted rows | Directional only |
| Multilingual | Not ranked | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Math | 91.2Unranked · 3 rankable rows | 58.3#11/12 | Not comparableProvisional lane · 2 vs 3 weighted rows | Not comparable |
Ranks count the models scored in each category’s lane, so the agentic, coding, and knowledge denominators (BenchAlign v5.8) differ from the provisional-lane categories. Unranked scores sit on the provisional lane’s scale but never name a winner. Like-for-like rows within 0.5 points read as a practical tie.
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
Inkling has the lower modeled cost
Costs use the listed standard API rates.
50K fresh input + 3K output tokens
Inkling has the lower modeled cost
Costs use the listed standard API rates.
200K cached + 20K fresh input + 10K output tokens
Inkling has the lower modeled cost
Costs use the listed standard API rates.
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.
GPT-5.5
Inkling
1M
GPT-5.5
gpt-5.5
OpenAI pricingInkling
Not sourced
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
GPT-5.5
$0.5 per 1M cached input tokens
OpenAI pricingInkling
$0.374 per 1M cached input tokens
GPT-5.5
Not sourced
Inkling
Not sourced
GPT-5.5
Not sourced
Inkling
Not sourced
GPT-5.5
Not sourced
Inkling
Not sourced
GPT-5.5
Reasoning
Inkling
Hybrid
GPT-5.5
Proprietary
Inkling
Open Weight
GPT-5.5
Proprietary
Inkling
Open Weight
GPT-5.5
2026-04-23
Inkling
2026-07-15
GPT-5.5 has the higher public score estimate, 68.42 versus 52.13, but the 90% score intervals overlap. The higher estimate is not a decisive winner because the uncertainty ranges overlap.
GPT-5.5 has the higher public coding point estimate, 62.1 to 34, with Supported evidence for both models. The conditional ranges do not establish rank confidence.
GPT-5.5 has the higher public agentic tasks point estimate, 61.5 to 36.2, with Supported evidence for both models. The conditional ranges do not establish rank confidence.
For the stated presets, chat costs $0.02 on GPT-5.5 and $0.00421 on Inkling; repository review costs $0.34 and $0.10754; the cache-heavy agent loop costs $0.5 and $0.159. Costs use the listed standard API rates.
Both models list the same context window, 1M.
The full public result ledger is available for audit without forcing a wide desktop table onto a phone.
Terminal-Bench 2.0
Not directly comparable
CyberGym
Not directly comparable
BrowseComp
GPT-5.5 leads this result
OSWorld-Verified
Not directly comparable
MCP Atlas
GPT-5.5 leads this result
Toolathlon
Not directly comparable
τ²-bench results
Not directly comparable
Gert Labs
Not directly comparable
ResearchClawBench
Not directly comparable
OSWorld 2.0
Not directly comparable
JobBench
Not directly comparable
ExploitGym
Not directly comparable
Terminal-Bench 2.1 (Vals)
GPT-5.5 leads this result
ApprenticeBench
Not directly comparable
Terminal-Bench 2.1
Not directly comparable
CWE-bench v1
Not directly comparable
SWE-bench Pro
GPT-5.5 leads this result
Terminal-Bench 2.0
Not directly comparable
Vibe Code Bench
Not directly comparable
React Native Evals
Not directly comparable
cursorBench31
Not directly comparable
CursorBench 3.2
Not directly comparable
FrontierCode 1.1 Main
Not directly comparable
LiveCodeBench (Vals)
Inkling leads this result
SWE-bench (Vals)
GPT-5.5 leads this result
PostTrainBench v1.1
Not directly comparable
SWE-bench Verified
Not directly comparable
Terminal-Bench 2.1
Not directly comparable
FrontierSWE v2
Not directly comparable
MRCR v2 64K-128K
Not directly comparable
MRCR v2 128K-256K
Not directly comparable
ARC-AGI-2
Not directly comparable
ARC-AGI-3
Not directly comparable
ARC-AGI-1
Not directly comparable
MMMU-Pro
GPT-5.5 leads this result
MMMU-Pro w/ Python
Not directly comparable
OfficeQA Pro
Not directly comparable
CharXiv
Not directly comparable
CharXiv w/o tools
Not directly comparable
GPQA
GPT-5.5 leads this result
GPQA-D
GPT-5.5 leads this result
HLE
GPT-5.5 leads this result
HLE w/o tools
GPT-5.5 leads this result
GPQA Diamond (Vals)
GPT-5.5 leads this result
MMLU-Pro (Vals)
GPT-5.5 leads this result
IFBench
Not directly comparable
FrontierMath (legacy)
Not directly comparable
FrontierMath v2 (Tiers 1-3)
Shared sourceGPT-5.5 leads this result
FrontierMath v2 (Tier 4)
Shared sourceGPT-5.5 leads this result
AIME26
Not directly comparable
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 5,500+ readers.
Last updated October 14, 2026