Skip to main content

How keys work in Wirebase

Provider API keys belong to your organization, not to individual users. Once an admin adds a key, every member can chat with the models enabled for that provider. Usage is billed by the provider directly to the key’s owner.
  • Keys are encrypted at rest and are never shown again after you save them.
  • A key is validated with the provider before it is saved.
  • Keys set as server environment variables are ignored. Keys are always configured in the app.
Only organization admins can add, change or remove keys.

Add a key

1

Open API Keys

Go to Admin → API Keys and stay on the Provider Keys tab.
2

Choose a provider

Find the provider and click Add.
3

Paste the key and save

Wirebase validates the key, saves it encrypted, and switches on that provider’s default models.
4

Review models (optional)

Go to Admin → Models to turn individual models on or off. See Models.

Connect OpenRouter without a key

Under Quick start, click Connect next to OpenRouter. You’ll authorize Wirebase on OpenRouter and a key is created for your organization automatically. OpenRouter gives access to models from many providers through a single key.

Supported providers

Wirebase supports chat models from OpenAI, Anthropic, Google Gemini, xAI, Groq, Mistral, DeepSeek, Fireworks, Cohere, Amazon Bedrock, OpenRouter and Ollama (local server or Ollama Cloud), plus any OpenAI-compatible endpoint you add as a custom provider.
Enter an AWS Access Key ID, Secret Access Key and Region (default us-east-1). Use the region where your Bedrock models are available.
For Ollama (Local), enter the base URL of your Ollama server, for example http://localhost:11434/api. The server must be reachable from Wirebase. Wirebase checks connectivity and lists the models it finds. For Ollama Cloud, paste an API key from ollama.com/settings/keys.

Service keys

The Service Keys tab holds keys for services that aren’t chat models, such as the web search provider. See Chat features.

Troubleshooting

Your organization has no provider keys yet, or every model is switched off. Ask an admin to add a key or enable models.
The provider rejected the key. Check that you copied it completely, that it hasn’t been revoked, and that billing is set up on the provider’s side.