OpenAI Provider
Configure the OpenAI-compatible endpoint for/openai/v1/* requests.
| Option | Description |
|---|---|
base_url | API endpoint (any OpenAI-compatible URL) |
api_key | Optional. Used if client doesn’t send Authorization header |
Compatible APIs
Any OpenAI-compatible API works:Anthropic Provider
Configure the Anthropic endpoint for/anthropic/v1/* requests.
| Option | Description |
|---|---|
base_url | Anthropic API endpoint |
api_key | Optional. Used if client doesn’t send x-api-key header |
Codex CLI Backend
Configure the Codex ChatGPT-login endpoint for/codex/* requests.
| Option | Description |
|---|---|
base_url | Codex backend endpoint for ChatGPT-login Codex CLI traffic |
Authorization header to the Codex backend. Use /codex for Codex users signed in with ChatGPT. Use /openai/v1 only for OpenAI API-key traffic.
Local LLM
Required for route mode only. Your local LLM for PII requests.| Option | Description |
|---|---|
type | ollama or openai (for compatible servers) |
base_url | Local LLM endpoint |
model | Model to use for all PII requests |
api_key | Only needed for OpenAI-compatible servers |
Ollama
vLLM
llama.cpp
LocalAI
API Key Handling
PasteGuard forwards your client’s authentication headers to the configured upstream. You can optionally setapi_key in config as a fallback for OpenAI and Anthropic. Codex CLI traffic uses the CLI’s ChatGPT-login authorization header: