chore(catalog): sync from gateway — 0 added, 2 corrected, 3 retired - #391
Merged
Merged
Conversation
Every added param and every corrected bound was verified end-to-end through the gateway.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
mainon 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/xai/grok-4.20-0309-non-reasoning.yamltop_p: declared min 0 refused (HTTP 400: top_p must be positive but top_p = 0); 0.01 accepted → min corrected to 0.01models/xai/grok-4.20-0309-reasoning.yamltop_p: declared min 0 refused (HTTP 400: top_p must be positive but top_p = 0); 0.01 accepted → min corrected to 0.01Needs a human: params now refused (20)
Re-verification found these declared params refused. Not removed — the param guard blocks removals and dropping a param is a maintainer's call.
models/alibaba/kimi-k3.yamltemperature: temperature=1.9 → HTTP 400: <400> InternalError.Algo.InvalidParameter: Parameter 'temperature'=1.9 is not supported for kimi-k3 model.models/alibaba/kimi-k3.yamltop_p: top_p=0 → HTTP 400: <400> InternalError.Algo.InvalidParameter: Parameter 'top_p'=0.0001 is not supported for kimi-k3 model.models/google/gemma-4-31b-it.yamlgenerationConfig.maxOutputTokensgenerationConfig.temperaturegenerationConfig.topPgenerationConfig.topKgenerationConfig.thinkingConfig.thinkingBudgetgenerationConfig.thinkingConfig.includeThoughtsgenerationConfig.responseMimeType: generationConfig.maxOutputTokens=1 → HTTP 400: Thinking budget is not supported for this model. (same error for each)models/google/gemma-4-31b-it.yamlgenerationConfig.thinkingConfig.thinkingLevel: generationConfig.thinkingConfig.thinkingLevel="minimal" → HTTP 400: You can only set only one of thinking budget and thinking level.models/mistral/glm-5-2.yamlresponse_format.type: response_format.type="json_schema" → HTTP 400: ThirdPartyException - {"error":{"message":"When response_format type is 'json_schema', the 'json_schema' field must be provided. (parameter=response_format)","tmodels/mistral/ministral-3b-2512.yamlresponse_format.type: response_format.type="json_schema" → HTTP 400: Schema response format type requires a json_schemamodels/mistral/ministral-8b-2512.yamlresponse_format.type: response_format.type="json_schema" → HTTP 400: Schema response format type requires a json_schemamodels/mistral/mistral-small-2603.yamlresponse_format.type: response_format.type="json_schema" → HTTP 400: Schema response format type requires a json_schemamodels/nvidia/laguna-xs-2.1.yamlseed: seed=18446744073709552000 → HTTP 400: invalid type: floating point1.8446744073709552e+19, expected i64models/openai/gpt-4.yamlreasoning_effort: reasoning_effort="low" → HTTP 400: Unrecognized request argument supplied: reasoning_effortmodels/openai/gpt-4.yamlresponse_format.type: response_format.type="json_schema" → HTTP 400: Missing required parameter: 'response_format.json_schema'.models/openai/gpt-4.yamltool_choice: tool_choice="auto" → HTTP 400: Invalid value for 'tool_choice': 'tool_choice' is only allowed when 'tools' are specified.models/xai/grok-4.20-0309-non-reasoning.yamlresponse_format.type: response_format.type="json_schema" → HTTP 422: Upstream provider rejected the requestmodels/xai/grok-4.20-0309-reasoning.yamlresponse_format.type: response_format.type="json_schema" → HTTP 422: Upstream provider rejected the requestMarked retired (3)
No longer listed by the provider's live
/modelsfor N consecutive daily runs.models/openai/gpt-5.3-codex-spark-subscription.yaml(missing n/a — not served runs)models/openai/gpt-5.4-mini-subscription.yaml(missing n/a — not served runs)models/openai/gpt-5.4-subscription.yaml(missing n/a — not served runs)