Skip to main content
The webapp has three scopes. The organization console covers organization-wide resources, the workspace console covers the keys and policies used by an application, and the instance console gives instance administrators a cross-organization view. The menus shown to you depend on your role and permissions.

​
Choose an organization and workspace

After signing in, choose an organization if you belong to more than one. In the organization console, use the workspace selector at the top of the sidebar to switch workspaces. Choose Create Workspace from the selector menu if you have permission to add one. Organization pages remain available below the workspace menu.
Production workspace with $294.47 estimated spend, 1,190 requests, and 4,651,263 tokens across 30 days

Workspace navigation and a 30-day usage overview with historical activity

The account area at the bottom of the sidebar shows the signed-in user and provides Sign out. If your account has an instance role, select the shield button there to open the instance console. The instance console’s Workspace console link returns to the organization console.

​
Organization menu

These pages apply to the selected organization:
Organization overview with historical daily spend, 1,548 requests, and production and staging attribution

Organization usage across a 30-day history, attributed to its production and staging workspaces

​
Workspace menu

Select a workspace to see its pages. The workspace menu applies to that workspace only:
Workspace Requests page listing recent production requests with cost, model, and token totals

Production workspace usage across the last 30 days

An inference key is for application traffic. A management key is for authorized control-plane operations and can have a restricted permission set. Keep those credentials separate.

​
Instance management

The instance console is available to accounts with an instance role. Select the shield icon from the organization console or Workspace console from the instance sidebar to switch between the two consoles. Opening an organization shows its details and workspaces, with actions to rename or delete the organization when you have permission. Open a workspace from there to inspect or manage that workspace. Instance menus are permission-filtered, so an auditor or other limited role may see fewer actions than an owner.
Instance overview showing one organization, an online connected service, and recent activity

Instance overview with an online data plane and recent activity

Instance Organizations page showing the organization list

Instance organization list

​
Common tasks

​
Add a provider credential for a workspace

  1. Select the organization and workspace
  2. Open BYOK
  3. Add a credential for the provider and give it a recognizable name
  4. Use Rotate on the credential when its secret needs replacing
Manage instance provider credentials under Instance → Provider Keys. For organization-scoped credentials, use the CLI, for example airmux provider-credentials add openai --org, or the control-plane API.

​
Create an application key

  1. Select the workspace that should own the key
  2. Open Inference Keys and create a key
  3. Copy the secret when it is shown; it is only displayed at creation
  4. Give the key to the application that sends requests to the gateway

​
Review a request

Open Requests at the organization or workspace scope. Set the available filters to narrow the report, then open a request to inspect its details. Workspace reports stay within one workspace; organization reports cover the organization’s workspaces.

​
Invite a person

Open Organization → Settings → Members to invite someone to the organization. You can assign an organization role and optionally add a workspace membership. The webapp creates an invitation link for you to share. Workspace membership can also be managed from Workspace → Settings. For role definitions and service-account setup, see Manage users and access. For policy design, see Workspace policies.
The usage screenshots use the repository’s synthetic development fixtures: 1,200 Production events and 360 Staging events spread across 30 days, plus recent example requests. The totals and catalog prices are illustrative. No external provider was called or billed.