@@ -408,6 +408,12 @@ Local models can also be configured via OpenAI-compatible API. Here are two comm
408Crush supports custom provider configurations for both OpenAI-compatible and
408Crush supports custom provider configurations for both OpenAI-compatible and
409Anthropic-compatible APIs.
409Anthropic-compatible APIs.
412+> Note that we support two "types" for OpenAI. Make sure to choose the right one
413+> to ensure the best experience!
414+> * `openai` should be used when proxying or routing requests through OpenAI.
415+> * `openai-compat` should be used when using non-OpenAI providers that have OpenAI-compatible APIs.
411#### OpenAI-Compatible APIs
417#### OpenAI-Compatible APIs
413Here’s an example configuration for Deepseek, which uses an OpenAI-compatible
419Here’s an example configuration for Deepseek, which uses an OpenAI-compatible