Lyria 3.5 vs Ternary Bonsai 2 27B

At a Glance

Compare
Lyria 3.5Google DeepMind
Pricing and Limits
Input priceFrom · USD / 1M tokensNot reported$0.075Openrouter · Sep 22, 2026
Output priceFrom · USD / 1M tokensNot reported$0.50Openrouter · Sep 22, 2026
Context windowMaximum documented tokens1,049K262K
Model facts checkedSep 22, 2026View model evidence →Sep 18, 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.5Ternary Bonsai 2 27B
DeveloperGoogle DeepMindPrismML
FamilyLyriaBonsai 2
ModelLyria 3.5Ternary Bonsai 2 27B
VersionLyria 3.5Ternary Bonsai 2 27B
Lifecycleactiveactive
Released2026-07-292026-09-17
Knowledge cutoffUnknownUnknown
Input modalitiesText, ImageText, Image
Output modalitiesText, AudioText
Context window1,049K262K
Total parametersUnknown27.4B
Active parametersUnknownUnknown
LicenseUnknownapache-2.0
Open weightsNoYes
API availableYesYes
Self-hostableNoYes
Provider accessGoogle AI (Standard), Google Gemini (Standard)Openrouter (Standard)
Capabilitiesgeneration, image-to-music, lyrics, music-generation, synthid, vocalschat, generation, reasoning, tools, vision
Base modelUnknownQwen3.8 27B
Effective bit widthUnknown1.76 bits per weight
Language model sizeUnknown5.93 GB
Weight formatUnknownTernary g128 with FP16 group scales

Lyria 3.5 Capabilities

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

Ternary Bonsai 2 27B Capabilities

chatgenerationreasoningtoolsvision
Serving providers1
Canonical IDprism-ml/Ternary-Bonsai-2-27B

Primary Evidence

Sources and Freshness

Questions

Lyria 3.5 vs Ternary Bonsai 2 27B FAQs

Is Lyria 3.5 or Ternary Bonsai 2 27B better for coding?+

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

Which is cheaper, Lyria 3.5 or Ternary Bonsai 2 27B?+

Only Ternary Bonsai 2 27B has a directly sourced input price: $0.075 per million tokens. Only Ternary Bonsai 2 27B has a directly sourced output price: $0.50 per million tokens.

Which has a larger context window, Lyria 3.5 or Ternary Bonsai 2 27B?+

Lyria 3.5 has the larger sourced context window. Lyria 3.5 supports 1,049K and Ternary Bonsai 2 27B supports 262K.

Which performs better in benchmarks, Lyria 3.5 or Ternary Bonsai 2 27B?+

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 Ternary Bonsai 2 27B be self-hosted?+

Ternary Bonsai 2 27B is the only model in this pair currently marked as self-hostable. Lyria 3.5 is not marked open weight; Ternary Bonsai 2 27B is open weight.

Can Lyria 3.5 and Ternary Bonsai 2 27B understand images?+

Lyria 3.5 is documented with image input; Ternary Bonsai 2 27B is documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Lyria 3.5 or Ternary Bonsai 2 27B?+

Neither has a larger sourced maximum output. Lyria 3.5 is 66K and Ternary Bonsai 2 27B is —.

Do Lyria 3.5 and Ternary Bonsai 2 27B support reasoning and tool use?+

Lyria 3.5: image input. Ternary Bonsai 2 27B: reasoning, tool calling, and image input. Feature support does not establish relative quality.

Which is available from more inference providers, Lyria 3.5 or Ternary Bonsai 2 27B?+

Lyria 3.5 has 2 sourced provider routes; Ternary Bonsai 2 27B has 1, so Lyria 3.5 has broader tracked availability.

Which offers better value, Lyria 3.5 or Ternary Bonsai 2 27B?+

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