Time to First Token · GPT-5 (high)
—
Time to First Token · Inkling Small
—
GPT-5 (high) vs Inkling Small: The Ultimate Performance & Pricing Comparison
Deep dive into reasoning, benchmarks, and latency insights.
The Final Verdict in the GPT-5 (high) vs Inkling Small Showdown
The current catalog does not contain complete performance evidence for both models, so this page does not declare an overall winner. Use the available fields as comparison signals and validate the models on your own workload.
Model Snapshot
Key decision metrics at a glance.
GPT-5 (high)Inkling Small
9.0
Reasoning6.0
4.0
Coding5.0
3.0
Multimodal3.0
4.0
Long Context5.0
$3.438
Blended Price / 1M tokens$0.525
—
P95 Latency—
—
Tokens per second123.278
Machine-readable comparison data
| Model | Metric | Value | Unit | Source / snapshot |
|---|---|---|---|---|
| GPT-5 (high) | Reasoning | 9.0 | benchmark or capability score | Artificial Analysis · current catalog |
| Inkling Small | Reasoning | 6.0 | benchmark or capability score | Artificial Analysis · current catalog |
| GPT-5 (high) | Coding | 4.0 | benchmark or capability score | Artificial Analysis · current catalog |
| Inkling Small | Coding | 5.0 | benchmark or capability score | Artificial Analysis · current catalog |
| GPT-5 (high) | Multimodal | 3.0 | benchmark or capability score | Artificial Analysis · current catalog |
| Inkling Small | Multimodal | 3.0 | benchmark or capability score | Artificial Analysis · current catalog |
| GPT-5 (high) | Long Context | 4.0 | benchmark or capability score | Artificial Analysis · current catalog |
| Inkling Small | Long Context | 5.0 | benchmark or capability score | Artificial Analysis · current catalog |
| GPT-5 (high) | Blended Price / 1M tokens | $3.438 | USD per 1M tokens | Artificial Analysis · current catalog |
| Inkling Small | Blended Price / 1M tokens | $0.525 | USD per 1M tokens | Artificial Analysis · current catalog |
| GPT-5 (high) | P95 Latency | — | milliseconds | Artificial Analysis · current catalog |
| Inkling Small | P95 Latency | — | milliseconds | Artificial Analysis · current catalog |
| GPT-5 (high) | Tokens per second | — | tokens per second | Artificial Analysis · current catalog |
| Inkling Small | Tokens per second | 123.278 | tokens per second | Artificial Analysis · current catalog |
Data provided by Artificial Analysis; live values use the current catalog.
Overall Capabilities
This radar chart visually maps the core capabilities (reasoning, coding, math proxy, multimodal, long context) of `GPT-5 (high)` vs `Inkling Small`.
GPT-5 (high)Inkling Small
Benchmark Breakdown
This grouped bar chart provides a side-by-side comparison for each benchmark metric.
37.852.9
ARTIFICIAL ANALYSIS CODING34.740.2
ARTIFICIAL ANALYSIS INTELLIGENCE94.3—
ARTIFICIAL ANALYSIS MATHGPT-5 (high)Inkling Small
Speed & Latency
Lower time to first token is better; higher tokens per second is better.
Tokens per Second · GPT-5 (high)
—
Tokens per Second · Inkling Small
123.278
The Economics of GPT-5 (high) vs Inkling Small
Pricing Breakdown
Compare input and output pricing in USD per 1M tokens.
$1.25$0.3
Input Pricing$10$1.2
Output PricingGPT-5 (high)Inkling Small
Real-World Cost Scenario
Per run: 1M input tokens + 250k output tokensGPT-5 (high)$3.75
Inkling Small$0.6
Inkling Small costs $3.15 less per run
Your Questions about the GPT-5 (high) vs Inkling Small Comparison
Is `GPT-5 (high)` a direct replacement for `Inkling Small`?
The current GPT-5 (high) vs Inkling Small data does not establish a universal replacement. Compare the available metrics, then validate quality, latency, reliability, and cost on your own workload.
For coding, which is better in the `GPT-5 (high) vs Inkling Small` debate?
The benchmark data in our GPT-5 (high) vs Inkling Small comparison shows Inkling Small has a clear advantage, scoring 52.9 on LiveCodeBench versus 37.8.
How was this `GPT-5 (high) vs Inkling Small` comparison conducted?
Our GPT-5 (high) vs Inkling Small comparison uses published benchmark, pricing, speed, and latency fields provided by Artificial Analysis. Missing values remain unavailable, and the result should be checked against your workload.