What AI Manager sends to providers, and where it keeps your keys
Exactly what leaves your Laramin with each AI request, which calls send no content at all, how your API keys are stored and who can change them, and what AI Manager records about each call.
- Applies to
- AI Manager 2.2 and later
- Who can do this
- Platform owner, Administrator
On this page
In short
An AI request carries the instructions and content that an add-on needs for one job, and goes only to the provider AI Manager picks for it. It doesn't carry who you are. Your API keys are stored encrypted in your Laramin's database, are never shown again after you save them, and are kept out of usage records and alerts. AI Manager records the cost and outcome of every call, but not what was asked or answered.
What each request sends
When an add-on asks for AI, AI Manager sends the chosen provider:
| Sent | Details |
|---|---|
| The model's name | For example the Model value on the model's row. |
| The add-on's instructions and content | Text, and images when the job needs Image understanding. The add-on decides what goes in. For example, Question Bank sends the questions it analyzes and the images of the question papers you upload. |
| How to answer | Whether to answer in JSON, and the most tokens the answer may use. |
| Your API key | In a request header, never in the address. With OpenAI, also your Organization ID if you've set one. |
AI Manager doesn't add your name, your user account, your workspace or any other detail of who made the request. Add-ons can attach context, such as the id of the question being analyzed. That context stays in your Laramin's usage record and isn't sent.

Where it goes
Each request goes to one provider only, chosen as How AI Manager works explains. If that provider fails and failover is on, the same request goes to the next provider in line, so content can reach more than one of the providers you've made Active. To keep a job with one provider, make only that provider Active, or turn off Try the next provider on failure.
By default, each provider's requests go to its public address, such as https://api.openai.com. If you fill in a provider's Base URL, requests and your key go there instead. AI Manager only accepts a Base URL that starts with https://, or http:// on the same server (localhost), and doesn't contain a user name or password.
Calls that send no content
Two kinds of call only ask the provider for its list of models. They carry your key, but no content:
- Test Connection on a provider's row.
- The daily model check at 04:10, and Check now on a model's comparison page.
What the provider does with it
What a provider may keep or use from your requests is set by your account and agreement with that provider, not by AI Manager. Before you make a provider Active, check that its terms suit the content your add-ons send.
Careful: Content you upload for AI work, such as a scanned question paper, may include personal details. Make Active only providers whose terms you accept for that kind of data.
Where your keys are kept
- In your Laramin's database, encrypted with your Laramin's application key. They aren't in the
.envfile or in your Laramin's settings. A provider's Base URL, Organization ID and other connection fields are stored the same way. - Never shown again. After you save a key, its field shows Stored - leave blank to keep it. Nobody can read it back on screen, in the provider list or in an export. To change it, type a new one.
- Read at the moment of each call, so a new key works from the next call. Nothing needs restarting.
- Kept out of records. Usage records, alerts and error messages use AI Manager's own wording, never the provider's raw reply, so they don't repeat your key.
If your Laramin's application key changes, for example when a database is restored onto a newly set-up Laramin, the stored keys can no longer be read. The provider then shows No credentials in Availability, and you enter its key again. Database backups contain the keys in their encrypted form.
Who can change keys
| Permission | Lets someone |
|---|---|
List AI providers (feature.) | See the providers and whether each has a key, but not the key. |
Edit an AI provider and its credentials (feature.) | Replace a key, change where requests go with Base URL, and switch a provider on or off. |
Run an AI provider connection test (feature.) | Use Test Connection. |
Give Edit an AI provider and its credentials only to people you trust with your AI spend and your data. Someone with it can point a provider's Base URL at another server.
What AI Manager records about each call
Every attempt is a usage record in AI Manager › Usage & Cost, with:
- the provider, model, tier and capability, and which add-on asked (Used by);
- the tokens used, the cost, and the rates applied;
- the outcome: Answered, Failed or Skipped, with the reason and a short error message;
- a Request ID and the add-on's context, such as a question id.
The instructions, content and answers aren't stored in the usage record. The add-on that asked keeps whatever it needs from the answer, for example Question Bank saves the questions it read. Usage records can't be edited or deleted on screen, and nothing removes them automatically.
Next steps
Thanks. That helps us decide what to write next.
Thanks for telling us what was missing.
You already answered for this article today. Thanks.
We got a lot of answers from your network just now. Try again in a few minutes.
We couldn't send that. Check your connection and try again.
Links in this article
Printed from help.bsscn.com. The online article may have changed since.