2026 大模型 API 价格横评:20 个模型的单价怎么读

输入与输出单价、超长上下文加价、tokenizer 对中文的压缩率,三件事共同决定你的大模型账单。本文用 2026-09-15 复核的 20 个模型报价,给出可手算的换算方法。

发布于 2026-09-16最后更新 2026-09-16中文约 10 分钟模型定价成本估算API

价格与窗口数据来自站内模型库 src/data/free-tools/models.json(最后复核 2026-09-15,来源为各厂商定价页与三家聚合站),以官网实时报价为准。模型类数据基准日期:2026-09-15(数据集更新后此日期与正文数字一并复核)

先看结论

同一份业务量,选错模型可以让月账单差出接近 30 倍,而这不是因为哪家「更聪明」,而是因为大模型 API 的计费表里有三个互相牵扯的变量:输入与输出的单价比、超长上下文是否加价、以及 tokenizer 对中文的压缩率。本文用站内模型库 models.json 在 2026-09-15 复核的 20 个模型报价,把这三件事拆开讲清楚,并给出三类场景的算法。所有数字都是每百万 token 的美元价格,可以直接和官网对表。

价格表本身:20 个模型的输入与输出单价

下面这张表是站内模型库的原始数据,输入价与输出价的差距(通常是 3 到 6 倍)决定了「长输入、短输出」和「短输入、长输出」两类业务选的不是同一批模型。

模型厂商输入 $/M输出 $/M上下文开放权重
GPT-5.6 SolOpenAI5301,050,000否
GPT-5.6 TerraOpenAI2.5151,050,000否
Claude Opus 4.6Anthropic5251,000,000否
Claude Sonnet 4.6Anthropic3151,000,000否
Claude Haiku 4.5Anthropic15200,000否
Gemini 3 ProGoogle2121,000,000否
Gemini 3 FlashGoogle0.531,000,000否
Gemini 2.5 FlashGoogle0.1750.751,000,000否
Grok 4.6xAI26500,000否
Grok 4.1 FastxAI0.20.52,000,000否
Qwen 3.7 Max阿里云2.57.51,000,000否
GLM 5.2智谱1.44.41,000,000是
GLM 5.3 Flash智谱0.190.191,000,000是
DeepSeek V4 FlashDeepSeek0.140.281,000,000是
DeepSeek V4 ProDeepSeek1.743.481,000,000是
Kimi K3月之暗面3151,000,000是
MiniMax M3MiniMax0.31.21,000,000是
Llama 4 ScoutMeta0.10.310,000,000是
Qwen3 32B阿里云0.10.432,768是
Gemma 3 27BGoogle0.10.3128,000是

表里最贵的一档(GPT-5.6 Sol 的 30 美元输出)和最便宜的一档(DeepSeek V4 Flash 的 0.28 美元输出)相差约 100 倍量级;但真正决定账单的是下面这个算式,而不是任何单一数字。

把单价换算成账单:一个可以手算的例子

假设一个内部摘要任务:每次调用输入 8,000 个 token(系统提示 + 待摘要文档),输出 1,200 个 token,每天 2,000 次调用,按月 30 天计算。单次成本 = 输入 token 数 ÷ 1,000,000 × 输入单价 + 输出 token 数 ÷ 1,000,000 × 输出单价。

两者相差约 29 倍,不是表头的 100 倍,原因就是这个任务的输入占绝对多数,而 DeepSeek 的输入价与输出价之比是 1:2,比常见的 1:6 更便宜。「按你的输入输出比例选模型」这句话,只有算过一次才会变成直觉。上面这组算式在站内的 LLM API 成本计算器 里可以直接改参数复算,它用的就是同一份模型库数据。

第二个变量:超长上下文是否加价

同是百万级窗口,收费结构不同,长文档任务的实际单价可能翻倍:

这类分档细节很容易在采购时被忽略,等账单出来才发现。判断自己是否踩线,只需要知道单次请求的输入 token 数——用 Token 计数器 粘一段真实文档就能量出来,它同样按 models.json 的 tokenizer 参数估算,并标注了近似值。

