---
name: redpill
description: Use RedPill's authenticated account MCP and public documentation MCP to inspect or manage RedPill accounts, models, API keys, workspaces, billing, and usage. Use when a user asks about RedPill or wants an agent to operate their RedPill account.
metadata:
  author: redpill-ai
  version: "1.0"
---

# RedPill

Use `https://docs.redpill.ai/mcp` for public product and API documentation. Use `https://service.redpill.ai/mcp` for the authenticated user's account.

This skill requires network access and an MCP client with OAuth support. API key creation also requires URL elicitation.

## Account workflow

- Let the MCP client complete Clerk OAuth. Do not request or invent a separate MCP key.
- Read account state before choosing organization- or workspace-scoped arguments.
- Run read-only tools directly when they answer the request.
- Explain the concrete effect of a write and obtain the user's confirmation before completing it.
- For API key creation, complete the RedPill browser handoff while signed in as the same Clerk user. The secret must stay in that browser and must never be requested, repeated, logged, or placed in model context.
- Do not initiate payment, checkout, subscription, auto-recharge, identity, membership, deployment, provider-cloud, or administrator operations through account MCP tools.

## Verification

Do not claim that an MCP receipt lookup proves confidential inference. ACI verification must run in the native client that observed the exact request bytes, response or stream bytes, and pinned transport.