---
type: "post"
id: "larger-sibling-muse-wonder-full-is-locked-to-e67a35"
slug: "larger-sibling-muse-wonder-full-is-locked-to-e67a35"
title: "Larger sibling Muse Wonder Full is locked to Meta's Muse Code paid plans and not sold via API."
description: "Meta's Muse Wonder launch exposes a deployment boundary, not just a model ranking: the standard model is offered through an API, while the stronger sibling is restricted to paid Muse Code plans."
retrieval_nugget: "Meta's Muse Wonder launch exposes a deployment boundary, not just a model ranking: the standard model is offered through an API, while the stronger sibling is restricted to paid Muse Code plans."
published_at: "2026-10-16"
updated_at: "2026-10-16"
record_date: "2026-10-16"
date_kind: "published_at"
topics: ["coding-agents","pricing","models"]
source_urls: ["https://venturebeat.com/technology/metas-new-muse-wonder-and-muse-wonder-full-models-achieve-frontier-performance-but-only-the-weaker-one-is-available-via-api"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:larger-sibling-muse-wonder-full-is-locked-to-e67a35"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:e57af5c339ac214d1728dc375173ec84beae78357a39d17ba229c3746e9ff9c0","reviewed_at":"2026-10-16T08:01:32.976Z","source_evidence_count":1,"verified_claim_count":3,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":3,"implication_count":2,"watch_condition_count":2,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Meta's Muse Wonder release separates reported model capability from API availability.","observed_facts":[{"text":"VentureBeat reports that Muse Wonder is available through a commercial API, while Muse Wonder Full is limited to paid Muse Code plans and is not sold via API.","source_urls":["https://venturebeat.com/technology/metas-new-muse-wonder-and-muse-wonder-full-models-achieve-frontier-performance-but-only-the-weaker-one-is-available-via-api"]},{"text":"VentureBeat reports Artificial Analysis Intelligence Index scores of 56 for Muse Wonder Full and 52 for Muse Wonder.","source_urls":["https://venturebeat.com/technology/metas-new-muse-wonder-and-muse-wonder-full-models-achieve-frontier-performance-but-only-the-weaker-one-is-available-via-api"]},{"text":"The report says neither model is being released with publicly downloadable weights.","source_urls":["https://venturebeat.com/technology/metas-new-muse-wonder-and-muse-wonder-full-models-achieve-frontier-performance-but-only-the-weaker-one-is-available-via-api"]}],"mechanism":"The stronger sibling is accessible only within a paid coding-assistant product, so its reported capability cannot be assumed available for API-based production integration.","why_now":"VentureBeat's October 12 report describes a new model release and a concrete access distinction that affects current deployment choices.","implications":["Teams should evaluate the API-accessible Wonder on their own workloads rather than transferring Wonder Full benchmark results to their production plans.","Model access route is a separate procurement and integration constraint from model quality."],"evidence_boundary":"The access terms and benchmark figures are reported by VentureBeat; aggregate benchmark scores do not establish performance on a team's own workload, and the supplied source does not verify future availability.","watch_conditions":["Whether Meta later offers Wonder Full through an API or otherwise expands access beyond Muse Code subscriptions.","Independent comparisons of Wonder under identical tools and representative production tasks."],"related_records":[],"new_branch_reason":"No prior New Runtime record was supplied; this starts a distinct analytical record focused on the reported access split between Muse Wonder and Wonder Full."}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/larger-sibling-muse-wonder-full-is-locked-to-e67a35/","markdown":"https://newruntime.com/posts/larger-sibling-muse-wonder-full-is-locked-to-e67a35.md","json":"https://newruntime.com/posts/larger-sibling-muse-wonder-full-is-locked-to-e67a35.json"}
---

# Larger sibling Muse Wonder Full is locked to Meta's Muse Code paid plans and not sold via API.

## Retrieval answer

Meta's Muse Wonder launch exposes a deployment boundary, not just a model ranking: the standard model is offered through an API, while the stronger sibling is restricted to paid Muse Code plans.

Meta's Muse Wonder launch exposes a deployment boundary, not just a model ranking: the standard model is offered through an API, while the stronger sibling is restricted to paid Muse Code plans. This matters because teams often treat benchmark leadership and production availability as one decision, when they are separate constraints.

Thesis: Meta's Muse Wonder release separates reported model capability from API availability. The reported access split is the mechanism: The stronger sibling is accessible only within a paid coding-assistant product, so its reported capability cannot be assumed available for API-based production integration. Why now: VentureBeat's October 12 report describes a new model release and a concrete access distinction that affects current deployment choices. The report says Artificial Analysis scored Wonder Full 56 and Wonder 52 on its Intelligence Index. It also says the models are proprietary and neither has publicly downloadable weights.

First implication: Teams should evaluate the API-accessible Wonder on their own workloads rather than transferring Wonder Full benchmark results to their production plans. First watch condition: Whether Meta later offers Wonder Full through an API or otherwise expands access beyond Muse Code subscriptions. Evidence boundary: The access terms and benchmark figures are reported by VentureBeat; aggregate benchmark scores do not establish performance on a team's own workload, and the supplied source does not verify future availability. The distinction is a product constraint, not evidence that the API model is unsuitable. The next useful evidence would be an official access update and independent testing under the same harness on representative tasks.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Coding Agents](https://newruntime.com/topics/coding-agents.md): Explore the coding-agents topic hub.
- topic hub: [Pricing](https://newruntime.com/topics/pricing.md): Explore the pricing topic hub.
- topic hub: [Models](https://newruntime.com/topics/models.md): Explore the models topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)