第三个变量:tokenizer 对中文的压缩率

每百万 token 的报价只有在「一个 token 装多少内容」可比的时候才可比。站内模型库给出的中文平均每 token 字符数是:Claude 1.3、Gemini 1.4、OpenAI 1.5。同一篇 3,000 字的中文文档,在 Claude 上约 2,308 个 token,在 GPT-5.6 系列上约 2,000 个 token,相差约 15%。也就是说,只看输入单价会把 tokenizer 差异当成 15% 的噪声忽略掉,而在高频调用里,这 15% 就是真金白银。这些数值是 approximate 标记下的估算值,用来选路可以,写进合同不行;要精确数字必须调用官方 tokenizer。

开放权重与本地部署:别把托管价当成自成本

表里有三个模型标了可本地运行(Llama 4 Scout、Qwen3 32B、Gemma 3 27B)。它们的 0.1 美元输入价来自第三方托管服务,自托管时真正的成本是显存与吞吐。Qwen3 32B 的 32,768 窗口和 Gemma 3 27B 的 128,000 窗口决定它们不适合长上下文任务,而 Llama 4 Scout 的千万级窗口在自托管下意味着 KV 缓存先行爆炸。要不要买显卡、买哪一档,本地 LLM 硬件匹配器 按参数量与量化位宽给出显存区间,避免用一句「需要 24G 显存」糊过去。

三类场景的选法

  1. 高并发短输出(分类、抽取、路由):优先考虑输出单价与延迟,GLM 5.3 Flash 的输入输出同价(0.19/0.19)在这种场景里很占便宜,Grok 4.1 Fast 的 0.2/0.5 同理。
  2. 长文档问答(RAG、合同审阅):先看窗口是否分档加价,再算检索块大小;Gemini 3 Pro 与 Claude Sonnet 4.6 属于两条路线——前者窗口大但超过 200K 加价,后者一口价但输入单价更高。把两份报价按你的真实 token 分布代进上面的算式,答案往往和直觉相反。
  3. 需要中文理解与合规留痕:Qwen 3.7 Max 与 Kimi K3 属于国内可直接采购的一档;DeepSeek V4 Pro 的 1.74/3.48 在同级里仍是最便宜的位置,但对数据出域有要求的场景要把自托管算进来一起比。

想横向看能力差异,可以用 模型对比表生成器 生成一张带价格与窗口的对照表再决策;两家旗舰助手的长期使用差异另有 ChatGPT vs Claude 与 DeepSeek R1 vs ChatGPT 两篇逐维度对照。

数据说明与免责

本文全部价格来自站内模型库 models.json,最后复核日期为 2026-09-15,来源为公开定价页与三家聚合站。大模型 API 价格变动频繁(同一个模型可能在一个月内调价两次),采购前请以厂商官网为准。文中的月度金额是把单价按假设用量线性外推得到的示例,不含缓存折扣、批量折扣、失败重试与网络成本,也不构成任何预算承诺。

常见问题

为什么同一份表里输入价和输出价差这么多?
输出 token 需要逐步生成,占用的算力随长度线性增长,而输入可以并行处理,所以厂商普遍把输出价定在输入价的 3 到 6 倍。表里 DeepSeek V4 Flash 与 GLM 5.3 Flash 的比例只有 2 倍和 1 倍,这正是它们在短输出任务上特别便宜的原因。
缓存命中与批量调用的折扣要算进来吗?
稳定复用同一段系统提示的任务,缓存命中后的输入成本可能降到原来的一个小比例,但这取决于各家缓存的最小可缓存长度与计费口径,本文没有把这些折扣算进示例,因为站外折扣规则变化很快。批量接口通常另计一档价格,采购前需要在合同里确认。
这些月度金额可以直接写进预算吗?
不能。它们是把公开单价按假设用量线性外推的示例,用来比较两条路线的量级差;真实预算还要计入失败重试、超长输出的截断策略、汇率与账单周期。要按自己的量级测算,请在成本计算器里替换 token 数与调用次数。
模型库的数据多久复核一次?
每次复核都会更新文件里的 dataLastUpdated 字段,本文发布时该字段为 2026-09-15。价格类数据的有效期很短,如果你看到与官网不一致的地方,请以官网为准并告诉我们,我们会复核后更新数据并重算结论。

