Ask a platform team what one agent task costs to run and most cannot answer. They know the monthly bill. They do not know what a single document extraction costs.
On November 9, 2026, Meta released Muse Ember (opens in a new tab), the smallest model in its Muse family. Meta built it for one job: the high-volume work that sits underneath an agent's thinking.
What Meta shipped
Muse Ember (muse-ember-1.0) targets repetitive, bounded execution rather than open-ended reasoning.
| Spec | Value |
|---|---|
| Context window | 1,048,576 tokens |
| Max output | 512,000 tokens per reply |
| Inputs | Text, image, audio, video |
| Price up to 200k context | $0.10 per M input, $0.50 per M output |
| Price over 200k context | $0.30 per M input, $1.50 per M output |
| Cached input | $0.004 per M to read, $0.125 per M to write |
| Availability | Meta Model API and Muse Code, hosted only |
On the Artificial Analysis Intelligence Index it scores 36 at maximum reasoning effort. That matches Anthropic's Claude Haiku 5.5 at its max setting, at roughly a third of the cost per completed task: about $0.14 against about $0.41.
Meta positions it as the executor in a pair. Larger models in the family, such as Muse Wonder, handle planning and orchestration. Ember handles the steps in between: tool calls, code refactoring, data extraction, request routing, long-document summarisation.
Why the split matters
An agent run is not one request. It is a loop.
A SINGLE AGENT TASK
Plan the approach -> needs judgement
Call the search tool -> mechanical
Extract fields from 40 documents -> mechanical
Route to the right handler -> mechanical
Refactor the generated code -> mechanical
Judge whether the result is good -> needs judgement
Summarise it for the user -> light judgement
Two of those seven steps need a frontier model. Five are execution. Sending all seven to your most expensive model is the default, and it is also the expensive way to run an agent.
That is the case for routing: not one model that does everything, but a cheap one wherever cheap is enough.
How CommandLyne routes the work
CommandLyne's multi-model layer does not send every request through the same model. It routes on four signals:
- Task complexity. Right-sized access (opens in a new tab) matches everyday requests with efficient models and gives specialised work access to more capable ones.
- User role. An org admin query and a routine status check do not need the same model.
- Latency. When a faster model is equivalent for the task, use it.
- Cost. Balance capability against price instead of paying frontier rates for mechanical work.
You bring your own keys. Gemini, Claude, OpenAI and other providers (opens in a new tab) connect under your own credentials with no reseller markup, and model choice is not tied to the hosting cloud.
Because the layer sits under every request, cost becomes visible. Token-level usage and spend track across models, users, teams and workflows in one view, with a cost-by-model breakdown. You can see which model is doing the mechanical work and what it costs, instead of reading a single line on a monthly invoice.
| One model for everything | Routed by task | |
|---|---|---|
| Planning step | Frontier model | Frontier model |
| Tool calls and extraction | Frontier model | Lightweight executor |
| Cost per task | Frontier rate on every step | Frontier rate only where it is needed |
| Latency | Same for every step | Faster model where equivalent |
| Visibility | Monthly total | Token-level, by model, team and workflow |
| Model choice | Locked to one vendor | Your keys, multiple providers |
Where to start
Find the mechanical work first. Look at what your agents do repeatedly: extractions, classifications, routing, format conversions. That is the work an executor model handles well, and it is usually the largest share of your request volume.
Then set the routing rule so the hard steps still reach a frontier model. The point is not to spend less everywhere. It is to stop paying frontier rates for work that does not need them, and to hold the receipt that shows which is which.
Meta shipping a cheap, capable executor model makes that split easier to justify. The routing layer is what makes it automatic.
Try CommandLyne to route each task to the right model under your own keys, or book a demo and we will map the split to your workload.
Try CommandLyne (opens in a new tab) | Book a demo (opens in a new tab)

