RedPill
qwen logo

Qwen: Qwen3.6 35B A3B

GPU TEE
Chat
qwen/qwen3.6-35b-a3b
Created May 26, 2026|262K context|$0.20/M input tokens|$1.27/M output tokens
Intel TDXNVIDIA CC

Qwen3.6-35B-A3B is an open-weight model from Alibaba Cloud with 35 billion total parameters and 3 billion active parameters per token. It uses a hybrid sparse mixture-of-experts architecture combining Gated attention. Served as a text-only TEE deployment via NEAR AI.

Providers for Qwen: Qwen3.6 35B A3B

RedPill routes requests across these providers with automatic fallbacks to maximize uptime. Pricing is unified — you pay the same price no matter which provider serves your request.

Total Context
262K
Input
$0.20/M
Output
$1.27/M
ProviderTTFTThroughputUptime
phala logophala
near-ai logonear-ai

API

RedPill provides a unified completion API to all models & providers that you can call directly, or using the OpenAI SDK. Additionally, some third-party SDKs are available.

fetch("https://api.redpill.ai/v1/chat/completions", {
  method: "POST",
  headers: {
    "Authorization": "Bearer <YOUR-REDPILL-API-KEY>",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "model": "qwen/qwen3.6-35b-a3b",
    "messages": [
      {
        "role": "user",
        "content": "What is the meaning of life?"
      }
    ]
  })
})
Verify Evidence

Confidential GPU-TEE responses carry two proof layers you can check yourself: a nonce-bound attestation report for the gateway, and a signed receipt that binds your request and response to an attested upstream session.

# 1. Attest the gateway (nonce-bound, proves which TEE workload serves you)
NONCE="$(openssl rand -hex 16)"
curl -s "https://api.redpill.ai/v1/aci/attestation?nonce=$NONCE" \
  -H "Authorization: Bearer $REDPILL_API_KEY" -o report.json

# 2. Call the model and capture the x-receipt-id response header
curl -s "https://api.redpill.ai/v1/chat/completions" -D headers.txt \
  -H "Authorization: Bearer $REDPILL_API_KEY" -H "Content-Type: application/json" \
  -d '{"model":"qwen/qwen3.6-35b-a3b","messages":[{"role":"user","content":"Hello"}]}' -o response.json
RECEIPT_ID="$(grep -i ^x-receipt-id headers.txt | tr -d '\r' | awk '{print $2}')"

# 3. Fetch the signed receipt, then follow it to the attested session
curl -s "https://api.redpill.ai/v1/aci/receipts/$RECEIPT_ID" \
  -H "Authorization: Bearer $REDPILL_API_KEY" -o receipt.json
SESSION_ID="$(jq -r '.event_log[]|select(.type=="upstream.verified").session_id' receipt.json)"
curl -s "https://api.redpill.ai/v1/aci/sessions/$SESSION_ID" \
  -H "Authorization: Bearer $REDPILL_API_KEY"
Full verification walkthrough →
RedPill

The confidential AI cloud: verifiable inference with attestation reports, signed receipts, audit sessions, and E2EE paths.