All models

Qwen3.8 27B

Qwenqwen/qwen3.8-27b

Qwen's 27B multimodal reasoning model for long-context chat, visual understanding, tool use, and structured output.

1 provider online
Modality
Chat
Input
$0.05
per M tokens
Output
$0.35
per M tokens
Listed
Sep 2, 2026
Uptime
96.2%
last 3 days, measured

Playground

Run this model right here. Billed to your account credits per use through the same signed-receipt pipeline as the API.

Checking your session…

Pricing

Charged per use against a signed receipt. Current price version v55; versions are immutable, so the chart below is the platform's actual pricing record.

Input
$0.05
per M tokens
Output
$0.35
per M tokens
$0.30$0.35$0.40Sep 2Today

Trust & routing

Current trust properties and dispatch capacity advertised by the OpenMayhem network.

Registered tiers
T1
Live tiers
T1
Quantizations
nvfp4
Live routes
1
Live providers
1
Prompt processing
Provider-visible
Context capacity
262.1K
Concurrent requests
1

Routing providers

f326ef81…9b42

Activity

What actually ran on the platform, per day over the last 30 days. Settled usage from receipts; nothing synthetic.

5M10MAug 12Sep 10
Show as table
Dayinput tokensoutput tokensRequests
Sep 101,641,61226,96319
Sep 96,917,681347,945153
Sep 89,623,979166,094190
Sep 72,666,509106,880138
Sep 61,299,733437,6031,091
Sep 55,2753,48515
Sep 462,0099,88036
Sep 322,2004,44148
Sep 2965,64624
Sep 1000
Aug 31000
Aug 30000
Aug 29000
Aug 28000
Aug 27000
Aug 26000
Aug 25000
Aug 24000
Aug 23000
Aug 22000
Aug 21000
Aug 20000
Aug 19000
Aug 18000
Aug 17000
Aug 16000
Aug 15000
Aug 14000
Aug 13000
Aug 12000

Performance

Measured from real, settled requests over the last 30 days. No synthetic benchmarks.

Time to first token
635 ms
median · 1,374 streams
Request latency
17 s
median · p95 262 s · 1,445 requests
Throughput
17.2 tok/s
1445 requests
Success rate
88.9%
1,686 finished requests, 30 days

This week: 23.3M tokens across 1476 requests.

Availability

Provider availability polled every minute by the platform itself, replayed hour by hour.

96.2%online over the last 3 days

3 days ago online down no dataNow

Providers

Who actually served this model, attributed from signed receipts over the last 30 days.

ProviderRequestsShareTokensAvg latencyLast seen
f326ef81…9b421,517100%24.4M (100%)60 sSep 10

Supported parameters

From the network's signed model contract; anything else is rejected before a provider runs.

frequency_penaltyinputmax_completion_tokensmax_output_tokensmax_tokensmessagesmetadatamin_pmodelpresence_penaltypromptreasoning_effortresponse_formatseedstopstreamtemperaturetextthinking_historythinking_modetool_choicetoolstop_ktop_puser

Use it

OpenAI-compatible: point an existing SDK at api.openmayhem.ai and use this model ID.

curl https://api.openmayhem.ai/v1/chat/completions \
  -H "Authorization: Bearer $OPENMAYHEM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "qwen/qwen3.8-27b",
    "messages": [{"role": "user", "content": "Hello"}],
    "max_tokens": 2000
  }'

FAQ

What does Qwen3.8 27B cost on OpenMayhem?

Qwen3.8 27B currently costs $0.05 / M input · $0.35 / M output. There is no subscription: you buy credit and every request settles against a signed receipt for exactly what it used. Prices are versioned, and the full price history is published on this page.

Is Qwen3.8 27B available right now?

Yes. 1 provider serving Qwen3.8 27B right now, and it was online 96.2% of the last 3 days as measured by our own polling.

How do I use Qwen3.8 27B?

Send an OpenAI-compatible request to https://api.openmayhem.ai/v1/chat/completions with "model": "qwen/qwen3.8-27b" and your API key. Existing OpenAI SDKs work by changing the base URL. Create an account to get a key and starting credit.

Who serves Qwen3.8 27B?

Independent providers on the OpenMayhem network run the model on their own hardware. Over the last 30 days, 1 provider served it; the providers table on this page is attributed from signed receipts, not self-reporting.

Are my prompts stored?

OpenMayhem does not persist prompt or completion text. Requests are proxied to the serving provider and only billing metadata is retained: usage counts, the price applied, and the provider's signed receipt. The provider that serves a request necessarily processes its content.

More like this