Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Muse Spark Open - Model - OpenSmartRoute
Modelv1.0.0
Muse Spark Open
Muse Spark Open is a coding-optimized open-weight model. Trained specifically for agentic coding workflows, it delivers higher first-attempt accuracy, reliable tool calling, and deep codebase…
Reference model card from the OpenRouter listing - model meta/muse-spark-open. Prices are per million tokens as listed; ratings and installs below are from this marketplace.
Muse Spark Open
Muse Spark Open is a coding-optimized open-weight model. Trained specifically for agentic coding workflows, it delivers higher first-attempt accuracy, reliable tool calling, and deep codebase understanding across the repos developers...
Facts
Vendor
Meta
Context window
1,048,576 tokens
Max output
943,718 tokens
Input price
$1.25 / 1M tokens
Output price
$4.25 / 1M tokens
Input
text, image, video, file, audio
Output
text
Tool calling
yes
Structured outputs
yes
Reasoning
yes
Open weights
meta-models/Muse-Spark-Open-816B-A42B
Endpoint: https://openrouter.ai/api/v1 (OpenAI-compatible), model meta/muse-spark-open
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - nothing else to configurecurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'# or pin it on the OpenAI-compatible endpoint: {"model": "model-meta-muse-spark-open", ...}
Installed into a catalogue, chosen by a router
Install Muse Spark Open and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
