Keep the products separate
The consumer Muse App, Muse Code, and the Meta Model API serve different workflows. A consumer app experience is not evidence that your developer account has a Muse Code subscription or Model API billing enabled. Confirm the product and account shown during the official flow instead of assuming that access carries across.
The names describe different layers: Muse Code is the supported coding tool and experience; Muse Wonder and Muse Wonder Full are model names; and the Meta Model API is the programmatic channel.
| Path | Use it for | Billing and access check |
|---|---|---|
| Consumer Muse App | Consumer-facing product use. | Check its own account experience; this guide does not publish its pricing or regional availability. |
| Muse Code | Work in the supported Muse Code coding experience. | A monthly subscription applies only to the credential connected during Muse Code CLI onboarding. |
| Meta Model API | Programmatic model requests from your own product or tool. | API keys are pay-as-you-go; review token and tool charges in the Model API billing flow. |
Muse Wonder and Muse Wonder Full can be available in either Contributor or non-Contributor mode on the plans that include them. Mode affects how content may be used and should be checked in the current product settings before you send sensitive material.
The official documentation says Muse Code subscriptions default to Contributor mode. You can turn it off in Muse Code settings; check the current setting for the workspace and account you intend to use.
Before paying
- Decide whether the work must run inside Muse Code or from your own application. Use the model picker if you need help separating those paths.
- Sign in to the official account experience and review the plans, eligibility, available models, current benefits, and renewal terms shown for your account. Benefits and availability can vary by region.
- For a Muse Code subscription, confirm that you will onboard in the supported Muse Code CLI with the intended Meta Model API account.
- For API work, treat a subscription and an API budget as separate decisions. Additional Model API keys are billed pay-as-you-go.
- Read the official subscription details before checkout, including change, cancellation, and billing-cycle terms.
Before starting
- Use the official Muse Code onboarding flow and complete sign-in for the account whose plan you reviewed. Do not assume a credential intended for Muse Code works in another harness.
- Check the models visible to you after onboarding. Plan eligibility, account state, and current availability determine what you can select.
- Start with a small representative task. For a guided coding exercise, open first coding task.
- If your work requires programmatic requests, follow the separate Model API setup guidance and use the documented API model ID
muse-wonder-1.0where appropriate.
Billing checklist
Use this short check before increasing usage, adding an API key, or assuming a plan covers a workflow.
- Muse Code subscription: verify the plan, renewal date, usage limit, and the account used for CLI onboarding.
- Model API: verify that billing is enabled for the account and estimate token usage before shipping traffic. The published standard rate for
muse-wonder-1.0is $4.00 input, $0.20 cached input, and $20.00 output per one million tokens. - Web search: account for the separate published $2.50 per 1,000 web-search queries when your API workflow uses the
web_searchtool. - Budget review: use the cost calculator for token estimates, then compare the estimate with the official billing view and your actual usage data.
Rates and limits are provider-published information that can change. Read the current pricing and rate-limit documentation before a larger launch.
Common questions
Does a Muse Code subscription cover every API key I create?
No. The subscription is for the credential automatically connected by Muse Code CLI onboarding. The official documentation says additional API keys under the same Model API account are pay-as-you-go.
Can I use a Muse Code subscription as an API integration plan?
Treat them as different paths. The subscription works through Muse Code CLI while signed in; programmatic Model API requests use API credentials and pay-as-you-go billing.
Is Contributor mode available for Muse Wonder everywhere?
No. The current Model API pricing documentation says Contributor mode is not available for Muse Wonder on Model API. The subscription documentation separately says that Muse Wonder and Muse Wonder Full are available in either mode on Muse Code plans that include them.
What if I cannot select the model I expected?
Review plan eligibility, account sign-in, and provider availability first, then follow the Muse Code troubleshooting guide.