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

> Choose the hosted LIBERO variant of LingBot-VA.

LingBot-VA predicts robot actions from camera observations and a language task, conditioning later
predictions on the actions already executed. Reactor hosts inference; your application runs the
simulator or robot controller.

| Hosted variant | Model identifier | Observation and action contract |
| - | - | - |
| [LIBERO](/robotics/lingbot-va/libero/overview) | `reactor/lingbot-va` | Two cameras; 16 rows of six end-effector delta components and one gripper command |

The hosted variant uses LIBERO-Long post-training. The upstream
[LingBot-VA project](https://github.com/Robbyant/lingbot-va/tree/7c6ffa9bfc4b83582cafc860fab4c82cc7deeeeb)
also includes other embodiment configurations. Those configurations are not selectable through this
endpoint and do not share a hardware action contract automatically.

Start with [Get your first actions](/robotics/lingbot-va/libero/quickstart), then
[run LIBERO](/robotics/lingbot-va/libero/simulation) or review the
[robot integration requirements](/robotics/lingbot-va/libero/integration).


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