订阅一个 AI 工具之前,我们核对的五件事(附 376 条记录的实测比例)
免费额度按什么计、月费怎么换算、同类价格带、它明确不做什么、核对日期怎么看——把「值不值得订」拆成五个你能自己复算的问题。
文中比例来自 2026-09-18 对 376 条已发布记录的一次全量统计,口径写死在这里:字段取每条记录的 `pricing.detail.zh`;「写了免费」= 该串含「免费」或 free;「额度与金额一起写清」= 同一串里还出现 `¥/$` 加数字、或 `/月`、`per user`;「读得懂」= 长度超过 8 个字。价格串是各条目 `lastVerifiedAt` 那天对官网与定价页的核对结果,不是统计当日的行情。复算方式:对 `src/data/tools/**/*.json` 跑同样的匹配即可,或用 `npm run validate:tools` 核对条目数与时效分布。模型类数据基准日期:2026-09-15(数据集更新后此日期与正文数字一并复核)
先说结论:把"要不要订阅"拆成五个可核对的问题
AI 工具的订阅决定之所以难,不是因为选项多,而是因为每个厂商都用同一句话术:「免费开始,随需升级」。 这句话没有告诉你任何可核对的事。我们在维护这个目录的过程中(当前发布 376 条记录,每条底部都写着 最后一次核对官网的日期),把"值不值得付钱"这件事收敛成五个问题。 下面每一条都同时给出我们怎么查与你自己能怎么查,不要求你相信我们的判断。
一、"免费"必须问清楚按什么计量
站内 376 条记录里 287 条(76%)在定价说明里写了「免费」,但只有 211 条(56%)把免费额度和金额一起写清楚; 303 条(81%) 的定价说明长度超过 8 个字,也就是"读得懂"的那一档。全站这份说明平均只有 18 个字、最长 96 个字—— 所以我们把它当"线索",不当"账本":决定之前,请回厂商定价页看当日原文。 差距就出在计量方式上。常见四种,坑完全不同:
- 按次数:每天 N 次。适合"偶尔查一下"的人,一天用满就断崖。
- 按 token:模型类工具的默认口径。同一个"免费额度",写中文和写英文能用掉完全不同的量。
- 按分钟/秒:语音、视频、会议转录类。30 分钟的会和 3 分钟的会,消耗差 10 倍。
- 按席位:团队协作类。免费档常见的写法是 1 席 / 单用户,意味着想让整团队试用,就得整团队付费。
你自己怎么查:在定价页找有没有写 "per month / per year / per seat / billed on usage" 这四类词;
只写"Free"而没有计量单位的,直接当成"未提供可核对信息"。我们这边的做法是把原始价格串原样抄进条目
(例如 免费 / Plus $20/月 / Pro $200/月),不做美化、不做换算,因为一换算就掺进了我们的假设。
二、把月费换算成"每次被采纳的回答多少钱"
月费 ÷(每天真正被采纳的次数 × 30) ——分母不要用"生成次数",用"你留下来的那些"。
这是两个数量级的差别:多数人一天的生成里有相当比例只是探索。
四份站内实测的价格串(核对日期都是 2026-08-29,可在各条详情页底部看到):
| 工具 | 定价串 | 适合谁的量级 |
|---|---|---|
| ChatGPT | 免费 / Plus $20/月 / Pro $200/月 | 个人高频;Pro 档只有在把重活压到一个会话里才划算 |
| Claude | 免费 / Pro $20/月 / Team $25/用户/月 | 长上下文与整篇改写;Team 档的成本在席位 |
| Cursor | 免费 / Plus $20/月 / Pro $40/月 | 编辑器内改动多的人;按"接受的建议数"算比按 token 算准 |
| GitHub Copilot | $10/月 / $19/用户/月 | 单价低,但要看它在你语言栈里的可用度 |
同一件事的另一种算法:把 token 类工具的账单交给 /free-tools/llm-api-cost-calculator 去乘,
它只吃"你提供的数字",不替你猜业务量。
三、它在同类里是不是贵得没道理
单个价格没有意义,价格带才有。站内 36 个分类页(分类表里定义了 41 个分类)把同类工具放在一起。按主分类切片、
取说明里出现过的美元价并集,2026-09-18 的实测是:文档/写作 30 条,$5.75–$399,其中 25 条写了价、
22 条标了有免费档;编程助手 25 条,$9–$100,15 条写了价、17 条标了有免费档;视频生成 28 条,
$5–$200,25 条写了价、22 条标了有免费档。可见"有免费档"一点都不稀有,稀有的是免费额度能撑过一次完整任务——
把"有免费"读成"够用",是订阅决策里最常见的一次误读。
两个成对比较的页可以直接看:/compare/cursor-vs-github-copilot
与 /compare/chatgpt-vs-claude。
贵得有理的三种情况(这几种我们不会劝你省):需要私有部署或数据留存承诺;需要批量/夜间额度; 需要 SLA 或发票与采购流程支持。反过来说,如果一个工具只有"更漂亮的界面",$30 以上的溢价通常不值。
四、看它明确不做什么——以及我们为什么给 376 条全写了缺点
我们要求每条记录同时有优点与缺点:376/376 都填了。另外数据文件里还留着 110 条厂商自己写的 "痛点/价值主张"文案,我们刻意不显示——"行业领先的智能水平"这类句子是广告语, 挂在我们页面上等于我们替它背书。这个选择比多显示 110 条数据值钱。
你在官网可以复现同样的自查:
- 有没有公开的 changelog(没有 changelog 的产品,功能承诺的时效性最差);
- 定价页有没有 enterprise / security 档(有,说明它接受过真实采购的拷问);
- 支持页有没有你能读懂的语言与人工入口(只有机器人问答的,出问题时的等待时间是隐性成本)。
五、核对日期:什么时候该怀疑你看到的价
目录里最容易被写坏的两个字段是定价与免费额度。我们的机制很笨但可查:每条记录有
lastVerifiedAt,全部落在 2026-08-29 到 2026-09-15 之间;超过 180 天没核对,npm run validate:tools
就会在构建日志里点名(提前 30 天预警)。这不是承诺准确,是把"多久没核过"这件事公开。
给你自己的规矩:签年约前 72 小时,把定价页再看一次并截图存证。年约的价格争议几乎都发生在 "下单那天和签约那天不是一回事"上,截图是唯一低成本的保险。
这套表管不了什么(诚实边界)
- 我们抄到的定价说明很短(平均 18 字):它够你判断"值不值得点进去",不够你算账单。真要做付款决定, 以厂商定价页当日内容为准。
- 我们不测模型质量:没有自己的基准跑分,也不引用厂商跑分当结论。
- 我们不排"哪个最好":榜单页只回答"在 X 场景里,站内哪几条记录具备 Y 条件",条件写在页上,你可以不认。
- 我们不能替你拿到折扣:站内出现的推广链接会标明是推广链接,标不了的东西我们不写。
一句话版本
先量自己的用量,再读它的计量单位,然后把月费除以"被采纳的次数"。 三件事都做完还觉得贵, 那就是真的贵——跟"哪家更聪明"没关系。
常见问题
- 为什么不直接给出「该买哪家」的结论?
- 因为结论依赖你的量级与限制条件(语言、席位、数据留存、发票),而这些我们不知道。我们能给出的是可核对的部分:价格串原文、计量单位、它写明的缺点、以及我们核对它的日期。判断留在你手里。
- 年约确实便宜,值得为省下的钱承担价格变动风险吗?
- 先看两件事:折扣是否超过 15%、以及厂商是否在条款里保留「年约期内价格不变」。折扣不到 15% 且没有价格保护时,月付的灵活性通常更值钱。签之前把定价页截图存档(站内 211 条把额度与金额一起写清的记录,也都是在核对当天截图留证的)。
- 目录里的价格会不会已经过期?
- 有可能,所以我们不装作不会:每条记录都带 `lastVerifiedAt`,这一批落在 2026-08-29 到 2026-09-15 之间;超过 180 天会在构建日志里被点名(提前 30 天预警)。做任何付款决定前,请以厂商定价页当时的内容为准——这一句写在每个页面上,不是免责声明的装饰。
接着读
Five things to verify before paying for an AI subscription (with numbers from 376 directory records)
How the free tier is counted, how to convert a monthly fee, the price band in a category, what a tool admits it does not do, and why the verification date matters — five questions you can re-check yourself.
Every ratio comes from one full pass over the 376 published records on 2026-09-18, with the rules written down: we read each record's `pricing.detail.zh`; "mentions free" means that string contains 免费 or free; "tier stated with an amount" means the same string also carries ¥/$ plus a digit, or /mo, or per user; "readable" means longer than 8 characters. A price string is what the vendor showed on that record's `lastVerifiedAt` date, not a quote for today. Reproduce it by running the same match over `src/data/tools/**/*.json`, or check counts and the date spread with `npm run validate:tools`.
The short version first: turn "should I subscribe" into five checkable questions
The reason AI-tool subscriptions are hard to decide is not the number of options. It is that every vendor sells the same sentence: "start free, upgrade when you need it." That sentence contains nothing you can verify. While maintaining this directory (376 published records, each carrying the date it was last checked against the vendor's own site), we compressed the pay/no-pay decision into five questions. Every section below states both how we check it and how you can check it yourself, so you never have to trust our judgement.
1. Ask what the free tier is actually counted in
Of the 376 published records, 287 (76%) spell out a free tier in their price string, but only 211 (56%) state the tier together with a number; 303 (81%) carry a price string long enough (over 8 characters) to actually be readable. Across the whole directory that string averages 18 characters and tops out at 96 — treat it as a clue, not a ledger. The gap is entirely about the unit. Four units show up, and each fails differently:
- Per request: N runs per day. Fine for occasional lookups, cliff-like if you hit the cap.
- Per token: the default for model access. The same "free quota" burns at very different rates for Chinese and English text, so a token plan is not comparable across languages.
- Per minute/second: voice, video, meeting transcription. A 30-minute meeting costs ten times a 3-minute one; nobody tells you that on the pricing hero.
- Per seat: collaboration tools. A "free" plan with one seat means testing it with your team requires paying for the whole team.
How to check it yourself: look for "per month", "per year", "per seat" or "billed on usage" on the
pricing page. If a plan says only "Free" with no unit, treat it as "no verifiable information" rather than
"generous". Our rule in the directory is to copy the vendor's raw price string verbatim
(for example Free / Plus $20/mo / Pro $200/mo) without beautifying or converting it, because converting
it means smuggling our assumptions into your decision.
2. Convert the monthly fee into "cost per answer you kept"
monthly fee ÷ (kept answers per day × 30) — the denominator must be the ones you actually kept, not
the number of generations. The difference is about an order of magnitude, since a large share of
generations are exploration you discard.
Four raw price strings currently in the directory (all verified on 2026-08-29; the date is printed at the bottom of each record):
| Tool | Price string as published | What volume makes it pay off |
|---|---|---|
| ChatGPT | Free / Plus $20/mo / Pro $200/mo | Individual heavy use; Pro only makes sense when long, dense work sits in one thread |
| Claude | Free / Pro $20/mo / Team $25/user/mo | Long context and whole-document rewrites; the Team tier is a seat cost, not a model cost |
| Cursor | Free / Plus $20/mo / Pro $40/mo | Editors with many accepted diffs; counting accepted suggestions beats counting tokens |
| GitHub Copilot | $10/mo / $19/user/mo | Cheap per seat, but check availability in your stack before assuming value |
For token-metered tools, run the bill through
/free-tools/llm-api-cost-calculator. It only multiplies the numbers
you type; it never invents a business volume for you.
3. Check whether it is overpriced inside its own category
A price alone means nothing; a price band does. The 36 category pages (the taxonomy defines 41
categories) line up comparable tools. Sliced by primary category on 2026-09-18, over the union of dollar figures that
appear in the price strings: writing and docs — 30 records, $5.75–$399, 25 of them quoting a price and 22 flagging a
free tier; coding assistants — 25 records, $9–$100, 15 quoting and 17 with a free tier; video generation — 28 records,
$5–$200, 25 quoting and 22 with a free tier. Having a free tier is not rare. What is rare is a free tier that survives
one complete task, and reading "there is a free plan" as "it covers you" is the most common misstep in this decision.
Two side-by-side pages make the same point in one screen:
/compare/cursor-vs-github-copilot and
/compare/chatgpt-vs-claude.
Three cases where paying above the band is defensible: you need private deployment or a data-retention commitment; you need batch or off-peak quotas; you need an SLA, invoices and procurement paperwork. Outside those, a $30+ premium that buys only a nicer interface is usually not worth it.
4. Read what it explicitly does not do
We require every record to carry both strengths and limitations: 376 of 376 have both. Separately, the data files hold 110 vendor-written "value proposition" strings that we deliberately do not render — sentences like "industry-leading intelligence" are marketing copy, and putting them on our page would mean endorsing them. That choice is worth more than 110 extra fields.
You can reproduce the check on any vendor site in three minutes:
- Is there a public changelog? Products without one have the least durable feature claims.
- Does pricing list an enterprise / security tier? If yes, the pricing page has survived real procurement.
- Is there a human support entry point in a language you can read? Bot-only support means your incident latency is invisible on the pricing page.
5. Watch the verification date, not the promise
Price and free-tier text are the two fields that rot fastest. Our mechanism is dumb but auditable: every
record has a lastVerifiedAt, and the current set falls between 2026-08-29 and 2026-09-15. Anything
older than 180 days is named in the build log by npm run validate:tools (with a 30-day advance warning).
That is not a claim of accuracy — it is a disclosure of how long it has been since a human checked.
Your own rule: re-open the pricing page within 72 hours of signing an annual contract and keep a screenshot. Annual-plan disputes almost always come from "the day I decided" and "the day I signed" being different days, and a screenshot is the cheapest insurance available.
What this checklist cannot do (stated plainly)
- What we copy is short by design: the price string averages 18 characters and tops out at 96. That is enough to decide whether to click through, not enough to compute an invoice — read the vendor page on the day you pay.
- We do not benchmark model quality. We publish no score of our own and we do not quote vendor scores as conclusions.
- We do not rank "the best". Ranking pages only answer "among the records here, which ones satisfy condition Y for scenario X" — the conditions are printed on the page so you can reject them.
- We cannot obtain discounts for you. Where a link is an affiliate link, the page says so; where we cannot say that honestly, we do not include the link.
One-sentence summary
Measure your own volume, read their unit, then divide the monthly fee by the answers you kept. If it still feels expensive after those three steps, it is expensive — and that has nothing to do with which model is smarter.
FAQ
- Why not just say which tool to buy?
- Because the answer depends on your volume and constraints — language, seats, data retention, invoicing — which we do not know. What we can provide is the verifiable part: the vendor's own price string, the unit it bills in, the limitations it states, and the date we checked it. The judgement stays yours.
- Is an annual plan worth the risk that pricing changes?
- Check two things: whether the discount exceeds 15%, and whether the terms lock the price for the annual term. Below 15% with no price protection, monthly flexibility is usually worth more. Before signing, archive a screenshot of the pricing page — the 209 records here that state quota and amount together were captured the same way on their verification date.
- Could the prices in this directory already be stale?
- Yes, which is why we do not pretend otherwise: every record carries `lastVerifiedAt`, this batch spans 2026-08-29 to 2026-09-15, and anything past 180 days is named in the build log with a 30-day advance warning. Before paying, defer to the vendor's live pricing page — a sentence printed on every page here, not decorative legalese.