Phala: Qwen3.6 35B-A3B Uncensored (Aggressive)
DeprecatedTEETrusted Execution Environmentphala/qwen3.6-35b-a3b-uncensoredUncensored "Aggressive" variant of Qwen3.6-35B-A3B from Alibaba's Qwen team. The fine-tune by HauhauCS removes refusal behaviors (0/465 refusals) without modifying datasets or core capabilities. The base architecture is a 35B-parameter Mixture-of-Experts model with 256 experts routing 8 per token (~3B active params), 40 layers, and a hybrid linear+full-softmax attention mechanism (3:1 ratio). Supports a native 262K context and is natively multimodal across text, images, and video. Served on Phala in TDX-attested H200 enclave with end-to-end ECDSA response signing; FP8 quantization by lamianlbe.
- Modalities
- TextImagetoText
- In / out price
- $0.30 / $1.50per 1M
- Context
- 131K
- Released
- May 23, 2026
Providers
RedPill routes this private model across verified providers with automatic fallbacks. Pricing is unified, so you pay the same price no matter which provider serves your request, while live metrics show first-token latency, speed, and uptime.
| Checking | Checking | Checking |
Gateway API
Call this model through RedPill's OpenAI-compatible API.
- Create an API key
- Set
REDPILL_API_KEY - Run the request
- Verify the response
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://tee.redpill.ai/v1",
apiKey: process.env.REDPILL_API_KEY,
});
const response = await client.chat.completions.create({
model: "phala/qwen3.6-35b-a3b-uncensored",
messages: [{ role: "user", content: "Say hello." }],
});Check privacy evidence
Follow the receipt from the gateway response to its verified session using four curl requests.
- 1Check the gateway
Fetch the current TEE evidence and check that the keyset has not expired.
curl -fsS "https://tee.redpill.ai/v1/aci/attestation" \ -H "Authorization: Bearer $REDPILL_API_KEY"Output
{ "api_version": "aci/1", "workload_keyset_digest": "sha256:4f3dc45e...", "attestation": { "workload_keyset": { "not_after": 1790498751, ... }, ... }, ... } - 2Send a private request
The response header contains the receipt ID, not the receipt itself.
curl -fsS -i "https://tee.redpill.ai/v1/chat/completions" \ -H "Authorization: Bearer $REDPILL_API_KEY" --json '{"model":"phala/qwen3.6-35b-a3b-uncensored","messages":[{"role":"user","content":"Hello"}],"provider":{"aci_verified":true}}'Output
HTTP/2 200 x-receipt-id: rcpt-e0eefe63b3673e2a5984951f ... { "model": "phala/qwen3.6-35b-a3b-uncensored", ... } - 3Inspect the receipt
Paste the x-receipt-id above and compare its keyset digest with step 1.
curl -fsS "https://tee.redpill.ai/v1/aci/receipts/REPLACE_WITH_RECEIPT_ID" \ -H "Authorization: Bearer $REDPILL_API_KEY"Output
{ "api_version": "aci/1", "receipt_id": "rcpt-e0eefe63b3673e2a5984951f", "workload_keyset_digest": "sha256:4f3dc45e...", "event_log": [ ..., { "type": "upstream.verified", "session_id": "63c5a08de14e5c5253e6fb29271151f40621beb83b552ccca65772772856053f", "result": "verified", "required": true }, { "type": "response.returned", "body_hash": "sha256:..." } ], ... } - 4Inspect the session
Copy session_id from the upstream.verified event above, then fetch that session.
curl -fsS "https://tee.redpill.ai/v1/aci/sessions/PASTE_SESSION_ID_FROM_RECEIPT" \ -H "Authorization: Bearer $REDPILL_API_KEY"Output
{ "api_version": "aci/1", "upstream_name": "...", "verifier_id": "...", "claims": { "tee_attested": { "status": "asserted", ... }, ... }, ... }