Skip to main content
BenchLM
Data

GLiDE vs Inkling

Updated November 13, 2026. We do not rank this pair: at least one has no public score. Public scores include evidence status and uncertainty.

Share or export
Share on XLinkedInAPI/MCP

Decision reading

The public evidence has no benchmark result shared by both models, so it does not support a quality verdict. Use the documented cost, context, and runtime rows instead. 0 results are shared. Category rows resting on Estimated evidence or different benchmark sets are marked directional and do not name a winner.

Model A

Fastino

—

Evidence status unavailable

90% interval unavailable

Model B
Thinking Machines Lab logo

Thinking Machines Lab

48.23/100

Supported · Public rank #104

90% interval 30.8–65.7

API price per 1M tokens

GLiDE: $0.15 input / $0 output

Inkling: $1.87 input / $4.68 output

Context window

GLiDE: 40K

Inkling: 1M

Released

GLiDE: September 30, 2026

Inkling: July 15, 2026

Shared results
0
GLiDE only
0
Inkling only
24
Like-for-like categories
0 / 8
Supported: 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.

  • 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

    GLiDE

    GLiDE 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
  • Coding work

    Code generation, repair, and software-engineering tasks

    Not enough matched evidence

    GLiDE is not ranked on the public lane for coding, so no winner is named for coding.

    Confidence: limited
  • Agentic work

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

    Not enough matched evidence

    GLiDE is not ranked on the public lane for agentic, so no winner is named for agentic.

    Confidence: limited
  • Cache-heavy agent loop cost

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

    Not enough matched evidence

    The page does not recommend a cost winner because at least one model cannot fit the stated workload in one request. GLiDE does not fit this workload in one request. GLiDE 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

    Not enough matched evidence

    The page does not recommend a cost winner because at least one model cannot fit the stated workload in one request. GLiDE does not fit this workload in one request.

    Confidence: listed-rates

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.

—GLiDE35.1Inkling

Not comparable · BenchAlign v5.8

The coding row is not comparable on the public lane: at least one model is not measured or not ranked there.

Coding scores combine specific tasks and setups. Match the editor, harness, and effort to your workflow.

Same basis rules as the category table below

Or describe your own job

The LLM Selector reads what you need a model for and returns a shortlist, ranked in the same order the job pages publish.

Describe the task and constraints. This selector recommends models; it cannot carry out the task or access your files and accounts.

We keep what you type here, drafts included, for 180 days, and after that only the job and requirements read from it. Nothing is tied to your IP address or account. Leave out names and other personal details. Privacy

What is actually comparable

Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.

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.

A shared-evidence shape is not available.

BenchLM does not draw a radar or infer missing axes when the matched evidence is too sparse.

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, reasoning, multimodal, 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.

Agentic

Not comparable
GLiDE
Not ranked
Inkling
35.8
Supported · #78/135
Basis
BenchAlign v5.8 lane · 0 vs 5 public rows
Reading
Not comparable

Coding

Not comparable
GLiDE
Not ranked
Inkling
35.1
Supported · #84/162
Basis
BenchAlign v5.8 lane · 0 vs 6 public rows
Reading
Not comparable

Reasoning

Not comparable
GLiDE
Not ranked
Inkling
38.2
Estimated · #96/160
Basis
BenchAlign v5.8 lane · 0 vs 0 public rows
Reading
Not comparable

Multimodal

Not comparable
GLiDE
Not ranked
Inkling
50.6
Estimated · #57/67
Basis
BenchAlign v5.8 lane · 0 vs 3 public rows
Reading
Not comparable

Knowledge

Not comparable
GLiDE
Not ranked
Inkling
51.1
Supported · #75/180
Basis
BenchAlign v5.8 lane · 0 vs 6 public rows
Reading
Not comparable

Multilingual

Not comparable
GLiDE
Not ranked
Inkling
Not ranked
Basis
Provisional lane · 0 vs 0 weighted rows
Reading
Not comparable

Instruction following

Not comparable
GLiDE
Not ranked
Inkling
87.6
#40/157
Basis
Provisional lane · 0 vs 1 weighted rows
Reading
Not comparable

Math

Not comparable
GLiDE
Not ranked
Inkling
54.6
#9/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, reasoning, multimodal, 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

GLiDE
$0.00015
Fits in one request
Inkling
$0.00421
Fits in one request

GLiDE has the lower modeled cost

Costs use the listed standard API rates.

Repository review

50K fresh input + 3K output tokens

GLiDE
$0.0075
Does not fit in one request
Inkling
$0.10754
Fits in one request

GLiDE does not fit this workload in one request.

Cache-heavy agent loop

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

GLiDE
$0.033
Does not fit in one request
Cached input priced at the published list-input rate
Inkling
$0.159
Fits in one request

GLiDE does not fit this workload in one request. GLiDE has no published cached-input rate, so cached tokens use its listed input rate.

Your workload

Enter a month of tokens to price it at both models’ listed API rates.

GLiDE
$1.50
per month
Inkling
$28.06
per month

Standard listed rates, no batch or volume discounts.

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

Price against score, among all priced models

Overall score against output price per 1M tokens, one model per family. Pricing as of November 12, 2026.

Inkling

