VerifiedChat
Qwen3.5-Omni-Plus
by 0G Foundation
Alibaba Qwen3.5-Omni-Plus, the high-capability any-modality-in / text-out model of the Qwen3.5-Omni series, accepting text, image, audio and video input. 192K-token context and function calling.
OpenAITool CallingModalities
Context
197K
196,608 tokens
Max Output
—
Input
$1.0208
per 1M tokens
Output
$5.8333
per 1M tokens
Provider
2 endpoints across 2 providersAliyun
Verified
Input / 1M
$1.0208 ·4.51000G/M
Output / 1M
$5.8333 ·25.80000G/M
Aliyun
Verified
Input / 1M
$1.0208 ·4.51000G/M
Output / 1M
$5.8333 ·25.80000G/M
API
POSThttps://router-api.0g.ai/v1/chat/completions
curl "https://router-api.0g.ai/v1/chat/completions" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <YOUR_API_KEY>" \
-d '{
"model": "qwen3.5-omni-plus",
"messages": [
{"role": "user", "content": "Hello!"}
],
"stream": true
}'Additional Features
TEE Verification
Request on-chain signature verification with verify_tee. The response includes a tee_verified field in the trace.
{
"model": "qwen3.5-omni-plus",
"messages": [{"role": "user", "content": "Hello!"}],
"verify_tee": true
}Provider Routing
Control which provider handles your request using the X-0G-Provider-* request headers.
X-0G-Provider-Address pins a provider; X-0G-Provider-Identity pins which of its upstreams to route through — both values come from the address and provider_identity fields of GET /v1/providers. Together they address one specific upstream of one provider. Send neither and the router picks by price and health, exactly as before.
curl "https://router-api.0g.ai/v1/chat/completions" \
-H "Authorization: Bearer <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-H "X-0G-Provider-Address: <PROVIDER_ADDRESS>" \
-H "X-0G-Provider-Identity: <UPSTREAM>" \
-H "X-0G-Provider-Sort: latency" \
-H "X-0G-Provider-Allow-Fallbacks: true" \
-d '{
"model": "qwen3.5-omni-plus",
"messages": [{"role": "user", "content": "Hello!"}]
}'