延伸阅读:这些条目可以直接开通

  • ChatGPT免费 / Plus $20/月 / Pro $200/月按团队用量选订阅档,可与 API 并行使用前往官网
  • Claude免费 / Pro $20/月 / Team $25/用户/月长上下文一口价,适合文档密集的团队前往官网

LLM API pricing in 2026: how to read 20 models' rates

Input and output rates, long-context surcharges and tokenizer compression decide your LLM bill. Worked through with 20 verified price rows.

Published 2026-09-16 · Last updated 2026-09-16 · English reading time about 7 min

Prices and context windows come from our model dataset src/data/free-tools/models.json (last verified 2026-09-15 against vendor pricing pages and three aggregators).

The short version

Picking the wrong model can inflate the same workload's bill by close to 30x, and that has little to do with which model is smarter. An LLM API invoice is set by three interacting variables: the input-to-output price ratio, whether long contexts are surcharged, and how efficiently a tokenizer compresses your language. This piece unpacks all three using the 20 model rows in our models.json dataset, verified on 2026-09-15. Every figure is US dollars per million tokens, so you can check it against the vendors' pricing pages.

The price sheet itself

ModelVendorInput $/MOutput $/MContextOpen weights
GPT-5.6 SolOpenAI5301,050,000no
GPT-5.6 TerraOpenAI2.5151,050,000no
Claude Opus 4.6Anthropic5251,000,000no
Claude Sonnet 4.6Anthropic3151,000,000no
Claude Haiku 4.5Anthropic15200,000no
Gemini 3 ProGoogle2121,000,000no
Gemini 3 FlashGoogle0.531,000,000no
Gemini 2.5 FlashGoogle0.1750.751,000,000no
Grok 4.6xAI26500,000no
Grok 4.1 FastxAI0.20.52,000,000no
Qwen 3.7 MaxAlibaba Cloud2.57.51,000,000no
GLM 5.2Z.ai1.44.41,000,000yes
GLM 5.3 FlashZ.ai0.190.191,000,000yes
DeepSeek V4 FlashDeepSeek0.140.281,000,000yes
DeepSeek V4 ProDeepSeek1.743.481,000,000yes
Kimi K3Moonshot AI3151,000,000yes
MiniMax M3MiniMax0.31.21,000,000yes
Llama 4 ScoutMeta0.10.310,000,000yes
Qwen3 32BAlibaba Cloud0.10.432,768yes
Gemma 3 27BGoogle0.10.3128,000yes

The most expensive row (GPT-5.6 Sol at 30 dollars for output) and the cheapest hosted row (DeepSeek V4 Flash at 0.28) differ by roughly two orders of magnitude. The formula below, not any single cell, is what decides your invoice.

From unit price to invoice: a hand-checkable example

Take an internal summarisation job: 8,000 input tokens per call (system prompt plus document), 1,200 output tokens, 2,000 calls per day, 30 days a month. Cost per call = input tokens / 1,000,000 x input price + output tokens / 1,000,000 x output price.

  • Claude Sonnet 4.6: 8,000 / 1,000,000 x 3 = 0.024 dollars, 1,200 / 1,000,000 x 15 = 0.018 dollars, 0.042 per call, about 2,520 dollars a month.
  • DeepSeek V4 Flash: 8,000 / 1,000,000 x 0.14 = 0.00112 dollars, 1,200 / 1,000,000 x 0.28 = 0.000336 dollars, 0.001456 per call, about 87 dollars a month.

That is a factor of roughly 29, not the 100 the table header suggests, because this workload is input-heavy and DeepSeek prices output at only 2x input instead of the more common 6x. Our LLM API cost calculator runs the same arithmetic on the same dataset if you want to substitute your own volumes.

The second variable: long-context surcharges

