At a glance
| Question | Muse Wonder | Muse Wonder Full |
|---|---|---|
| Documented access | API model muse-wonder-1.0 | Muse Code subscription access |
| Context window | 1M tokens | 1M tokens |
| How it is billed | Per input, cached-input, and output token | Power or Maximum monthly subscription |
| Best first question | Do you need programmatic API access? | Are you eligible for supported Muse Code access? |
Choose by access, not by hype
Start with the workflow you actually need. If you are building an application, service, or automation that must call a model from code, the documented API path is Muse Wonder. API requests usemuse-wonder-1.0 and token-based billing.
If you want model access inside the supported Muse Code experience, review the Full subscription options. That route is tied to plan eligibility, available quota, and region. It is not a substitute for an API integration.
Find the access path that fitsKnow the constraints
A 1M-token context window describes the supported context size; it does not guarantee output quality, speed, availability, or a particular result on your task.
Do not compare these paths with invented benchmark scores or assumed quotas. Confirm the current model documentation and subscription terms for the account and region you will use.