Skip to main content
NodePad can use provider keys that belong to you or your organization. That is useful when you want usage, limits, and billing to stay attached to your own provider account.

​
Why teams do this

Keep spend where it belongs

Usage lands on your provider account instead of a shared platform pool.

Use your own limits

Your team’s rate limits come from your provider relationship.

Match your security model

Enterprise teams often want provider credentials managed inside their own environment.

Unlock deployment-specific models

Some model options may only appear once the relevant provider key is configured.

​
Where keys live

In the hosted product, a user can add keys through settings when that feature is enabled. In self-hosted environments, operators often configure provider access at the deployment level.

Open provider configuration

Open the app settings and go to the area for API keys or provider configuration.

Choose the provider

Select the provider you want NodePad to use through your account.

Paste the key and save

Paste the key, give it a label if you want one, and save it.

Pick a model in your workspace

Return to your workspace and choose one of the models exposed through that provider configuration.
The exact providers available depend on your NodePad environment. The UI lists only the providers that environment knows how to use. If your current environment already exposes the models you need, you may not need to add anything. BYOK matters most when you want control over billing, throughput, compliance posture, or model availability.
Removing a key can change what appears in the model picker. If a workspace depends on that provider, update the default model after the key change.

​
Continue

Models in NodePad

How model selection fits into the workflow.

Self-hosting

Provider keys at the deployment level.