Getting started
Send a first Responses Proxy request with a registered model alias and connect Codex to the proxy endpoint.
Managed CLI setup
Configure organization-scoped Codex and Claude routing with the private Morph CLI plugin, secure OAuth import, tiered activation, and diagnostics.
Concepts
Understand Responses Proxy providers, model aliases, adapters, affinity, telemetry, and durable routing state.
Provider registration
Register OpenAI, OpenAI-compatible Chat, Kimi/OpenRouter, and Anthropic providers for Responses Proxy routing.
Proxy keys
Create and use org-scoped Responses Proxy keys for data-plane requests.
Claude Code BYOS
Use Responses Proxy with Claude Code through Anthropic, OpenAI Responses, and OpenAI-compatible Chat Completions aliases.
ServiceProvider
Understand how ServiceProvider records make registered providers routable without redeploying Responses Proxy.
Architecture
Learn how Responses Proxy resolves model aliases, routes through provider adapters, records telemetry, and separates frontend dashboard traffic from backend routing.
API reference
Review Responses Proxy public routes, authenticated admin routes, registry endpoints, metrics, and routing contracts.
Configuration
Configure Responses Proxy admin auth, SQL persistence, Redis state, provider routing refresh, health checks, and deployment settings.
Dashboard
Understand the Responses Proxy dashboard, frontend BFF contract, provider management, metrics, routing state, and telemetry views.
Security
Secure Responses Proxy admin routes, provider credentials, frontend BFF calls, telemetry payload capture, and deployment secrets.
Troubleshooting
Diagnose Responses Proxy provider registration, alias routing, admin auth, dashboard metrics, Codex metadata, and provider adapter failures.