
Why it is different
Verifiable privacy
The gateway runs in a TEE and proves it with a hardware-backed
attestation report. It does not retain request or response
bodies.
Confidential models
Confidential models run on verified TEE providers, with the channel
bound before your prompt is forwarded.
Drop-in compatible
Point your OpenAI or Anthropic SDK at the base URL. Same request and response shapes you already
use.
Pick your path
Build with the API
For developers. Call confidential and standard models through one endpoint, with attestation and
signed receipts on every response.
Use the chat app
For people who want a private AI assistant. End-to-end encrypted chat with confidential models and
private document search.
Verify, don’t trust
You do not have to take the API’s word. After one request you can check, locally, that:- The gateway is a specific reviewed workload running in a genuine TEE. Attestation report →
- The response came from that workload, was not altered, and (for a confidential model) ran on a verified upstream enclave. Receipts →
Start building
Get an API key
Create a key in the dashboard and store it as an environment
variable. See Authentication.
Make your first call
Point an OpenAI client library at
https://api.redpill.ai/v1. See the
Quickstart.Verify the response
Fetch the attestation report and the receipt, then check the signatures and hashes.
Verify a response.