Skip to main content
A cluster invite creates an organization in an existing deployment. It does not deploy a cluster. If you already have an API key, start with the developer quickstart.

​
Accept your cluster invite

Open the cluster invite link your administrator sent you. It carries a one-time token and lands you on the Set up your organization page. A cluster invite is an owner invite - accepting it creates a new organization and sets you as the owner. Your administrator may also have preset a request quota and enabled compute on the invite, so the new organization starts with those in place.

​
Do this

  1. Open the invite link. The page validates the token and shows an Owner invite badge (and an expiry date, if one was set). If it says the invite is unavailable, the invite token has expired or been revoked. Ask your administrator for a fresh link.
  2. Name your organization. Type a name such as Acme Inc, and upload a logo if you have one (PNG, JPEG, WebP, GIF, or SVG, up to 5 MB). A workspace URL slug is generated for you (e.g. acme-inc); expand Customize if you want to edit it. A slug is 1 to 64 characters: lowercase letters, numbers, and hyphens. If a slug is reserved or already taken, the server rejects it and you pick another.
  3. Choose how to sign in. Create an account with email and password, or continue with Google. If the invite was pinned to your email address, that address is pre-filled and locked.
  4. Verify your email. If you signed up with a password, MKA1 sends a verification email. Click the link to confirm; you’re then dropped straight into your new organization.
  5. Walk through the setup wizard. You land in a short setup wizard, not the dashboard. Its steps run in this order: Enable your models (runs automatically), Invite your team, Create teams, Create your first API key, Create your first response, and You’re all set. Every step except the last has a Skip for now button, and each page links back to this guide. The models step is covered under Enable your models below. See Teams and members, API keys, and Quickstart for those steps. The key the wizard creates uses the Standard preset and no rate limit. When you finish, you land in the console as the owner of your organization.
You are now the organization ownerThe owner has full control. Usage, members, teams, and settings. Everyone else you bring in will be an admin or a member (see Teams and members). If you were already signed in to MKA1 with a different email than the invite, sign out first: invites are bound to a specific address.

​
Enable your models

Your cluster keeps a catalog of models, and each organization has its own registry. A cluster admin grants your organization access to catalog models, either in the invite’s Model access picker or later under Access → Organizations → Cluster, on your organization’s Available models tab, but access alone does nothing. You must activate a model in your organization’s registry before any request can resolve it, and that includes model: "auto"; the gateway never activates a model on its own. The wizard’s first step activates every available cluster model you have access to, as long as nothing in your registry is active yet. If you skipped that step, or the cluster admin adds models later, go to Admin → Model Registry → Models and click Activate. Each entry shows available, active, or name in use (available_name_blocked in the API). Name in use means another entry already holds that id, so deactivate that entry first. You can do the same over the API: list the catalog with sdk.llm.models.listCatalog() and activate an entry with sdk.llm.models.activateRegistryEntry({ modelId, source: 'cluster' }) (in Python, sdk.llm.models.list_catalog() and sdk.llm.models.activate_registry_entry(model_id=..., source="cluster")). The Model registry guide covers the catalog, the activation states, and what auto resolves to.

​
Next steps

Create an API key, invite your team, or explore the console.