Skip to main content
BenchLM
Data

Muse Wonder vs Muse Wonder Full

Updated October 12, 2026. Rank says Muse Wonder Full is ahead. Price, access, and your workload can each overturn that. Public scores include evidence status and uncertainty. This is a same-family comparison, so migration details appear when the source data supports them.

Share or export
Share on XLinkedInAPI/MCP

Decision reading

Muse Wonder Full has the higher public point estimate, 73.81 versus 70.44. Their conditional score ranges overlap. These ranges do not establish rank confidence. 6 results are shared. Category rows resting on Estimated evidence or different benchmark sets are marked directional and do not name a winner.

Model A
Meta logo

Meta

70.44/100

Estimated · Public rank #16

Conditional range 56.1–84.8

Model B
Meta logo

Meta

73.81/100

Estimated · Public rank #11

Conditional range 59.5–88.2

Shared results
6
Muse Wonder only
0
Muse Wonder Full only
0
Like-for-like categories
2 / 8
Estimated: Muse Wonder and Muse Wonder Full. 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 Full

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

    Confidence: limited
Show secondary and unsupported calls
  • Agentic work

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

    Not enough matched evidence

    Muse Wonder and Muse Wonder Full are 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
  • Chat turn cost

    1K fresh input + 500 output tokens

    Not enough matched evidence

    A complete comparable API-rate estimate is not available for both models.

    Confidence: listed-rates
  • Cache-heavy agent loop cost

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

    Not enough matched evidence

    A complete comparable API-rate estimate is not available for both models.

    Confidence: listed-rates
  • Repository review cost

    50K fresh input + 3K output tokens

    Not enough matched evidence

    A complete comparable API-rate estimate is not available for both models.

    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.

69.8Muse Wonder74.0Muse Wonder Full

Like-for-like · BenchAlign v5.8

Muse Wonder Full 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
Muse Wonder
69.8
Supported · #10/148
Muse Wonder Full
74.0
Supported · #5/148
Basis
BenchAlign v5.8 lane · 3 vs 3 public rows
Reading
Muse Wonder Full leads · intervals overlap

Knowledge

Like-for-like
Muse Wonder
74.0
Supported · #12/180
Muse Wonder Full
77.9
Supported · #10/180
Basis
BenchAlign v5.8 lane · 1 vs 1 public rows
Reading
Muse Wonder Full leads · intervals overlap

Agentic

Not comparable
Muse Wonder
Not ranked
Muse Wonder Full
Not ranked
Basis
BenchAlign v5.8 lane · 2 vs 2 public rows
Reading
Not comparable

Reasoning

Not comparable
Muse Wonder
81.3
Unranked · 2 rankable rows
Muse Wonder Full
83.4
Unranked · 2 rankable rows
Basis
Provisional lane · 0 vs 0 weighted rows
Reading
Not comparable

Multimodal

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

Multilingual

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

Instruction following

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

Math

Not comparable
Muse Wonder
Not ranked
Muse Wonder Full
Not ranked
Basis
Provisional lane · 0 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

Muse Wonder
$0.014
Fits in one request
Muse Wonder Full
API rate not published
Fits in one request

Muse Wonder Full has no comparable published API token rate.

Repository review

50K fresh input + 3K output tokens

Muse Wonder
$0.26
Fits in one request
Muse Wonder Full
API rate not published
Fits in one request

Muse Wonder Full has no comparable published API token rate.

Cache-heavy agent loop

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

Muse Wonder
$0.32
Fits in one request
Muse Wonder Full
API rate not published
Fits in one request
Cached-input rate unavailable

Muse Wonder Full has no comparable published API token 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.

Documented inputs

Muse Wonder

Not sourced

Muse Wonder Full

Not sourced

Documented outputs

Muse Wonder

Not sourced

Muse Wonder Full

Not sourced

Provider availability

Muse Wonder

Not sourced

Muse Wonder Full

Not sourced

Reasoning profile

Muse Wonder

Reasoning

Muse Wonder Full

Reasoning

Weight access

Muse Wonder

Proprietary

Muse Wonder Full

Proprietary

License

Muse Wonder

Proprietary

Muse Wonder Full

Proprietary

Release date

Muse Wonder

2026-10-12

Muse Wonder Full

2026-10-12

If you are choosing between sibling variants

Deployment change
Both entries list Meta as the provider. Confirm endpoint, model ID, limits, and feature support before switching.
Quality signal
Muse Wonder Full has the higher public point estimate, 73.81 versus 70.44. Their conditional score ranges overlap. These ranges do not establish rank confidence.
Workload cost
A complete comparable API-rate estimate is not available for both models.
Context tradeoff
Both models list 1M.
Run the same representative tasks against both endpoints before changing production traffic.

Questions

Which is better, Muse Wonder or Muse Wonder Full?

Muse Wonder Full has the higher public point estimate, 73.81 versus 70.44. Their conditional score ranges overlap. These ranges do not establish rank confidence. The page therefore keeps the decision tied to the specific documented workload.

Which is better for coding, Muse Wonder or Muse Wonder Full?

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

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

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

Which costs less, Muse Wonder or Muse Wonder Full?

Both models do not have comparable published API token rates, so this page does not name a universal price winner.

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

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 evidence6 rows

Agentic

  • Muse Wonder70.5%
    Muse Wonder Full75.3%

    Muse Wonder Full leads this result

  • Finance Agent v2

    Shared source
    Muse Wonder56.6%
    Muse Wonder Full59.1%

    Muse Wonder Full leads this result

Coding

  • Muse Wonder78.8%
    Muse Wonder Full79.0%

    Muse Wonder Full leads this result

  • ProgramBench

    Shared source
    Muse Wonder50.0%
    Muse Wonder Full59.0%

    Muse Wonder Full leads this result

  • sweMarathon

    Shared source
    Muse Wonder53.1%
    Muse Wonder Full57.5%

    Muse Wonder Full leads this result

Knowledge

  • HealthBench Professional

    Shared source
    Muse Wonder60.5%
    Muse Wonder Full62.3%

    Muse Wonder Full leads this result

6 public results · 6 shared

Watch Muse Wonder vs Muse Wonder Full

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