Skip to main content
Request one DreamZero YAM 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 actions: (24, 14) and 14 numeric values for the first row. The synthetic observations check connectivity and reply shape; do not execute their outputs on hardware. The helper repeats fixture images for this check. Use actual camera samples for an integration: repeated images can erase useful temporal history. The 15 fps setting is video publishing, not robot control cadence. See integration. Printed timing excludes session startup and the half-second settling wait, which does not guarantee synchronization. inference_seconds also excludes client transport. Next, use the integration guide or build a YAM simulator adapter. For missing replies, see troubleshooting.