Skip to main content
Configure endpoints for OpenAI-compatible APIs, Anthropic, local LLMs, and Codex CLI traffic.

OpenAI Provider

Configure the OpenAI-compatible endpoint for /openai/v1/* requests.
OptionDescription
base_urlAPI endpoint (any OpenAI-compatible URL)
api_keyOptional. 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.
OptionDescription
base_urlAnthropic API endpoint
api_keyOptional. Used if client doesn’t send x-api-key header

Codex CLI Backend

Configure the Codex ChatGPT-login endpoint for /codex/* requests.
OptionDescription
base_urlCodex backend endpoint for ChatGPT-login Codex CLI traffic
PasteGuard forwards the Codex CLI 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.
OptionDescription
typeollama or openai (for compatible servers)
base_urlLocal LLM endpoint
modelModel to use for all PII requests
api_keyOnly 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 set api_key in config as a fallback for OpenAI and Anthropic. Codex CLI traffic uses the CLI’s ChatGPT-login authorization header: