Requesty
Sign in

identity

open weights
Meta logo

muse-glimmer-30bMeta

from /1M in$0.35fireworks ai
context131K131K out
providers21 region
endpoints21 region
endpoints
2
regions
1
api
chat
released
August 2026

capabilities 5/8

visionreasoningtoolscachingweb searchjson schemacomputer useimage gen

endpoints

2 / 1 region
Providers serving muse-glimmer-30b, with pricing and measured performance. Best value in each column is coloured.
#flags
1NVIDIAGlobal131Kfreefreefree-
2Fireworks AIGlobal131K$0.35$1.50$0.04zdr
provider price, no markupper 1M tokensblank where no qualifying sample

measured

through Sep 12

no measured traffic for this model yet. the endpoints table above carries provider pricing

benchmarks

artificial analysis

no published benchmark scores for this model

call it

model=
muse-glimmer-30b

requesty routes this id across every provider serving muse-glimmer-30b, picking on price and health and failing over automatically. the id stays valid when a provider changes underneath it

Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.

quickstart

openai compatible
main.py
from openai import OpenAI client = OpenAI(    api_key="YOUR_REQUESTY_API_KEY",    base_url="https://router.requesty.ai/v1",) response = client.chat.completions.create(    model="muse-glimmer-30b",    messages=[        {"role": "user", "content": "Explain quantum computing in one paragraph."},    ],) print(response.choices[0].message.content)

Change the base url, use your Requesty key, set the model to any id in the call pane. Existing OpenAI SDK code needs no other edit, and the same key reaches every other model in the catalog, so switching later is a one-parameter change. Browse all models

notes

reference

Muse Glimmer 30B is a dense causal language model distilled from Muse Spark and purpose-built for autonomous agentic work. It combines multi-step reasoning, reliable schema-based tool calling, and failure recovery with multimodal understanding via a ~1.8B ViT-G/14 perception encoder, supporting interleaved text and image input, a 131K+ context window, and selectable reasoning strength (low through xhigh). Trained on data from over 100 languages, Muse Glimmer performs strongly for its size class on agentic benchmarks including MCP Atlas, DeepSearch QA, Gaia2 and SWE-Bench Pro, and is released under Apache 2.0.

questions 6

Which providers serve muse-glimmer-30b?
muse-glimmer-30b is available from 2 providers through Requesty: NVIDIA, Fireworks AI. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.
How much does muse-glimmer-30b cost?
Pricing starts at free per million input tokens and free per million output tokens on the cheapest provider. Prices vary by provider and region; the table above shows every endpoint. Requesty charges exactly what the upstream provider charges, with no markup.
Is muse-glimmer-30b open weights?
Yes. muse-glimmer-30b is an open-weights model from Meta, which is why multiple inference providers can host it. Provider choice affects price, latency, and data-privacy terms, all compared above.
What is the context window of muse-glimmer-30b?
muse-glimmer-30b supports up to 131K tokens of context, with up to 131K output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.
How do I use muse-glimmer-30b with the OpenAI SDK?
Install the OpenAI SDK, set base_url to "https://router.requesty.ai/v1", set your API key to your Requesty key, and set the model to "muse-glimmer-30b" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.
Should I call muse-glimmer-30b by its managed id or a provider id?
Use the managed id, "muse-glimmer-30b". Requesty picks which of the 2 providers serves each request based on price and health, and fails over when one degrades, so the id keeps working while the routing changes underneath it. Send a provider id like "nvidia/muse-glimmer-30b" only when you need one specific deployment and want no failover.

more from meta 6

Other Meta models
modelcontextfrom /Mproviders
llama-4-maverick-17b-128e-instruct1.0M$0.201
llama-3.3-70b-instruct131K$0.133
llama-3.3-70b-instruct-turbo131K$0.081
llama-3.2-90b-vision-instruct131K$0.351
llama-3.1-8b-instruct16K$0.051
meta-llama-3.1-405b-instruct131K$0.801

route muse-glimmer-30b through one endpoint

One key for 2 providers on this model and 600+ others. No markup on provider prices, automatic failover, caching built in. Weekly aggregates in the measured pane come from production traffic routed through Requesty, one line per provider on a shared axis. Methodology

muse-glimmer-30b2 providers2 endpointsfrom $0.35 /1M inctx 131Kupdated Sep 12