Helix 02 vs Lyria 3.5

At a Glance

Compare
Helix 02Figure
Lyria 3.5Google DeepMind
Pricing and Limits
Context windowMaximum documented tokensNot reported1,049K
Model facts checkedAug 29, 2026View model evidence →Sep 22, 2026View model evidence →
Different Model RolesThese models do not share a sourced market category. Their primary-source facts remain comparable below, while performance claims require matched evidence.

Available Benchmarks

All benchmark results →
No Protocol-Matched Benchmark Yet.Results appear here only when both models share the same benchmark version, metric, evaluation protocol, and evidence class.

Side-by-Side Facts

FieldHelix 02Lyria 3.5
DeveloperFigureGoogle DeepMind
FamilyHelixLyria
ModelHelix 02Lyria 3.5
Version02Lyria 3.5
Lifecycleactiveactive
Released2026-01-052026-07-29
Knowledge cutoffUnknownUnknown
Input modalitiesText, Image, Robot stateText, Image
Output modalitiesRobot actionText, Audio
Context windowUnknown1,049K
Total parametersUnknownUnknown
Active parametersUnknownUnknown
LicenseUnknownUnknown
Open weightsNoNo
API availableNoYes
Self-hostableNoNo
Provider accessUnknownGoogle AI (Standard), Google Gemini (Standard)
Capabilitiesdexterous-manipulation, long-horizon-control, tactile-control, whole-body-controlgeneration, image-to-music, lyrics, music-generation, synthid, vocals
Robotics model typeVision-language-action modelUnknown
Action representationFull-body joint targetsUnknown
Control architectureSemantic reasoning, visuomotor policy, and kHz whole-body controllerUnknown
Inference locationOn deviceUnknown
Native control rate (Hz)UnknownUnknown
Supported embodimentsFigure 03Unknown
Training dataFigure reports more than 1,000 hours of human motion data plus sim-to-real reinforcement learning for its whole-body controller.Unknown

Helix 02 Capabilities

dexterous-manipulationlong-horizon-controltactile-controlwhole-body-control
Model typeVision-language-action model
InferenceOn device
Action representationFull-body joint targets
Supported embodiments1
Canonical IDfigure/helix-02

Lyria 3.5 Capabilities

generationimage-to-musiclyricsmusic-generationsynthidvocals
Model typeUnknown
InferenceUnknown
Action representationUnknown
Supported embodimentsUnknown
Canonical IDlyria-3.5

Primary Evidence

Sources and Freshness

Questions

Helix 02 vs Lyria 3.5 FAQs

Is Helix 02 or Lyria 3.5 better for coding?+

This comparison does not currently contain a protocol-matched coding benchmark for both Helix 02 and Lyria 3.5, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.

Which is cheaper, Helix 02 or Lyria 3.5?+

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 Lyria 3.5?+

Neither model has a larger sourced context window in this comparison. Helix 02 is — and Lyria 3.5 is 1,049K.

Which performs better in benchmarks, Helix 02 or Lyria 3.5?+

There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.

Can Helix 02 or Lyria 3.5 be self-hosted?+

Both models have the same recorded self-hosting status: unsupported. Helix 02 is not marked open weight; Lyria 3.5 is not marked open weight.

Can Helix 02 and Lyria 3.5 understand images?+

Helix 02 is documented with image input; Lyria 3.5 is documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Helix 02 or Lyria 3.5?+

Neither has a larger sourced maximum output. Helix 02 is — and Lyria 3.5 is 66K.

Do Helix 02 and Lyria 3.5 support reasoning and tool use?+

Helix 02: image input. Lyria 3.5: image input. Feature support does not establish relative quality.

Which is available from more inference providers, Helix 02 or Lyria 3.5?+

Helix 02 has 0 sourced provider routes; Lyria 3.5 has 2, so Lyria 3.5 has broader tracked availability.

Which offers better value, Helix 02 or Lyria 3.5?+

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.

Send Feedback