Skip to main content
BenchLM
Data

Inkling vs Muse Wonder

Updated October 12, 2026. Rank says Muse Wonder 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

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
Thinking Machines Lab logo

Thinking Machines Lab

52.81/100

Supported · Public rank #80

90% interval 42.4–63.2

Model B
Meta logo

Meta

70.44/100

Estimated · Public rank #16

Conditional range 56.1–84.8

Shared results
0
Inkling only
22
Muse Wonder only
6
Like-for-like categories
2 / 8
Supported: Inkling · Estimated: Muse Wonder. Conditional ranges do not establish rank confidence.How 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

    Muse Wonder

    Muse Wonder has the higher public coding point estimate, 69.8 to 34.7, with Supported evidence for both models. The conditional ranges do not establish rank confidence.

    Confidence: limited
  • 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
  • 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. Costs use the listed standard API rates.

    Confidence: listed-rates
Show secondary and unsupported calls
  • 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

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

    Confidence: limited
  • Long documents

    Prompts that approach the documented context limit

    No clear pick

    The documented context windows are equal.

    Confidence: documented

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.

34.7Inkling69.8Muse Wonder

Like-for-like · BenchAlign v5.8

Muse Wonder 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.

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, 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
Inkling
34.7
Supported · #80/148
Muse Wonder
69.8
Supported · #10/148
Basis
BenchAlign v5.8 lane · 6 vs 3 public rows
Reading
Muse Wonder leads

Knowledge

Like-for-like
Inkling
55.4
Supported · #57/180
Muse Wonder
74.0
Supported · #12/180
Basis
BenchAlign v5.8 lane · 6 vs 1 public rows
Reading
Muse Wonder leads · intervals overlap

Agentic

Not comparable
Inkling
36.5
Supported · #71/123
Muse Wonder
Not ranked
Basis
BenchAlign v5.8 lane · 5 vs 2 public rows
Reading
Not comparable

Reasoning

Not comparable
Inkling
79.0
#14/29
Muse Wonder
81.3
Unranked · 2 rankable rows
Basis
Provisional lane · 0 vs 0 weighted rows
Reading
Not comparable

Multimodal

Not comparable
Inkling
67.5
#35/54
Muse Wonder
Not ranked
Basis
Provisional lane · 2 vs 0 weighted rows
Reading
Not comparable

Multilingual

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

Instruction following

Not comparable
Inkling
87.6
#35/127
Muse Wonder
Not ranked
Basis
Provisional lane · 1 vs 0 weighted rows
Reading
Not comparable

Math

Not comparable
Inkling
81.2
Unranked · 1 rankable row
Muse Wonder
Not ranked
Basis
Provisional lane · 1 vs 0 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

Inkling
$0.00421
Fits in one request
Muse Wonder
$0.014
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

Inkling
$0.10754
Fits in one request
Muse Wonder
$0.26
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

Inkling
$0.159
Fits in one request
Muse Wonder
$0.32
Fits in one request

Inkling has the lower modeled cost

Costs use the listed standard API rates.

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.

Inkling

$0.374 per 1M cached input tokens

Muse Wonder

$0.2 per 1M cached input tokens

Meta: Muse Wonder models and pricing

Documented inputs

Inkling

Not sourced

Muse Wonder

Not sourced

Documented outputs

Inkling

Not sourced

Muse Wonder

Not sourced

Provider availability

Inkling

Not sourced

Muse Wonder

Not sourced

Reasoning profile

Inkling

Hybrid

Muse Wonder

Reasoning

Weight access

Inkling

Open Weight

Muse Wonder

Proprietary

License

Inkling

Open Weight

Muse Wonder

Proprietary

Release date

Inkling

2026-07-15

Muse Wonder

2026-10-12

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.10754 vs $0.26. Cache-heavy agent loop: $0.159 vs $0.32.
Context tradeoff
Both models list 1M.
Run the same representative tasks against both endpoints before changing production traffic.

Questions

