Skip to main content
Everything in Omnia is scoped to a workspace: API keys, wallet, usage, dedicated endpoints, and fine-tuning jobs all belong to one. You manage your workspace and its members from the dashboard.
Team and billing features are dashboard-managed, not a public API. The API is for inference and resource management (dedicated endpoints, fine-tuning), authenticated with a workspace key. There is no API to create workspaces, invite members, or move funds.

Workspaces

Your workspace is created during onboarding, and each account has one workspace; multiple workspaces per account are not currently supported. The workspace is the unit of:
  • Billing: one prepaid wallet per workspace. Dedicated GPU-hours and fine-tuning trained-token charges all draw from this wallet.
  • Access: every API key resolves to exactly one workspace, and all usage from that key is attributed to it.
  • Resources: dedicated endpoints and fine-tuning jobs live in the workspace and are visible to its members.

How keys resolve to a workspace

An API key uniquely identifies its workspace. When you make an inference or management call, Omnia resolves the key to its workspace and applies that workspace’s catalog, wallet, and resources. A key cannot act on another workspace, and it cannot override the workspace it belongs to.

Team members and roles

Invite teammates to your workspace from the dashboard. Members have roles that control what they can do: Certain actions are admin-gated: creating, updating, or deleting dedicated endpoints and launching fine-tuning jobs all require an owner or admin. Managing billing is owner/admin as well. Regular members can run inference against shared models and existing dedicated endpoints.

Inviting members

1

Open team settings

In the dashboard, go to your workspace’s team settings.
2

Send an invitation

Enter the teammate’s email and choose their role. They receive an invitation link.
3

They accept

The invitee accepts and joins your workspace with the role you assigned.

API keys and members

Each API key is created by a member and belongs to the workspace. Usage from a key is attributed to the workspace, and admin-gated management operations respect the member’s role. Revoke a key any time from the dashboard.

Authentication

How workspace API keys work.

Billing

How the per-workspace wallet is charged.