Developer Keys

Developer Keys is where you manage API keys that let your applications connect to AI models on the GLBNXT platform. From here you can create new keys, control which models each key can access, and revoke keys you no longer need.

Overview

The GLBNXT platform exposes an OpenAI-compatible API endpoint, which means any tool or application that already works with the OpenAI API can connect to your organization's AI models with minimal changes. Developer Keys is the starting point: you create a key here, then use it in your application to authenticate API requests.

This feature needs to be provisioned for your organization. If you see a "Feature Not Available" message, contact your administrator or GLBNXT support to get it enabled.

Only administrators have access to Developer Keys. Other users in your organization will not see this page.

Connection Info

At the top of the page you will find the Base URL for the API endpoint:

https://ai.glbnxt.com/v1

Use this URL together with your API key to connect your applications. A copy button makes it easy to grab the URL.

Key List

Once you have created keys, the page shows them in a table. Each key displays its name, how many models it can access, when it was created, when it expires, and when it was last used. This helps you keep track of which keys are active and whether they are still in use.

The table footer shows a summary of how many keys are active and how many have been revoked. You can toggle "Show revoked keys" to include revoked keys in the list. Revoked keys are marked with a badge and cannot be used or modified.

If no keys exist yet, the page shows an empty state with a button to create your first key.

Model IDs

When connecting your application, you need to specify which model to use. Each model has an ID that you pass in your API requests. The available models and their IDs depend on what your organization has provisioned.

You can find the exact model IDs available to your key in the Assign Models dialog. Model IDs come in different formats depending on how they were set up:

• claude-opus-4-6

• glbnxt/gpt-oss-120b (custom organization prefix)

The model ID you see in the Assign Models dialog is what you use in your API calls and tool configurations.

Key List

Once you have created keys, the page shows them in a table. Each key displays its name, how many models it can access, when it was created, when it expires, and when it was last used. This helps you keep track of which keys are active and whether they are still in use.

The table footer shows a summary of how many keys are active and how many have been revoked. You can toggle "Show revoked keys" to include revoked keys in the list. Revoked keys are marked with a badge and cannot be used or modified.

If no keys exist yet, the page shows an empty state with a button to create your first key.

Creating a Key

Click Create Key to open the creation dialog. You give the key a name that identifies its purpose (for example, "Production Backend" or "Analytics Pipeline") and choose how long it should remain valid: 30 days, 90 days, 1 year, or indefinitely. The default is 1 year.

After creation, the portal displays the API key one time. Copy it immediately and store it securely. The key cannot be retrieved later. If you lose it, you will need to create a new one.

Managing Models

Each key can be scoped to specific AI models. Open the actions menu on a key and select Assign Models to choose which models the key can access. You can search and filter the available models, select individual ones, or use "Allow all models" to grant access to everything your organization has available.

If you are not sure which models to assign, allowing all models is a safe starting point. You can always narrow the scope later.

Renaming a Key

Open the actions menu on the key and select Rename to change its display name. Keeping names descriptive helps your team understand what each key is used for.

Deleting a Key

Open the actions menu and select Delete to permanently revoke a key. Any application using the key will immediately lose access, so make sure the key is no longer in use before deleting it. Deleted keys remain visible in the revoked keys list for reference.