Use Fireworks Responses endpoint for Kimi K3 - #29607
Open
fontanierh wants to merge 3 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
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.
Description
service_tier: "priority", disable provider storage, and adapt named forced tools to the tool-choice shape Fireworks accepts.Tests
service_tier: "priority": all 46 cases passed, including multi-turn following, forced tools, reasoning efforts, and structured output.store: false: Fireworks accepted the replayed reasoning item ID and tool result, then returned fresh reasoning and the expected final answer.Risk
The provider endpoint change is scoped to Kimi K3. Reasoning-ID detection now applies to any Responses provider that persists an
id, matching the Responses wire contract. The endpoint ID and pricing remain unchanged, so rollback is a normal code revert.Fireworks' Responses frontend parses
service_tier, but the current Responses reference does not document it and responses do not expose the selected tier. Confirm priority routing and billing with Fireworks before production rollout.Deploy Plan
Standard deploy after Fireworks confirms Responses routes and bills the priority tier.