Responses Proxy

One tenant URL in front. Any chat-completions provider behind it.

Paste your upstream endpoint, optionally probe support, then copy the generated Responses API base URL into Codex. If you send X-Tenant-Secret from your first request onward, stored chats are encrypted so only the holder of that secret can decrypt them.

Create

Mint a unique tenant path

Probe

Store supported capabilities

Use

Point clients at one Responses URL

Endpoint shape
https://chat-response.federation.workers.dev/t/<tenantHash>/v1/responses

Create Tenant

Upstream settings

The probe key is only used to test support during setup. Runtime requests still use your real upstream provider key.

Upstream chat-completions endpoint

Probe model Optional label

Provider API key for probe only, not stored

Advanced

Auth mode API key header

Extra query params JSON Extra headers JSON

Force developer role support Force audio input support Force file part support

Tenant Ready

Copy this into your client

The tenant id scopes stored history. If you also send X-Tenant-Secret, stored chats are encrypted and only that secret can decrypt them later.

Recovery warning

One tenant URL in front. Any chat-completions provider behind it.

Create

Probe

Use

Upstream settings

Copy this into your client

Responses base URL

Simple Codex config.toml

Encrypted Codex config.toml

Provider API key env

Tenant secret env

Tenant id

One-time tenant secret

Encrypted curl example

Subagent project config

Custom subagent file

Detected capabilities