Repository navigation
docs(config): describe the current STRIX_API_TYPE default - #1602
Merged
Merged
Conversation
Since 99c0711 the API route follows the model's catalog entry, not LLM_API_BASE, so the doc saying a custom base URL defaults to chat completions was out of date.
Preview approval requiredThis pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit |
Contributor
 [Low impact] This documentation-only change appears safe to merge. SummaryUpdates
Reviews (1) · Last reviewed commit: "docs(config): describe the current STRIX..." · Reviewed by Greptile |
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.
The
STRIX_API_TYPEentry indocs/advanced/configuration.mdxsays a customLLM_API_BASEdefaults to chat completions. That stopped being true in 99c0711:resolve_api_typenow picks Responses whenever LiteLLM's catalog lists/v1/responsesfor the model, whatever the base URL is (seetest_resolve_api_type_follows_the_catalog_not_the_base_urlandtest_api_type_overrides_the_api_base_route).So someone pointing
openai/gpt-5.4at a chat completions only gateway reads the docs, expects chat completions, and gets Responses requests instead. This updates the entry to describe the current behavior and tells them when to setSTRIX_API_TYPE=chat_completions.Docs only, no code change.