DOCUMENTATION / INVITED PREVIEW
Start with your workspace.
A practical guide to the features available today: project data, diagnostic training, model candidates, evaluation recordings, and resource API access.
01 / Activate and sign in
Your project administrator provides a username and one-time invitation code. Open the console, select “Have an invitation? Activate your account,” create a password of at least 12 characters, and sign in.
Invitations expire after 24 hours and can be used once. Public registration and billing are not available. Owners can manage their authorized projects; viewers can inspect them. Session validity is separate from an experiment's compute budget.
Open console ↗02 / Explore project resources
| PAGE | AVAILABLE TODAY | CURRENT SCOPE |
|---|---|---|
| Datasets | View records; owners can upload JSON demonstrations | 16 MiB limit; large-video uploads are in development |
| Training jobs | Inspect jobs; owners can submit diagnostics or request cancellation | Fixed VPP2 dataset, one GPU, 1–20 update steps |
| Models | Inspect checkpoints, deployment state, and approval | No automatic candidate promotion |
| Evaluations | Review paired outcomes and original recordings | Small diagnostic samples, not an independent benchmark |
| Runs & videos | Inspect simulation runs and three camera views | Original simulation recordings |
| API keys | Create and revoke project resource read keys | Public policy-inference writes are not enabled |
03 / Run a diagnostic experiment
Owners can submit the fixed output-head recipe from Training jobs. It uses four prepared reference training episodes and two held-out episodes. Uploading another JSON dataset does not make it compatible with that recipe.
Training requires sufficient time in the existing four-hour experiment budget. An inactive or expired budget rejects the request. A user must explicitly start a new experiment through the existing terminal workflow; the web console does not renew budgets automatically.
queued means waiting. completed means execution and artifact checks finished; it does not establish task success. After a cancellation request, verify cleanup before treating the process as stopped.
04 / Use the resource API
An owner can create a read key under API keys. Save it when it is displayed, because its plaintext value is shown only once. Revoke and replace a lost key. Keys can read only projects assigned to their account.
curl 'https://openembody.ai/api/v1/models?project_id=<PROJECT_ID>' \
-H 'Authorization: Bearer <YOUR_READ_KEY>'Supported resource collections: robots, datasets, jobs, models, runs, evaluations, programs, program-runs, and memory.
Public policy inference is not enabled yet. Windows and Debian installers will be provided after build and installation validation. The invited web console requires no client installation.
05 / Read evaluation evidence
Paired evaluations retain the baseline, candidate, seed, native outcome, cleanup status, and audit references. Original recordings include the head camera and both wrist cameras. The comparison view shows seed 0 at normal playback speed.
The October 20, 2026 diagnostic recorded baseline 0/2 and candidate 0/2 successful episodes. No improvement was established. Independent layouts, larger samples, and reliable collision metrics remain to be completed.
The interface uses English. Original uploaded records, names, source code, and diagnostic messages remain available unchanged in resource details.
06 / Release notes and feedback
October 20, 2026 — Invited preview. Website, account activation, project resources, fixed-recipe training controls, read keys, and protected evaluation videos are available. The interface now uses an English research-platform visual style.
Additional policy backends, full assisted self-improvement, and physical robot execution remain separate milestones. Applications, accounts, files, and computation are hosted on server 153; Los Angeles provides HTTPS ingress.
For feedback, contact the administrator who issued your invitation. Include the resource ID, time, and visible error. Keep passwords, complete keys, and invitation codes private.