A model for work that takes several steps
Muse Wonder joins Meta’s catalog on 12 October 2026. It is aimed at coding and agent workflows that must keep going after an initial answer: inspect a workspace, use tools, revise an approach and deliver a finished result. Active Memory and Active Focus are the names attached to its context retrieval and sustained execution capabilities. Their usefulness depends on the surrounding agent and the information it can access.
Calling the intended model
Use muse-wonder-1.0 for the hosted API route. The service accepts text, images, video, audio and PDFs and returns text within a 1,048,576-token context window. The registry records a 131,072-token output allowance; request and account limits still need checking. Reasoning effort ranges from minimal through max. Selecting max does not switch the request to Muse Wonder Full.
Budgeting a complete agent run
The Standard route charges $4 per million input tokens and $20 per million output tokens, with cached input at $0.20. Search grounding adds a separate query charge. Long inputs do not carry a different token rate on this route. Compare finished runs with the same tools and account settings, especially when several attempts are needed to complete a repository change.
Evaluating Muse Wonder
Give the agent a repository change with clear acceptance checks and a deliberate blocker, such as missing documentation or a failing existing check. Inspect whether the final patch meets the original constraints, whether tool failures were resolved, and whether unfinished work is reported accurately. Compare sustained task completion separately from the quality of a single generated answer.
Record the exact model identifier, deployment route and request settings with each result. Count complete runs, including rejected outputs, retries and tool calls. When the workflow creates files or code, open the files or execute the existing checks before accepting the result. A plausible first response can hide an incomplete final deliverable.
The specifications describe supported interfaces and request capacity. They do not establish a measured quality ranking or a latency guarantee for your account. SyncDev has not independently benchmarked this model. Choose a deployment after testing the languages, input formats and operating conditions that matter to your users.
Explore meta models, browse model tasks, or compare two models with the same acceptance criteria.