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

# LingBot-VA LIBERO

> Two-camera, action-conditioned inference for the LIBERO embodiment.

LingBot-VA LIBERO takes an external camera, a wrist camera, and a language task. It returns a chunk
of end-effector delta commands and uses the executed actions and observed video to predict the next
chunk. It has no proprioception input or generated-video output on this endpoint.

| Property | Value |
| - | - |
| Model identifier | `reactor/lingbot-va` |
| Upstream checkpoint | [LingBot-VA posttrain LIBERO-Long](https://huggingface.co/robbyant/lingbot-va-posttrain-libero-long) |
| Reference embodiment | LIBERO's Panda arm, gripper, and `OSC_POSE` controller |
| Input tracks | `agentview`, `eye_in_hand`; RGB, 128 × 128 reference resolution |
| Output | `(16, 7)` action chunk; first episode chunk has four conditioning rows to skip |
| Reference control rate | 20 Hz: 0.6 seconds for the first 12 executed rows, 0.8 seconds for subsequent 16-row chunks |
| Documented model release | `0.2.3`; see [release notes](/robotics/lingbot-va/libero/changelog) |

The control rate describes execution, not inference throughput. Replies arrive after inference and
transport delay; the reference simulator pauses between chunks.

| Path | What is provided |
| - | - |
| First actions | Synthetic camera fixtures and a Python client; no local model weights |
| Simulation | A LIBERO/robosuite environment and Reactor bridge |
| Physical robot | Contract and adapter guidance; no validated hardware driver, IK implementation, or calibrated mapping |

Follow [Get your first actions](/robotics/lingbot-va/libero/quickstart), then
[simulation](/robotics/lingbot-va/libero/simulation) or
[robot integration](/robotics/lingbot-va/libero/integration). The
[reference](/robotics/lingbot-va/libero/reference) defines the wire and action semantics.


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