A million-token window does not mean a flat million-token price:

  • Claude Opus 4.6 charges one rate across its whole 1,000,000 window, with no long-context premium.
  • Gemini 3 Pro roughly doubles the input price beyond 200,000 input tokens, so a 300K-token retrieval question is billed at 4 dollars per million, not 2.
  • Grok 4.1 Fast offers 2,000,000 tokens of context with both rates under one dollar, which suits large-context, short-output jobs.
  • Llama 4 Scout's 10,000,000 window is a hosted reference price; self-hosting bills you in GPU hours instead of tokens.

Our token counter tells you whether a request crosses a surcharge threshold in the first place; it estimates with the same tokenizer parameters and labels its output as approximate.

The third variable: how much text fits in one token

Per-million-token prices are only comparable when a token carries comparable content. Our dataset records 1.3 Chinese characters per token for Claude, 1.4 for Gemini and 1.5 for the OpenAI family, so the same 3,000-character Chinese document is about 2,308 tokens on Claude and 2,000 on GPT-5.6, a 15 percent gap. Fifteen percent is noise in a benchmark and real money in a high-volume pipeline. These are flagged estimates: good enough for routing decisions, not for contracts.

Open weights and self-hosting

Three rows in the table are marked as locally runnable (Llama 4 Scout, Qwen3 32B, Gemma 3 27B). Their 0.10 dollar input price comes from third-party hosts; self-hosting trades tokens for VRAM and throughput. Qwen3 32B's 32,768 window and Gemma 3 27B's 128,000 window rule out long-context work, while Llama 4 Scout's ten-million window makes KV cache the first thing that breaks. The local LLM hardware matcher converts parameter counts and quantisation into a VRAM range instead of a vague "you need 24GB".

Three procurement patterns

  1. High-volume classification, extraction and routing: weight output price and latency. GLM 5.3 Flash prices input and output identically (0.19/0.19), and Grok 4.1 Fast (0.2/0.5) works on the same logic.
  2. Long-document QA and contract review: check the surcharge tiers before the headline price. Gemini 3 Pro and Claude Sonnet 4.6 are two different philosophies, and only your own token distribution decides which wins.
  3. Chinese-language work with compliance constraints: Qwen 3.7 Max and Kimi K3 sit in the directly purchasable tier, DeepSeek V4 Pro (1.74/3.48) is the cheapest comparable row, and anything with data-residency requirements has to be compared against self-hosted cost.

To line up capabilities beside the prices, generate a side-by-side sheet with the model comparison table builder; for sustained product comparisons we keep separate write-ups on ChatGPT vs Claude and DeepSeek R1 vs ChatGPT.

Sources and limits

Every price here comes from our model dataset, last verified on 2026-09-15 against vendor pricing pages and three aggregator articles. API prices change often, sometimes twice in a month, so treat this as a framework and confirm the numbers before you sign anything. The monthly figures are linear extrapolations from a hypothetical workload: they exclude prompt caching, batch discounts, retries and network cost, and they are not budget advice.

FAQ

Why are input and output prices so different in the same table?
Output tokens are generated one at a time, so the compute grows with length, while input is processed in parallel. Most vendors therefore price output at 3 to 6 times input. DeepSeek V4 Flash and GLM 5.3 Flash sit at 2x and 1x, which is exactly why they win on short-output jobs.
Should prompt caching and batch discounts be included?
Cached prompts can cut the input cost to a small fraction of list price, but the minimum cacheable length and billing rules vary by vendor, so the examples here deliberately exclude them. Batch endpoints are priced separately and belong in the contract review.
Can the monthly figures be used as a budget?
No. They are linear extrapolations from list prices and an assumed volume, useful for comparing orders of magnitude. A real budget needs retries, truncation policy, currency and billing-period effects; substitute your own token counts in the cost calculator instead.
How often is the dataset re-verified?
Every verification updates the dataLastUpdated field, which was 2026-09-15 when this post shipped. Price data goes stale quickly, so trust the vendor page when the two disagree and tell us, we will re-check and recompute.

Where to go from here

  • ChatGPTFree / Plus $20/mo / Pro $200/moTeam plans can sit beside API accessOpen the site
  • ClaudeFree / Pro $20/mo / Team $25/user/moFlat-rate long context for document-heavy teamsOpen the site