Choose an action policy
Each embodiment has its own variant guide, which defines its camera setup, observation and action contract, and integration requirements. Matching tensor dimensions alone does not establish compatibility with a different robot.More action policies are coming soon.
Try it with your robot or simulator
Start with your chosen policy’s quickstart to install the Python client and send an example request. The example uses test inputs so you can try the API before connecting cameras or a robot. Once you can send inputs and receive actions, evaluate a task in simulation or on a physical robot using observations from your setup. For simulation, follow your chosen model’s simulation guide. Each guide explains the simulator setup and whether it includes runnable connection code or describes the adapter you need to build. When you’re ready to use a physical robot, follow the model’s integration guide to send camera images and robot state, then pass the returned actions to your controller. Your application then controls when the robot moves and enforces its safety limits. The model’s API reference covers the exact inputs, action format, and settings you’ll use along the way.Simulation
These models generate visual observations; the action policies above predict robot actions. See the Simulation guides to get started.
Prices are in USD per minute of session time, metered per second—not per minute of generated video.
See Pricing & Billing for billing and session termination details.