Environments & URLs¶

Reference for all LiveKit Platform Service (LKPS) and LiveKit SFU server endpoints across regions and environments.

Important

EU and US are isolated deployments — there is no cross-region communication. An agent registered with the EU LKPS instance is only available in EU, and sessions started in EU use the EU LiveKit SFU server. Choose one region and use it consistently for LKPS, agents, and clients.

LiveKit Platform Service (LKPS)¶

The LKPS endpoint — all API calls (/api/agent/register, /api/session/start, /api/health) go through these URLs via the Ocelot reverse proxy.

Non-Production¶

Region	URL
EU	`https://eu-livekit-platform-service-np.int.bayer.com`
US	`https://us-livekit-platform-service-np.int.bayer.com`

Production¶

Region	URL
EU	`https://eu-livekit-platform-service.int.bayer.com`
US	`https://us-livekit-platform-service.int.bayer.com`

LiveKit SFU Server¶

The LiveKit SFU (Selective Forwarding Unit) server — agents and participants connect here using tokens issued by LKPS.

Non-Production¶

Region	URL
EU	`https://eu.livekit-np.int.bayer.com`
US	`https://us.livekit-np.int.bayer.com`

Production¶

Region	URL
EU	`https://eu.livekit.int.bayer.com`
US	`https://us.livekit.int.bayer.com`

Note

You do not connect to these URLs directly. LKPS returns the correct livekit_url in the API response based on the region of the LKPS instance you called.

Ocelot Control Plane¶

Ocelot UI for managing reverse proxy routes and requesting access.

Environment	Ocelot UI URL
Non-Prod	https://devtools-np.bayer.com/ocelot ⧉
Prod	https://devtools.bayer.com/ocelot ⧉

Direct Links to LKPS Ocelot Routes¶

Use these links to navigate directly to the LKPS route page and request access:

Environment	Region	Direct Route Link
Non-Prod	EU	devtools-np.bayer.com/ocelot?route=eu-livekit-platform-service-np.int.bayer.com ⧉
Non-Prod	US	devtools-np.bayer.com/ocelot?route=us-livekit-platform-service-np.int.bayer.com ⧉
Prod	EU	devtools.bayer.com/ocelot?route=eu-livekit-platform-service.int.bayer.com ⧉
Prod	US	devtools.bayer.com/ocelot?route=us-livekit-platform-service.int.bayer.com ⧉

Tip

See Ocelot Access Setup for step-by-step instructions on requesting access.

Entra ID & Identity¶

Resource	URL
Bayer Entra Tenant ID	`fcb2b37b-5da0-466b-9b83-0014b67a7c78`
Entra ID token endpoint	`https://login.microsoftonline.com/fcb2b37b-5da0-466b-9b83-0014b67a7c78/oauth2/v2.0/token`
Azure Portal (App Registrations)	https://portal.azure.com ⧉ → App registrations
Entra Admin Center	https://entra.microsoft.com ⧉
IT4U App Registration Request	ServiceNow ⧉
BEAT Portal	https://go.bayer.com/beat ⧉

LKPS API Audience (Application ID URI)¶

Use the environment-specific value as the scope parameter when acquiring Entra tokens for LKPS:

Environment	Application ID URI	Scope
Non-Production	`api://livekit-platform-service-np.int.bayer.com`	`api://livekit-platform-service-np.int.bayer.com/.default`
Production	`api://livekit-platform-service.int.bayer.com`	`api://livekit-platform-service.int.bayer.com/.default`

Important

The API audience differs between non-prod and prod. Using the wrong audience will result in AADSTS70011: Invalid scope errors.

Environment Strategy¶

Environment	Purpose	When to use
Non-Production (NP)	Development, testing, integration	During development, CI/CD pipelines, staging
Production	Live workloads, end users	After successful testing in non-prod

Recommendations¶

Start with non-production. Develop and test your agent or client application against *-np.int.bayer.com endpoints.
Use separate Entra app registrations for non-prod and prod (e.g., MY-AGENT-NP and MY-AGENT).
Promote to production only after successful end-to-end testing in non-prod.
Do not mix environments. A non-prod LKPS instance returns tokens for the non-prod LiveKit SFU server and vice versa.

Region Selection¶

Choose the region closest to your users and agent infrastructure for optimal latency.

Region	Best for
EU	Users and infrastructure in Europe
US	Users and infrastructure in the Americas

Quick Copy Reference¶

Non-Production Configuration¶

# LKPS endpoint (EU)
LKPS_URL=https://eu-livekit-platform-service-np.int.bayer.com

# API audience for token acquisition (non-prod)
AZURE_API_AUDIENCE=api://livekit-platform-service-np.int.bayer.com

# Entra credentials (your app registration — non-prod)
AZURE_CLIENT_ID=<your-np-client-id>
AZURE_CLIENT_SECRET=<your-np-client-secret>
AZURE_TENANT_ID=fcb2b37b-5da0-466b-9b83-0014b67a7c78

Production Configuration¶

# LKPS endpoint (EU)
LKPS_URL=https://eu-livekit-platform-service.int.bayer.com

# API audience for token acquisition (prod)
AZURE_API_AUDIENCE=api://livekit-platform-service.int.bayer.com

# Entra credentials (your app registration — prod)
AZURE_CLIENT_ID=<your-prod-client-id>
AZURE_CLIENT_SECRET=<your-prod-client-secret>
AZURE_TENANT_ID=fcb2b37b-5da0-466b-9b83-0014b67a7c78