Lyria 3.5 vs GPT-5.2

At a Glance

Compare
Lyria 3.5Google DeepMind
GPT-5.2OpenAI
Intelligence, Cost, and Efficiency
IntelligenceHigher is better · MM Intelligence v2.5UnrankedNot in the 46-model eligible cohort#33 of 4649.3 score · 3/3 sources · complete
CostLower is better · Published-token output estimateUnrankedNot in the 44-model eligible cohort#28 of 44$0.161 per LiveBench case
EfficiencyHigher is better · MM Efficiency v1.5UnrankedNot in the 38-model eligible cohort#34 of 3844.0 score · 3/3 sources · complete
Pricing and Limits
Input priceFrom · USD / 1M tokensNot reported$1.75Openai · Sep 3, 2026
Output priceFrom · USD / 1M tokensNot reported$14.00Openai · Sep 3, 2026
Context windowMaximum documented tokens1,049K400K
Model facts checkedSep 22, 2026View model evidence →Sep 3, 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.5GPT-5.2
DeveloperGoogle DeepMindOpenAI
FamilyLyriaGpt 5 2
ModelLyria 3.5GPT-5.2
VersionLyria 3.5GPT-5.2
Lifecycleactiveactive
Released2026-07-292025-12-11
Knowledge cutoffUnknown2025-08-31
Input modalitiesText, ImageText, Image
Output modalitiesText, AudioText
Context window1,049K400K
Total parametersUnknownUnknown
Active parametersUnknownUnknown
LicenseUnknownUnknown
Open weightsNoNo
API availableYesYes
Self-hostableNoNo
Provider accessGoogle AI (Standard), Google Gemini (Standard)Openai (Standard), Openrouter (Standard)
Capabilitiesgeneration, image-to-music, lyrics, music-generation, synthid, vocalschat, generation, reasoning, structured_outputs, tools

Lyria 3.5 Capabilities

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

GPT-5.2 Capabilities

chatgenerationreasoningstructured outputstools
Serving providers2
Canonical IDopenai/gpt-5.2

Primary Evidence

Sources and Freshness

Questions

Lyria 3.5 vs GPT-5.2 FAQs

Is Lyria 3.5 or GPT-5.2 better for coding?+

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

Which is cheaper, Lyria 3.5 or GPT-5.2?+

Only GPT-5.2 has a directly sourced input price: $1.75 per million tokens. Only GPT-5.2 has a directly sourced output price: $14.00 per million tokens.

Which has a larger context window, Lyria 3.5 or GPT-5.2?+

Lyria 3.5 has the larger sourced context window. Lyria 3.5 supports 1,049K and GPT-5.2 supports 400K.

Which performs better in benchmarks, Lyria 3.5 or GPT-5.2?+

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 GPT-5.2 be self-hosted?+

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

Can Lyria 3.5 and GPT-5.2 understand images?+

Lyria 3.5 is documented with image input; GPT-5.2 is documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Lyria 3.5 or GPT-5.2?+

GPT-5.2 has the larger sourced maximum output: Lyria 3.5 supports 66K and GPT-5.2 supports 128K output tokens.

Do Lyria 3.5 and GPT-5.2 support reasoning and tool use?+

Lyria 3.5: image input. GPT-5.2: reasoning, tool calling, and image input. Feature support does not establish relative quality.

Which is available from more inference providers, Lyria 3.5 or GPT-5.2?+

Lyria 3.5 has 2 sourced provider routes; GPT-5.2 has 2, a tie.

Which offers better value, Lyria 3.5 or GPT-5.2?+

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