Align request path with openai sdk

[wxpjimmy]

In our scenario, we want to support customer consuming Mistral endpoint with both Mistral AI sdk and OpenAI sdk, but when testing we found that there's a difference between these two clients.

In OpenAI sdk, if customer provides their own base_url, OpenAI sdk won't make any change to that url and there will be no default "v1" prefix added; only when customer doesn't provide base_url, OpenAI sdk will set the url to a default value "https://api.openai.com/v1", this is the code link: https://github.com/openai/openai-python/blob/main/src/openai/_client.py

While in Mistral AI sdk, it will by default add a "v1" prefix for API calls.

To support Mistral AI sdk, the server had to provide the API with "v1” prefix, this also means that customer needs to use different base_url for these 2 sdk:

• OpenAI: https://<domain>/v1
• MistralAI: https://<domain>

Of course, to mitigate this impact, we can do some trick in the server side to support both "v1/<api_path>" and "<api_path>", this will be an extra effort for any org who has the same scenario as us.

We'd like to know whether this is by design and whether it's possible to follow the openai sdk way to remove the default "v1" prefix in the request path?

[wxpjimmy]

@Bam4d any comments for this?

[wxpjimmy]

ping for this......