Helix 02Figure source ↗Helix 02 vs pi 0.7
At a Glance
| Compare | Helix 02Figure | pi 0.7Physical Intelligence |
|---|---|---|
| Pricing and Limits | ||
| Context windowMaximum documented tokens | Not reported | Not reported |
| Model facts checked | Aug 29, 2026View model evidence → | Aug 29, 2026View model evidence → |
Available Benchmarks
Helix 02Figure source ↗
pi 0.7Physical Intelligence source ↗Side-by-Side Facts
| Field | Helix 02 | pi 0.7 |
|---|---|---|
| Developer | Figure | Physical Intelligence |
| Family | Helix | pi |
| Model | Helix 02 | pi 0.7 |
| Version | 02 | 0.7 |
| Lifecycle | active | active |
| Released | 2026-01-05 | 2026-04-16 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text, Image, Robot state | Text, Image, Robot state |
| Output modalities | Robot action | Robot action |
| Context window | Unknown | Unknown |
| Total parameters | Unknown | Unknown |
| Active parameters | Unknown | Unknown |
| License | Unknown | Unknown |
| Open weights | No | No |
| API available | No | Unknown |
| Self-hostable | No | Unknown |
| Provider access | Unknown | Unknown |
| Capabilities | dexterous-manipulation, long-horizon-control, tactile-control, whole-body-control | cross-embodiment, dexterous-manipulation, language-steering, visual-subgoals |
| Robotics model type | Vision-language-action model | Vision-language-action model |
| Action representation | Full-body joint targets | Continuous robot actions conditioned by multimodal prompts |
| Control architecture | Semantic reasoning, visuomotor policy, and kHz whole-body controller | High-level policy, world model, and action expert |
| Inference location | On device | Unknown |
| Native control rate (Hz) | Unknown | Unknown |
| Supported embodiments | Figure 03 | mobile manipulators, bimanual UR5e, multiple fixed manipulators |
| Training data | Figure reports more than 1,000 hours of human motion data plus sim-to-real reinforcement learning for its whole-body controller. | Robot demonstrations, autonomous data, egocentric human data, and multimodal web data described by the publisher. |
Helix 02 Capabilities
pi 0.7 Capabilities
Primary Evidence
Sources and Freshness
Questions
Helix 02 vs pi 0.7 FAQs
Is Helix 02 or pi 0.7 better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Helix 02 and pi 0.7, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Helix 02 or pi 0.7?+
Neither model has a directly sourced input price in this comparison. Neither model has a directly sourced output price in this comparison.
Which has a larger context window, Helix 02 or pi 0.7?+
Neither model has a sourced context window in this comparison, so a larger limit cannot be determined.
Which performs better in benchmarks, Helix 02 or pi 0.7?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Helix 02 or pi 0.7 be self-hosted?+
Helix 02's sourced self-hosting status is unsupported; pi 0.7's is unknown. An unknown status does not establish support or lack of support. Helix 02 is not marked open weight; pi 0.7 is not marked open weight.
Can Helix 02 and pi 0.7 understand images?+
Helix 02 is documented with image input; pi 0.7 is documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Helix 02 or pi 0.7?+
Neither model has a sourced maximum output in this comparison, so a larger limit cannot be determined.
Do Helix 02 and pi 0.7 support reasoning and tool use?+
Helix 02: image input. pi 0.7: image input. Feature support does not establish relative quality.
Which is available from more inference providers, Helix 02 or pi 0.7?+
Helix 02 has 0 sourced provider routes; pi 0.7 has 0, a tie.
Which offers better value, Helix 02 or pi 0.7?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.