Skip to main content
These are your provider credentials, not Pretty credentials. Pretty does not issue API keys and has no public API or SDK. When workspace settings say “API keys”, it means the keys your organization holds with a model provider, which Pretty then calls on your behalf.
By default your workspace runs on Pretty’s own provider access. Bring-your-own-key (BYOK) points it at yours instead: the requests go to your account, on your terms, and appear on your provider bill.

​
Setting it up

From the settings drawer, Workspace → Edit Workspace Settings, then the Custom API Keys section. Owners and Admins only. Pick a Provider, paste the key, fill in whatever else that provider needs, and click Connect. For LiteLLM and for OpenAI’s regional endpoints the button reads “Verifying connection…” while Pretty checks the credentials actually work before saving them. Once connected, the section collapses to a single row showing the provider name and its state, such as Connected · eu-central-1, with Disconnect next to it. Disconnecting returns the workspace to Pretty’s provider access, unless BYOK is required (below). One provider is active at a time. To move to a different one, disconnect the current provider first. The form only reappears once nothing is connected.

​
The four providers

Fields: OpenAI API key (sk-…), Region.Region controls data residency and offers three choices:Regional endpoints only accept keys from an OpenAI project created in that region, which requires data-residency approval from OpenAI. If your key is an ordinary one, leave the region on Default.Models in the picker: GPT-5.6 Terra (High), GPT-5.6 Sol (Medium), GPT-5.6 Sol (High).
Whichever you connect, the model picker in chat is stocked from that provider, so the list your team sees changes with the provider, not with their account.

​
Requiring BYOK

A workspace can be set to refuse Pretty’s provider access entirely, so chat never silently falls back to it. With that flag on and no key configured, requests stop with:
Your organization requires an API key, but none is configured. Add one in settings to continue.
Admins get an Open settings action on that message. Members cannot fix it themselves. They need an admin to connect a key.

​
Troubleshooting

“Please check that your key is valid in settings.” The key was revoked, mistyped, or has no access to the model being used. Reconnect with a fresh key. For OpenAI on a regional endpoint, check the key belongs to a project in that region. An ordinary key against eu.api.openai.com is rejected.
“An admin needs to add it to the proxy’s model list.” Pretty offers the model; your proxy does not route it. Add it to the proxy config, or tell people which models to stay on.
This is your provider’s limit, not Pretty’s: “Please check your plan and billing details, or update your API key.” Raise the quota with the provider. For Pretty’s own monthly budget, which is a different thing, see Usage and limits.
Model access in Bedrock is granted per region. Enable the models in that region, or reconnect against a region where they are already enabled.