> ## 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; The launch policies are Cosmos Nano DROID (/robotics/cosmos/nano-policy-droid/), DreamZero DROID (/robotics/dreamzero/droid/), and FLUX Action DROID (/robotics/flux-action/droid/), organized by model family and embodiment. 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. # reactor model access > Share a private model with other accounts ## Description Share a private model with other accounts. An account with access to an environment of a model uses it the way any account uses a public model: every member and API key of the account can mint tokens for the environment and start sessions on it. The account pays the model's price for its sessions, and it gets no releases, deployments or settings of the model. The owner account's account\_admin grants and revokes access; its developer lists it. Accounts are named by ID: a member of the account finds it with `reactor whoami`. ## Global options | Flag | Description | | - | - | | `--server string` | Reactor API server URL (default "[https://api.reactor.inc](https://api.reactor.inc)") | | `-v, --verbose` | Enable verbose output | ## See also * [reactor model](https://docs.reactor.inc/deploy/cli-reference/reactor_model.md) - Model management commands * [reactor model access grant](https://docs.reactor.inc/deploy/cli-reference/reactor_model_access_grant.md) - Give another account access to an environment of a model * [reactor model access ls](https://docs.reactor.inc/deploy/cli-reference/reactor_model_access_ls.md) - List the accounts with access to a model * [reactor model access revoke](https://docs.reactor.inc/deploy/cli-reference/reactor_model_access_revoke.md) - Take an account's access to a model away This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.