# Meta introduces Muse Spark with a limited API preview > Meta’s Muse Spark launch brings a new multimodal reasoning model to its consumer products, while API access begins as a private preview. Canonical URL: https://www.devobs.io/news/news-meta-muse-spark-introduction/ By: Owen Park Published: 2026-09-06T11:58:54.632Z Updated: 2026-09-06T11:58:54.632Z Event date: 2026-04-08 Section: AI Meta introduced Muse Spark on April 8, the first model in a new family from Meta Superintelligence Labs. The [launch announcement](https://ai.meta.com/blog/introducing-muse-spark-msl/) describes multimodal reasoning, tool use and coordination between agents, with access through Meta’s consumer AI products. ## Product access and API access differ The announcement places Muse Spark on meta.ai and the Meta AI app. API availability begins with a private preview for selected users. Meta also describes a gradual rollout of a Contemplating mode that uses multiple agents in parallel. These availability details define the launch’s practical scope. The post is not an open-weight release or an announcement of unrestricted API availability. Meta also acknowledges areas needing further development, including longer-running agent tasks and coding. ## Test the deployment surface you can use Our analysis: an interactive demonstration is useful for exploring behavior, but it does not establish the characteristics of a production integration. Teams evaluating the model should record which interface, reasoning mode and version produced each result. For tool-using workloads, assess whether a complete task succeeds within a budget. More parallel activity can improve exploration while also increasing the number of intermediate outputs a system must reconcile. Measure completion quality, elapsed time and operational cost together when those controls become available. Keep external actions behind application-owned permissions and inspect the final artifacts independently of the model’s explanation. A persuasive account of completed work is not the same as a verified change in another system. The immediate engineering takeaway is to treat the consumer rollout and private API preview as separate evaluation opportunities. A dependency decision should follow evidence from the actual integration path, including its access conditions and supported operational controls. ## Source references -