Skip to main content
Start with the job you want to do. Most integrations need a RedPill API key, the correct protocol base URL, and an exact model ID from the live catalog.

​
Choose your path

Pi

Native provider with automatic ACI verification.

OpenCode

Native plugin with /connect, /models, and automatic ACI verification.

Other coding agents

Configure Claude Code, Codex CLI, or Cline through their official provider paths.

Run a long-lived agent

Use RedPill as the main model provider for OpenClaw or Hermes.

Build an agent workflow

Use LangChain, CrewAI, PydanticAI, or the OpenAI Agents SDK.

Build a web app

Stream model output in a TypeScript or React application.

Use a desktop app

Chat with RedPill models in Cherry Studio.

Migrate an app

Switch an OpenAI or OpenRouter integration to RedPill.

​
Choose the protocol

Most SDKs accept https://api.redpill.ai/v1 as their base URL. Claude Code expects ANTHROPIC_BASE_URL=https://api.redpill.ai because it appends /v1/messages.

​
Connect a client

1

Set the key

2

Choose a live model

3

Set the base URL

Use the URL required by the client’s protocol. Follow its guide when it expects a host instead of a /v1 base URL.
4

Run a small request

Test authentication, the model ID, and required capabilities before unattended use.

​
Verification boundary

Pi and OpenCode use native providers that verify ACI automatically. Generic SDK and coding-agent configurations are API-compatible only: a base URL cannot inject attested TLS or local receipt verification. Node and Bun applications with a custom fetch hook can use the verified runtime. https://api.redpill.ai serves standard and confidential models. Use https://tee.redpill.ai only when every request must use an is_tee: true model and reject standard upstreams.