Which is better, Inkling or Muse Wonder?

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, Inkling or Muse Wonder?

Muse Wonder has the higher public coding point estimate, 69.8 to 34.7, with Supported evidence for both models. The conditional ranges do not establish rank confidence.

Which is better for agentic tasks, Inkling or Muse Wonder?

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

Which costs less, Inkling or Muse Wonder?

For the stated presets, chat costs $0.00421 on Inkling and $0.014 on Muse Wonder; repository review costs $0.10754 and $0.26; the cache-heavy agent loop costs $0.159 and $0.32. Costs use the listed standard API rates.

Which has the larger context window, Inkling or Muse Wonder?

Both models list the same context window, 1M.

Benchmark evidence

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

Browse raw public benchmark evidence28 rows

Agentic

  • Terminal-Bench 2.1

    Inkling63.8%
    Source
    Muse Wonder—

    Not directly comparable

  • BrowseComp

    Inkling77.1%
    Source
    Muse Wonder—

    Not directly comparable

  • MCP Atlas

    Inkling74.1%
    Source
    Muse Wonder—

    Not directly comparable

  • Terminal-Bench 2.1 (Vals)

    Inkling47.6%
    Source
    Muse Wonder—

    Not directly comparable

  • CWE-bench v1

    Inkling37.0%
    Source
    Muse Wonder—

    Not directly comparable

  • JobBench

    Inkling—
    Muse Wonder70.5%
    Source

    Not directly comparable

  • Finance Agent v2

    Inkling—
    Muse Wonder56.6%
    Source

    Not directly comparable

Coding

  • SWE-bench Verified

    Inkling77.6%
    Source
    Muse Wonder—

    Not directly comparable

  • SWE-bench Pro

    Inkling54.3%
    Source
    Muse Wonder—

    Not directly comparable

  • Terminal-Bench 2.1

    Inkling63.8%
    Source
    Muse Wonder—

    Not directly comparable

  • FrontierSWE v2

    Inkling4.1%
    Source
    Muse Wonder—

    Not directly comparable

  • LiveCodeBench (Vals)

    Inkling85.5%
    Source
    Muse Wonder—

    Not directly comparable

  • SWE-bench (Vals)

    Inkling77.6%
    Source
    Muse Wonder—

    Not directly comparable

  • DeepSWE

    Inkling—
    Muse Wonder78.8%
    Source

    Not directly comparable

  • ProgramBench

    Inkling—
    Muse Wonder50.0%
    Source

    Not directly comparable

  • sweMarathon

    Inkling—
    Muse Wonder53.1%
    Source

    Not directly comparable

Multimodal

  • MMMU-Pro

    Inkling73.5%
    Source
    Muse Wonder—

    Not directly comparable

  • CharXiv

    Inkling82%
    Source
    Muse Wonder—

    Not directly comparable

  • CharXiv w/o tools

    Inkling78.1%
    Source
    Muse Wonder—

    Not directly comparable

Knowledge

  • GPQA

    Inkling87.9%
    Source
    Muse Wonder—

    Not directly comparable

  • GPQA-D

    Inkling87.9%
    Source
    Muse Wonder—

    Not directly comparable

  • HLE

    Inkling46%
    Source
    Muse Wonder—

    Not directly comparable

  • HLE w/o tools

    Inkling30%
    Source
    Muse Wonder—

    Not directly comparable

  • GPQA Diamond (Vals)

    Inkling87.1%
    Source
    Muse Wonder—

    Not directly comparable

  • MMLU-Pro (Vals)

    Inkling86.3%
    Source
    Muse Wonder—

    Not directly comparable

  • HealthBench Professional

    Inkling—
    Muse Wonder60.5%
    Source

    Not directly comparable

Instruction following

  • IFBench

    Inkling79.8%
    Source
    Muse Wonder—

    Not directly comparable

Math

  • AIME26

    Inkling97.1%
    Source
    Muse Wonder—

    Not directly comparable

28 public results · 0 shared

Watch Inkling vs Muse Wonder

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 12, 2026