Lyria 3.5 vs PII Tracer

At a Glance

Compare
Lyria 3.5Google DeepMind
PII TracerPerplexity
Pricing and Limits
Context windowMaximum documented tokens1,049K4K
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.5PII-Tracer
DeveloperGoogle DeepMindPerplexity
FamilyLyriaPii Tracer
ModelLyria 3.5PII-Tracer
VersionLyria 3.5PII-Tracer
Lifecycleactiveactive
Released2026-07-292026-09-01
Knowledge cutoffUnknownUnknown
Input modalitiesText, ImageText
Output modalitiesText, AudioText
Context window1,049K4K
Total parametersUnknown596.1M
Active parametersUnknownUnknown
LicenseUnknownmit
Open weightsNoYes
API availableYesNo
Self-hostableNoYes
Provider accessGoogle AI (Standard), Google Gemini (Standard)Unknown
Capabilitiesgeneration, image-to-music, lyrics, music-generation, synthid, vocalsclassification, pii-detection, redaction, sensitivity-classification, token-classification

Lyria 3.5 Capabilities

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

PII Tracer Capabilities

classificationpii-detectionredactionsensitivity-classificationtoken-classification
Serving providers0
Canonical IDperplexity-ai/pplx-pii-masking

Primary Evidence

Sources and Freshness

Questions

Lyria 3.5 vs PII Tracer FAQs

Is Lyria 3.5 or PII Tracer better for coding?+

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

Which is cheaper, Lyria 3.5 or PII Tracer?+

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, Lyria 3.5 or PII Tracer?+

Lyria 3.5 has the larger sourced context window. Lyria 3.5 supports 1,049K and PII Tracer supports 4K.

Which performs better in benchmarks, Lyria 3.5 or PII Tracer?+

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 PII Tracer be self-hosted?+

PII Tracer is the only model in this pair currently marked as self-hostable. Lyria 3.5 is not marked open weight; PII Tracer is open weight.

Can Lyria 3.5 and PII Tracer understand images?+

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

Which can generate longer answers, Lyria 3.5 or PII Tracer?+

Neither has a larger sourced maximum output. Lyria 3.5 is 66K and PII Tracer is —.

Do Lyria 3.5 and PII Tracer support reasoning and tool use?+

Lyria 3.5: image input. PII Tracer: none of these features are definitively sourced. Feature support does not establish relative quality.

Which is available from more inference providers, Lyria 3.5 or PII Tracer?+

Lyria 3.5 has 2 sourced provider routes; PII Tracer has 0, so Lyria 3.5 has broader tracked availability.

Which offers better value, Lyria 3.5 or PII Tracer?+

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