Skip to main content
Cyberwave doesn’t have one API per robot. Every device, whether an arm, a quadruped, a rover, a drone or a camera, becomes a digital twin. What a twin can do comes from its capabilities, declared once in the catalog, not from its brand. Two arms from different vendors take the same calls. A quadruped with a camera gets both the locomotion and the camera methods.

​
Capabilities, not brands

When you call cw.twin("<vendor>/<model>"), the SDK reads the asset’s capabilities and returns a twin with the matching methods: Capabilities combine. Everything above the hardware works the same whatever the form factor: environments, simulation, controllers, workflows, recording and AI models.

​
From twin to hardware, one path

You can build and test against the twin before the hardware arrives. When it does, cyberwave pair on the edge device starts the robot’s driver, and the same twin now mirrors the real machine. Your code switches with cw.affect("live").

​
How well is a device supported?

Support is measured in levels, from “you can see it” to “you can train a policy on it”: The compatibility table lists every supported device. How a robot moves up the levels: Add your robot.

Robotic arms

SO-101, Universal Robots, AgileX Piper, OpenArm and more.

Quadrupeds and rovers

Unitree Go2, Boston Dynamics Spot and other mobile robots.

Drones

DJI Mini 3 Pro, DJI Mini 4 Pro, PX4 Vision.

Cameras and sensors

USB, RTSP and GigE Vision cameras, RealSense depth cameras.

​
Next steps

Is my robot supported?

Every supported device, by form factor.

Add your robot

From a URDF and a ROS 2 driver to a fully supported robot.