Skip to content

chore(catalog): sync from gateway — 0 added, 2 corrected, 0 retired - #407

Merged
guillaumegay13 merged 1 commit into
mainfrom
bot/catalog-sync
Oct 10, 2026
Merged

guillaumegay13 merged 1 commit into
mainfrom
bot/catalog-sync

Conversation

@guillaumegay13

Copy link
Copy Markdown
Collaborator

Automated sync between the Manifest gateway and this catalog (modelparams-agent).

How entries are verified: the local gateway loads this branch's catalog; for every declared param and test value the agent configures it through the gateway's model-params API, sends a request through the proxy pinned to the model, and checks the gateway applied the value upstream and got a 200 from that model. Params that fail are removed from the entry before it is filed.

This PR is rebuilt from main on every run and merged automatically once CI is green.

Corrected (2)

Existing entries re-verified through the gateway (daily rotation). A declared bound was refused by the vendor and one step inside was accepted; or enum values were refused by the vendor and the corrected list (refused values removed, values the vendor lists as supported added) was served to the gateway on a draft catalog and every value passed.

  • models/google/gemini-3.1-pro-preview.yaml
    • generationConfig.thinkingConfig.thinkingLevel: values [minimal, low, medium, high] → [low, medium, high]; default minimal → low
    • vendor: "Thinking level MINIMAL is not supported for this model. Please retry with other thinking level."
    • proof through the gateway (draft catalog with the corrected entry): low ✅ medium ✅ high ✅
    • note: default minimal refused and the vendor names no default; set to low (nearest remaining value in the declared order) — a maintainer may prefer the vendor's documented default
    • other params re-verified on the corrected entry: generationConfig.maxOutputTokens generationConfig.temperature generationConfig.topP generationConfig.topK generationConfig.thinkingConfig.includeThoughts generationConfig.responseMimeType ✅
  • models/groq/gpt-oss-safeguard-20b.yaml
    • reasoning_format: values [hidden, raw, parsed] → [hidden, parsed]; default undefined (unchanged)
    • vendor: "reasoning_format=raw is not supported with this model"
    • proof through the gateway (draft catalog with the corrected entry): hidden ✅ parsed ✅
    • other params re-verified on the corrected entry: max_completion_tokens temperature top_p frequency_penalty presence_penalty reasoning_effort response_format.type ✅

Removing an enum value is not a parameter removal for guard:params (it compares param paths per model, not values), and the removed values are refused by the vendor anyway.

Needs a human: params now refused (11)

Re-verification found these declared params refused. Not removed — the param guard blocks removals and dropping a param is a maintainer's call.

  • models/anthropic/claude-opus-4-5-20251101.yaml top_p: top_p=1 → gateway did not apply it upstream (recorded undefined)
  • models/anthropic/claude-opus-4-5-20251101.yaml thinking.type thinking.budget_tokens thinking.display: thinking.type="enabled" → HTTP 400: max_tokens must be greater than thinking.budget_tokens. Please consult our documentation at https://platform.claude.com/docs/en/build-with-claude/extended-t (same error for each)
  • models/mistral/codestral-2508.yaml response_format.type: response_format.type="json_schema" → HTTP 400: Schema response format type requires a json_schema
  • models/mistral/ministral-14b-2512.yaml response_format.type: response_format.type="json_schema" → HTTP 400: Schema response format type requires a json_schema
  • models/mistral/ministral-14b-latest.yaml response_format.type: response_format.type="json_schema" → HTTP 400: Schema response format type requires a json_schema
  • models/mistral/mistral-medium-3.5.yaml response_format.type: response_format.type="json_schema" → HTTP 400: Schema response format type requires a json_schema
  • models/moonshot/kimi-k3.yaml response_format.type: response_format.type="json_schema" → HTTP 400: Invalid request: missing required parameter: 'response_format.json_schema'
  • models/moonshot/kimi-k3.yaml tool_choice: tool_choice="required" → HTTP 400: Invalid request: tool_choice 'required' requires at least one tool
  • models/xai/grok-4.20-multi-agent-0309.yaml text.format.type: text.format.type="json_schema" → HTTP 422: Failed to deserialize the JSON body into the target type: text.format: missing field schema

Every added param and every corrected bound was verified end-to-end through the gateway.
@vercel

vercel Bot commented Oct 10, 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 Oct 10, 2026 5:52am UTC

Request Review

@github-actions github-actions Bot added the model Add a model that's missing label Oct 10, 2026
@guillaumegay13
guillaumegay13 merged commit 960a68c into main Oct 10, 2026
13 checks passed
@guillaumegay13
guillaumegay13 deleted the bot/catalog-sync branch October 10, 2026 05:53

This branch was successfully deployed

1 active deployment
Preview — 44d59421 Deployed Oct 10, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

model Add a model that's missing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant