RedactCloud – LLM Proxy & Data Anonymization API

Quick Start

Replace your OpenAI base URL with RedactCloud's endpoint. Everything else stays the same.

// Before
$client = OpenAI::client($apiKey);
// After
$client = OpenAI::client($apiKey, 'https://api.redactcloud.com/v1');

Authentication

Include your API key in the Authorization header or the X-API-Key header.

Authorization: Bearer rc_your_api_key_here

Endpoints

POST /v1/chat/completions

Accepts the same request body as the OpenAI Chat Completions API. All string fields in messages are automatically redacted for PII/PHI before being forwarded to the upstream provider.

Example Request

curl -X POST https://api.redactcloud.com/v1/chat/completions \
  -H "Authorization: Bearer rc_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-4",
    "messages": [
      {"role": "user", "content": "My SSN is 123-45-6789"}
    ]
  }'

Example Response

The response is identical to what the upstream provider returns. The LLM never sees your sensitive data.

Supported Providers

OpenAI — gpt-4*, gpt-3.5-turbo*, o1*, o3*
Anthropic — claude-*
Cohere — command-*

Rate Limits

Rate limits depend on your plan. See Pricing for details. Exceeded limits return 429 Too Many Requests.

Redacted Entities

The following entity types are automatically detected and redacted:

Social Security Numbers (SSN)
Credit Card Numbers
Email Addresses
IP Addresses
JWT Tokens
AWS Access Keys
OpenAI API Keys
US Phone Numbers
US ZIP Codes

Compliance

RedactCloud is SOC 2 Type II certified and HIPAA compliant. We execute BAAs for covered entities. Read our security overview.

API Documentation