When to use it
Use it when the capture room is live.
The teleop server is optional for Robotics Studio Open. Use it when a full operator cell needs realtime video, observer roles, and a clean handoff into reviewed clips.
Live review
observer token
Safety reviewers can join as read-only observers while the operator continues the task.
Routing
LiveKit room
Operator, coach, and reviewer channels stay separated while the session remains one auditable object.
Handoff
clip pipeline
Approved clips can feed Robotics Studio review queues or the commercial Robotics Studio Cloud surface.
Native logs
MCAP · ROSbag
Mirror a session into existing telemetry without forcing a new robot-side stack.
Lifecycle
One session becomes reviewed clips.
The API creates a session, returns room credentials, and emits clips to the scoring/review pipeline when the room closes.
// 1. Create a session
// Base URL: https://api.auraone.ai
// Auth: Authorization: Bearer <API_KEY> (scope: robotics:write)
POST /v1/robotics/sessions
Authorization: Bearer sk_live_...
Content-Type: application/json
{
"task_brief_id": "tb_01J...",
"operator_id": "op_01J...",
"tier": 4
}
// 2. Server returns a LiveKit room token
{
"session_id": "sess_01J...",
"room_url": "wss://...",
"token": "ey..."
}
// 3. Operator cell connects; reviewer joins as observer
// 4. On end, clips emit to the scoring pipeline, each carrying
// its consent, license scope, safety signals, and provenance
// 5. Approved clips land in review; rejected clips land in the regression bankBoundary
Robotics Studio Open does not require this server.
Local dataset review works without a hosted teleop stack. If your team already has capture infrastructure, feed Robotics Studio exported datasets or reviewed clips through the SDK and keep this server out of the path.