Skip to Content
Baseera Docs

Provider keys

Add, replace and remove the model provider keys your agents run on, and read their health.

Baseera runs on your own model provider key, so your usage is billed by your provider, to you. You add the key once, and agents and knowledge bases pick it from a list. Baseera encrypts the key and never shows it again.

Only Owners and Admins can add, replace or remove provider keys. Developers and viewers do not see the buttons.

Add a key

Open Provider keys from the account menu. The page is titled Model providers.

Press Add a provider key.

Choose the Provider: Anthropic, OpenAI, Google (Gemini) or OpenRouter.

Paste the API key. Keys have a recognisable start: Anthropic keys begin sk-ant-, OpenAI keys sk-, Google keys AIza and OpenRouter keys sk-or-. Give it a Name (optional) such as "Production".

Press Check and save.

Baseera first checks the shape of the key, then makes one read-only call to the provider to confirm it works. A key the provider rejects is not saved. After a successful save you see "Saved." and the key appears in the list as its provider, name and last four characters.

Use a key made for Baseera, so you can revoke it at the provider without touching anything else. Create a spending limit at the provider too, as a second safety net next to Baseera's spending limits.

Use the key

Choose it in two places:

  • On the agent's Assistant page, under Model, in Provider key.
  • On a knowledge base, as its embedding key. Anthropic does not offer embedding models, so an Anthropic key cannot embed. Use an OpenRouter, OpenAI or Google key for knowledge.

Replace a key

Press Replace on the key, paste the New API key and press Check and save. The key keeps its place, so agents that use it carry on with the new secret. The old secret is destroyed and the key's health resets.

Remove a key

Press Remove on the key. The dialog "Remove this key?" lists the agents that use it.

Press Remove key to confirm.

The stored secret is destroyed and cannot be recovered. Agents that used it stop answering until you pick another key on their Assistant page and publish. You see "Key removed" on those agents.

Read the key's health

Each key and each agent that uses it shows a health state, taken from real use:

StateWhat it meansWhat to do
Key rejectedThe provider rejected the key. Assistants that use it cannot answer.Replace it with a valid key.
Out of creditThe provider says the key has no credit left.Add credit with the provider.
Rate limitedThe provider is limiting this key's requests.Usually clears by itself.
Provider unavailableThe provider is not responding.Usually clears by itself.
Key removedThe agent's key was removed.Pick another key for the agent.

The state shows "since" a date in UTC. A banner on the agent, "This agent can't answer right now", links to Open provider keys. At the top of the page the tiles Keys, In use and Need attention summarise the list.

Owners get one email when a key becomes Key rejected or Out of credit, at most once per key per 24 hours. Rate limits and outages do not send email because they usually pass.

Your end users never see the provider's message. They see "The assistant is unavailable right now", or "The assistant is busy right now" for a rate limit.

Where keys are stored

Provider keys are stored encrypted at rest. Baseera keeps only the provider, the name, the last four characters and the health state in readable form. No page and no API returns a key after you save it, and keys are kept out of logs. Only the runtime that calls the model can read a key, and only the one for the agent making the call.

Creating or replacing a key counts as a sensitive action. If your organization requires two-factor sign-in, you must have entered your code in this session first. See Team and roles.

What can go wrong

MessageCause and fix
"That doesn't look like a key for this provider. Check you copied all of it."The key has the wrong shape or is cut off. Copy it again.
"The provider rejected this key. Check it and try again."The key is wrong, revoked or from another provider.
"The key is valid but has no access to models. Check its permissions."Give the key access to models at the provider.
"The key has no credit left. Add credit with the provider, then try again."Top up at the provider.
"The provider is limiting requests right now. Try again in a minute."Wait, then retry.
"We couldn't reach the provider to check the key. Try again."A temporary network problem.
"This organization already has 20 provider keys. Remove one first."Remove a key you no longer use.
"Too many key checks in a minute. Try again in N seconds."Checks are limited to 10 a minute per person and per organization. Wait.
"Enter your two-factor code before adding or changing provider keys. Open Security to continue."Sign in with your authenticator code, then retry.
"Only owners and admins can manage provider keys."Ask an owner or admin.

Next steps

On this page