Skip to content

Error "Invalid URL (POST /v1/chat/completions)" when using gpt-4o-mini with azure-ai-inference library #40757

Open
@nischays

Description

@nischays
  • Package Name: azure-ai-inference
  • Package Version: 1.0.0b9
  • Python Version: 3.11

Describe the bug
When attempting to use the gpt-4o-mini model (Deployment type: Standard) with ChatCompletionsClient, an error occurs:

Error: (None) Invalid URL (POST /v1/chat/completions)
Code: None
Message: Invalid URL (POST /v1/chat/completions)

To Reproduce
Steps to reproduce the behavior:

  1. Set the environment variables AZURE_INFERENCE_ENDPOINT and AZURE_INFERENCE_KEY correctly.
  2. Run the following code:
import os
from azure.ai.inference import ChatCompletionsClient
from azure.core.credentials import AzureKeyCredential
from azure.ai.inference.models import SystemMessage, UserMessage

try:
    client = ChatCompletionsClient(
        endpoint=os.getenv("AZURE_INFERENCE_ENDPOINT"),
        credential=AzureKeyCredential(os.getenv("AZURE_INFERENCE_KEY")),
    )

    response = client.complete(
        messages=[
            SystemMessage(content="You are a helpful assistant."),
            UserMessage(content="What is the capital of France?"),
        ],
        model="gpt-4o-mini",
    )

    print("azure-ai-inference response:", response.choices[0].message.content)

except Exception as e:
    print(f"Error: {e}")

Expected behavior
I expected the API call to succeed and return a chat completion response from the gpt-4o-mini model, similar to how it works with other models like gpt-4o.

Screenshots
N/A (Error is text-based and printed to console)

Additional context

  • I have verified that the endpoint and key are correct.
  • The same code structure works with other models.
  • The same model works when using the AzureOpenAI library

Metadata

Metadata

Assignees

Labels

AI Model InferenceIssues related to the client library for Azure AI Model Inference (\sdk\ai\azure-ai-inference)ClientThis issue points to a problem in the data-plane of the library.Service AttentionWorkflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions