Understand a repository before editing
Share the relevant files to compare implementation options and understand how a change will affect existing behavior.
Muse Wonder is Meta’s reasoning model for coding and complex tasks.
Share the relevant files to compare implementation options and understand how a change will affect existing behavior.
Provide the error and expected behavior so the assistant can suggest a likely cause and a focused way to verify it.
Review a patch against its acceptance criteria and ask for edge cases, inconsistent behavior and useful validation.
Treat generated code as a proposal: read it, run suitable tests and check permissions before applying it in production.
Sign in, describe the expected result and provide relevant source or logs while leaving credentials out of the prompt.
Choose the result you need: an explanation, patch, review or plan, with compatibility requirements and a clear scope.
Review the answer, verify changes in your development environment and share the results when you need a revision.
Move from a feature idea to an implementation plan with dependencies and acceptance criteria your team can discuss.
Example prompt
Help me turn this feature idea into an implementation plan. List dependencies, tradeoffs and acceptance criteria.
Discuss a feature, outline a change and review a patch while keeping the conversation tied to your users’ requirements.
Request a plain-language explanation and a small example, then compare the answer with reliable learning material.
Evaluate representative tasks for correctness, useful output and token spend before choosing a model for team workflows.
| Muse Wonder for complex coding tasks | Muse Code versus browser chat | Muse Wonder API through OpenRouter |
|---|---|---|
| Discuss code, investigate errors and compare implementation approaches. | Muse Code runs a terminal agent; browser chat here does not automatically edit repositories or control your computer. | OpenRouter provides an OpenAI-compatible endpoint with token-based billing. |
OpenRouter lists $4 input, $20 output and $0.20 cached input per million tokens, checked on October 13, 2026. These are upstream provider rates; this site's chat and API credit prices are shown in Pricing.
View OpenRouter ratesCompare the edition, reasoning settings, tools and test setup before using a benchmark score to choose a coding model.
Choose monthly or annual billing, or buy credits with a one-time pack.
Annual option
Pay once and receive your annual credit allowance up front.
Annual credits
Check the displayed allowance before checkout
$0.01 per credit
$174 charged once a year
Works with
AI coding chat
Credit allowance
17,400 credits for the year, up front
Credit rate
$0.01 per credit on the yearly plan
What's included
$0.01 per credit
$294 charged once a year
Works with
AI coding chat
Credit allowance
29,400 credits for the year, up front
Credit rate
$0.01 per credit on the yearly plan
What's included
$0.01 per credit
$588 charged once a year
Multiplier
Works with
AI coding chat
Credit allowance
58,800 credits for the year, up front
Credit rate
$0.01 per credit on the yearly plan
What's included
Pay safely and securely with
Also available at checkout in supported regions: EPS, Kakao Pay, Naver Pay, PAYCO, Samsung Pay, MB WAY and SEPA Direct Debit. Checkout shows the methods that work for your country, currency and plan.
Muse Wonder answers below explain the model, API access and subscriptions so you can choose the right way to use it.
Muse Wonder is Meta’s multimodal reasoning model for coding and complex agent tasks. It accepts several input types upstream and returns text.
Yes. Complex software engineering is a key use case, alongside general reasoning and document understanding. Share the relevant code and requirements, then verify proposed changes with your own tests.
Create an API key in your account settings and use the OpenAI-compatible chat completions endpoint. See the API guide for authentication, examples and usage limits.
Choose a monthly or annual subscription, or a one-time credit pack. Credits cover chat and API usage; the pricing page lists each plan’s price and credit allowance.
Prompt length, conversation history, reasoning effort and response length affect token use. Long context can improve understanding but also increases spend, so give the model relevant material rather than an entire unrelated repository.
Check which edition was tested, the reasoning settings and the tools available during evaluation. Use a small set of your own coding tasks to compare results before making a decision based on a published score.
No. Muse Wonder returns text and code. It can help explain, analyze and reason about the material you provide.
No. You can begin with a browser conversation here. Muse Code and OpenCode are separate agent tools for development environments, and their integrations, permissions and billing depend on their own setup.
Community discussions can offer examples and impressions from particular workflows. Check claims about availability, pricing and model capabilities against the current Meta documentation and provider model page, then test the model on your own representative task.