API key deployment type: Custom vs Napster-managed – Napster Help

Overview

When generating an API key in the Napster Omniagent dashboard, you are prompted to choose a deployment type. There are two options: Napster-managed and Custom. Choosing the wrong type is a common source of silent connection failures at session time.

Deployment types explained

Napster-managed (recommended)

Napster provisions and manages the underlying Azure OpenAI real-time endpoint on your behalf. This is the correct option for the vast majority of developers and is required for standard WebRTC and WebSocket sessions.

Use this if: You are building on the Omniagent API and do not have your own Azure OpenAI real-time endpoint. This is the default recommended option.

Custom (bring-your-own endpoint)

You supply your own Azure OpenAI real-time endpoint. The API key is configured to connect to that endpoint instead of Napster's managed infrastructure.

Use this only if: You are an enterprise customer with your own Azure OpenAI real-time deployment. If selected incorrectly, sessions will fail with a provider_connection_aborted error — the failure happens silently at session time, not at key creation time.

Symptom: provider_connection_aborted

If your API key was created with the Custom deployment type but you do not have a bring-your-own Azure OpenAI endpoint configured, live sessions will fail immediately with:

provider_connection_aborted

The API key creation itself succeeds — the error only appears when you try to start a live session.

Fix

Go to your Napster Omniagent dashboard → API Keys
Delete the existing key created with the Custom deployment type
Generate a new API key and select Napster-managed as the deployment type
Make sure the new key and your companion are in the same project
Test a live session — it should connect successfully

Confirmed fix: Recreating the API key as Napster-managed and ensuring the key and companion are in the same project resolves provider_connection_aborted errors caused by incorrect deployment type selection. (Confirmed June 16, 2026)