LFM3-1.7B vs GLM 5.2: pricing comparison
GLM 5.2 is the cheaper option at $0.01/$6.80 per 1M input/output tokens — LFM3-1.7B ($0.08/$0.20) costs about 11x more per input token. Full spec-by-spec breakdown below.
| LFM3-1.7B | GLM 5.2 | |
|---|---|---|
| Input /1M tokens | $0.08 | $0.01 |
| Output /1M tokens | $0.20 | $6.80 |
| Cache read /1M | $0.02 | $0.01 |
| Context window | 262K | 1.0M |
| Provider | Liquid | Z-ai |
| Vision input | No | No |
| Released | Nov 2026 | Jun 2026 |
Real workload costs: LFM3-1.7B vs GLM 5.2
Cost per single request at common token profiles — the cheapest model for each workload is highlighted.
| Workload | Tokens (in / out) | LFM3-1.7B | GLM 5.2 |
|---|---|---|---|
| Chatbot message | 500 / 300 | $0.0001 | $0.0020 |
| RAG query with context | 4,000 / 500 | $0.0004 | $0.0034 |
| Document summarization | 20,000 / 1,000 | $0.0018 | $0.0069 |
| Agent coding session | 100,000 / 5,000 | $0.0090 | $0.03 |
Frequently asked questions
Which is cheaper: LFM3-1.7B vs GLM 5.2?
GLM 5.2 is the cheapest on input tokens at $0.01 per 1M, and LFM3-1.7B is cheapest on output at $0.20 per 1M. LFM3-1.7B costs about 11x more per input token than GLM 5.2.
How much does LFM3-1.7B cost per 1M tokens?
LFM3-1.7B costs $0.08 per 1M input tokens and $0.20 per 1M output tokens on the Liquid API, with a 262K-token context window.
How much does GLM 5.2 cost per 1M tokens?
GLM 5.2 costs $0.01 per 1M input tokens and $6.80 per 1M output tokens on the Z-ai API, with a 1.0M-token context window.
What does a typical request cost on LFM3-1.7B vs GLM 5.2?
For a typical request with 2,000 input and 500 output tokens: LFM3-1.7B costs $0.0003, GLM 5.2 costs $0.0034. At 1,000 requests/day for a month that is $7.80 for LFM3-1.7B vs $102 for GLM 5.2.
Estimate your own workload with the per-model calculators (LFM3-1.7B, GLM 5.2), browse all current prices on the live model pricing dashboard, or run these models head-to-head on a real prompt (free account required). Prices may differ from provider list prices for batch or tiered usage.
Pricing data via the OpenRouter models API.