Choose an account interface
Use one account interface on a given host, not both. Each keeps its own OAuth grant. MCP is the
preferred agent integration because it provides typed tools and keeps API key creation in the
browser; use the CLI when MCP is unavailable.
Connect
Add the account URL as a remote HTTP server. On first use the client opens your browser: sign in and approve access to your RedPill account. One OAuth grant covers every organization you can access; organization selection is an explicit tool argument, not another authorization. No API key, client secret, or app registration is needed.- Claude Code
- Codex
- OpenCode
/mcp in Claude Code to sign in.https://docs.redpill.ai/mcp is optional and does not require
sign-in.
Capabilities
Every call checks your current organization membership and the same permission the dashboard uses,
so an agent can do exactly what you can do there, and no more. Key listings show metadata and
limits only. Archiving a workspace revokes its keys.
Confirmations and secrets
A write returns a preview first. Clients that support MCP forms show a confirmation; other clients repeat the call withconfirm=true.
Creating an API key finishes in the browser. The agent receives a short-lived link; you open it
signed in as the same user, click Create, and see the secret once. The secret never passes
through MCP or the model. Clients without URL elicitation support create keys in the
dashboard instead.
Limits
- Payments, top-ups, auto-recharge, and subscriptions.
- Organization membership, identity, and administrator operations.
- Receipt verification. Verification has to run in the client that sent the request; see Verify a response.