Skip to content

feat: add nvidia/meta/muse-glimmer-30b - #347

Open
guillaumegay13 wants to merge 1 commit into
mainfrom
mp/add-nvidia-meta-muse-glimmer-30b
Open

feat: add nvidia/meta/muse-glimmer-30b#347
guillaumegay13 wants to merge 1 commit into
mainfrom
mp/add-nvidia-meta-muse-glimmer-30b

Conversation

@guillaumegay13

Copy link
Copy Markdown
Collaborator

✨ What changed

  • Adds meta/muse-glimmer-30b (nvidia) to the catalog, params cloned from nvidia/deepseek-v4-flash-0731.yaml.
  • Hosted serving: the model is developed by meta (OpenRouter: meta/muse-glimmer-30b); this entry documents nvidia's serving of it, probed against nvidia's endpoint.

💭 Why

The provider serves it but the catalog doesn't list it. Param surfaces differ per serving provider, so each host gets its own probed entry (models.dev-style).

📝 Notes

  • Liveness ✅ only: the model answers on its real endpoint; unverified params are listed in the evidence table below.
  • Draft PR, auto-proposed by the modelparams agent.
Param verification evidence
param check ok detail
(baseline) accepted 1-shot answers 200
temperature min=0
temperature max=1
temperature range policed temperature=2 accepted — declared max 1 may be too low or unenforced
top_p max=1
top_p range policed top_p=2 rejected
max_tokens min=1
max_tokens max=16384 too large for a non-streaming probe — upper bound from docs
max_tokens range policed vendor reports max 1048576, YAML says 16384
frequency_penalty min=-2
frequency_penalty max=2
frequency_penalty range policed frequency_penalty=4 rejected
presence_penalty min=-2
presence_penalty max=2
presence_penalty range policed presence_penalty=4 rejected
seed min=0
seed max=18446744073709552000 Failed to deserialize the JSON body into the target type: invalid type: floating point 1.8446744073709552e+19, expected i64 at line 1 column 125
seed range policed seed=36893488147419103000 rejected
stop declared type string has no probe — value carried from sibling/docs, not verified

@guillaumegay13 guillaumegay13 added the liveness-verified Model verified live on its endpoint; params sibling-cloned, not individually probed label Sep 2, 2026
@vercel

vercel Bot commented Sep 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
modelparams.dev Ready Ready Preview Sep 2, 2026 6:14pm UTC

Request Review

@github-actions github-actions Bot added the model Add a model that's missing label Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

liveness-verified Model verified live on its endpoint; params sibling-cloned, not individually probed model Add a model that's missing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant