Skip to main content
Request one LIBERO action chunk using synthetic observations.

Install the reference client

New to Reactor? How the API works explains the session, camera streams, commands, and action messages used below. You need Python 3.12, uv, a Reactor API key, and Reactor’s public cookbook. The client code is public; your Reactor account still needs access to the selected hosted model. No local model weights or GPU are required for this example.
Run the example below from robotics/sim/notebooks/. This environment installs the Python SDK (reactor-sdk, imported as reactor_sdk) and the reactor_robotics helper directory in Reactor’s public cookbook. The helpers provide camera publishing and message queues; they are separate from the SDK. Keep your API key in the environment. On Linux, the published glibc wheel requires glibc 2.34 or newer. The default endpoint is https://api.reactor.inc; REACTOR_API_URL overrides it. Examples select a model by slug, not a frozen release; check its release notes when the deployed contract changes. If setup or connection fails, see first-run troubleshooting.

Request a chunk

Run the cookbook example from the current robotics/sim/notebooks/ directory:
Expect action shape: (16, 7) and executable shape: (12, 7). The first four rows are conditioning slots, not predicted motion. Synthetic images check connectivity and reply shape; do not execute the outputs on hardware. The example starts a fresh session and sets the task after reset, preventing an earlier task from triggering a seed chunk. Timing excludes connection setup and the 300 ms frame wait. A fixed sampling seed does not fix video delivery or observation timing. Next, run LIBERO or follow the execution protocol in your own integration.