WebWorld-14B
WebWorld-14B
Version: 1
Hugging FaceLast updated May 2026
Qwen/WebWorld-14B powered by vLLM

Chat Completions API

Send Request

You can use cURL or any REST Client to send a request to the Azure ML endpoint with your Azure ML token.
curl <AZUREML_ENDPOINT_URL> \
    -X POST \
    -H "Authorization: Bearer <AZUREML_TOKEN>" \
    -H "Content-Type: application/json" \
    -d '{"model":"Qwen/WebWorld-14B","messages":[{"role":"user","content":"What is Deep Learning?"}]}'

Supported Parameters

The following are the only mandatory parameters to send in the HTTP POST request to v1/chat/completions.
  • model (string): Model ID used to generate the response, in this case since only a single model is deployed within the same endpoint you can either set it to Qwen/WebWorld-14B or leave it blank instead.
  • messages (array): A list of messages comprising the conversation so far. Depending on the model you use, different message types (modalities) are supported, like text, images, and audio.
The rest of the parameters are optional, and since this model is powered by vLLM with an OpenAI compatible interface on top for the Chat Completions API for text generation, then the I/O interfaces for both generation and streaming are the same as in OpenAI Chat Completions API. You can find the whole specification of the allowed parameters in the OpenAI Chat Completion API Specification , or alternatively in the endpoint /openapi.json for the current Azure ML Endpoint.

Example payload

{
  "model": "Qwen/WebWorld-14B",
  "messages": [
    {"role":"user","content":"What is Deep Learning?"}
  ],
  "max_completion_tokens": 256,
  "temperature": 0.6
}

Responses API

Alternatively, given that Qwen/WebWorld-14B is a reasoning model, note that the recommended API is the OpenAI Responses API over the default OpenAI Chat Completions API aforementioned.

Send Request

curl <AZUREML_ENDPOINT_URL>/v1/responses \
    -X POST \
    -d '{"model":"Qwen/WebWorld-14B","input":"What is Deep Learning?","reasoning":{"effort":"medium"}}' \
    -H "Authorization: Bearer <AZUREML_TOKEN>" \
    -H "Content-Type: application/json"

Supported Parameters

This being said, the following are the only mandatory parameters to send in the HTTP POST request to /v1/responses.
  • model (string): Model ID used to generate the response, in this case since only a single model is deployed within the same endpoint you can either set it to Qwen/WebWorld-14B or leave it blank instead.
  • input (str or array): A text, image, or file inputs to the model, or even a list of messages comprising the conversation so far, used to generate the response. Depending on the model you use, different message types (modalities) are supported, like text, images, and audio; whilst in this case only text generation is supported so image and audio inputs are disallowed.
The rest of the parameters are optional, and since this model is powered by vLLM with an OpenAI compatible interface, you can find the whole specification of the allowed parameters in the OpenAI Responses API Specification , or alternatively in the endpoint /openapi.json for the current Azure ML Endpoint.

Example Payload

{
  "model": "Qwen/WebWorld-14B",
  "input": "What is Deep Learning?",
  "max_output_tokens": 1024,
  "temperature": 0.6,
  "reasoning": {
    "effort": "medium"
  }
}

Hugging Face on Foundry

This model is sourced from Hugging Face, which offers thousands of open models for easy deployment on Microsoft Foundry. This model is a Non-Microsoft Product that has not been tested or evaluated by Microsoft. Customers should ensure that the model is appropriate for their specific use, including by evaluating any legal or export-control considerations and conducting their own model risk and safety evaluations. You can learn about Foundry risk and safety evaluations here . You can learn about Hugging Face security measures and requirements for models offered in Foundry here .
Model Specifications
LicenseApache-2.0
Last UpdatedMay 2026
ProviderHugging Face