Models & capabilities, read from an operations desk

Latest

Meta AI releases Muse Ember, a small model for agent tasks

Meta AI released Muse Ember, its smallest and most efficient model, aimed at repetitive agent work such as tool calls, routing, extraction and long document parsing. Under 200k tokens it costs $0.10 per million input and $0.50 output, the same as GPT-6 Luna and Claude Haiku 5.5 at short length.

What changes for operators — If your support or ops team already runs high-volume steps like ticket routing, field extraction from contracts or invoices, or tool calls inside an agent, Ember is a new price point to test. Take a sample of real tasks, run them on Ember and on your current small model, and compare cost per finished task as well as price per token. Check how long your prompts are: the price rises sharply past 200k tokens, so long-document jobs cost more than the headline rate. Cached input is the cheapest line on the price sheet, so workflows that resend the same instructions or reference documents benefit most.

Meta ships Muse Wonder, with six reasoning levels

If any workflow of yours calls a Meta model, such as lead qualification, ticket triage or drafting replies, treat Muse Wonder as a candidate to test, not a switch to flip. Run your own sample of real tickets or CRM records through it at a low and a high reasoning level and compare the quality of the output. Then compare the cost and the wait for each answer, because the source gives no pricing. The release pace matters more than any single model. With a new Meta model arriving roughly monthly, keep the model name and reasoning level in one config setting, and keep a fixed test set so that re-checking takes an afternoon rather than a project.

TypeSafe AI's Jev Turns Classification Into a Cheap API Call

For a B2B team running lead scoring, support ticket triage, spam filtering or search relevance ranking, Jev's format maps directly onto those workflows: feed it a customer record or ticket text plus a set of yes/no or scored questions, and get back structured confidence numbers cheaply enough to run on every record rather than a sampled subset. The catch is that Jev gives no explanation for its scores, so anything touching hiring, credit, or other high-stakes decisions needs structured evals before deployment, and even lower-stakes uses like ticket prioritization should be spot-checked for skewed outputs.