# RedPill AI

- [Introduction](https://docs.redpill.ai/get-started/introduction.md): A confidential AI inference API you can verify. Every response is served from a TEE and backed by an attestation report and a signed receipt.
- [Quickstart](https://docs.redpill.ai/get-started/quickstart.md): Make your first API call, then confirm it was served from an attested gateway.
- [Models](https://docs.redpill.ai/get-started/models.md): Browse the model catalog, and tell confidential models from standard ones.
- [Authentication](https://docs.redpill.ai/get-started/authentication.md): Create an API key and send it as a bearer token.
- [How Confidential AI Works](https://docs.redpill.ai/confidential-ai/how-it-works.md): The platform serves an API from a TEE-attested gateway and proves each response with an attestation report and a signed receipt.
- [Attestation Report](https://docs.redpill.ai/confidential-ai/attestation-report.md): The gateway attestation report proves which TEE workload served your request and publishes the keys it signs with.
- [Receipts](https://docs.redpill.ai/confidential-ai/receipts.md): A signed receipt is a per-response transparency log that binds your request and response hashes to the attested gateway.
- [Attested Sessions](https://docs.redpill.ai/confidential-ai/attested-sessions.md): An attested session is the verified security context behind a confidential response: one immutable record per verified TEE channel, with typed claims and an enforceable binding.
- [Channel Binding and Fail-Closed Forwarding](https://docs.redpill.ai/confidential-ai/channel-binding.md): Before forwarding a prompt to a confidential provider, the gateway binds the connection to the verified enclave and refuses to send if it cannot.
- [End-to-End Encryption (E2EE)](https://docs.redpill.ai/confidential-ai/e2e-encryption.md): Field-level encryption between your client and the attested gateway, on top of TLS.
- [Trust Boundary](https://docs.redpill.ai/confidential-ai/trust-boundary.md): What the attested gateway protects, what it does not, and where your plaintext is visible.
- [Confidential Providers](https://docs.redpill.ai/confidential-ai/providers.md): The verified upstream providers behind the platform's confidential models, the binding each enforces, and what each attests.
- [Confidential Models](https://docs.redpill.ai/confidential-ai/confidential-models.md): Confidential responses are served by a verified upstream TEE provider. Confirm a confidential response from its receipt.
- [Reading TCB and Claims](https://docs.redpill.ai/confidential-ai/tcb-and-claims.md): How to interpret typed claims on a verified upstream: status, source, and reason, including TCB freshness.
- [Open Source](https://docs.redpill.ai/confidential-ai/open-source.md): Review the open-source gateway and bind an approved deployment to its measured compose hash.
- [Compliance](https://docs.redpill.ai/confidential-ai/compliance.md): How the confidential computing architecture supports common compliance requirements, and how to request reports.
- [Confidential AI FAQ](https://docs.redpill.ai/confidential-ai/faqs.md): Common questions about the platform's attestation, receipts, confidential models, and trust boundary.
- [Streaming Responses](https://docs.redpill.ai/guides/streaming.md): Real-time streaming for chat completions
- [Function Calling](https://docs.redpill.ai/guides/function-calling.md): Enable AI models to call external functions and APIs
- [Vision Models](https://docs.redpill.ai/guides/vision.md): Using image understanding with multimodal models
- [Error Handling](https://docs.redpill.ai/guides/error-handling.md): Understand the API error format and handle errors gracefully.
- [Attested Routing](https://docs.redpill.ai/guides/attested-routing.md): Restrict a request to an upstream the gateway verified inside the TEE, and pin it to a specific attested channel.
- [TEE-only Endpoint](https://docs.redpill.ai/guides/tee-endpoint.md): Point your base URL at tee.redpill.ai to serve confidential models only, on attested providers, with no per-request configuration.
- [Zero Data Retention](https://docs.redpill.ai/guides/zero-data-retention.md): Restrict a request to providers that do not retain prompt or completion content, and list the models that support it.
- [End-to-End Encryption](https://docs.redpill.ai/guides/e2ee-encryption.md): Add field-level encryption to requests, on top of TLS, using a key from the attested keyset.
- [Verified ACI Clients](https://docs.redpill.ai/guides/verified-aci-client.md): Verify the TEE workload, pinned TLS channel, and response receipt from native clients.
- [Verify a Response](https://docs.redpill.ai/guides/verify-a-response.md): Verify the gateway workload, pinned TLS channel, signed response receipt, and cited upstream session.
- [Migrate from OpenAI](https://docs.redpill.ai/guides/migration-from-openai.md): Switch from OpenAI in minutes and keep your SDK and code.
- [Migrate from OpenRouter](https://docs.redpill.ai/guides/migration-from-openrouter.md): Switch from OpenRouter for verifiable, TEE-served inference.
- [Integrations](https://docs.redpill.ai/guides/integrations/overview.md): Choose a RedPill integration by what you want to build or run.
- [Coding Agents](https://docs.redpill.ai/guides/integrations/coding-agents.md): Choose a RedPill coding-agent integration and understand its verification boundary.
- [Pi](https://docs.redpill.ai/guides/integrations/coding-tools/pi.md): Install RedPill as a native Pi provider with automatic ACI verification.
- [Claude Code](https://docs.redpill.ai/guides/integrations/coding-tools/claude-code.md): Connect Claude Code to RedPill's Anthropic-compatible Messages API
- [Codex CLI](https://docs.redpill.ai/guides/integrations/coding-tools/codex-cli.md): Add RedPill as a custom Responses provider in Codex CLI
- [OpenCode](https://docs.redpill.ai/guides/integrations/coding-tools/opencode.md): Install RedPill as a native OpenCode provider with automatic ACI verification.
- [Cline](https://docs.redpill.ai/guides/integrations/coding-tools/cline.md): Connect Cline to RedPill through its OpenAI-compatible provider
- [OpenClaw](https://docs.redpill.ai/guides/integrations/runtimes/openclaw.md): Use RedPill as the main model provider for OpenClaw
- [Hermes](https://docs.redpill.ai/guides/integrations/runtimes/hermes.md): Use RedPill as a named custom provider in Hermes Agent
- [Cherry Studio](https://docs.redpill.ai/guides/integrations/cherry-studio.md): Chat with RedPill models in the Cherry Studio desktop app
- [OpenAI SDK](https://docs.redpill.ai/guides/integrations/openai-sdk.md): Use RedPill through the OpenAI SDK, with optional local ACI verification on Node and Bun.
- [Anthropic SDK](https://docs.redpill.ai/guides/integrations/anthropic-sdk.md): Use the official Anthropic Python or TypeScript SDK with RedPill's Messages API
- [Vercel AI SDK](https://docs.redpill.ai/guides/integrations/vercel-ai-sdk.md): Generate and stream RedPill responses in TypeScript applications.
- [LangChain](https://docs.redpill.ai/guides/integrations/langchain.md): Use RedPill for LangChain chat, streaming, retrieval, and agents.
- [CrewAI](https://docs.redpill.ai/guides/integrations/frameworks/crewai.md): Run a CrewAI task with a RedPill-backed LLM
- [PydanticAI](https://docs.redpill.ai/guides/integrations/frameworks/pydanticai.md): Build a typed PydanticAI agent with RedPill
- [OpenAI Agents SDK](https://docs.redpill.ai/guides/integrations/frameworks/openai-agents-sdk.md): Use RedPill with the OpenAI Agents SDK
- [Langfuse](https://docs.redpill.ai/guides/integrations/langfuse.md): Trace RedPill API calls with Langfuse and an explicit data boundary
- [API Overview](https://docs.redpill.ai/api-reference/overview.md): Base URL, authentication, and the full list of API endpoints.
- [Chat Completions](https://docs.redpill.ai/api-reference/chat-completions.md): Create chat completion responses.
- [Responses](https://docs.redpill.ai/api-reference/responses.md): Create a model response using the Responses API format.
- [Messages](https://docs.redpill.ai/api-reference/messages.md): Create a message using the Anthropic Messages format.
- [Embeddings](https://docs.redpill.ai/api-reference/embeddings.md): Create text embeddings.
- [List Models](https://docs.redpill.ai/api-reference/models.md): List available models with providers, context windows, and pricing.
- [Get Attestation Report](https://docs.redpill.ai/api-reference/attestation.md): The gateway TEE attestation report, bound to a caller-supplied nonce.
- [Get Receipt](https://docs.redpill.ai/api-reference/receipts.md): The signed receipt for a response, with the full transparency event log.
- [Get Session](https://docs.redpill.ai/api-reference/sessions.md): The immutable attested-session record behind a confidential response.
- [Completions](https://docs.redpill.ai/api-reference/completions.md): Create a text completion (legacy).
- [Signature](https://docs.redpill.ai/api-reference/signature.md): The legacy receipt wrapper for a response.
- [Attestation Report](https://docs.redpill.ai/api-reference/attestation-report.md): The legacy gateway attestation report.
- [Overview](https://docs.redpill.ai/chat/overview.md): A private AI assistant: end-to-end encrypted, running in hardware-protected enclaves.
- [Getting Started](https://docs.redpill.ai/chat/getting-started.md): Create your account and send your first private message in under 2 minutes
- [Private Knowledge](https://docs.redpill.ai/chat/private-rag.md): Your private AI research assistant - upload sources, generate insights, all within TEE

## OpenAPI Specs

- [openapi](/openapi.yaml)

## Optional

- [Community](https://discord.gg/P2ukR4Z5ps)
- [GitHub](https://github.com/redpill-ai)