Lyria 3.5 vs Inkling
At a Glance
| Compare | Lyria 3.5Google DeepMind | InklingThinking Machines Lab |
|---|---|---|
| Intelligence, Cost, and Efficiency | ||
| IntelligenceHigher is better · MM Intelligence v4.4 | UnrankedNot in the 57-model eligible cohort | #27 of 5747.4 score · 3/3 sources · complete |
| CostLower is better · Published-token output estimate | UnrankedNot in the 27-model eligible cohort | #13 of 27$0.090 per LiveBench case |
| EfficiencyHigher is better · MM Efficiency v1.9 | UnrankedNot in the 27-model eligible cohort | #22 of 2742.0 score · 3/3 sources · complete |
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | Not reported | $0.95Deepinfra ↗ · Oct 15, 2026 |
| Output priceFrom · USD / 1M tokens | Not reported | $4.05Deepinfra ↗ · Oct 15, 2026 |
| Context windowMaximum documented tokens | 1,049K | 1,049K |
| Model facts checked | Oct 19, 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
Side-by-Side Facts
| Field | Lyria 3.5 | Inkling |
|---|---|---|
| Developer | Google DeepMind | Thinking Machines Lab |
| Family | Lyria | Inkling |
| Model | Lyria 3.5 | Inkling |
| Version | Lyria 3.5 | Inkling |
| Lifecycle | active | active |
| Released | 2026-07-29 | 2026-07-15 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text, Image | Text, Image, Video, Audio |
| Output modalities | Text, Audio | Text |
| Context window | 1,049K | 1,049K |
| Total parameters | Unknown | 975B |
| Active parameters | Unknown | 41B |
| License | Unknown | apache-2.0 |
| Open weights | No | Yes |
| API available | Yes | Yes |
| Self-hostable | No | Yes |
| Provider access | Google AI (Standard), Google Gemini (Standard) | Deepinfra (Standard), Fireworks Ai (Standard), Openrouter (Standard), Together Ai (Standard) |
| Capabilities | generation, image-to-music, lyrics, music-generation, synthid, vocals | agents, chat, coding, generation, reasoning, tools, vision |
Lyria 3.5 Capabilities
Inkling Capabilities
Primary Evidence
Sources and Freshness
Questions
Lyria 3.5 vs Inkling FAQs
Is Lyria 3.5 or Inkling better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Lyria 3.5 and Inkling, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Lyria 3.5 or Inkling?+
Only Inkling has a directly sourced input price: $0.95 per million tokens. Only Inkling has a directly sourced output price: $4.05 per million tokens.
Which has a larger context window, Lyria 3.5 or Inkling?+
Both models have the same sourced context window: 1,048,576 tokens each.
Which performs better in benchmarks, Lyria 3.5 or Inkling?+
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 Inkling be self-hosted?+
Inkling is documented as self-hostable; Lyria 3.5 is documented as not self-hostable. Lyria 3.5 is not marked open weight; Inkling is open weight.
Can Lyria 3.5 and Inkling understand images?+
Lyria 3.5 is documented with image input; Inkling is documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Lyria 3.5 or Inkling?+
Lyria 3.5 has a sourced maximum output of 65,536 tokens; Inkling's maximum output is not reported. A larger limit cannot be determined.
Do Lyria 3.5 and Inkling support reasoning and tool use?+
Lyria 3.5: image input. Inkling: reasoning, tool calling, and image input. Feature support does not establish relative quality.
Which is available from more inference providers, Lyria 3.5 or Inkling?+
Lyria 3.5 has 2 sourced provider routes; Inkling has 4, so Inkling has broader tracked availability.
Which offers better value, Lyria 3.5 or Inkling?+
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.