Skip to main content
API keys authenticate Qualia with AI model providers. Enter your keys here to enable access to different models.

​
Quadrillion API Key

Your Quadrillion API key provides access to Qualia’s hosted models and services. Get your key from the Quadrillion dashboard.

​
Google Gemini API Key

Add a Google Gemini API key to use Gemini models directly. Get your key from the Google AI Studio.

​
Custom provider endpoints

Enterprise BYOK deployments can route provider calls to a custom OpenAI, Anthropic, or Google Gemini compatible endpoint. In Provider key overrides, choose the provider auth mode, add the provider API key when needed, and set the matching base URL. Leave the base URL blank to use the provider’s default endpoint. Include any required path prefix in the URL, such as /v1 for OpenAI-compatible endpoints. A base URL must be http or https. A server you run yourself is fine, whether that is http://localhost:1234/v1 or a machine on your network. Addresses that no endpoint of yours could occupy are rejected, including cloud instance metadata addresses such as 169.254.169.254, because your provider API key is sent to whatever the base URL points at. On a backend shared by more than one person, pointing a provider at your own base URL also requires your own API key for that provider. A key the server supplies through its environment belongs to the deployment rather than to you, so it is never sent to an endpoint you chose. Save your key in Settings alongside the base URL and the endpoint works normally. For a basic Bedrock-compatible gateway that accepts API key authentication, configure the matching provider API key plus the gateway base URL.

​
Model ID aliases

Self-hosted endpoints sometimes serve a model under an internal ID that differs from the catalog’s (for example, claude-fable-5 deployed as claude-fable-5-CAVEAT[1m]). Under each provider override, add a Model ID alias mapping the catalog model to the ID your endpoint expects. Requests to your endpoint use the alias, while the model picker, context window, and capability handling continue to follow the catalog entry. Aliases never apply when requests route through Quadrillion.

​
Azure endpoints

For Azure OpenAI or Anthropic models in Azure Foundry, set the provider auth mode to Azure Entra ID and enter the Azure endpoint URL. If your Azure deployment authenticates with a key instead, choose Azure (API key) and paste the provider key alongside the endpoint URL. Azure Entra ID uses credentials already available on the host, such as managed identity, Azure CLI login, or service-principal values (AZURE_TENANT_ID, AZURE_CLIENT_ID, and AZURE_CLIENT_SECRET). Leave the Entra scope blank unless your administrator gives you a custom scope.

​
Managing keys

  • Keys are stored securely and masked in the UI
  • Click the eye icon to reveal a key temporarily
  • Keys persist across sessions
  • Remove a key by clearing the field and saving

​
Troubleshooting

​
Invalid key errors

  • Verify the key is copied correctly without extra spaces
  • Check that the key is active in the provider’s dashboard
  • Some keys have usage limits — verify you haven’t exceeded them

​
Model not available

  • Ensure you’ve entered the correct key for that provider
  • Some models require specific API access or waitlist approval