> ## 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. # List your account's models > Returns the models your account owns (`owned`, paged with `limit` and `offset`) and the models other accounts shared with it (`shared`, not paged). Deleted models are left out. Callable by an `account_admin` or `developer` of the account. Another account's ID returns `403`. `shared` rows have the public view: no `project_id` or GPU fields. Their `environments` lists the environments you were granted. ## OpenAPI ````yaml /openapi.yaml get /accounts/{account_id}/models openapi: 3.1.0 info: title: Reactor Platform API version: '1' description: > The Reactor Platform API mints session tokens, starts and operates sessions, negotiates media transport, and manages your account, models, and deployments. Every path is relative to `https://api.reactor.inc`. See the [Introduction](/platform-api/introduction) and [Authentication](/platform-api/authentication) pages for credentials, versioning, and errors. contact: name: Reactor support url: https://docs.reactor.inc/resources/support servers: - url: https://api.reactor.inc description: Production security: - apiKey: [] tags: - name: Status description: >- Public, unauthenticated endpoints for service health, pricing, and the values the API accepts. - name: Tokens description: > Exchange a long-lived API key for a short-lived, session-scoped token that a client can use to create and operate sessions without holding the key. - name: Users description: > Read your own user record, your account's roster, and account memberships, and manage member roles as an account admin. - name: API Keys description: >- Revoke API keys. Use the [Dashboard](https://reactor.inc/dashboard) to list or create keys. The CLI can also create a key with `reactor auth login`. - name: Sessions description: > Create, inspect, and end sessions. A session holds one running model for one client application; media and messages flow over a transport you attach to it afterwards. - name: Transport description: > Attach a client to a session. WebRTC signaling carries ICE servers, SDP, and ICE candidates; a LiveKit room connection lets the session join a room you host. - name: Files description: > Upload files a model reads, either for one running session or ahead of time for sessions you have not started yet. - name: Recordings description: > Fetch the recorded video of a session as an HLS playlist, during the session or after it ends. - name: Accounts description: > Read and manage the account your credential acts in: its name and slug, its credit balance, its effective quotas, and its accelerator capacity. - name: Invitations description: > Invite people to your account by email, and manage pending invitations. The recipient accepts from the emailed link while signed in to the dashboard. - name: Usage description: > List the sessions your account has run, filter them by status, date, model, or API key, and read exact session totals for a date window. - name: Models description: > Register, read, update, and delete the models your account serves, and list the models you can use. The `reactor model` CLI commands are built on these endpoints. - name: Releases description: > Register a model's versioned releases, push their container image, and deploy a release with a per-region instance plan. - name: Model Weights description: > Upload and inspect the weights bundle of a release: single-request uploads, multipart uploads for large files, and the server-side finalize that marks a bundle complete. - name: Model Schemas description: > Attach an OpenAPI schema to a release that describes the model's commands, messages, and tracks. Schemas of public models are readable without credentials. - name: Model Access description: | Share a private model with other accounts, one environment at a time. - name: Projects description: > A project is the deploy identity of a model you serve on Reactor. Each model is one project, with its own UUID. Creating a project also creates its `production` environment. - name: Environments description: > An environment is a named deploy target of a project, such as `production` or `staging`. Each write to an environment creates its next revision, and the newest revision is what the environment runs. Environment access grants let another account start sessions on one environment. - name: Revisions description: > A revision is an immutable, numbered snapshot of one environment: its model image, weights, resources, instances, and variables. An environment's revisions, newest first, are its change log. - name: Images description: > Model images are the container images pushed to your model's repository, named by digest. Experimental: this API can change without notice. - name: Weight Sets description: > A weight set is a version-2 weights bundle, named by its set digest. Push the files, then put the manifest. Available when weight sets are enabled for your account. Experimental: this API can change without notice. - name: Tags description: > A tag is a movable name on one model image or one weight set of a project. A release of the model is a read-only tag. Experimental: this API can change without notice. paths: /accounts/{account_id}/models: parameters: - $ref: '#/components/parameters/AccountId' get: tags: - Models summary: List your account's models description: > Returns the models your account owns (`owned`, paged with `limit` and `offset`) and the models other accounts shared with it (`shared`, not paged). Deleted models are left out. Callable by an `account_admin` or `developer` of the account. Another account's ID returns `403`. `shared` rows have the public view: no `project_id` or GPU fields. Their `environments` lists the environments you were granted. operationId: listAccountModels parameters: - name: limit in: query required: false description: >- Page size of `owned`. Defaults to 50; values above 200 are clamped to 200. schema: type: integer minimum: 1 default: 50 - name: offset in: query required: false description: Rows of `owned` to skip. schema: type: integer minimum: 0 default: 0 responses: '200': description: The account's own and shared models. content: application/json: schema: $ref: '#/components/schemas/ModelAccountModels' example: owned: - id: 7b3f1bc2-a4e5-4d78-b9c1-0e6c2f9a1d34 name: your-org/your-model status: active created_at: '2025-05-11T21:46:40Z' is_public: false is_owned: true access_granted: false project_id: 0d3c6f4e-8a1b-4c2d-9e7f-1a2b3c4d5e6f is_gpu: true gpu_type: NVIDIA_H100 gpu_count: 1 shared: - id: c41a8e2d-3b7f-4a9c-b1d0-6e5f4a3b2c1d name: partner-org/partner-model status: active created_at: '2025-04-18T18:13:20Z' is_public: false is_owned: false access_granted: true environments: - production '400': description: >- `account_id` is not a UUID (`error` `invalid_request`, `reason` `invalid_id`), or `limit` or `offset` is invalid. content: application/json: schema: $ref: '#/components/schemas/Error' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' components: parameters: AccountId: name: account_id in: path required: true description: The account's ID. Use the `account_id` from `GET /me`. schema: type: string format: uuid schemas: ModelAccountModels: type: object required: - owned - shared properties: owned: type: array items: $ref: '#/components/schemas/ModelListItem' shared: type: array items: allOf: - $ref: '#/components/schemas/ModelListItem' - type: object properties: environments: type: array items: type: string description: The environments your account was granted. Error: type: object required: - error properties: error: type: string description: >- A stable error code (for example `not_found`) on newer routes, or a sentence on older ones. When `message` is present, branch on `error`. message: type: string description: >- A human-readable explanation. Do not parse it; its wording may change. resource: type: string description: The type of the resource a `not_found` refers to. reason: type: string description: >- A more specific cause for `failed_precondition`, `aborted`, and some `invalid_request` errors. ModelListItem: type: object required: - id - name - status - created_at - is_public - is_owned - access_granted properties: id: type: string format: uuid name: type: string description: The full `owner/name`. example: your-org/your-model description: type: string description: Omitted when empty. status: $ref: '#/components/schemas/ModelStatus' created_at: type: string format: date-time description: When it was created, as an RFC 3339 timestamp. example: '2026-01-15T10:30:00Z' is_public: type: boolean description: Whether every account may use the model. is_owned: type: boolean description: Whether your account owns the model. access_granted: type: boolean description: >- Whether the owner granted your account at least one environment of the model. project_id: type: string format: uuid description: The model's project. Only on models you manage. is_gpu: type: boolean description: Only on models you manage. gpu_type: type: string description: Only on models you manage. example: NVIDIA_H100 gpu_count: type: integer description: GPUs per instance. Only on models you manage. ModelStatus: type: string enum: - active - deprecated - disabled description: The model's status, always lowercase in responses. responses: Unauthorized: description: The credential is missing, invalid, or expired. content: application/json: schema: $ref: '#/components/schemas/Error' Forbidden: description: >- The credential is valid but may not perform this action, or the resource is outside the caller's permission boundary. A resource you cannot see returns `403` whether or not it exists. content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: apiKey: type: http scheme: bearer description: >- A Reactor API key (`rk_...`), sent as `Authorization: Bearer rk_...`. Keep it on a server. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.