> ## 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=<slug>` scaffolds a complete app with secure auth wired up. Typed TypeScript SDKs are published as @reactor-models/<model>; 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.

# Get session totals

> Returns exact session counts and run time for one date window: a total, one entry per
UTC day, and one entry per model. Use it for counts and charts. The access rule is the
same as `GET /accounts/{account_id}/sessions`.

A session counts on the UTC day it was created, including all of its run time. A
closed session ran from `created_at` to `updated_at`; an open session runs until the
time of the request.

The window may be at most 366 days. A window holding more than 200,000 sessions
returns `422`, and a read longer than 20 seconds returns `504`. Neither returns partial
counts; use a narrower window.




## OpenAPI

````yaml /openapi.yaml get /accounts/{account_id}/sessions/stats
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}/sessions/stats:
    get:
      tags:
        - Usage
      summary: Get session totals
      description: >
        Returns exact session counts and run time for one date window: a total,
        one entry per

        UTC day, and one entry per model. Use it for counts and charts. The
        access rule is the

        same as `GET /accounts/{account_id}/sessions`.


        A session counts on the UTC day it was created, including all of its run
        time. A

        closed session ran from `created_at` to `updated_at`; an open session
        runs until the

        time of the request.


        The window may be at most 366 days. A window holding more than 200,000
        sessions

        returns `422`, and a read longer than 20 seconds returns `504`. Neither
        returns partial

        counts; use a narrower window.
      operationId: getAccountSessionStats
      parameters:
        - $ref: '#/components/parameters/AccountId'
        - name: after
          in: query
          required: true
          description: >-
            Inclusive lower bound on `created_at`, as a `YYYY-MM-DD` date read
            as midnight UTC.
          schema:
            type: string
            format: date
            example: '2026-10-01'
        - name: before
          in: query
          required: true
          description: >-
            Exclusive upper bound on `created_at`, as a `YYYY-MM-DD` date read
            as midnight UTC. At most 366 days after `after`.
          schema:
            type: string
            format: date
            example: '2026-11-01'
        - $ref: '#/components/parameters/AccountSessionModel'
      responses:
        '200':
          description: The session totals for the window.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AccountSessionStats'
              example:
                total: 10432
                by_day:
                  - day: '2026-10-01'
                    sessions: 312
                    seconds: 48120
                  - day: '2026-10-02'
                    sessions: 0
                    seconds: 0
                by_model:
                  - model: reactor/helios
                    sessions: 8001
                    seconds: 1200400
                  - model: your-org/your-model
                    sessions: 2431
                    seconds: 301877
        '400':
          description: >
            `invalid_request`: `account_id` is not a UUID, `after` or `before`
            is missing or not

            `YYYY-MM-DD`, `after` is not before `before`, or the window is
            longer than 366 days.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: invalid_request
                message: 'invalid window: must be at most 366 days'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '422':
          description: >-
            `session_stats_too_large`: the window holds more than 200,000
            sessions. Use a narrower window.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: session_stats_too_large
                message: >-
                  the window holds more than 200000 sessions; use a narrower
                  window
        '503':
          $ref: '#/components/responses/ServiceUnavailable'
        '504':
          description: >-
            `session_stats_timeout`: the read took longer than 20 seconds. Use a
            narrower window.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: session_stats_timeout
                message: >-
                  the session stats took too long to compute; use a narrower
                  window
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
    AccountSessionModel:
      name: model
      in: query
      required: false
      description: >-
        Exact, case-sensitive match on the session's model name, for example
        `reactor/helios`. Surrounding spaces are trimmed; an empty value means
        no filter.
      schema:
        type: string
        example: reactor/helios
  schemas:
    AccountSessionStats:
      type: object
      required:
        - total
        - by_day
        - by_model
      properties:
        total:
          type: integer
          format: int64
          description: Sessions created in the window, after the model filter.
        by_day:
          type: array
          description: >-
            One entry per UTC day in the window, oldest first, including days
            with no sessions.
          items:
            $ref: '#/components/schemas/AccountSessionDayStats'
        by_model:
          type: array
          description: >-
            One entry per model with sessions in the window, by `sessions`
            descending, then `model` ascending.
          items:
            $ref: '#/components/schemas/AccountSessionModelStats'
    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.
    AccountSessionDayStats:
      type: object
      properties:
        day:
          type: string
          format: date
          description: The UTC day.
        sessions:
          type: integer
          format: int64
          description: Sessions created that day.
        seconds:
          type: integer
          format: int64
          description: Total run time of those sessions in whole seconds.
    AccountSessionModelStats:
      type: object
      properties:
        model:
          type: string
          description: The model's name, for example `reactor/helios`.
        sessions:
          type: integer
          format: int64
          description: Sessions of this model in the window.
        seconds:
          type: integer
          format: int64
          description: Total run time of those sessions in whole seconds.
  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'
    ServiceUnavailable:
      description: A dependency is temporarily unavailable. Retry with backoff.
      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.