Skip to content

Cheapest Qwen3.6 27B Inference Providers

Ranks providers by estimated cost using a 1,000-input/500-output token ratio, shown per 1 million total tokens.

Chutes currently ranks first at $0.866667 / 1M tokens via chutes/fp8.

Provider options:
9
Ranked:
9
Metric:
Estimated cost / 1M tokens

Cheapest endpoint ranking

Cheapest Qwen3.6 27B Inference Providers
RankProvider / routeEstimated cost / 1M tokensSpeed measurementsEndpoint details
#1Provider / route
Chuteschutes/fp8
Estimated cost / 1M tokens$0.866667 / 1M tokensSpeed measurements
500-token response
13.73 s
Response starts
1.53 s
Output speed
41.0 tok/s
Endpoint details
Input price
$0.3 / 1M tokens
Output price
$2 / 1M tokens
Uptime (30 min)
98.40%
Context
262.1K
#2Provider / route
io.netio-net/fp8
Estimated cost / 1M tokens$0.9801 / 1M tokensSpeed measurements
500-token response
15.26 s
Response starts
0.56 s
Output speed
34.0 tok/s
Endpoint details
Input price
$0.2822 / 1M tokens
Output price
$2.38 / 1M tokens
Uptime (30 min)
99.94%
Context
262.1K
#3Provider / route
Morphmorph
Estimated cost / 1M tokens$0.992667 / 1M tokensSpeed measurements
500-token response
15.19 s
Response starts
1.30 s
Output speed
36.0 tok/s
Endpoint details
Input price
$0.289 / 1M tokens
Output price
$2.4 / 1M tokens
Uptime (30 min)
97.32%
Context
131.1K
#4Provider / route
Phalaphala
Estimated cost / 1M tokens$1.113333 / 1M tokensSpeed measurements
500-token response
4.92 s
Response starts
0.57 s
Output speed
115.0 tok/s
Endpoint details
Input price
$0.32 / 1M tokens
Output price
$2.7 / 1M tokens
Uptime (30 min)
99.03%
Context
262.1K
#5Provider / routeEstimated cost / 1M tokens$1.2 / 1M tokensSpeed measurements
500-token response
9.16 s
Response starts
0.83 s
Output speed
60.0 tok/s
Endpoint details
Input price
$0.45 / 1M tokens
Output price
$2.7 / 1M tokens
Uptime (30 min)
99.84%
Context
262.1K
#6Provider / route
SiliconFlowsiliconflow/fp8
Estimated cost / 1M tokens$1.266667 / 1M tokensSpeed measurements
500-token response
13.14 s
Response starts
1.24 s
Output speed
42.0 tok/s
Endpoint details
Input price
$0.3 / 1M tokens
Output price
$3.2 / 1M tokens
Uptime (30 min)
99.88%
Context
262.1K
#7Provider / route
DeepInfradeepinfra/fp8
Estimated cost / 1M tokens$1.28 / 1M tokensSpeed measurements
500-token response
10.98 s
Response starts
0.34 s
Output speed
47.0 tok/s
Endpoint details
Input price
$0.32 / 1M tokens
Output price
$3.2 / 1M tokens
Uptime (30 min)
99.62%
Context
262.1K
#8Provider / route
Venicevenice/fp8
Estimated cost / 1M tokens$1.3 / 1M tokensSpeed measurements
500-token response
7.13 s
Response starts
0.46 s
Output speed
75.0 tok/s
Endpoint details
Input price
$0.325 / 1M tokens
Output price
$3.25 / 1M tokens
Uptime (30 min)
99.76%
Context
256K
#9Provider / route
Estimated cost / 1M tokens$1.6 / 1M tokensSpeed measurements
500-token response
62.74 s
Response starts
0.24 s
Output speed
8.0 tok/s
Endpoint details
Input price
$0.6 / 1M tokens
Output price
$3.6 / 1M tokens
Uptime (30 min)
100.00%
Context
262.1K

Endpoint data fetched .

Qwen3.6 27B endpoint guide

How to interpret the Cheapest Qwen3.6 27B Inference Providers

9 of 9 Qwen3.6 27B endpoints currently have the published data required for this ranking. Chutes leads at $0.866667 / 1M tokens via chutes/fp8. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.

How estimated token cost is ranked

The cheapest ranking uses a 1,000-input/500-output-token ratio and reports the blended result per 1 million total tokens. Because providers can price input and output differently, a workload with a different token ratio may produce a different order.

Compare Chutes with the next option

io.net currently ranks second at $0.9801 / 1M tokens. Compare that gap with input and output price, response-start time, output speed, 30-minute uptime, context length, and the exact route before deciding whether first place is meaningful for your workload.

Use the route, not only the provider name

Qwen3.6 27B has 9 published provider options, and performance data is matched to each exact OpenRouter routing tag. Different quantization, context, regional deployment, or provider configuration can change price and behavior even when the underlying model name is identical.