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.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 currentrobotics/sim/notebooks/ directory:
actions: (16, 60) and 12 active values in the printed simulator action. The first execution
echo is required even though no actions have been executed. The model waits for at least four
complete camera sets while the helper continues publishing.
Constant synthetic images and zero state check connectivity and reply shape; do not execute these
outputs on hardware. Repeating frames is appropriate only for this artificial static history. A
rollout requires aligned camera and state history.
Printed timing starts at the execution echo, excluding connection and frame warmup. Next, use the
integration guide and
history contract.