Lyria 3.5 vs Grok 4.20 Multi Agent

At a Glance

Compare
Lyria 3.5Google DeepMind
Intelligence, Cost, and Efficiency
IntelligenceHigher is better · MM Intelligence v2.5UnrankedNot in the 46-model eligible cohort#22 of 4663.4 score · 2/3 sources · provisional · missing LiveBench · full-core range 42.3–75.6
Pricing and Limits
Input priceFrom · USD / 1M tokensNot reported$1.25Xai · Sep 3, 2026
Output priceFrom · USD / 1M tokensNot reported$2.50Xai · Sep 3, 2026
Context windowMaximum documented tokens1,049K1,000K
Model facts checkedSep 22, 2026View model evidence →Aug 29, 2026View model evidence →

Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →

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

FieldLyria 3.5Grok 4.20 Multi-Agent
DeveloperGoogle DeepMindxAI
FamilyLyriaGrok 4 20
ModelLyria 3.5Grok 4.20 Multi-Agent
VersionLyria 3.5Grok 4.20 Multi-Agent
Lifecycleactivepreview
Released2026-07-29Unknown
Knowledge cutoffUnknownUnknown
Input modalitiesText, ImageText, Image
Output modalitiesText, AudioText
Context window1,049K1,000K
Total parametersUnknownUnknown
Active parametersUnknownUnknown
LicenseUnknownUnknown
Open weightsNoNo
API availableYesYes
Self-hostableNoNo
Provider accessGoogle AI (Standard), Google Gemini (Standard)Xai (Standard)
Capabilitiesgeneration, image-to-music, lyrics, music-generation, synthid, vocalsgeneration, reasoning, research, tools

Lyria 3.5 Capabilities

generationimage-to-musiclyricsmusic-generationsynthidvocals
Serving providers2
Canonical IDlyria-3.5

Grok 4.20 Multi Agent Capabilities

generationreasoningresearchtools
Serving providers1
Canonical IDxai/grok-4.20-multi-agent-0309

Primary Evidence

Sources and Freshness

Questions

Lyria 3.5 vs Grok 4.20 Multi Agent FAQs

Is Lyria 3.5 or Grok 4.20 Multi Agent better for coding?+

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

Which is cheaper, Lyria 3.5 or Grok 4.20 Multi Agent?+

Only Grok 4.20 Multi Agent has a directly sourced input price: $1.25 per million tokens. Only Grok 4.20 Multi Agent has a directly sourced output price: $2.50 per million tokens.

Which has a larger context window, Lyria 3.5 or Grok 4.20 Multi Agent?+

Lyria 3.5 has the larger sourced context window. Lyria 3.5 supports 1,049K and Grok 4.20 Multi Agent supports 1,000K.

Which performs better in benchmarks, Lyria 3.5 or Grok 4.20 Multi Agent?+

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

Can Lyria 3.5 or Grok 4.20 Multi Agent be self-hosted?+

Both models have the same recorded self-hosting status: unsupported. Lyria 3.5 is not marked open weight; Grok 4.20 Multi Agent is not marked open weight.

Can Lyria 3.5 and Grok 4.20 Multi Agent understand images?+

Lyria 3.5 is documented with image input; Grok 4.20 Multi Agent is documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Lyria 3.5 or Grok 4.20 Multi Agent?+

Neither has a larger sourced maximum output. Lyria 3.5 is 66K and Grok 4.20 Multi Agent is —.

Do Lyria 3.5 and Grok 4.20 Multi Agent support reasoning and tool use?+

Lyria 3.5: image input. Grok 4.20 Multi Agent: reasoning, tool calling, and image input. Feature support does not establish relative quality.

Which is available from more inference providers, Lyria 3.5 or Grok 4.20 Multi Agent?+

Lyria 3.5 has 2 sourced provider routes; Grok 4.20 Multi Agent has 1, so Lyria 3.5 has broader tracked availability.

Which offers better value, Lyria 3.5 or Grok 4.20 Multi Agent?+

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