Verify a response

Using https://tee.redpill.ai forces confidential routing, but a base URL alone does not verify the TEE from your machine. A verified client checks the workload attestation before sending model traffic, binds TLS to a key in the attested keyset, and verifies the signed receipt for the exact request and response bytes.

Client	Verification
Private AI Proxy: Claude Code, Codex, DeepSeek Harness, Hermes, Pi, Oh My Pi, OpenCode, OpenClaw	Attestation and pinned channel before traffic; receipts audited after delivery
Node or Bun application	`connectAci()` from `@phala/aci-verifier`, below
Claude Code, Codex CLI, Pi, OpenCode, Cline, and other tools without the Proxy	None; they cannot inject the pinned transport through base-URL configuration

Agent tools, MCP servers, browser automation, and telemetry remain separate trust boundaries.

Node and Bun

npm install @phala/aci-verifier openai

Node 20.18+ and Bun 1.4+ share the same API; the /runtime export selects the pinned transport.

import OpenAI from "openai";
import { connectAci } from "@phala/aci-verifier/runtime";

const apiKey = process.env.REDPILL_AI_API_KEY;
if (!apiKey) throw new Error("REDPILL_AI_API_KEY is required");

const aci = await connectAci({
  baseURL: "https://tee.redpill.ai/v1",
  serving: { requireVerified: true, requireReceipt: true },
});

try {
  if (!aci.identity.transcript.verdict.verified) {
    throw new Error(aci.identity.transcript.verdict.line);
  }

  const client = new OpenAI({ apiKey, baseURL: aci.baseURL, fetch: aci.fetch });
  const response = await client.responses.create({
    model: "z-ai/glm-5.3",
    input: "Reply with exactly: verified",
  });

  const audit = await aci.verifyReceipt();
  if (!audit.transcript.verdict.verified) {
    throw new Error(audit.transcript.verdict.line);
  }
  console.log(response.output_text);
} finally {
  await aci.close();
}

connectAci() verifies the attestation before sending model traffic and pins TLS to a key in the attested workload keyset. Pass aci.fetch only to the client that uses this gateway; it records the exact request and response wire digests. verifyReceipt() fetches the matching signed receipt, verifies those digests, and verifies the cited upstream session. Audit a response before treating its serving path as verified.

Release policy

The SDK does not check whether the gateway runs a production or development dstack OS image. The deprecated requireProductionOs option is ignored. For OS-image assurance, verify the same quote, event log, and VM configuration with an independent dstack verifier and require is_valid: true. Without acceptedComposeHashes, the client verifies that the measured compose ran in a genuine TDX workload; it does not claim that RedPill reviewed that release.

Value	Meaning
`sha256(app_compose)`	Bound into RTMR3; suitable for a reviewed-release allowlist
`source_provenance.repo_url` and `repo_commit`	Workload-declared labels, useful for inspection but not a trust anchor

For reviewed-release enforcement, load accepted hashes from authenticated release metadata and pair compose appraisal with the independent OS verification above. Never copy a compose hash from the endpoint and trust it on first use.

const aci = await connectAci({
  baseURL: "https://tee.redpill.ai/v1",
  policy: {
    acceptedComposeHashes: ["<reviewed-compose-sha256>"],
  },
});

What a passing audit proves

the TDX quote binds the fresh challenge, workload keyset, and measured compose;
the model request used hostname-validated TLS bound to an attested SPKI;
the signed receipt binds the exact request and response bytes to that workload; and
a required confidential upstream was verified and its cited session is valid.

It does not prove that a release was reviewed unless an independently obtained compose allowlist was enforced.

Inspect the artifacts by hand

The curl and jq commands inspect artifacts; they do not verify hardware quotes, receipt signatures, or the actual TLS channel. Before sending sensitive data, use connectAci() above or Private AI Proxy, with the release policy your application requires. Get your API key from the dashboard. These examples use plain TLS and save the exact request and response bytes before formatting them with jq.

export REDPILL_AI_API_KEY=sk-rp-...
export BASE_URL=https://tee.redpill.ai

Fetch the attestation with your own nonce

Fetch the gateway’s attestation report before sending a request. Generate a fresh 64-character lowercase hex nonce:

NONCE=$(openssl rand -hex 32)
curl -fsS "$BASE_URL/v1/aci/attestation?nonce=$NONCE" \
  -H "Authorization: Bearer $REDPILL_AI_API_KEY" > attestation.json

Send a request and save the receipt id

Choose a current model from the catalog. The TEE-only endpoint requires verified, channel-bound serving.

cat > request.json <<'JSON'
{
  "model": "qwen/qwen3.8-27b",
  "messages": [{"role": "user", "content": "Reply with exactly one word: hello"}],
  "max_tokens": 12
}
JSON

curl -fsS -D headers.txt -o response.json "$BASE_URL/v1/chat/completions" \
  -H "Authorization: Bearer $REDPILL_AI_API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @request.json

jq '.choices[0].message.content' response.json
RECEIPT_ID=$(awk 'tolower($1) == "x-receipt-id:" {gsub("\r", "", $2); print $2}' headers.txt)
printf '%s\n' "$RECEIPT_ID"

Fetch the receipt

curl -fsS "$BASE_URL/v1/aci/receipts/$RECEIPT_ID" \
  -H "Authorization: Bearer $REDPILL_AI_API_KEY" > receipt.json
jq . receipt.json

See the receipt fields and transparency events for how to read it.

Follow the receipt to its session

Extract the successful upstream.verified event’s session_id, then fetch the full record:

if SID=$(jq -er '.event_log[] | select(.type == "upstream.verified" and .result == "verified") | .session_id' receipt.json); then
  curl -fsS "$BASE_URL/v1/aci/sessions/$SID" \
    -H "Authorization: Bearer $REDPILL_AI_API_KEY" > session.json
  jq '{upstream_name, channel_binding, evidence_digest: .evidence.digest, claims}' session.json
else
  echo "no verified upstream session" >&2
fi

Keep the full session.json for verification; the printed summary omits fields. See the session reference for field meanings and claims for how to appraise the evidence.

The verification checklist covers the checks a verifier must perform on these artifacts.

Get started

Use in agents

Build with the API

Features

How it works

Verify and control

Providers and trust

RedPill Chat

Node and Bun

Release policy

What a passing audit proves

Inspect the artifacts by hand

Attestation report

Receipts

Attested sessions

ACI verifier source

​Node and Bun

​Release policy

​What a passing audit proves

​Inspect the artifacts by hand

​Related

Attestation report

Receipts

Attested sessions

ACI verifier source

Node and Bun

Release policy

What a passing audit proves

Inspect the artifacts by hand

Related