AI Provider Key Settings

Register and manage account keys for account projects and local keys for local projects.

Account and local keys

The two key sources have different storage and project scopes and do not replace each other.

ItemAccount keyLocal key
Project scopeAccount projectsLocal projects
StorageEncrypted account storageOS secure storage
Device scopeAvailable in signed-in environmentsThis device only

Note: Signed-in Desktop manages both groups, but the current project type selects the source used for requests. Web uses account keys only; signed-out Desktop uses local keys only.

Supported providers

Each provider can use its default or a custom endpoint.

ProviderAPI KeyEndpoint
OpenAIRequiredDefault or custom
AnthropicRequiredDefault or custom
Google GeminiRequiredDefault or custom
OllamaOptionalDefault or custom

Register a Provider Key

Add a provider in the key group for the current project.

1

Open AI settings

Open AI settings from the user menu and select the account or local key group.

2

Enter provider credentials

Choose OpenAI, Anthropic, Google Gemini, or Ollama, then enter its API Key and endpoint. The Ollama API Key is optional.

3

Select a model

Load and select a model. Local keys can also enter a custom model name not in the list.

4

Save and choose the primary key

Save the settings and, when needed, make it the primary Provider Key for that source.

Note: AI model add in Chat also opens the registration screen for the current project.

Key options

Models, endpoints, and primary selection are managed independently for each key.

  • Local keys can enter a custom model name.
  • Account and local sources each have their own independent primary key.
  • Max output tokens limits the size of one response. A value that is too small can truncate an explanation or SQL.
  • Account keys support monthly budgets and estimated costs based on recorded usage.
  • Local keys call the provider from the device, so NeoSQL does not provide monthly budgets or cost tracking.

Caution: Estimated cost may differ from provider billing, and a monthly budget is not an absolute cap including concurrent requests.

Manage keys

Manage credentials and availability from each key card.

  • Edit: change the API Key, endpoint, model, and options.
  • Disable: prevent selection for new AI requests.
  • Delete: remove an unused key. You may need to select another primary key first.
  • Switching projects also switches the key group available in Chat between account and local.

Storage and endpoint security

Storage and allowed endpoints depend on the key source.

  • Account keys are encrypted in account storage, and the original secret is not shown again.
  • Local keys stay in the OS secure storage and do not sync to another device or account project.
  • Account keys on Web use public HTTPS endpoints. Desktop local keys can also use localhost and private endpoints.

Troubleshooting

If a key or model is unavailable, check the current project type and key group first.

  • If Send is disabled, verify that the current project source has an active key.
  • For authentication errors, check key expiration and provider permissions.
  • If a model is missing, reload after checking the endpoint and credentials, or enter a custom model for a local key.
  • Web cannot use localhost, HTTP, or private-IP endpoints.