LFM3-1.7B vs Palmyra X6

Liquid AI · US  |  Writer · US · Updated June 2026

Quick verdict

Pick LFM3-1.7B for very small open-weight text model - about 1.73b parameters with a 256k-token context for on-device use or liquid says it can power agentic applications that used to need 9b parameters. Pick Palmyra X6 for enterprise agentic workflows - built specifically for marketing/revenue teams running multi-step agents or writer says its harness upgrades cut agent-workflow token costs by roughly 52% and improve speed by roughly 48% (writer's own figures). Choose LFM3-1.7B if you need self-hosting or data privacy; Palmyra X6 if you want a managed API.

LFM3-1.7B (Liquid AI) and Palmyra X6 (Writer) are two of the models people most often weigh against each other in 2026. LFM3-1.7B is liquid AI's October 27, 2026 on-device text model - about 1.73B parameters and 256K context, with open weights under a license capped at $10M annual revenue. Palmyra X6 is writer's enterprise agentic flagship - a GLM-5.2-based model with harness upgrades Writer says cut agent token costs by roughly half. They diverge most on context window and open vs. closed weights — each quantified below from the models' real specs.

Key differences at a glance

Side-by-side specs

SpecLFM3-1.7BPalmyra X6
ProviderLiquid AI (US) Writer (US)
ReleasedOctober 27, 2026 August 13, 2026
Context window256K tokens (~384 pages) 128K (~192 pages)
Price (in/out)Open weight (self-host / free) Not published
Open weight?Yes — self-hostable No — API only
Modalitiestext text, code
SWE-Bench VerifiedNot published Not published
MRCR v2 @ 1MNot published Not published

Who wins what

Very small open-weight text model - about 1.73B parameters with a 256K-token context for on-device use

LFM3-1.7B

Its 256K tokens window holds about 2× more than Palmyra X6's 128K in a single prompt.

Liquid says it can power agentic applications that used to need 9B parameters

LFM3-1.7B

Liquid AI's October 27, 2026 on-device text model - about 1.73B parameters and 256K context, with open weights under a license capped at $10M annual revenue — and it carries the larger 256K tokens context.

Part of a six-model LFM3 family covering text, vision, audio, omni and decision tasks

LFM3-1.7B

Liquid AI's October 27, 2026 on-device text model - about 1.73B parameters and 256K context, with open weights under a license capped at $10M annual revenue — and its weights are open while Palmyra X6 is API-only.

Enterprise agentic workflows - built specifically for marketing/revenue teams running multi-step agents

Palmyra X6

LFM3-1.7B is comparatively weak here — lFM Open License v1.0 covers commercial use only below $10M annual revenue; larger firms need a paid license

Writer says its harness upgrades cut agent-workflow token costs by roughly 52% and improve speed by roughly 48% (Writer's own figures)

Palmyra X6

LFM3-1.7B is comparatively weak here — liquid says it is not recommended for agentic coding or complex multi-step reasoning because of its size

A post-trained variant built on Z.ai's open-weight GLM-5.2, tuned specifically for business agent use

Palmyra X6

Palmyra X6 lists a post-trained variant built on Z.ai's open-weight GLM-5.2, tuned specifically for business agent use among its strengths; LFM3-1.7B does not.

Largest single-prompt input

LFM3-1.7B

Its 256K tokens window is about 2× larger than Palmyra X6's 128K, fitting roughly 384 pages in one prompt.

Which should you pick?

Someone analysing very long documents or codebases

→ LFM3-1.7B

Larger 256K tokens window fits more in one prompt.

A team with data-privacy or self-hosting needs

→ LFM3-1.7B

Open weights let you run it on your own hardware; Palmyra X6 is API-only.

Anyone whose priority is very small open-weight text model - about 1.73b parameters with a 256k-token context for on-device use

→ LFM3-1.7B

It is specifically built for that.

Anyone whose priority is enterprise agentic workflows - built specifically for marketing/revenue teams running multi-step agents

→ Palmyra X6

That is its strongest area.

LFM3-1.7B: where it fits

Liquid AI's October 27, 2026 on-device text model - about 1.73B parameters and 256K context, with open weights under a license capped at $10M annual revenue. Released October 27, 2026 by Liquid AI, it is built for very small open-weight text model - about 1.73B parameters with a 256K-token context for on-device use, liquid says it can power agentic applications that used to need 9B parameters, part of a six-model LFM3 family covering text, vision, audio, omni and decision tasks, and supports 16 languages.

Its trade-offs are real: lFM Open License v1.0 covers commercial use only below $10M annual revenue; larger firms need a paid license, liquid says it is not recommended for agentic coding or complex multi-step reasoning because of its size, text-only; vision and audio need other LFM3 checkpoints, and no published per-token API price found. As an open-weight model, its running cost is your own hardware rather than a per-token fee.

Palmyra X6: where it fits

Writer's enterprise agentic flagship - a GLM-5.2-based model with harness upgrades Writer says cut agent token costs by roughly half. Released August 13, 2026 by Writer, it is built for enterprise agentic workflows - built specifically for marketing/revenue teams running multi-step agents, writer says its harness upgrades cut agent-workflow token costs by roughly 52% and improve speed by roughly 48% (Writer's own figures), and a post-trained variant built on Z.ai's open-weight GLM-5.2, tuned specifically for business agent use.

Its trade-offs: no public per-token API price - sold through Writer's enterprise platform, not a self-serve API, not independently benchmarked on general leaderboards like SWE-bench or Artificial Analysis, and built for a narrower enterprise-agent use case rather than general-purpose chat.

The bottom line for this matchup

The defining split here is open vs. closed. LFM3-1.7B gives you weights you control — self-host it, fine-tune it, keep data in-house, pay only for hardware. Palmyra X6 gives you a managed, always-updated API with no infrastructure to run. Teams with GPUs, privacy requirements, or huge volume often favour the open model; teams that want zero ops and the latest capabilities favour the closed one. Capability is close enough that this operational question, not the benchmark, usually decides it.

Want both LFM3-1.7B and Palmyra X6 without two subscriptions? LumiChats gives you these plus 40+ models under one ₹69/day pass (about $1/day) — draft with one, cross-check with the other.

See pricing

Frequently asked questions

Is LFM3-1.7B or Palmyra X6 better for coding?

Public SWE-Bench figures are not available for either model, so the honest test is your own repository — run an identical real bug through both. By design, LFM3-1.7B leans toward very small open-weight text model - about 1.73b parameters with a 256k-token context for on-device use while Palmyra X6 leans toward enterprise agentic workflows - built specifically for marketing/revenue teams running multi-step agents, and that positioning usually predicts which feels better on your codebase.

Which is cheaper, LFM3-1.7B or Palmyra X6?

LFM3-1.7B is open-weight, so self-hosting means no per-token fee (you pay for hardware instead), while Palmyra X6 is API-metered at Not published. For most teams without GPUs, the API model is cheaper to start; at very high volume, self-hosting can win.

Which has the bigger context window?

LFM3-1.7B — 256K tokens vs 128K, about 2× larger. Useful only if the model actually reasons over the full window, which not all do.

Can I use both LFM3-1.7B and Palmyra X6 together?

Yes — a multi-model platform like LumiChats gives you LFM3-1.7B, Palmyra X6 and 40+ others under one ₹69/day pass (about $1/day), so you can draft with one and cross-check with the other instead of buying two subscriptions.

Which is newer, LFM3-1.7B or Palmyra X6?

LFM3-1.7B — released October 27, 2026, about 3 months after Palmyra X6.

Related comparisons

Specifications and benchmarks reflect publicly reported figures as of June 2026 and may change as providers release updates. Always verify on your own workload.