Skip to main content
BenchLM
Data

GPT-5.3 Codex vs Inkling

Updated October 14, 2026. Rank says GPT-5.3 Codex is ahead. Price, access, and your workload can each overturn that. Public scores include evidence status and uncertainty.

Share or export
Share on XLinkedInAPI/MCP

Decision reading

GPT-5.3 Codex has the higher public score estimate, 59.84 versus 52.13, but the 90% score intervals overlap. Treat that as a lead, not a settled winner. 4 results are shared. Category rows resting on Estimated evidence or different benchmark sets are marked directional and do not name a winner.

Model A
OpenAI logo

OpenAI

59.84/100

Supported · Public rank #53

90% interval 52.4–67.2

Model B
Thinking Machines Lab logo

Thinking Machines Lab

52.13/100

Supported · Public rank #85

90% interval 41.7–62.5

Shared results
4
GPT-5.3 Codex only
7
Inkling only
20
Like-for-like categories
1 / 8
Supported: GPT-5.3 Codex and InklingHow the comparison works

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.3 Codex

    GPT-5.3 Codex has the higher public coding point estimate, 54.5 to 34, with Supported evidence for both models. The conditional ranges do not establish rank confidence.

    Confidence: limited
  • Long documents

    Prompts that approach the documented context limit

    Inkling

    Inkling has the larger documented context window.

    Confidence: documented
  • Chat turn cost

    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.

    Confidence: listed-rates
Show secondary and unsupported calls
  • Cache-heavy agent loop cost

    200K cached + 20K fresh input + 10K output tokens

    Inkling

    Inkling has the lower estimated token cost for this stated workload. GPT-5.3 Codex 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

    Inkling has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.

    Confidence: listed-rates
  • Agentic work

    Tool use, computer use, and multi-step task completion

    Not enough matched evidence

    GPT-5.3 Codex is scored on Estimated evidence for agentic, so the reading is directional rather than like-for-like.

    Confidence: limited

Which one for a specific job

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.

54.5GPT-5.3 Codex34.0Inkling

Like-for-like · BenchAlign v5.8

GPT-5.3 Codex 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.

Same basis rules as the category table below

What is actually comparable

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.

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.

Bars run 0–100 on each benchmark’s normalized display scale

Category results, on a stated basis

Each 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.

Coding

Like-for-like
GPT-5.3 Codex
54.5
Supported · #31/149
Inkling
34.0
Supported · #80/149
Basis
BenchAlign v5.8 lane · 7 vs 6 public rows
Reading
GPT-5.3 Codex leads · intervals overlap

Agentic

Directional only
GPT-5.3 Codex
55.2
Estimated · #35/124
Inkling
36.2
Supported · #72/124
Basis
BenchAlign v5.8 lane · 4 vs 5 public rows
Reading
Directional only

Knowledge

Directional only
GPT-5.3 Codex
65.3
Estimated · #31/181
Inkling
54.5
Supported · #62/181
Basis
BenchAlign v5.8 lane · 0 vs 6 public rows
Reading
Directional only

Instruction following

Directional only
GPT-5.3 Codex
92.6
#18/128
Inkling
87.6
#35/128
Basis
Provisional lane · 0 vs 1 weighted rows
Reading
Directional only

Reasoning

Not comparable
GPT-5.3 Codex
83.1
Unranked · 2 rankable rows
Inkling
79.0
#14/29
Basis
Provisional lane · 0 vs 0 weighted rows
Reading
Not comparable

Multimodal

Not comparable
GPT-5.3 Codex
80.1
Unranked · 1 rankable row
Inkling
67.5
#35/54
Basis
Provisional lane · 0 vs 2 weighted rows
Reading
Not comparable

Multilingual

Not comparable
GPT-5.3 Codex
Not ranked
Inkling
Not ranked
Basis
Provisional lane · 0 vs 0 weighted rows
Reading
Not comparable

Math

Not comparable
GPT-5.3 Codex
Not ranked
Inkling
58.3
#11/12
Basis
Provisional lane · 0 vs 3 weighted rows
Reading
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.

Supported evidence per lane · bars run 0–100Methodology

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.3 Codex
$0.00875
Fits in one request
Inkling
$0.00421
Fits in one request

Inkling has the lower modeled cost

Costs use the listed standard API rates.

Repository review

50K fresh input + 3K output tokens

GPT-5.3 Codex
$0.1295
Fits in one request
Inkling
$0.10754
Fits in one request

Inkling 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.3 Codex
$0.525
Fits in one request
Cached input priced at the published list-input rate
Inkling
$0.159
Fits in one request

Inkling has the lower modeled cost

GPT-5.3 Codex has no published cached-input rate, so cached tokens use its listed input rate.

Cached input falls back to the list input rate only where a cached rate is unpublished

Specification differences

Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.

Cached-input rate

A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.

GPT-5.3 Codex

Not published

Inkling

$0.374 per 1M cached input tokens

Provider availability

GPT-5.3 Codex

Generally Available · OpenAI Responses API

OpenAI model catalog

Inkling

Not sourced

Reasoning profile

GPT-5.3 Codex

Reasoning

Inkling

Hybrid

Weight access

GPT-5.3 Codex

Proprietary

Inkling

Open Weight

License

GPT-5.3 Codex

Proprietary

Inkling

Open Weight

Release date

GPT-5.3 Codex

2026-02-05

Inkling

2026-07-15

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.3 Codex has the higher public score estimate, 59.84 versus 52.13, but the 90% score intervals overlap.
Workload cost
Repository review: $0.1295 vs $0.10754. Cache-heavy agent loop: $0.525 vs $0.159.
Context tradeoff
Inkling has the larger documented window (1M).
Run the same representative tasks against both endpoints before changing production traffic.

