Meta announced Muse Ember on November 9, 2026, as a model for the work AI agents repeat: calling tools, routing requests, extracting information and processing collections of files or records. It is designed to handle bounded subtasks alongside a larger planning model. For developers, there is a consequential billing rule: above 200,000 input tokens, higher rates apply to the entire API request.

How Ember fits into an agent

Julian Goldie uses slides to explain Ember’s agent role, multimodal inputs and benchmark comparisons drawn from Meta and Artificial Analysis.

Meta’s proposed division of labor gives Muse Wonder or Muse Spark the planning and harder work, while Ember executes repeated steps. In that setup, a sub-agent handles a delegated piece of a larger workflow, such as analyzing a document or tackling a coding subtask. Meta says Ember is its first specialized model trained using Muse Wonder Full.

Cline founder Saoud Rizwan described that intended role in Meta’s launch announcement:

“Muse Ember is purpose-built for, and excels at, subagent work like coding and document analysis.”— Saoud Rizwan, founder of Cline

While our earlier coverage of Meta Muse examined the trust involved in delegating personal tasks, Ember addresses a developer decision: which model should handle each step of an agent’s work?

Which tasks belong with Ember?

If your workflow repeatedly extracts information from records, routes incoming requests or delegates small coding assignments, it matches the workload Meta recommends for Ember. The common feature is a bounded assignment that can be repeated across a collection.

For hard single-shot coding, knowledge-heavy questions and visual coding, Meta instead points developers to Muse Spark or Muse Wonder. That boundary matters when choosing how much responsibility to give a sub-agent: extracting fields from many files is a different assignment from solving a difficult engineering problem in one go.

Box supplied a concrete early example. Yashodha Bhavnani, Box’s VP of AI Products, described Ember scoring contract clauses against a company’s negotiation playbook and arriving at an overall risk rating. Box also evaluated screening candidates against a detailed hiring brief, including identifying borderline candidates who qualified as alternates.

Those examples explain the proposed task structure: apply detailed criteria repeatedly, then assemble the results into a larger assessment.

The API settings that affect integration

The Standard-mode model ID is muse-ember-1.0, and Meta supports three endpoints: Responses, Chat Completions and Messages.

Ember accepts text, images, video, audio and PDFs, and produces text. Meta also lists tool calling, structured output, search grounding, image understanding and computer use among its supported capabilities. Structured output is particularly relevant when the next step in a workflow needs a defined response format rather than free-form prose.

The two headline token limits serve different purposes:

  • Context window: 1,048,576 tokens. This is the model’s context capacity.
  • Maximum output: 524,288 tokens. This caps the generated response.

Tokens are the units used to represent content for model processing and billing. The context capacity is substantially larger than the API’s lower-priced request tier, so a request can fit within the model’s capacity while already qualifying for higher rates.

Reasoning effort runs from minimal through max, and the default is max. That is worth checking when adapting an existing agent: leaving the setting unspecified selects maximum effort. Meta places the effort parameter differently across its endpoints, so use the reasoning instructions for your chosen endpoint when setting it explicitly.

The 200,000-token pricing cliff

Meta’s advertised Model API prices have two request tiers. All amounts in this table are US dollars per million tokens.

Input tokens in the requestUncached inputCached inputOutput
Up to 200,000$0.10$0.004$0.50
More than 200,000$0.30$0.012$1.50

The input count determines the tier. It includes cached input and conversation history carried through previous_response_id. Once a request exceeds 200,000 input tokens, every token category uses the higher rates for that whole request, including its output.

Caching therefore has two separate effects to keep track of: cached input gets its discounted unit price, while those tokens still count toward the threshold.

What one additional input token can change

For an input-only illustration, assume all input is uncached and exclude output charges:

  • 200,000 input tokens: $0.10 × 0.2 million = $0.02.
  • 200,001 input tokens: $0.30 × 0.200001 million = $0.0600003.

That single additional token moves the input subtotal to roughly three times its previous value because the rate changes across the full request. Any generated output would also be billed at the higher output rate.

