Regions
Deploy to the region closest to your users. See Regions for all available endpoints.
Telnyx-specific regional deployment: nyc1 is the default agent deployment region. To deploy to another region, set LK_AGENTS_URL to that region’s agent deployment endpoint and set LIVEKIT_URL to the matching regional LiveKit endpoint.Use the same region slug for both variables. For example, if your rooms and SIP traffic use sfo3.livekit-telnyx.com, set LK_AGENTS_URL to https://sfo3.agents.livekit-telnyx.com before deploying. Telnyx also prefixes room names for routing; see Room name prefixes. Environment variables and livekit.toml
Set LIVEKIT_URL, LIVEKIT_API_KEY, and LIVEKIT_API_SECRET as environment variables. You also need a livekit.toml in your project directory that defines the subdomain and agent ID:
lk agent create writes the agent ID to livekit.toml. Don’t edit the [agent] section manually. If you clone an example repo, remove the [agent] section before running lk agent create so a fresh ID is generated.
--config flag to point at different TOML files:
Multiple environments
Use separate API keys for dev, staging, and production environments. Each key operates independently.
Log access
Stream logs from your running agent:
Log forwarding to third-party services (Datadog, Sentry, CloudWatch) is coming soon.
