Thanks — I can help with this. To make sure I give the right steps, a few quick clarifying questions about your setup and goal: 1. By “self host APIs on agent-gateway.livekit.cloud” do you mean: ◦ You want your self-hosted LiveKit cluster to accept requests routed through agent-gateway.livekit.cloud (i.e., integrate with LiveKit’s gateway), or ◦ You want to run your own API endpoints that replicate functionality hosted at agent-gateway.livekit.cloud (i.e., replace the hosted gateway with your own)? 1. Which LiveKit components are you currently running self-hosted? (e.g.,

livekit-server

,

signal-server

,

web

, or a Kubernetes deployment via the LiveKit Helm chart) 2. Are you using DNS and TLS already for your self-hosted domain(s)? If so, please share whether you’ve configured a reverse proxy (nginx/traefik) or an ingress in Kubernetes. 3. Which APIs/endpoints do you need to expose? Examples: ◦ REST or gRPC control APIs for room/session management ◦ Webhooks/callback endpoints ◦ Client connection signaling (WSS) 1. Is your goal to have clients connect to agent-gateway.livekit.cloud directly, or to have agent-gateway proxy to your self-hosted cluster? With those answers I’ll give step-by-step options tailored to your situation (DNS/TLS config, reverse-proxy or ingress rules, required LiveKit config values, and any auth/credentials considerations). If you’re not sure about some details, tell me what you do have (e.g., Kubernetes vs VM, domain names, and whether you already run a proxy) and I’ll propose the most straightforward approach. , with interactive elements