Provider keys are credentials needed by external services such as OpenAI or xAI text-to-speech and assistant providers. They are project-scoped so authorized project members can render with a configured provider key without seeing the secret.
Adding or replacing a key requires the administrator-granted project.byok.configure scope. Existing keys can still be used or cleared after that scope is removed; sign out and back in after an administrator changes access.
For OpenAI and xAI speech, choose Use plan TTS minutes when BadgerLeaf should fund the provider call. Daily, weekly, and billing-period allowances apply. Choose Use project API key when the provider should charge the key owner; this does not consume included TTS minutes.
Plan allowance counts only successfully synthesized audio, even if the enclosing render later fails. Failed, ambiguous, and cached attempts consume no included TTS minutes. BadgerLeaf reconciles any provider billing for unsuccessful or uncertain calls separately and never turns it into customer TTS usage.
BadgerLeaf never switches between plan funding and a project key automatically. If the selected source is unavailable or has reached a limit, choose another available source and submit again.
xAI voices are discovered from the provider. A configured voice that later disappears remains selected with an unavailable warning until you intentionally replace it.
Add only keys required for the project. Rotate or remove keys that should no longer be used. If a render fails because a provider is unavailable, check the selected funding source, provider key, and voice configuration together.