Intranet searchRAG over policy documents
Models3 selected
Expires4 Nov 2026
GLBNXT Platform / API Keys
One key per application. Scoped, dated and classified.
Give every app its own key. Decide which models it may call and when it expires, and record its AI Act risk level. Keys marked unacceptable risk are blocked automatically.
1
base URL for every app
4
expiry options, 30 days to none
4
AI Act risk levels per key
1×
a new key is shown once
From key to first call
Four steps, then your app is talking to a model.
The endpoint speaks the OpenAI format. If your tool already works with OpenAI, it needs a new base URL and a GLBNXT key. Nothing else.
- 1
Create a key
Name it after the app that uses it, add a short description and choose how long it stays valid.
- 2
Assign models
Pick the models this app may call, or allow all of them for now.
- 3
Copy it once
The key appears one time. Put it in your secrets manager right away.
- 4
Connect
Point your code at ai.glbnxt.com/v1 and use a model ID from the key's list.
That is the whole migration.
Two lines change. The rest of your code, your prompts and your tooling stay as they are.
Works with n8n · Open WebUI · LibreChat · Langflow · LangChain · LiteLLM
Least privilege
A key only reaches the models you pick.
Each row is an application, each column a model. Tick what the app needs and leave the rest closed. Not sure yet? Allow all models and narrow it down later.
| Key | glbnxt/gpt-oss-120b | glbnxt/gemma-4:26b | glm-5.3 | deepseek-v4.1-flash | claude-opus-5-5 |
|---|---|---|---|---|---|
| Claims intake assistant2 selected | |||||
| Contract review1 selected | |||||
| Intranet search3 selected | |||||
| Marketing draftsAll models |
Model IDs come straight from the Model Hub →
Key lifecycle
Every key has a start, a last use and an end.
Forgotten keys are how access leaks. The key list shows when each one was created, when it was last used and when it expires, so stale keys stand out.
Claims intake assistantLevel 3 · Limited risk
Created12 Mar 2026Shown once, then stored in the app's secrets.
Last used3 Oct 2026Unused for months? Time to review the key.
Expires12 Mar 2027One year, the default validity.
RevokeAny timeAccess stops at once. The key stays listed as revoked.
Validity options30 days90 days1 year · defaultNo expiry
Level 1 · Unacceptable · blockedEmotion recognition at work
Level 2 · High riskScreening job applications
Level 3 · Limited riskCustomer service chatbot
Level 4 · Minimal riskInternal document search
UnclassifiedNo level set yet. Visible, so gaps in your AI inventory show.
AI Act risk level, per key
Classify each application where it connects to AI.
Your administrator gives every key a level that matches what the application does. The level sits next to the key, so anyone reviewing access sees it straight away.
Level 1 is a hard stop.
A key marked unacceptable risk is blocked automatically and cannot call any model.
GLBNXT records the level you choose. The classification itself stays your organisation’s call.
Built for audits
Know which app called what, and when.
One key per app means every request in the logs points back to one application and one owner. Including the ones that were stopped.
TimeKeyRisk levelModelTokensResult
09:41:07Claims intake assistantLevel 3 · Limitedglbnxt/gpt-oss-120b1,284200 · OK
09:41:12CV screeningLevel 2 · Highglbnxt/gemma-4:26b642200 · OK
09:41:19Intranet searchLevel 4 · Minimalglbnxt/gemma-4:26b918200 · OK
09:41:23Contract reviewLevel 2 · Highglm-5.33,910200 · OK
09:41:30Claims intake assistantLevel 3 · Limitedclaude-opus-5-50Model not assigned
09:41:36Marketing draftsLevel 4 · Minimaldeepseek-v4.1-flash2,077200 · OK
Usage per key. Token use and response times for each key, so cost and load have an owner.
Secrets stay secret. Keys for platform workloads live in the secrets vault, not in workflow settings.
Admins only. Only administrators can see, create, edit or delete keys.
Questions admins ask us
Something missing? The full reference lives in the Developer Keys documentation.
Who can create and manage API keys?
Only administrators of your organisation. Other users do not see the API Keys page. The feature has to be enabled for your organisation; ask your GLBNXT contact if you do not see it.
I lost a key. Can you send it again?
No. A key is shown once, when you create it, and cannot be retrieved later. Create a new key, update your application and delete the old one.
Who decides a key's risk level?
Your administrator does, based on your organisation's own AI Act assessment of the application. GLBNXT records and displays the level; it does not classify your use case for you.
What happens with a Level 1 key?
Level 1 stands for unacceptable risk. A key at that level is blocked automatically and cannot call any model.
Can one key use every model?
Yes, with Allow all models. You can also select specific models and change the selection at any time. The model IDs shown in the dialog are the ones you use in your code.
How long does a key stay valid?
30 days, 90 days, 1 year or without expiry. One year is the default. You choose when you create the key.
What happens when I delete a key?
Every application using it loses access immediately. The key stays visible in the revoked list so you keep a record.
Set up your first scoped key today.
Start a free trial and connect your first app, or walk through key policies and risk levels with us in a 30-minute demo.
