Repository navigation
chore: add model to catalog - #1716
Erin McNulty (erin2722) merged 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 701a138077
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "Codex (@codex) address that feedback".
| "input_cost_per_mil_tokens": 2, | ||
| "output_cost_per_mil_tokens": 10, | ||
| "input_cache_read_cost_per_mil_tokens": 0.2, | ||
| "displayName": "Kimi K3.1 Pro", |
There was a problem hiding this comment.
Mark the Fireworks Kimi entry as reasoning-capable
When clients inspect the exact accounts/fireworks/models/kimi-k3p1-pro catalog entry, the omitted reasoning field reports no reasoning support. Every listed fallback for this same underlying Kimi K3.1 Pro model, as well as the existing Baseten entry, sets reasoning: true, so capability-driven clients may hide or disable reasoning features specifically when the Fireworks ID is selected; add the same capability flag here.
Useful? React with 👍 / 👎.
Automated targeted model-catalog addition from the model-drop workflow.