Is Muse Spark 1.1 live in VUST?

Manual text chat is wired locally with exact identity and access checks. It remains qualified-pending until two authorized live calls return the exact served id with measured latency and cost.

Can VUST generate Muse images or videos?

No. Muse Image and Muse Video are separate products. VUST does not currently provide either route.

Will Auto Router choose Muse Spark 1.1?

Not while qualification is pending. Manual selection remains available; Auto excludes M16 before scoring.

VUST MUSE · CURRENT RUNTIME TRUTH

Muse Spark 1.1 in VUST: Meta’s agentic model in one AI chat

VUST currently exposes Muse Spark 1.1 as a manually selected text-Messages model in @vustbot. It does not yet expose Muse image generation, video generation, audio input, computer use, or a full agent harness.

Manual Pro/Max model · exact Balance option · Auto qualification pendingChecked 2026-07-23

Open VUST Muse in Telegram

Text Messages only in VUSTExact served-model idManual selection; Auto pending

Comparison basis

Official sources and verification date

Muse facts come from Meta's official releases and the current OpenRouter model card. VUST capability claims were checked against the runtime matrix and provider contract; no head-to-head quality benchmark is claimed.

Unless a separate method is stated above, this page does not claim a head-to-head product-quality benchmark.

Checked: 2026-07-23

Direct answer

The short answer

Choose VUST Muse — Muse Spark 1.1 when you want this exact model for a text task. VUST keeps that manual choice sticky for follow-ups, requires exact served-model identity, and shows access or the exact Balance quote before provider work. Auto Router will not select it until two authorized live checks both return the exact model id with measured latency and cost.

This is a bounded integration, not a claim that every capability described by Meta is available in VUST.

Muse products: what VUST actually supports

Product	Meta status	VUST today	VUST status
Muse Spark 1.1	Released model and public-preview API	Manual text Messages; text response	Qualified-pending
Muse Image	Separate image model available in Meta products	No generation or editing route	NOT-YET
Muse Video	Separate preview; coming later in Meta products	No video generation route	NOT-YET

Why the capability list is narrower in VUST

A model can support many inputs and tools at the provider layer while an application implements only one transport. VUST currently sends text Messages through OpenRouter and returns text. Image generation belongs to the separate Muse Image product; Muse Video is a separate preview. Until those routes, safety checks, delivery formats, billing, and runtime tests exist, they remain outside the VUST product.

How VUST evaluated the integration

1. Matched the runtime matrix to the exact OpenRouter slug meta/muse-spark-1.1.
2. Checked accepted request parameters and forced non-streaming text delivery with caller cancellation.
3. Fail closed on a substituted or dated served id for M16; no cross-model fallback is accepted.
4. Record provider latency and reported or catalog-estimated cost without exposing provider branding in the picker.
5. Keep live qualification pending until 2/2 authorized exact-id calls succeed; no paid probe was run for this page.

Copyable, citable summary

Citable summary (checked 2026-07-23): VUST offers Muse Spark 1.1 as a manual text-chat model through @vustbot. Exact model identity, access checks, prompt preservation, cost and latency telemetry are implemented locally; two live qualification calls are still pending. Muse Image and Muse Video are not available through VUST.

Run VUST Muse — Muse Spark 1.1