Available on Julius

Meta: Muse Wonder

Bring a task with several steps into Julius: reconcile your files, investigate exceptions, and explain the result.

Try Muse Wonder 1.0 on Julius

Explore a worked example

Available on Pro, Max, Ultra, and Business. Compare plans

Reviewed October 13, 2026 · Sources

Reconciliation table separating $750 outstanding, $400 overpaid, and $100 unmatched cash, with split-payment and duplicate checks. — Invoice reconciliationIllustrative output · Fictional dataView full size

Best suited to: Planning and checking work across multiple steps
Published context: 1,048,576 tokens
Native inputs: Text, images, audio, video, and PDFs
Released: October 12, 2026

Muse Wonder pricing

Compare the provider’s API rates with access through Julius.

Meta API

Input / 1M tokens: $4
Output / 1M tokens: $20

Standard API rates per million tokens; cached input is $0.20. Meta lists no long-context premium. Provider web search has a separate charge.

Check provider pricing

Use your Julius plan

Available on Pro, Max, Ultra, and Business. Credits cover the work performed with models and tools.

View Julius plans and credits

Prices in USD, reviewed October 13, 2026. API token charges are separate from Julius subscriptions and credits.

What is Muse Wonder?

Muse Wonder is Meta’s reasoning model for complex coding and long-running tasks. Its published API supports text, images, audio, video, and PDFs as input, with text output and a 1,048,576-token context window.

Meta describes Wonder as a model that can plan work, use tools, and recover from errors during a longer task. In Julius, try a bounded analysis with clear checkpoints, such as cleaning a file, checking the calculations, and writing up the findings.

Planning and recovery

Meta’s release emphasizes complex tasks involving tool use, planning, delegation, and recovery from errors.

Multimodal foundation

The provider API accepts several input formats. Julius’s integration and file tools determine which inputs you can use in the product.

Reconcile invoices without hiding payment exceptions

One invoice has split payments, one payment is duplicated, and one invoice is overpaid.

Worked example · Fictional sample data · Expected results calculated from the CSVs

1. Input
Invoices and payments
2. Check
Deduplicate, then match
3. Deliver
Balances and separate exceptions

Expected result

After removing one repeated payment, $750 remains outstanding. Report $400 in overpayments and $100 of unmatched cash separately. Invoice I03 is fully settled by its two payments.

Outstanding: $750
Unmatched cash: $100

Reconciliation exceptions · USD

Outstanding: $750
Overpaid: $400
Unmatched cash: $100

What the analysis needs to catch

A single net balance hides the unpaid invoice and the overpayment. Match payments first, then keep each exception visible.

Make this deliverable

An invoice-level reconciliation and a clearly separated exceptions list.

Continue with your own invoice and payment spreadsheets using Julius for Excel.

Try this example in Julius

The prompt includes the sample data. Review it in chat before sending. Results may vary; compare your answer with the calculations shown here.

View the sample output (PNG)View the workflow and chart (SVG)Download invoices.csv Download payments.csv Download all data and calculations

View the prompt and sample data

Reconcile these invoices and payments. Deduplicate exact payment records by payment_id and flag conflicting duplicates. Sum split payments by invoice. Report outstanding balances, overpayments, and payments with no matching invoice separately. Do not offset one customer’s overpayment against another customer’s unpaid invoice. Create an exception table and a short reconciliation report.

invoices.csv

invoice_id,customer,amount
I01,Acme,1000
I02,Acme,650
I03,Birch,1200
I04,Cedar,400
I05,Birch,750

payments.csv

payment_id,invoice_id,amount
P01,I01,1000
P02,I02,650
P03,I03,700
P04,I03,500
P04,I03,500
P05,I04,800
P06,I99,100

These expected results come from the downloadable Python calculations. This example illustrates a workflow; it is not a measured benchmark of Muse Wonder.

Using Muse Wonder in Julius

Start with your task

The try buttons carry Muse Wonder 1.0 into a new chat when your plan includes it. Example buttons also fill the composer with the sample data. Review the prompt, or replace it with your own files and question, before sending.

If the model is unavailable on your plan, Julius explains the access requirement. You can choose another option in the model menu.

Work through an analysis in code Analyze a spreadsheet Create a report

Know the boundaries

Do not assume all Meta API modalities, computer-use features, or multi-agent features are exposed in Julius. Julius currently configures text and image input for this model.
Muse Wonder Full is a separate Muse Code offering. The Julius menu provides Muse Wonder 1.0.

Model details and official research

Go to the original documentation for specifications, release details, and evaluation methods.

Muse Wonder release

Meta’s announcement and explanation of the Wonder and Wonder Full offerings.

Meta model specifications

Published input formats, model versions, and context limits.

Meta API pricing

Standard token pricing, cached input, and search charges.

Muse Wonder: frequently asked questions

Is Muse Wonder available on Julius?

Yes. It appears as Muse Wonder 1.0 in the model menu. Available on Pro, Max, Ultra, and Business plans.

How much does Muse Wonder cost?

Meta lists $4 per million input tokens and $20 per million output tokens. Standard API rates per million tokens; cached input is $0.20. Meta lists no long-context premium. Provider web search has a separate charge. Julius subscriptions and credits are separate.

Can I use Muse Wonder Full on Julius?

No. Julius offers Muse Wonder 1.0. Meta describes Muse Wonder Full as a separate model available through a Muse Code subscription.