The upstream model card describes
the DROID policy and its checkpoint variants. Compatibility requires the DROID camera, state, and
action conventions, not only a seven-joint arm.
Checkpoint choices
For a first run, use the available default returned by
get_checkpoint, as the quickstart does. To
select another checkpoint, call get_checkpoint and inspect checkpoint_selected.available before
selecting. The schema enumerates six choices, but a worker may expose only a subset.
select_checkpoint pins the choice for the session. Repeating that choice is accepted; changing it
requires a new session, including after reset. If no selection is made, the first valid request
pins the default; inspect the reported choice rather than assuming availability.
Checkpoint labels identify model variants and precision, not an end-to-end latency guarantee.
Evaluate task quality and capture-to-execution latency in your own setup.
Request your first actions, then implement the
simulator bridge. Use the
API reference for exact fields and payloads.