Robot and controller
Exact make, model, joints, end effectors, and local control API.
Robots
Start with the body, sensors, state, actions, and safety executor.
Mech is prelaunch. No public Operator route is represented as production-ready.
Cameras and state
Names, dimensions, capture rate, and state-vector order.
Action representation
Joint, end-effector, relative, absolute, and normalization rules.
Local authority
Limits, watchdogs, disconnect path, and safe state.
No robots defined
Add one exact embodiment before choosing a compatible VLA.
Operators
VLA candidates become Operators only for qualified robot routes.
Qualification targetsnot callable
| Checkpoint family | Known route | Output | Mech status |
|---|---|---|---|
| π0.5 | Checkpoint-specific | Action chunk | Qualification |
| MolmoAct2 | Embodiment-specific | Action chunk | Qualification |
| SmolVLA | LeRobot bodies | Action chunk | Qualification |
| Your checkpoint | Your robot | Your schema | Request |
Episodes
Closed-loop evidence from a connected robot, simulator, or Station.
0
real episodes
—
task success
—
p99 round trip
0
safe disconnect tests
No episodes
Static frames can inspect an action schema. Only a closed-loop run can test an Operator.
Deployments
Release a qualified Operator through cloud, customer cloud, or edge.
Exact robot, checkpoint, and adapter.
Cloud region, private cloud, or edge.
Latency, disconnect, cost, and behavior.
Stage, observe, promote, or roll back.
No deployable route
A catalog entry cannot bind a deployment until the exact model-to-robot route passes qualification.