Questions

Which is better, GPT-5.3 Codex or Inkling?

GPT-5.3 Codex has the higher public score estimate, 59.84 versus 52.13, 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.3 Codex or Inkling?

GPT-5.3 Codex has the higher public coding point estimate, 54.5 to 34, with Supported evidence for both models. The conditional ranges do not establish rank confidence.

Which is better for agentic tasks, GPT-5.3 Codex or Inkling?

GPT-5.3 Codex scores higher for agentic tasks on the public lane, 55.2 to 36.2. GPT-5.3 Codex 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, GPT-5.3 Codex or Inkling?

For the stated presets, chat costs $0.00875 on GPT-5.3 Codex and $0.00421 on Inkling; repository review costs $0.1295 and $0.10754; the cache-heavy agent loop costs $0.525 and $0.159. GPT-5.3 Codex has no published cached-input rate, so cached tokens use its listed input rate.

Which has the larger context window, GPT-5.3 Codex or Inkling?

Inkling has the larger documented context window: 1M, compared with 400K.

Benchmark evidence

The full public result ledger is available for audit without forcing a wide desktop table onto a phone.

Browse raw public benchmark evidence31 rows

Agentic

  • Terminal-Bench 2.0

    GPT-5.3 Codex77.3%
    Source
    Inkling—

    Not directly comparable

  • OSWorld-Verified

    GPT-5.3 Codex64.7%
    Source
    Inkling—

    Not directly comparable

  • Gert Labs

    GPT-5.3 Codex57.47%
    Source
    Inkling—

    Not directly comparable

  • JobBench

    GPT-5.3 Codex33.7%
    Source
    Inkling—

    Not directly comparable

  • Terminal-Bench 2.1

    GPT-5.3 Codex—
    Inkling63.8%
    Source

    Not directly comparable

  • BrowseComp

    GPT-5.3 Codex—
    Inkling77.1%
    Source

    Not directly comparable

  • MCP Atlas

    GPT-5.3 Codex—
    Inkling74.1%
    Source

    Not directly comparable

  • Terminal-Bench 2.1 (Vals)

    GPT-5.3 Codex—
    Inkling47.6%
    Source

    Not directly comparable

  • CWE-bench v1

    GPT-5.3 Codex—
    Inkling37.0%
    Source

    Not directly comparable

Coding

  • SWE-bench Verified

    GPT-5.3 Codex85%
    Source
    Inkling77.6%
    Source

    GPT-5.3 Codex leads this result

  • SWE-bench Pro

    GPT-5.3 Codex56.8%
    Source
    Inkling54.3%
    Source

    GPT-5.3 Codex leads this result

  • SWE-Rebench

    GPT-5.3 Codex58.2%
    Source
    Inkling—

    Not directly comparable

  • Terminal-Bench 2.0

    GPT-5.3 Codex77.3%
    Source
    Inkling—

    Not directly comparable

  • Vibe Code Bench

    GPT-5.3 Codex61.77%
    Source
    Inkling—

    Not directly comparable

  • LiveCodeBench (Vals)

    GPT-5.3 Codex87.3%
    Source
    Inkling85.5%
    Source

    GPT-5.3 Codex leads this result

  • SWE-bench (Vals)

    GPT-5.3 Codex78.0%
    Source
    Inkling77.6%
    Source

    GPT-5.3 Codex leads this result

  • Terminal-Bench 2.1

    GPT-5.3 Codex—
    Inkling63.8%
    Source

    Not directly comparable

  • FrontierSWE v2

    GPT-5.3 Codex—
    Inkling4.1%
    Source

    Not directly comparable

Multimodal

  • MMMU-Pro

    GPT-5.3 Codex—
    Inkling73.5%
    Source

    Not directly comparable

  • CharXiv

    GPT-5.3 Codex—
    Inkling82%
    Source

    Not directly comparable

  • CharXiv w/o tools

    GPT-5.3 Codex—
    Inkling78.1%
    Source

    Not directly comparable

Knowledge

  • GPQA

    GPT-5.3 Codex—
    Inkling87.9%
    Source

    Not directly comparable

  • GPQA-D

    GPT-5.3 Codex—
    Inkling87.9%
    Source

    Not directly comparable

  • HLE

    GPT-5.3 Codex—
    Inkling46%
    Source

    Not directly comparable

  • HLE w/o tools

    GPT-5.3 Codex—
    Inkling30%
    Source

    Not directly comparable

  • GPQA Diamond (Vals)

    GPT-5.3 Codex—
    Inkling87.1%
    Source

    Not directly comparable

  • MMLU-Pro (Vals)

    GPT-5.3 Codex—
    Inkling86.3%
    Source

    Not directly comparable

Instruction following

  • IFBench

    GPT-5.3 Codex—
    Inkling79.8%
    Source

    Not directly comparable

Math

  • AIME26

    GPT-5.3 Codex—
    Inkling97.1%
    Source

    Not directly comparable

  • FrontierMath v2 (Tiers 1-3)

    GPT-5.3 Codex—
    Inkling33.333%
    Source

    Not directly comparable

  • FrontierMath v2 (Tier 4)

    GPT-5.3 Codex—
    Inkling4.878%
    Source

    Not directly comparable

31 public results · 4 shared

Watch GPT-5.3 Codex vs Inkling

One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.

Read a sample issue

Join 5,500+ readers.

Last updated October 14, 2026