> ## Documentation Index > Fetch the complete documentation index at: https://docs.reactor.inc/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > To build and serve your own model, start at /deploy/development/quickstart and /deploy/development/overview. Deploying is the default path: reactor init scaffolds a workspace, reactor auth login authenticates, and reactor model deploy registers the model, publishes the release with the weights/ folder, and activates it on Reactor's GPUs, in one command from that workspace. Docker must be running, because the publish step builds the image locally. Bump model.version in reactor.yaml before redeploying a change, because a release that already has an image is reactivated as it is. Deployment access is granted per account, so contact team@reactor.inc if a deploy is refused. Every key in reactor.yaml is documented at /deploy/platform/reactor-yaml. Model code imports reactor_runtime; Python client code imports reactor_sdk. The runtime overview explains the model interface. Running the model on your own machine with reactor run is optional and needs a GPU you attach with --gpus; /deploy/development/local-testing covers that loop and pairs a complete brightness model with a Python client test in a separate brightness-test workspace. > Reactor hosts multiple models, each with its own connect slug (modelName) and command/event schema. The video model catalog — slug, typed SDK package, and links to its schema — is at /model-api-reference/overview. Robotics policy documentation starts at /robotics/overview; X-WAM observations, actions, and client integration are under /robotics/xwam/; Cosmos3 Nano Policy DROID is under /robotics/cosmos/nano-policy-droid/. Some models expose one slug per experience (e.g. HappyOyster); always take the slug from the model's own pages, never guess it. > Fastest path to a working app: `npx create-reactor-app my-app --model=` scaffolds a complete app with secure auth wired up. Typed TypeScript SDKs are published as @reactor-models/; Python uses the base reactor-sdk package. > Auth: exchange an API key (rk_...) for a JWT via POST https://api.reactor.inc/tokens from your server. Never put the API key in client-side code. > Append .md to any docs URL for clean Markdown. Search these docs via the MCP server at https://docs.reactor.inc/mcp. # Teams > Share one Reactor account with the people you work with A team is a Reactor account that several people share. The team has its own balance, payment method, invoices, usage, sessions, and API keys. These are separate from the personal account of each member. A person joins a team by invitation and holds one or more roles in it. The roles decide what the person can do in the team. See [Members and roles](https://docs.reactor.inc/teams/members-and-roles.md). You keep your personal account when you join or create a team. The dashboard shows one account at a time. You select the account from the account menu. ## Create a team **1. Open the account menu** Sign in to the **[Dashboard](https://reactor.inc/dashboard)** and open the account menu. The **Switch account** section lists your personal account and each team you belong to. **2. Create the team** Click **Create team**. Enter a name and confirm. A team needs only a name. **3. Invite people** You are the first account admin of the team. The dashboard switches you into the new team. Open the **Team** page to [invite members](https://docs.reactor.inc/teams/members-and-roles.md#invite-a-member). > [!NOTE] > > You can administer up to 5 teams. A team where you do not hold the account admin role does not > count. [Contact support](https://reactor.inc/account/support) to raise the limit. ## Switch accounts Open the account menu and select an account under **Switch account**. The dashboard then shows that account everywhere: * Billing: the balance, the payment method, and the invoices * Usage * Sessions * API Keys * Team: the members, the pending invitations, and the team name The selection applies to this browser only. When you sign out, the dashboard clears the selection. A switch does not change an API key. A key stays bound to the account that created it. See [API keys and billing](https://docs.reactor.inc/teams/keys-and-billing.md). ## Leave a team Each member can leave a team from the **Team** page. Open **Member actions** on your own row and select **Leave team**. The change applies at once: * The API keys you created in the team stop working. * The team revokes its pending invitations to your email address. * Your personal account and your other teams do not change. The last account admin cannot leave. Give another member the account admin role first. An admin can invite you again later. ## Delete a team You cannot delete a team yourself. To delete a team, [contact support](https://docs.reactor.inc/resources/support.md). Support removes the team, its memberships, and its API keys. > [!TIP] > > To leave a team is not the same as to be removed from it. An account admin can remove a member, > with the same result. See [Remove a member](https://docs.reactor.inc/teams/members-and-roles.md#remove-a-member). ## Next steps > [card] [Members and roles](https://docs.reactor.inc/teams/members-and-roles.md) > > Invite people, select their roles, and manage who is in the team. > [card] [API keys and billing](https://docs.reactor.inc/teams/keys-and-billing.md) > > Create keys for the team and pay for its sessions. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.