Private Models





Working with agentsConnect RedPill to agent frameworks and runtimes.Full verification walkthrough
Z.ai: GLM 5.3
NewTEETrusted Execution Environmentz-ai/glm-5.3Model weightsGLM-5.3 is a large-scale reasoning model from Z.ai, built for complex software engineering and long-horizon agent tasks. It supports text input and output with a 1M-token context window. Served as a text-only TEE deployment via Phala.
- Modalities
- TexttoText
- In / out price
- $1.40 / $4.40per 1MCache read $0.26 per 1M
- Context
- 1M
- Released
- Aug 31, 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: "z-ai/glm-5.3",
messages: [{ role: "user", content: "Say hello." }],
});Verify Privacy Evidence
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. Verify the gateway (nonce-bound, proves which protected workload serves you)
NONCE="$(openssl rand -hex 16)"
curl -s "https://api.redpill.ai/v1/attestation/report?nonce=$NONCE" \
-H "Authorization: Bearer $REDPILL_API_KEY" -o report.json
# 2. Call the model and capture the x-receipt-id response header
cat > request.json <<'JSON'
{"model":"z-ai/glm-5.3","messages":[{"role":"user","content":"Hello"}],"provider":{"aci_verified":true}}
JSON
curl -s "https://api.redpill.ai/v1/chat/completions" -D headers.txt \
-H "Authorization: Bearer $REDPILL_API_KEY" -H "Content-Type: application/json" \
--data-binary @request.json -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"