Secure LLM Proxy

What is Secure LLM Proxy?

Secure LLM Proxy is an OpenAI-compatible proxy server that adds privacy controls, including PII scrubbing and audit logging, before forwarding requests to upstream LLM providers. It is designed for users who need a drop-in replacement for the OpenAI API with enhanced data protection.

How to use Secure LLM Proxy?

Set OPENAI_BASE_URL to https://nexus.exchange-secure.com/v1 and provide your API key. For MCP integration, configure the server with that URL and a Bearer token in your client’s settings. Use the chat_completion tool to send messages through the proxy.

Key features of Secure LLM Proxy

• PII scrubbing removes emails, phone numbers, SSNs, and credit card numbers.
• Audit logging records every request with a hash of the original content.
• OpenAI-compatible endpoint — just change OPENAI_BASE_URL.
• Model routing supports GPT-4o, Claude, Gemini, and Llama via a single endpoint.
• Rate limit pooling spreads load across multiple upstream keys.

Use cases of Secure LLM Proxy

• Send sensitive prompts to LLMs without exposing personal data.
• Maintain an auditable log of all LLM interactions in regulated environments.
• Route requests to multiple LLM providers from a single, privacy-preserving gateway.
• Load-balance across several API keys to avoid rate limits.

FAQ from Secure LLM Proxy

What PII does the proxy scrub?

It strips emails, phone numbers, social security numbers, and credit card numbers before forwarding the request.

Are my API keys stored by the proxy?

No, keys are never stored. They are used only to forward the request after PII scrubbing.

Where do audit logs live and what do they contain?

Every request is logged with a hash of the original content. The full content is not stored; only the hash is retained for audit purposes.

Which models does the proxy support?

It supports GPT-4o, Claude, Gemini, and Llama through a single endpoint. Model routing is handled automatically based on the model parameter.

How do I authenticate with the MCP server?

Include your API key as a Bearer token in the Authorization header when configuring the MCP server in your client.