For a long conversation, the relevant count is the input sent with that request, including retained history. A short new message can therefore arrive inside a request that has already crossed the threshold.

Benchmark results change with the task

Meta’s published comparison places Muse Ember, Claude Haiku 5.5 and GPT-6 Luna at maximum reasoning effort. It reproduces Artificial Analysis results alongside Meta’s own evaluations.

Meta identifies Agents’ Last Exam, Personal Superintelligence Index, OSWorld and PerceptionBench as internal evaluations. The Artificial Analysis tests cover other task groups, including business workflows, coding and professional work over long documents.

EvaluationMuse EmberClaude Haiku 5.5GPT-6 Luna
AutomationBench-AA, strict first-attempt success37.8%13.9%20.2%
Agents’ Last Exam, Linux subset61.6%57.0%57.1%
Personal Superintelligence Index46.8%36.1%37.0%
Terminal-Bench 4.040.9%39.2%16.4%
Coding Agent Index-AA, points463731
FrontierCode 2.0-AA, mergeability-focused tasks27.2%34.9%25.2%
GDP.pdf-AA, professional work over long documents22.8%20.8%22.8%
OSWorld 2.1, partial credit69.5%68.9%50.5%
OSWorld 2.1, binary scoring33.8%27.8%17.0%
PerceptionBench, with tools80.6%78.6%62.8%
Artificial Analysis Intelligence Index, rounded points363628

The coding results illustrate why the assignment matters. Ember scores higher than Claude Haiku 5.5 on Terminal-Bench, while Haiku scores higher on FrontierCode’s mergeability-focused engineering tasks. For a workflow producing patches for an existing codebase, readiness to merge is a directly relevant criterion.

The execution setup also varies. Meta says Terminal-Bench used each model’s best published harness—the software setup coordinating its actions—so each score reflects that model’s respective setup.

The rounded Intelligence Index tie prompted skepticism in an r/LocalLLaMA discussion, where a commenter questioned the scenario behind the comparison. Meta’s chart supplies more precise values: 35.8 for Ember and 36.2 for Claude Haiku 5.5, both rounded to 36 in its table.

Cost per benchmark task

At the high-scoring points shown in Meta’s Artificial Analysis chart, estimated task costs are $0.136 for Ember and $0.411 for Claude Haiku 5.5, with Ember costed at Meta’s proposed price. Dividing $0.411 by $0.136 gives approximately 3.02: Haiku’s estimated cost is about three times Ember’s for that benchmark workload and those settings.

That figure answers a different question from the token-price table. The API schedule prices each category of tokens; the benchmark estimate prices the tokens consumed while completing its particular tasks.

What early users reported about speed

The partner statements Meta published at launch add latency observations tied to specific early tests.

Cloudflare CTO Dane Knecht reported that Ember ran up to 30% faster at the slow end of its latency measurements against the comparison model Cloudflare tested. He also said it handled investigations spanning multiple repositories well.

You.com Inference Lead Chak Pothina reported that Ember completed every coding quest in You.com’s tests, with a p95 latency of 2.2 seconds. P95 is the 95th-percentile latency, a measure of the slower end of the response-time distribution. You.com described its results as roughly 4 to 13 times faster than the leading open-weight models it tested, with 36–48% fewer output tokens.

Public feedback also included a tentative coding report: one r/MuseAgent commenter said preliminary coding tasks worked well while longer-task testing was still underway.

For your own evaluation, separate task completion, output quality, latency and token consumption. The reported coding results and mergeability scores make each of those a useful criterion when deciding which steps to delegate.

The access routes Meta named at launch

At launch, Meta said Ember was available through Meta Model API, Muse Code, Google Cloud and Oracle Cloud. Its developer pages also list pay-as-you-go and subscription access through Muse Code.

On Meta Model API, Ember uses Standard mode; Contributor mode is unavailable. Meta says content submitted in Standard mode is not used to train its models.

Meta’s published limits for muse-ember-1.0 are 3,000 requests per minute and 4,000,000 tokens per minute per team. Size a multi-key worker pool against that shared team allowance.