Private Models

Z.ai: GLM 5.3 Flash

NewBetaTrusted Execution Environment
z-ai/glm-5.3-flashModel weights

GLM-5.3-Flash is Z.ai's natively multimodal 320B MoE model with 18B active parameters, designed for efficient coding, long-horizon agent tasks, visual understanding, and long-context inference. Served as a TEE deployment via Phala.

Modalities
TextImagetoText
In / out price
$0.15 / $0.50per 1MCache read $0.03 per 1M
Context
1M
Released
Aug 27, 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.

phalaCheckingCheckingChecking

Gateway API

Call this model through RedPill's OpenAI-compatible API.

  1. Create an API key
  2. Set REDPILL_API_KEY
  3. Run the request
  4. Verify the response
Working with agentsConnect RedPill to agent frameworks and runtimes.
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-flash",
  messages: [{ role: "user", content: "Say hello." }],
});

Check privacy evidence

Follow the receipt from the gateway response to its verified session using four curl requests.

  1. 1
    Check 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, ... }, ... },
      ...
    }
  2. 2
    Send 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":"z-ai/glm-5.3-flash","messages":[{"role":"user","content":"Hello"}],"provider":{"aci_verified":true}}'

    Output

    HTTP/2 200
    x-receipt-id: rcpt-e0eefe63b3673e2a5984951f
    ...
    
    {
      "model": "z-ai/glm-5.3-flash",
      ...
    }
  3. 3
    Inspect 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:..." }
      ],
      ...
    }
  4. 4
    Inspect 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", ... }, ... },
      ...
    }
Full cryptographic verification guide

Search

Search models and pages.