20406080100$0.10$0.50$1$5$10$50$100Output price, $ per 1M tokens (log)Overall score
  • GLiDE has no overall score yet, so it is not plotted.
  • 25 cheaper models score at least as high as Inkling. The nearest is GLM-5.2 (score 59.7, $4.40 per 1M output tokens).

Gray dots are the other priced models. The dark step line is the efficiency frontier: for a model under it, another model costs no more and scores at least as high.

See Inkling on the full price vs performance chart

Specification differences

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

Context window

Maximum documented context; output-token limits may be lower.

Inkling

1M

Cached-input rate

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

GLiDE

Inkling

$0.374 per 1M cached input tokens

Reasoning profile

GLiDE

Reasoning

Inkling

Hybrid

Weight access

GLiDE

Proprietary

Inkling

Open Weight

License

GLiDE

Proprietary

Inkling

Open Weight

Release date

GLiDE

2026-09-30

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
The public evidence has no benchmark result shared by both models, so it does not support a quality verdict.
Workload cost
Repository review: $0.0075 vs $0.10754. Cache-heavy agent loop: $0.033 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, GLiDE or Inkling?

The public evidence has no benchmark result shared by both models, so it does not support a quality verdict. The page therefore keeps the decision tied to the specific documented workload.

Which is better for coding, GLiDE or Inkling?

GLiDE is not ranked on the public lane for coding, so no winner is named for coding.

Which is better for agentic tasks, GLiDE or Inkling?

GLiDE is not ranked on the public lane for agentic tasks, so no winner is named for agentic tasks.

Which costs less, GLiDE or Inkling?

For the stated presets, chat costs $0.00015 on GLiDE and $0.00421 on Inkling; repository review costs $0.0075 and $0.10754; the cache-heavy agent loop costs $0.033 and $0.159. GLiDE does not fit this workload in one request. GLiDE has no published cached-input rate, so cached tokens use its listed input rate.

Which has the larger context window, GLiDE or Inkling?

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

Self-host vs API cost

Estimates at 50,000 req/day · 1000 tokens/req average.

GLiDE
API / mo$113
Self-host / moNot listed
Break-even—
Proprietary model — self-hosting not applicable.
Inkling
API / mo$4,913
Self-host / mo$27,962
Break-evenNot reached at 70% load
Model the full break-even

Benchmark evidence

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

Browse raw public benchmark evidence24 rows

Agentic

  • Terminal-Bench 2.1

    GLiDE—
    Inkling63.8%
    Source

    Not directly comparable

  • BrowseComp

    GLiDE—
    Inkling77.1%
    Source

    Not directly comparable

  • MCP Atlas

    GLiDE—
    Inkling74.1%
    Source

    Not directly comparable

  • Terminal-Bench 2.1 (Vals)

    GLiDE—
    Inkling47.6%
    Source

    Not directly comparable

  • CWE-bench v1

    GLiDE—
    Inkling37.0%
    Source

    Not directly comparable

Coding

  • SWE-bench Verified

    GLiDE—
    Inkling77.6%
    Source

    Not directly comparable

  • SWE-bench Pro

    GLiDE—
    Inkling54.3%
    Source

    Not directly comparable

  • Terminal-Bench 2.1

    GLiDE—
    Inkling63.8%
    Source

    Not directly comparable

  • FrontierSWE v2

    GLiDE—
    Inkling4.1%
    Source

    Not directly comparable

  • LiveCodeBench (Vals)

    GLiDE—
    Inkling85.5%
    Source

    Not directly comparable

  • SWE-bench (Vals)

    GLiDE—
    Inkling77.6%
    Source

    Not directly comparable

Multimodal

  • MMMU-Pro

    GLiDE—
    Inkling73.5%
    Source

    Not directly comparable

  • CharXiv

    GLiDE—
    Inkling82%
    Source

    Not directly comparable

  • CharXiv w/o tools

    GLiDE—
    Inkling78.1%
    Source

    Not directly comparable

Knowledge

  • GPQA

    GLiDE—
    Inkling87.9%
    Source

    Not directly comparable

  • GPQA-D

    GLiDE—
    Inkling87.9%
    Source

    Not directly comparable

  • HLE

    GLiDE—
    Inkling46%
    Source

    Not directly comparable

  • HLE w/o tools

    GLiDE—
    Inkling30%
    Source

    Not directly comparable

  • GPQA Diamond (Vals)

    GLiDE—
    Inkling87.1%
    Source

    Not directly comparable

  • MMLU-Pro (Vals)

    GLiDE—
    Inkling86.3%
    Source

    Not directly comparable

Instruction following

  • IFBench

    GLiDE—
    Inkling79.8%
    Source

    Not directly comparable

Math

  • AIME26

    GLiDE—
    Inkling97.1%
    Source

    Not directly comparable

  • FrontierMath v2 (Tiers 1-3)

    GLiDE—
    Inkling33.333%
    Source

    Not directly comparable

  • FrontierMath v2 (Tier 4)

    GLiDE—
    Inkling4.878%
    Source

    Not directly comparable

24 public results · 0 shared

Watch GLiDE vs Inkling

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

Read a sample issue

Join 7,000+ subscribers.

Last updated November 13, 2026