Private Models

OpenAI: GPT OSS 120B

Trusted Execution Environment
openai/gpt-oss-120bModel weights
CompareTry this model

gpt-oss-120b is an open-weight, 117B-parameter Mixture-of-Experts (MoE) language model from OpenAI designed for high-reasoning, agentic, and general-purpose production use cases. It activates 5.1B parameters per forward pass and is optimized to run on a single H100 GPU with native MXFP4 quantization. The model supports configurable reasoning depth, full chain-of-thought access, and native tool use, including function calling, browsing, and structured output generation.

Modalities
TexttoText
In / out price
$0.15 / $0.60per 1M
Context
131K
Released
Oct 3, 2025

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.

tinfoilCheckingCheckingChecking

Start building

Call this model from your application, or through your agents.

For applications

Point your OpenAI SDK at the Gateway. Chat, completions, and embeddings work unchanged.

1
Create a key
2
Set base URL
3
Verify receipt
Get API KeyDocumentation

For agents

Connect Claude Code, Codex, Pi, and more through Private AI Proxy. Traffic is protected while a verified session is active.

1
Install Proxy
2
Turn on Protected
3
Connect agents
Release notes
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: "openai/gpt-oss-120b",
  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":"openai/gpt-oss-120b","messages":[{"role":"user","content":"Hello"}],"provider":{"aci_verified":true}}'

    Output

    HTTP/2 200
x-receipt-id: rcpt-e0eefe63b3673e2a5984951f
...

{
  "model": "openai/gpt-oss-120b",
  ...
}
  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.