Multi-provider routing
OpenAI, Anthropic and other providers behind one endpoint.
Product
Provider-agnostic. BYOK by default. Sensitive data masked before any provider call.
One endpoint in front of OpenAI, Anthropic and other providers — with PII masking and rehydration applied at the edge so the model never sees personal or secret values.
Definition
An LLM gateway is a routing layer that accepts AI requests from your application and forwards them to one or more model providers. It is where authentication, model selection, rate limits and observability live. In Privian's case, it is also where PII masking and prompt privacy run before any provider call. See the glossary entry for a longer definition, or the AI Security Layer category page for how it fits into the broader stack.
Why it matters
A pure routing gateway changes nothing about what the provider sees. Customer emails, internal documents, support transcripts and developer scratch prompts all reach the model verbatim. A privacy-first gateway shrinks that exposure surface at the edge.
How it works
Step 1
Your app POSTs prompt + model to a single Privian endpoint with a gateway API key.
Step 2
Inbound prompt is scanned for personal and sensitive entities.
Step 3
Detected values are replaced with deterministic placeholders (PERSON_1, EMAIL_2, ...) for the request.
Step 4
Masked prompt is forwarded to the configured provider using your decrypted BYOK credentials.
Step 5
The provider response is scanned and placeholders are restored from the in-memory mapping.
Step 6
Your app receives a normal, rehydrated response. The mapping is discarded.
Technical
Models are addressed as provider/id, e.g. openai/gpt-5.5 or anthropic/claude-sonnet-4.5. The full list lives in the models catalog.
Provider keys are stored AES-GCM encrypted at rest. They are decrypted in-process only while routing a request.
One endpoint, three fields: prompt, model, optional stream. No SDK lock-in.
Raw prompts and responses are never persisted. Only structural counters are kept for observability.
Example
The beta exposes a single gateway endpoint with a small JSON body.
curl https://api.privian.io/v1/gateway \
-H "Authorization: Bearer $PRIVIAN_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "openai/gpt-5.5",
"prompt": "Email me at michael@example.com about ticket #4821.",
"stream": false
}'Provider-namespaced model ids. No messages[], no system prompt array, no tool definitions in the beta. See the API reference for the full request and response shape.
Capabilities
OpenAI, Anthropic and other providers behind one endpoint.
Personal and secret entities replaced before the provider call.
Placeholders restored in the response so your app sees real values.
Your provider credentials, encrypted at rest, used at request time.
Scoped Privian keys (sk-gw_live_… / sk-gw_test_…) for your apps.
Counters and metadata without storing raw prompts.
Transparency
messages[] / chat array supportstream: true returns artificially chunked textFAQ
Plans & pricing
Pricing is published transparently. BYOK, zero retention, provider-agnostic. Beta plans may change.