Qwen3.6 Plus

qwen3.6-plus

Use the Qwen3.6 Plus API for chat, coding, and reasoning. Send conversation messages and include tool definitions on supported routes. Build developer assistants for code review, debugging, and implementation. Compare the available provider routes, request examples, and usage prices on OpenAny.

Published price: From $0.224 / 1M tokens
Billing unit: / 1M tokens
Context / Max output: 1000K / 64K
Listed routes: 1

Auto route · $0.224 / 1M tokens

Provider	Pricing	Latency	Uptime	Supply	Route
Live	Input $0.224 / 1M tokensSave 21% vs official Output $1.345Save 21% vs official · Cache $0.032	4343ms	—	Verified

Selected pricing · AlibabaUSD / 1M tokens

Tier	Input	Output	Cache read	Cache write
≤256K · 0–256000 token	$0.224Save 21% vs official	$1.345Save 21% vs official	$0.032	$0.224
256K-1M · 256000–1000000 token	$0.897Save 21% vs official	$5.379Save 21% vs official	$0.072	$0.897

Source: the selected provider route in OpenAny's public model catalog. A price update timestamp is not supplied.

messagesMessages in conversation order.

Other parameters (21)

enable_searchenable_thinkingmax_completion_tokensMaximum number of output tokens to generate.max_tokensparallel_tool_callspresence_penaltypreserve_thinkingrepetition_penaltyresponse_formatsearch_optionsseedstopstreamEnable streaming responses.stream_optionstemperaturethinking_budgettool_choicetool_streamtoolstop_ktop_p

Result preview

Alibaba · 4343ms

Response example. Run to see the actual response.

{
  "id": "chatcmpl-2496b84e-745a-9d66-a591-e4820dd7054a",
  "model": "qwen3.6-plus",
  "usage": {
    "total_tokens": 249,
    "prompt_tokens": 11,
    "completion_tokens": 238,
    "prompt_tokens_details": {
      "text_tokens": 11
    },
    "completion_tokens_details": {
      "text_tokens": 238,
      "reasoning_tokens": 224
    }
  },
  "object": "chat.completion",
  "choices": [
    {
      "index": 0,
      "message": {
        "role": "assistant",
        "content": "Hello! How can I assist you today?",
        "reasoning_content": "Here's a thinking process:\n\n1.  **Analyze User Input:**\n   - User said: \"hello\"\n   - This is a standard greeting.\n\n2.  **Identify Intent:**\n   - The user is initiating a conversation.\n   - No specific question or request is made yet.\n\n3.  **Determine Response Strategy:**\n   - Acknowledge the greeting warmly.\n   - Offer assistance.\n   - Keep it concise and open-ended to encourage the user to state their needs.\n\n4.  **Draft Response (Internal Refinement):**\n   - \"Hello! How can I assist you today?\"\n   - \"Hi there! What can I help you with?\"\n   - \"Hello! I'm here to help. What's on your mind?\"\n\n5.  **Select Best Response:**\n   - \"Hello! How can I assist you today?\" is clear, polite, and standard.\n\n6.  **Final Output Generation:** (matches the selected response)\n   - \"Hello! How can I assist you today?\"✅"
      },
      "logprobs": null,
      "finish_reason": "stop"
    }
  ],
  "created": 1784603764,
  "openmodels_cost": 424,
  "system_fingerprint": null
}

Request example

POST /v1/chat/completions

curl 'https://api.openany.si/v1/chat/completions' \
  -H "Authorization: Bearer $OPENANY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "messages": [
    {
      "content": "hello",
      "role": "user"
    }
  ],
  "model": "qwen3.6-plus"
}'

Model API questions

How do I call Qwen3.6 Plus through OpenAny?

Use model ID qwen3.6-plus with an OpenAny key and the operation published in this model's API tab. The model API base is https://api.openany.si/v1. Confirm the protocol and request schema; model availability does not imply every OpenAI API operation is supported.

How is Qwen3.6 Plus billed?

Compare the published rate and billing unit of the selected provider route. Input, output and cache token rates may differ. Image, audio and video models can use other units. Recorded usage determines the charge under that route's billing contract.

Are Community and Verified routes the same as an official publisher API?

No. Inspect the provider name and supply classification for the specific route. A marketplace listing or a supply label is not a claim of publisher endorsement, identical service or measured uptime. Different route prices may reflect different supply and conditions.

Where do these prices come from, and when were they updated?

Rates come from the provider routes in OpenAny's public model catalog, not an independent quote from the model publisher. The catalog does not supply a price update timestamp. A page or catalog snapshot date is not a price revision date. Compare supply, billing units, tiers and conditions; a lower listed rate alone does not establish equivalent service or explain the price difference.

Use Qwen3.6 Plus with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.