> ## 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.

# Praxis-1 YAM

> Bimanual end-effector pose actions from Praxis-1 for two YAM arms.

Praxis-1 YAM predicts a chunk of end-effector pose targets and gripper targets for two arms. Its
inputs are a top camera, two wrist cameras, the measured pose and gripper of each arm, and a task
instruction. Reactor runs inference, and your application executes the returned targets.

## Model information

| Property | Value |
| - | - |
| Model identifier | `reactor/praxis-1-yam` |
| Family | [Praxis-1](https://docs.reactor.inc/robotics/praxis/overview) |
| Reference embodiment | Bimanual YAM: two YAM arms with grippers |
| Inputs | Three RGB camera tracks, both arms' measured end-effector poses and grippers, and a task instruction |
| Outputs | Absolute end-effector pose and gripper targets for each arm, one row per control step at 15 Hz. A chunk has 24 rows (1.6 seconds of motion). |
| Session price | **\$0.030/min**, metered per second. See [Pricing & Billing](https://docs.reactor.inc/resources/billing.md). |

The model identifier, `reactor/praxis-1-yam`, selects the YAM variant. Other Praxis-1 checkpoints
and robot embodiments do not inherit this observation and action contract. Matching the number of
input and output values does not establish compatibility: camera placement, pose frame, gripper
convention, and training distribution must match.

## Use the model

Start with [Get your first actions](https://docs.reactor.inc/robotics/praxis/yam/quickstart.md), then choose
[simulation](https://docs.reactor.inc/robotics/praxis/yam/simulation.md) or [robot
integration](https://docs.reactor.inc/robotics/praxis/yam/integration.md). The [reference](https://docs.reactor.inc/robotics/praxis/yam/reference.md)
specifies the wire contract. [Runway's Praxis-1 repository](https://github.com/runwayml/praxis-1)
describes the model and its training.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.